Robert Pfister [EMAIL PROTECTED] wrote:
> What I'd like to do is remove the outside most "pairs" of apostrophe's.
> The logic being that the trailing apostrophe would cause the message to
> be bounced anyhow.
If Sam Varshavchik changed Courier to do this, next week someone would
come and request that Courier also gracefully handle the case that the
recipient address is framed by double quotes (") or square brackets ([]),
because the trailing double quote or square bracket would cause the
message to be bounced anyway.
This is a bottomless pit.
Why can't your users' mail clients (or whatever produces those
misformatted e-mail addresses) just conform to the standards?
> 2nd choice would be to out-right remove the address with a trailing
> apostrophe, as they won't be delivered anyhow.
That would be against the standards.
When the sending mail client says "RCPT TO: <'[EMAIL PROTECTED]'>", and Courier
replies with an error message, the client could just skip this address and
continue with the next "RCPT TO:" command. Of course, many clients are
broken and stop the sending process at the first error message, even if
the error message in question is definitely non-fatal. But why does
*Courier* have to be fixed to accomodate those clients?
> Send a non-delivery notice on that, and at least the bad eMail won't
> get perpetrated to the next reply-all.
Sending an DSN AKA bounce is totally unwarranted. An intelligent mail
client can just skip recipient addresses that are not accepted by Courier.
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
