Re: backscatter issue
- On 2/11/2010 3:50 AM, Dimitar Penev wrote:
> Hi Noel,Looks as if procmail can't deliver mail for the root user.
> Thank you for your help!
> I have searched our log for 9FE3785BA10 signature and found the beginning.
> Please see below. I have searched the log for other similar signatures
> with "from=<>"
> and it seems each of those problematic e-mails starts with the two
> lines as I have put
> in the beginning of my log excerpt below. (those two lines have
> different signature though)
> I still however not sure what is causing this from=<>. As far as I can
> somebody is trying to send e-mails to the root account.
> In addition as I log as root I get in the shell "You have mail." message.
> And I see that /root/Maildir/cur is pretty big in size.
> In a addition in order to stop bounces I have commented in
> #bounce unix - - n - 0 bounce
> I think our senders can live without nondelivery notifications I
> think. Do you think this will help?
> I am attaching at the end of this message some info which I think may
> be relevant.
> Thank you in advance
> lines from the log related with 9FE3785BA10 signature
> Feb 7 10:58:53 uCpbx postfix/local: 9FE3785BA10:
> to=<root@...>, orig_to=<mail@...>,
> delay=3.9, delays=1.8/0.01/0/2.1, dsn=5.2.0, status=bounced (can't
> create user output file. Command output: procmail: Couldn't creat
> e "/var/spool/mail/nobody" procmail: Couldn't chdir to "/root/Maildir"
> procmail: Couldn't read "// " procmail: Unable to treat as di
> rectory "/root/Maildir" procmail: Lock failure on "/root/Maildir.lock"
> procmail: Error while writing to "/root/Maildir" )
> Feb 7 10:58:54 uCpbx postfix/local: 9FE3785BA10:
> to=<root@...>, orig_to=<postmaster@...>,
> ocal, delay=5, delays=1.8/0.03/0/3.1, dsn=5.2.0, status=bounced (can't
> create user output file. Command output: procmail: Couldn't c
> reate "/var/spool/mail/nobody" procmail: Couldn't chdir to
> "/root/Maildir" procmail: Couldn't read "// " procmail: Unable to
> treat a
> s directory "/root/Maildir" procmail: Lock failure on
> "/root/Maildir.lock" procmail: Error while writing to "/root/Maildir"
That's what you need to fix.
I don't use procmail, but I think you might have better luck
if you alias root's mail to a different non-root user.
-- Noel Jones