AW: AW: DSN and 4.62.9 problem

R. Ehle (MailScanner Mailinglist) mailscanner at
Tue Aug 7 07:58:52 IST 2007

I partly agree with you. We have to distinguish "Read Notifications" from "Delivery Notifications".

Delivery Notifications are sent by the MTA. If the delivery notification is sent by a MTA like sendmail, postfix or qmail, the Watermarking function works fine.

If the Delivery Notification is sent by a Microsoft Exchange Server, especially, if it is the new one (Exchange 2007), then the header of the original message is not included and so Watermarking function fails to recognize the message.


-----Ursprüngliche Nachricht-----
Von: mailscanner-bounces at [mailto:mailscanner-bounces at] Im Auftrag von René Berber
Gesendet: Dienstag, 7. August 2007 02:42
An: mailscanner at
Betreff: Re: AW: DSN and 4.62.9 problem

R. Ehle wrote:

> I experienced problems with the watermarking function too.
> As far as I found out, the errors only appear, when the DSN is sent from a
> Microsoft Exchange Server. Actually the Exchange Server sends a complete new
> message, which does not contain the header from the original message. So I
> don't think, that there will be a possibility to solve this issue.

No, I don't agree, I'm seeing the problem with only sendmail involved as server,
Outlook as client.  It's our own read receipts that are being marked as spam, as
well as our (business) clients, some of which do have Exchange.

FWIW I've never seen the need for milter-null or similar, greylisting + Botnet
takes care of that problem.
René Berber

MailScanner mailing list
mailscanner at

Before posting, read

Support MailScanner development - buy the book off the website!

Diese Nachricht wurde von mailMind(R) auf Viren und andere
gefaehrliche Inhalte untersucht und ist sauber.
--- mailMind(R) - we have your Mailsecurity in mind! ---

More information about the MailScanner mailing list