Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

incomming email server at home

11 views
Skip to first unread message

spar...@centurytel.net

unread,
Oct 31, 2004, 10:56:06 AM10/31/04
to
I want to run some sort of incomming email server on my home PC. No
for the purpose of recieving person to person email but for remote
control purposes. I would like to be able to send an email to my home
system that contains commands that would be forwarded on to some other
program.

I could do this with standard email programs and rule sets. Just link
up to a "real" pop server and filter the incomming messages but I want
something that runs in the background and is reliable. If someone
closes the email program (or it crashes) then nothing works.

The idea is to be able to communicate with my home system when I am
away from a computer. I have a two way pager that can send email for
example.

Alan Connor

unread,
Oct 31, 2004, 4:34:46 PM10/31/04
to
On 31 Oct 2004 07:56:06 -0800, spar...@centurytel.net
<spar...@centurytel.net> wrote:

Without knowing what OS you are using, specific answers are
problematic, but all you really need to do is to copy a
file from one location to another, and on Unix/Linux, at least,
there are numerous ways to do this, it being the essence of
networking.

What is done with the file on the remote box is up to you.

There is a package (Debian Linux) that contains a remote
execution server/feature, rexecd:

Package: rsh-server
Priority: extra
Section: net
Installed-Size: 168
Maintainer: Herbert Xu <her...@debian.org>
Architecture: i386
Source: netkit-rsh
Version: 0.17-6
Replaces: netstd
Depends: netbase, libc6 (>= 2.2.4-4), libpam0g (>= 0.72-1)
Filename: pool/main/n/netkit-rsh/rsh-server_0.17-6_i386.deb
Size: 35642
MD5sum: f77a802dfac67b5af3accf79f302421c
Description: rsh servers.
This package contains rexecd, rlogind and rshd.

(I'm sure there is an ssh version of the above.)

Or you could just use a little tcp tool like netcat:

remote box$ netcat -l -p 1234

local box$ cat file | netcat -w 3 1111.2222.3333.4444 1234

Where 1234 is the port and 1111.2222.3333.4444 is the IP of
the remote box, which will just sit there waiting on port
1234 until you send it the file.

If you are using Windows, you have my sympathy.


AC


--
Pro-Active Spam Fighter
Pass-list --> Block-list --> Challenge-Response
http://tinyurl.com/2t5kp

Sam

unread,
Oct 31, 2004, 7:44:21 PM10/31/04
to
Beavis writes:

> On 31 Oct 2004 07:56:06 -0800, spar...@centurytel.net
> <spar...@centurytel.net> wrote:
>
>> I want to run some sort of incomming email server on my home
>> PC. No for the purpose of recieving person to person email but
>> for remote control purposes. I would like to be able to send
>> an email to my home system that contains commands that would be
>> forwarded on to some other program.
>>
>> I could do this with standard email programs and rule sets.
>> Just link up to a "real" pop server and filter the incomming
>> messages but I want something that runs in the background
>> and is reliable. If someone closes the email program (or it
>> crashes) then nothing works.
>>
>> The idea is to be able to communicate with my home system when
>> I am away from a computer. I have a two way pager that can
>> send email for example.
>>
>
> Without knowing what OS you are using, specific answers are
> problematic,

Beavis, you illiterate, babbling babboon: I see that the last spanking you
got was enough to keep your out of this newsgroup for five days.

And, of course, by the time you've gathered enough courage to stick your
hairy nose back in, you still couldn't get it right. Your grand entrance,
once again, proves the old rule that whatever answer you give to a technical
question, the correct answer always lies 180 degrees to the opposite.

Let's see how big of a fuck-up you did this time:

> There is a package (Debian Linux) that contains a remote
> execution server/feature, rexecd:
>
> Package: rsh-server

*Sigh* If that poor soul was stupid enough to take your advice, he probably
will have his box hacked before the week is out.

Beavis, you sorry waste of perfectly good oxygen. Nobody who has any clue
about system security will ever, EVER, use rsh over the Internet. Even a
complete and a total cretin is still smart enough to figure out that in this
day and age use ssh (and scp) instead of rsh. Of course, that is, sadly,
something that you two firing neurons cannot comprehend.

Ever heard of Kevin Mitnick, you dumbass? You know why he spent a couple of
years in jail, you dipshit? Well, there were a bunch of reasons, of course,
but one of them, that eventually resulted in him getting hauled off to the
'pen, was Mitnick hacking into Tsutomu Shimomura's servers by exploiting the
vulnerability of rsh/rlogin services.

Of course, the reason why you shouldn't use rsh in today's Internet isn't
exactly the same reason for yesterday's Internet, but it's painfully obvious
that explaining the nuances to you would be a lost cause. In one ear, out
the other.

So, get the blazes out of this newsgroup again, and don't come back
until you figure out how much you fucked up again. But before you go, feel
free to remind the world that you never really read my posts. I'm sure
everyone's forgotten about that, by now, and you should remind everyone
again.


Andrew Butchart

unread,
Nov 4, 2004, 7:53:30 AM11/4/04
to
Using a web server would give you more functionality since web servers by
default contain scripting capabilities. The other (easy) option would be to
run a mail client that supports message rules that allow for scripted custom
actions. Outlook is one that comes to mind.

--
Andrew Butchart
and...@floatingbear.ca


<spar...@centurytel.net> wrote in message
news:1099238166.0...@f14g2000cwb.googlegroups.com...

Frank Slootweg

unread,
Nov 4, 2004, 8:28:11 AM11/4/04
to
Andrew Butchart <and...@floatingbear.ca> wrote:
> Using a web server would give you more functionality since web servers by
> default contain scripting capabilities. The other (easy) option would be to
> run a mail client that supports message rules that allow for scripted custom
> actions. Outlook is one that comes to mind.

That (Outlook rules) only works when Outlook runs and receives the
mail. I.e. in order to do what the OP wants, he would have to run
Outlook in some kind of daemon/'server' mode, where Outlook continuously
checks for new mail. While I think that is possible, I don't think it is
very convenient/reliable.

Kari Hurtta

unread,
Nov 4, 2004, 1:12:53 PM11/4/04
to
Frank Slootweg <th...@ddress.is.invalid> writes:

To me it is told, that it is possible to define rules on Outlook,
which are executed on server (ie. Exchange) when mail is arriving.

(If Outlook is using IMAP account, then this is not possible.)

Personally I have not used Outlook. I can not confirm.

/ Kari Hurtta

Frank Slootweg

unread,
Nov 5, 2004, 6:04:36 AM11/5/04
to

Yes, that is possible, but it is highly unlikely that the OP is
running a MS-Exchange server on his "home PC/system". If he did, then
why would he ask about an "incomming email server at home", when he
already has one? If the MS-Exchange server is not on his home PC, but on
a remote system (as it normally is), then being able to run stuff on
*that* (remote) system would not help him.

It would be nice if the OP would mention his platform/OS, so we can
propose other, 'better', solutions.

In the meantime, it is kind of funny that while normally AC's solution
to every problem is procmail, this time he didn't mention procmail, but
probably 'should' have.

BDS

unread,
Nov 7, 2004, 8:37:55 PM11/7/04
to
So the OS would either be win2k or winXPpro.
Although, surely if I were running some flavor of LINUX I would have
been able to figure it out without asking but...
I sure wish I had a LINUX box at home but I have kids and I just
bought a fixer-upper house so I barely have time to balance my
checkbook let alone configure a new LINUX install. But I digress.
So to rephrase my question in more general terms:
I want some program/service that will accept an incomming email and
pass the text content on. Emails will be short with no attachments.
(Ability to process/filter the data in the same program would be nice
but not required)
I want something that is very stable, runs in the "background" (at
least as much as this is possible in Windows)
Frank Slootweg <th...@ddress.is.invalid> wrote in message news:<418b5e44$0$76520$b83b...@news.wanadoo.nl>...

Frank Slootweg

unread,
Nov 8, 2004, 8:31:11 AM11/8/04
to
BDS <spar...@centurytel.net> wrote:
> So the OS would either be win2k or winXPpro.
> Although, surely if I were running some flavor of LINUX I would have
> been able to figure it out without asking but...
> I sure wish I had a LINUX box at home but I have kids and I just
> bought a fixer-upper house so I barely have time to balance my
> checkbook let alone configure a new LINUX install. But I digress.
> So to rephrase my question in more general terms:
> I want some program/service that will accept an incomming email and
> pass the text content on. Emails will be short with no attachments.
> (Ability to process/filter the data in the same program would be nice
> but not required)
> I want something that is very stable, runs in the "background" (at
> least as much as this is possible in Windows)

If you have Linux/UNIX expertise, then you may want to have a look at
Cygwin [1], which is a Linux-compatible environment for/on (MS-)Windows.
There are Cygwin packages for fetchmail and procmail, which I think
would satisfy your requirements. You could run fetchmail at regular
intervals from cron (or MS-Windows' Scheduled Tasks).

If you do not want to take the Cygwin route, then perhaps Hamster [2]
is a solution. Hamster is a 'small, 'personal', mail (and News) server
for MS-Windows, which (normally) sits between your mailer (and
newsreader) and your real mail (and News) server. Hamster has automation
capabilities, but I have no experience with that part of Hamster. Maybe
others can help with that.

[1] <http://cygwin.com> and the list of packages at
<http://cygwin.com/packages>.

[2] <http://www.tglsoft.de/misc/hamster_en.htm>

0 new messages