> People should not be addressing mail directly to your server, unless
> it has a sufficiently stable presence on the Internet (static IP,
> DDNS, etc.). They should be sending mail to you c/o your ISP.

Well that's fine. Once I get the static IP/domain I'll add that to the
rcpthosts and all will be well. I was just checking to see if I could send
to it from a remote host while online. Sendmail used to let me do it, but
then again it'd let a person get away with murder if they wished :)

> I'll guess that they say, "localhost" is not in rcpthosts. You could
> just add it; alternately run fetchmail with "-S
> localhost.localdomain", or add "smtphost localhost.localdomain" to
> your .fetchmailrc file. Presumably, "localhost.localdomain" IS in your
> rcpthosts.

That's the basic idea of it. I added the -S option and it worked great.
Hey it wasn't until just recently I realized that fetchmail runs through
the local mail server (duh@me). 

BTW, I notice (as I download 1718 messages from my remote server) that the
hard drive seems to run awfully hard during qmail operations. It's only for
a split second (after flushing each message) but it's somewhat loud. Is
that possibly because qmail writes to the drive asap instead of caching it
in memory or something? I've got Maildir access currently set up, so I
thought maybe the more frequent hd writes had to do with being in my
/home/ directory.

You mentioned setting up a .fetchmailrc. I've never managed to figure out
the syntax. What does a basic .fetchmailrc look like? I'd like to set up a
little cron script to dial up my ISP, make sure it connects, download all
my POP mail and then hangup afterwards. Unfortunately, that'd require me
learning how to write cron scripts as well.

I apologize for all the lame newbie questions. Mailer daemons are not
something I've dabbled with before. I've always just left my system with
whatever defaults it came with and never gave it a second thought.
Switching over to qmail has been a learning experience for me...one that
I'm not regretting.

Jason

Reply via email to