Alessandro Vesely writes:
The MIME boundary delimiter strings in the following message are ambiguous, and cannot be parsed.
The bad delimiters were boundary=wrefhhxwrefhhx inside wrefhhx, I suppose.
The software that produced them is W32/Yaha-E.
Curiously, Courier accepted the mail when it first came in. The AV filter
couldn't parse it because of the boundary, so Courier bounced it. The original
Define 'bounced'. If the AV filter rejected the message, this would be an SMTP reject, so the remote server would be the one doing the bouncing.
I see your point: it has been Exim who sent a malformend DSN.
I'll have to write to them. You confirm that Courier already
does put new boundaries on DSNs, don't you?
Sorry I bothered
Ale
------------------------------------------------------- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
