It seems strange that qmail wouldn't deliver to localhost, but if that's
true then what effect should modifying ~alias files have?

I've tried setting the values of .qmail-root, .qmail-postmaster and
.qmail-mailer-daemon to "root" and "&chris", neither of which settings
seemed to make any difference.

The reason I'm pursuing this is that there is at least one system
utility (ntpdate called from a cron job) that periodically mails status
reports to root, and they're currently dissappearing into the ether.

Thanks,
--Chris


On Sun, Feb 25, 2001 at 02:06:49PM -0800, Mark Lane wrote:
> All root requests need to be forwarded to postmaster or elsewhere in
> ~alias.  Qmail doesn't deliver to localhost.
>
> ----- Original Message -----
> From: "Chris Campbell" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Sunday, February 25, 2001 11:11 AM
> Subject: Sending mail to local users
>
>
> > Hello,
> >
> > I'm running a fetchmail/procmail/qmail combo on my single-user
> > workstation, a Red Hat 6.2 machine, which is behind an
> > IP-masquerading firewall.  Fetchmail grabs mail from a POP3 account
> > at my ISP (@Home.com), and qmail sends mail out the same way.
> > Nothing fancy.
> >
> > I can send and receive mail fine using my MUA (mutt), but when I
> > type 'mail root' at the command line, the maillog reveals that qmail
> > is trying to send the message to remote [EMAIL PROTECTED] and so
> > I'm getting a host-unknown error from [EMAIL PROTECTED]  Looking
> > at the control files, I can see why.  I have no defaulthost or
> > defaultdomain files, so it's using the value of 'me' (which is
> > 'deckard') for both of these.
> >
> > What I would like is for the message to go to the local root account
> > in this situation.  But what values can I use for defaulthost and
> > defaultdomain that will achieve this?  I've tried using 'localhost'
> > for defaulthost, but then qmail tries sending this message to
> > [EMAIL PROTECTED]; it's tacking on me in place of
> > defaultdomain.
> >
> > Thanks for any help,
> > --Chris
> >
>

Reply via email to