The RFC822 message body has a To: line which generally translates into what one sees in the To: line of a message (like this one). That need not correspond (and in the case of this massage actually does not correspond) to the actual recipient(s) of the message. The RFC821 envelope contains the list of recipients and that information is discarded once the message is delivered.
In the case of the message below some optional information was included which gives hints as to what the RFC821 envelope contained, but without SMTP protocol logs it's not possible to verify... and even with the protocol logs it's only possible to verify what was eventually attempted for delivery, not what some other MTA might have received before forwarding. > Received: from smtp107.sbc.mail.re2.yahoo.com > (smtp107.sbc.mail.re2.yahoo.com [68.142.229.98]) > by sa-relay.inch.com (8.12.9p2/8.12.8) with SMTP id > jB5J4E4p096652 > for <[EMAIL PROTECTED]>; Mon, 5 Dec 2005 14:04:14 -0500 (EST) The only for listed is iferr@ and while not a required header field it at least points to the only recipient of the message actually being [EMAIL PROTECTED] So if that's the only recipient passed, that's the only recipient who would get this message regardless of what appears in the To: line... since the To: line is not used for routing or delivery purposes. No idea what happened with the sender's mail client or intervening MTAs. The only thing you can troubleshoot is what your MTA did with mail once it received it... and based on what information is available, it would appear it did the correct thing given the information it received. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of titanic panic Posted At: Tuesday, December 06, 2005 8:43 AM Posted To: swynk Conversation: e.mails don't reach all recipients Subject: Re: e.mails don't reach all recipients Mr. Scharff, Thank you for your response. I won't pretend to have thoroughly researched the RFC's mentioned (other than seeing that 821 is for SMTP and 822 is for the formatting of the body text in an e.mail). Would you please elaborate on what was meant by "the To: did not in fact match"? And yes, you were correct that iferr@ was the only recipient to have received the e.mail. Is this a problem relating to RFC compliance of the sender's thunderbird client? Thanks again, joon On 12/5/05, Chris Scharff <[EMAIL PROTECTED]> wrote: > You've posted an RFC822 message body, that is not proof that the RFC821 > envelope matched and guessing that [EMAIL PROTECTED] is the only one > who received the message would seem to indicate what is in the RFC822 > portion of the message hints that the To: line did not in fact match. > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > titanic panic > Posted At: Monday, December 05, 2005 5:03 PM > Posted To: swynk > Conversation: e.mails don't reach all recipients > Subject: e.mails don't reach all recipients > > For: > > Exch 5.5 SP4 > Win NT4 SP6a > > Recently an e.mail was sent to 3 of my internal users. The e.mail > reached one of the three users. How can this problem be > troubleshooted? > > The users run desktop antivirus that do not monitor exchange or pop > e.mail. > > Also, our ISP runs our e.mail through a spamassassin filter, but that > component can be ruled out since the e.mail did reach one of the 3 > recipients. > > headers with name edits: > > ------------------------------------------------------------------------ > ------------------------------ > Received: from sa-relay.inch.com (216.223.198.59 [216.223.198.59]) by > chesed.somename.com with SMTP (Microsoft Exchange Internet Mail > Service Version 5.5.2658.3) > id TP0VHKR3; Mon, 5 Dec 2005 14:04:24 -0500 > Received: from smtp107.sbc.mail.re2.yahoo.com > (smtp107.sbc.mail.re2.yahoo.com [68.142.229.98]) > by sa-relay.inch.com (8.12.9p2/8.12.8) with SMTP id > jB5J4E4p096652 > for <[EMAIL PROTECTED]>; Mon, 5 Dec 2005 14:04:14 -0500 (EST) > (envelope-from [EMAIL PROTECTED]) > Received: (qmail 83450 invoked from network); 5 Dec 2005 19:04:08 -0000 > Received: from unknown (HELO ?192.168.1.211?) > ([EMAIL PROTECTED]@68.77.36.188 with plain) > by smtp107.sbc.mail.re2.yahoo.com with SMTP; 5 Dec 2005 19:04:06 -0000 > Message-ID: <[EMAIL PROTECTED]> > Date: Mon, 05 Dec 2005 13:08:00 -0600 > From: Joshua Vanderberg <[EMAIL PROTECTED]> > Reply-To: [EMAIL PROTECTED] > Organization: Album Group Inc. > User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) > X-Accept-Language: en-us, en > MIME-Version: 1.0 > To: [EMAIL PROTECTED], [EMAIL PROTECTED], David Peters > <[EMAIL PROTECTED]> > Subject: Today's meeting agend (3pm NY time) > References: <[EMAIL PROTECTED]> > In-Reply-To: <[EMAIL PROTECTED]> > Content-Type: multipart/mixed; > boundary="------------020008030902060500010606" > X-Spam-Status: No, hits=-0.828 required=6 tests=BAYES_20 > X-Scanned-By: MIMEDefang 2.49 on 216.223.198.59 > > This is a multi-part message in MIME format. > --------------020008030902060500010606 > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > Content-Transfer-Encoding: 7bit > > --------------020008030902060500010606 > Content-Type: application/vnd.ms-excel; > name="status mapping.xls" > Content-Transfer-Encoding: base64 > Content-Disposition: inline; > filename="status mapping.xls" > > --------------020008030902060500010606 > Content-Type: application/vnd.ms-excel; > name="Chicago Correspondence.xls" > Content-Transfer-Encoding: base64 > Content-Disposition: inline; > filename="Chicago Correspondence.xls" > > --------------020008030902060500010606-- > ------------------------------------------------------------------------ > ------------------------------ > > > > > > Thanks for any help, > > joon > > _________________________________________________________________ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange > To subscribe: http://e-newsletters.internet.com/discussionlists.html/ > To unsubscribe send a blank email to > [EMAIL PROTECTED] > Exchange List admin: [EMAIL PROTECTED] > To unsubscribe via postal mail, please contact us at: > Jupitermedia Corp. > Attn: Discussion List Management > 475 Park Avenue South > New York, NY 10016 > > Please include the email address which you have been contacted with. > > > > > _________________________________________________________________ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange > To subscribe: http://e-newsletters.internet.com/discussionlists.html/ > To unsubscribe send a blank email to [EMAIL PROTECTED] > Exchange List admin: [EMAIL PROTECTED] > To unsubscribe via postal mail, please contact us at: > Jupitermedia Corp. > Attn: Discussion List Management > 475 Park Avenue South > New York, NY 10016 > > Please include the email address which you have been contacted with. > > _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange To subscribe: http://e-newsletters.internet.com/discussionlists.html/ To unsubscribe send a blank email to [EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange To subscribe: http://e-newsletters.internet.com/discussionlists.html/ To unsubscribe send a blank email to [EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] To unsubscribe via postal mail, please contact us at: Jupitermedia Corp. Attn: Discussion List Management 475 Park Avenue South New York, NY 10016 Please include the email address which you have been contacted with.
