Postfix 2.3 and MailScanner

Holger Gebhard holger at
Sun Aug 20 20:06:22 IST 2006

I am also running Postfix in Version 2.3.2...

I forward a copy of all Spammails to a Mailbox (Spam Actions).
Maybe the failure comes from here?

It seems the failure produced by the DSN Recipient Line in the 

Only a idea...
But what will happen if MailScanner delete all the DSN Header in the 
When the Message is requeued, postfix might add new headers to the 

----- Original Message ----- 
From: "Julian Field" <mailscanner at>
To: "MailScanner discussion" <mailscanner at>
Sent: Sunday, August 20, 2006 8:23 PM
Subject: Re: Postfix 2.3 and MailScanner

Hash: SHA1

Can you make sure you are using the latest Postfix?
I am running 2.3.2 and I cannot re-create your symptoms. I have used all
the 4 messages you sent me and they all worked fine, bar a warning about
timestamps which I always get and is due to the way I am dropping things
into its queue directories.

I can't fix it until I can reproduce it, sorry.

Holger Gebhard wrote:
> Hi Julian,
> the failure happens only with some messages, not all.
> The attached archive contains some example messages.
> Thanks for help :-)
> Holger
> ----- Original Message ----- From: "Julian Field"
> <mailscanner at>
> To: "MailScanner discussion" <mailscanner at>
> Sent: Sunday, August 20, 2006 5:02 PM
> Subject: Re: Postfix 2.3 and MailScanner
> * PGP Signed by an unmatched address: 08/20/06 at 16:03:03
> * text/plain body
> * Julian Field <Jules at>
> * 0x1415B654(L)
> * PGP Signed by an unmatched address: 08/20/06 at 16:03:03
> Does this happen with all messages, or only some?
> Can you isolate a single message that causes this problem for me please?
> I would suggest using "Archive Mail =" to archive all your mail and then
> use the logs to identify a particular message that causes the problem to
> be logged, and one that doesn't cause the problem.
> It is essential that you archive as "Raw Queue Files".
> If you can then send me one message file that causes the problem, and
> one message that doesn't cause it, I can take a look and fix it.
> I haven't played with Postfix 2.3 much yet, so have little experience of
> it. This is clearly another hurdle Wietse has created for my benefit :-)
> Holger Gebhard wrote:
>> Hi Julian,
>> Hi Group,
>> i run mailscanner with postfix (split queues) for many years with no
>> problems.
>> Currently running mailscanner version 4.52.2.
>> The last week i upgraded postfix from 2.2 to 2.3.
>> After the upgrade i can see some strange warnings from postfix in my
>> mail-logs: "ignoring out-of-order DSN original recipient..."
>> I searched some group and found this threat:
>> The strange is that only some messages are affected by this failure not
>> all.
>> I tried both postfix implementations (single postfix with hold queue and
>> split queues with two postfix instances) with no success. The warning is
>> still there with some messages.
>> Fortunately the affected messages are still being delivered.
>> But where come this failure from?
>> Holger

- -- 
Julian Field
Buy the MailScanner book at

MailScanner customisation, or any advanced system administration help?
Contact me at Jules at

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
For all your IT requirements visit

Version: PGP Desktop 9.5.0 (Build 1112)
Charset: ISO-8859-1


This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
For all your IT requirements visit

MailScanner mailing list
mailscanner at

Before posting, read

Support MailScanner development - buy the book off the website!

More information about the MailScanner mailing list