48 messages in net.sourceforge.lists.courier-usersRE: [courier-users] Re: Whole message...
FromSent OnAttachments
Moshe GurvichMay 23, 2003 1:55 pm 
Stefan HornburgMay 23, 2003 2:12 pm 
Moshe GurvichMay 23, 2003 3:03 pm 
ScottMay 23, 2003 3:04 pm 
Joe LaffeyMay 23, 2003 3:09 pm 
James A BakerMay 23, 2003 9:32 pm 
James A BakerMay 23, 2003 9:39 pm 
umbe...@officeathome.itMay 23, 2003 10:42 pm 
Brian CandlerMay 24, 2003 1:01 am 
Mathias PayerMay 24, 2003 3:14 am 
James A BakerMay 24, 2003 6:13 am 
Moshe GurvichMay 24, 2003 11:53 pm 
Moshe GurvichMay 25, 2003 12:05 am 
James A BakerMay 25, 2003 1:07 am 
Gordon MessmerMay 25, 2003 1:09 am 
James A BakerMay 25, 2003 1:17 am 
Brian CandlerMay 25, 2003 1:47 am 
Brian CandlerMay 25, 2003 1:56 am 
Mathias PayerMay 25, 2003 2:11 am 
James A BakerMay 25, 2003 2:42 am 
Mathias PayerMay 25, 2003 1:19 pm 
Sam VarshavchikMay 25, 2003 1:36 pm 
Mitch (WebCob)May 25, 2003 1:53 pm 
Sam VarshavchikMay 25, 2003 2:00 pm 
Sam VarshavchikMay 25, 2003 2:02 pm 
Sam VarshavchikMay 25, 2003 2:06 pm 
Sam VarshavchikMay 25, 2003 2:19 pm 
Moshe GurvichMay 25, 2003 2:34 pm 
Moshe GurvichMay 25, 2003 2:39 pm 
Mitch (WebCob)May 25, 2003 2:51 pm 
Sam VarshavchikMay 25, 2003 3:03 pm 
Moshe GurvichMay 25, 2003 3:08 pm 
Sam VarshavchikMay 25, 2003 3:45 pm 
Sam VarshavchikMay 25, 2003 3:52 pm 
Joe LaffeyMay 25, 2003 4:27 pm 
James A BakerMay 25, 2003 6:02 pm 
Sam VarshavchikMay 25, 2003 8:03 pm 
James A BakerMay 25, 2003 8:48 pm 
Moshe GurvichMay 25, 2003 10:18 pm 
Moshe GurvichMay 25, 2003 10:32 pm 
Brian CandlerMay 26, 2003 2:48 am 
Brian CandlerMay 26, 2003 2:58 am 
Mitch (WebCob)May 26, 2003 7:06 am 
Sam VarshavchikMay 26, 2003 8:07 am 
Sam VarshavchikMay 26, 2003 6:11 pm 
James A BakerMay 27, 2003 12:06 am 
Moshe GurvichMay 28, 2003 4:57 am 
Rodrigo SeveroMay 28, 2003 6:42 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:RE: [courier-users] Re: Whole message rejected because of one faulty recepientActions...
From:Mitch (WebCob) (mit@webcob.com)
Date:May 25, 2003 2:51:40 pm
List:net.sourceforge.lists.courier-users

Whoa... 100% Agreement Sam. - it is the clients fault - they do make it look like the server

BUT, if we return the error address in the response like:

513 Syntax error <bob>

Then the user could at least find the problem address... might be an easier
change and better than opening up the server to accepting garbage mail...

Outlook seems to blindly return the error message, so in doing so it could
return the problem address.

Not saying this is a good change for all, or that it is something to put in the
main distribution, but can you suggest to the group where to start such a
change? Maybe we can throw together an optional patch for those of us saddled
with too many MS-Outlook users ;-)

Thanks.

-----Original Message----- From: cour@lists.sourceforge.net [mailto:cour@lists.sourceforge.net]On Behalf Of Sam Varshavchik Sent: Sunday, May 25, 2003 1:56 PM To: Courier Users Subject: [courier-users] Re: Whole message rejected because of one faulty recepient

Joe Laffey writes:

On Fri, 23 May 2003, Stefan Hornburg wrote:

On Fri, 23 May 2003 13:54:54 -0700 "Moshe Gurvich" <mosh@kabbalah.com> wrote:

Our users are sending messages to ~100 recipients in BCC and sometimes have syntax error in one of them. Courier rejects the whole message during SMTP session. The only notification user gets is:"The message could not be sent because one of the recipients was rejected by the server. Server Response: '513 Synax error.'"

And there's no way they can see which email exactly has the problem. Wastes lots of time.

Is it possible to elaborate little bit more in error message to show also which exactly recipient is wrong so they can find and fix it? Or maybe to let smtp session accept whole message, reject only invalid recipient and let other people receive the message?

I would tell the said users to use mailing lists. 100 recipients in BCC is ridiculous.

While this is true, it does not change the fact that a better error message, indicating the problematic address, is in order. Even if it only warns on the first bad address, at least this is better than nothing.

There's nothing wrong with this error message. The error message is returned in response to exactly one SMTP command, which names exactly one recipient. So what exactly would be the purpose of moronically repeating the recipient's address, when it is already perfectly clear, which address is being rejected?

No, the real problem here is a severely broken mail client that vomits a clump of SMTP commands, receives an error in response to one of them, and then whines about one command being rejected without bothering to indicate which address got tossed back (even though it perfectly knows which one it is), making it look like the server's fault.