Mailscanner + postfix Mail loss

[Glenn Steen]

On 19/09/2007, Ramprasad <ram at netcore.co.in> wrote:
> Julian Field wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> >
> >
> > ram wrote:
> >
> >> On Tue, 2007-09-18 at 13:45 +0100, Julian Field wrote:
> >>
> >>
> >>> -----BEGIN PGP SIGNED MESSAGE-----
> >>> Hash: SHA1
> >>>
> >>> I would certainly start by upgrading MailScanner to the latest. This
> >>> will only take a few minutes to do.
> >>>
> >>>
> >>>
> >> I have done the upgrade but still today I say atleast one mail
> >> disappearing without trace
> >>
> >> Now I have
> >> MailScanner 4.63 ( latest-stable as of today)
> >> postfix-2.3.4
> >> on Centos 4.4
> >>
> >>
> >>
> >>
> >>
> >>
> >> -------------
> >> grep 162A54747DD /var/log/maillog
> >>
> >> Sep 19 16:04:18 spam2 postfix/smtpd[22001]: 162A54747DD:
> >> client=unknown[210.212.203.3]
> >> Sep 19 16:04:24 spam2 postfix/cleanup[22875]: 162A54747DD: hold: header
> >> Received: from sender.tld (unknown [210.212.203.3])??by
> >> spam2.netcore.co.in (Postfix) with ESMTP id 162A54747DD??for
> >> <lokesh at rcpt.tld>; Wed, 19 Sep 2007 16:04:17 +0530 (IST) from
> >> unknown[210.212.203.3]; from=<meganasarkar.proj at sender.tld>
> >> to=<lokesh at rcpt.tld> proto=ESMTP helo=<sender.tld>
> >> Sep 19 16:04:24 spam2 postfix/cleanup[22875]: 162A54747DD:
> >> message-id=<000b01c7fa82$55f46140$960ba8c0 at MEGANA>
> >>
> >> -------------------------
> >>
> >>
> >>
> >> That is it--
> >>  the queueid doesnt figure  anywhere else in the entire maillog , nor is
> >> it there in the mailq
> >>
> >>
> > When the message is put in the postfix incoming queue, it is put in with
> > a new queue id. You can't re-use queue ids like you can with all the
> > other MTAs. So you won't see the queue id again.
> >
> >> Is this mail lost then ?
> >>
> >>
> > Not necessarily.
> >
> No but in all other mails if not marked high spam and deleted
>   I can see lines like ( Requeue $QID.$RANDOM to $NEWQID)
> or
>    $QID.$RANDOM action is delete
>
> Nevertheless , every mail must be trackable by the queueid. Actually now
> I am able to see some particular patterns of senders and recipients
> where this happens , If possible I will try to reproduce the system
>
>
> One more thing I have to mention is that I am also using a postfix
> Milter to do basic userlevel blacklist/whitelist and SPF checks. But
> these do not modify the mails other than adding a headder
>
>
> Thanks
> Ram
>
Well, now you really got _my_ attention... :-)
It would be perfect if you can make a reproducible test-case... Then
disable the milter and retry... What I (of course) want to know is if
my milter support thingies affect this situation in any way... They
shouldn't, but... who knows:-/

Cheers
-- 
-- Glenn
email: glenn < dot > steen < at > gmail < dot > com
work: glenn < dot > steen < at > ap1 < dot > se