[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Exim4 - local mail deliveries



On Thu, Mar 06, 2008 at 21:22:40 +0000, Felix Karpfen wrote:
> On Wed, 05 Mar 2008 21:05:48 +0100, Florian Kulzer wrote:
> > On Mon, Mar 03, 2008 at 20:22:12 +0000, Felix Karpfen wrote:
> >> Since switching to Debian Etch, I no longer get messages (from cron and
> >> logcheck) delivered to my user-mailbox. Exim 4 delivers them to the
> >> mail-queue in /var/spool/exim4/input; when the queue is emptied, they
> >> appear to end up in /dev/null.
> > 
> >The Lenny/Sid version of exim4 has a debconf dialog
> > question that lets you *choose between "mbox format in /var/mail"* and
> > "Maildir format in home directory".

Once the real problem is fixed (see below) it should be possible to
switch "Maildir/home directory" if you prefer that. (You might have to
create ~/Maildir/ yourself beforehand.)
 
> Etch offers the same choice and this may have been one of my problems. 
> 
> After switching to mbox format, I can receive
> 
> "echo "just a test..." | mail -s "test-local" $USER@localhost" 
> 
> when run from a "user" terminal.
> 
> ziltch for 
> 
> "echo "just a test..." | mail -s "test-local 2" $USER"

That means that exim4 knows how to do local deliveries, but it does not
seem to realize that carrot.cabbagepatch is "local".

(The first command above sends mail to felixk@localhost, the second one
 to felixk@carrot.cabbagepatch.)

> and ziltch if either command is run as "root".

Mails to root@localhost get redirected to felixk@carrot.cabbagepatch,
which does not work; mails to root@carrot.cabbagepatch get stuck
immediately.
 
> In case it is relevant:
> 
> $ echo $USER
> felixk
> 
> and the only entry in /etc/mailname is the name of the localhost
> (carrot.cabbage.patch).
> 
> Messages from logcheck continue to be delivered to /var/spool/exim4/input.

All the failed messages should be stuck ("frozen") in exim's queue. Run
"exim4 -bp" as root to check.

> The following logcheck header may reveal something:

[...]

> | 031T To: felixk@carrot.cabbagepatch
> | 071  Subject: Reboot: carrot.cabbage.patch 2008-03-06 11:33 Security Events
> | 053I Message-Id: <E1JX43I-00015E-M3@carrot.cabbage.patch>
> | 061F From: logcheck system account <logcheck@carrot.cabbagepatch>
> | 038  Date: Thu, 06 Mar 2008 11:33:40 +1100

See above.

> It is worth flagging that it might now be a "feature" of logcheck to
> send its notifications *only* to another computer.

Logcheck and other demons use the hostname in /etc/mailname. Exim does
not realize that this is the same machine, which means that you have to
fix your exim configuration and/or your /etc/hosts file.

I would try this:

Run "dpkg-reconfigure exim4-config" and make sure that "system mail
name" is set to "carrot.cabbagepatch" and "other destinations for which
mail is accepted" is set to "localhost;carrot.cabbagepatch". Then try
the mail commands again. If things work you can run "exim4 -qff" as root
to flush all the frozen messages out of the queue.

If it still does not work after you make the changes outlined above then
we need to see your /etc/hosts file and the output of "host
carrot.cabbagepatch".

-- 
Regards,            | http://users.icfo.es/Florian.Kulzer
          Florian   |


Reply to: