 | Start a set with this search |
 | Include this search in one of my sets |
 | Exclude this search from one of my sets |
 | Permalink to these results Paste this link in email or IM: |
 | Atom feed for tracking future search results Paste this URL into your reader: |
48 messages in net.sourceforge.lists.courier-users[courier-users] Re: Whole message rej...| From | Sent On | Attachments |
|---|---|---|
| Moshe Gurvich | May 23, 2003 1:55 pm | |
| Stefan Hornburg | May 23, 2003 2:12 pm | |
| Moshe Gurvich | May 23, 2003 3:03 pm | |
| Scott | May 23, 2003 3:04 pm | |
| Joe Laffey | May 23, 2003 3:09 pm | |
| James A Baker | May 23, 2003 9:32 pm | |
| James A Baker | May 23, 2003 9:39 pm | |
| umbe...@officeathome.it | May 23, 2003 10:42 pm | |
| Brian Candler | May 24, 2003 1:01 am | |
| Mathias Payer | May 24, 2003 3:14 am | |
| James A Baker | May 24, 2003 6:13 am | |
| Moshe Gurvich | May 24, 2003 11:53 pm | |
| Moshe Gurvich | May 25, 2003 12:05 am | |
| James A Baker | May 25, 2003 1:07 am | |
| Gordon Messmer | May 25, 2003 1:09 am | |
| James A Baker | May 25, 2003 1:17 am | |
| Brian Candler | May 25, 2003 1:47 am | |
| Brian Candler | May 25, 2003 1:56 am | |
| Mathias Payer | May 25, 2003 2:11 am | |
| James A Baker | May 25, 2003 2:42 am | |
| Mathias Payer | May 25, 2003 1:19 pm | |
| Sam Varshavchik | May 25, 2003 1:36 pm | |
| Mitch (WebCob) | May 25, 2003 1:53 pm | |
| Sam Varshavchik | May 25, 2003 2:00 pm | |
| Sam Varshavchik | May 25, 2003 2:02 pm | |
| Sam Varshavchik | May 25, 2003 2:06 pm | |
| Sam Varshavchik | May 25, 2003 2:19 pm | |
| Moshe Gurvich | May 25, 2003 2:34 pm | |
| Moshe Gurvich | May 25, 2003 2:39 pm | |
| Mitch (WebCob) | May 25, 2003 2:51 pm | |
| Sam Varshavchik | May 25, 2003 3:03 pm | |
| Moshe Gurvich | May 25, 2003 3:08 pm | |
| Sam Varshavchik | May 25, 2003 3:45 pm | |
| Sam Varshavchik | May 25, 2003 3:52 pm | |
| Joe Laffey | May 25, 2003 4:27 pm | |
| James A Baker | May 25, 2003 6:02 pm | |
| Sam Varshavchik | May 25, 2003 8:03 pm | |
| James A Baker | May 25, 2003 8:48 pm | |
| Moshe Gurvich | May 25, 2003 10:18 pm | |
| Moshe Gurvich | May 25, 2003 10:32 pm | |
| Brian Candler | May 26, 2003 2:48 am | |
| Brian Candler | May 26, 2003 2:58 am | |
| Mitch (WebCob) | May 26, 2003 7:06 am | |
| Sam Varshavchik | May 26, 2003 8:07 am | |
| Sam Varshavchik | May 26, 2003 6:11 pm | |
| James A Baker | May 27, 2003 12:06 am | |
| Moshe Gurvich | May 28, 2003 4:57 am | |
| Rodrigo Severo | May 28, 2003 6:42 am |
| Permalink for this message Paste this link in email or IM: |
| Permalink for this thread Paste this link in email or IM: |
| Atom feed for this thread Paste this URL into your reader: |
| Subject: | [courier-users] Re: Whole message rejected because of one faulty recepient | Actions... |
|---|---|---|
| From: | Sam Varshavchik (mrs...@courier-mta.com) | |
| Date: | May 25, 2003 8:03:39 pm | |
| List: | net.sourceforge.lists.courier-users | |
James A Baker writes:
The list of response codes in RFC 2821 doesn't list 513 -- unless I'm just *completely* blind. So why are you using it instead of one of the listed codes? ... Maybe there's some supplementary spec that I should have read too?? Is there? I'll read it, if you point it out.
Remember, I am *firmly* with you on the point that the originating problem of this thread is a client (not a server) issue. Firmly!
However, I do think they've (almost accidentally!) identified a non-RFC compliant response in Courier. Can you give us a clear, supportable reason why we're wrong here?
You are wrong because neither 513, nor 514, nor 569, nor any other reply code is an invalid indication of a failed command. It's crystal clear that any reply code 5yz indicates that the command failed.
Period.
It failed.
The recipient address was rejected.
End of story.
There might be some specific, popular reply codes in common usage that indicate a very specific reason why the recipient address was rejected. However it does not change the basic fact that the recipient address was rejected.