Hello Thank you for the replies suggesting that the problem could be caused by an amavis virus scanner. That was bullseye :-)
Indeed, amavis at recipioents site generates a delayed bounce, which is then sent directly to the MX of the sender and thus bypassed my sniffing between our filter and the customer's mailserver. It is this NDR which the sender referred to, not one generated on transit. The problem is that apparently lotus notes uses the § character in the Message-ID and amavis complains about it being an unencoded 8-bit character. So I'm trying to figure out, if lotus notes is wrong, or amavis being too picky? Not so easy... If I browse the RFC regarding Message ID and SMTP, I basically get the not so clear definition, that "all printable ASCII characters" can be used in the message ID. Well § is a printable character, but it is above the first 127 bytes (8-bit). So is ASCII defined as being only the first 127 characters, or is ASCII the full 255 character set, and the upper 127 ones containing certain control characters and some localized code-table specific characters. But from my understanding § definitely is the same in all code tables and printable :-) -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________ _______________________________________________ mailop mailing list [email protected] https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
