On 31 12 2004 at 7:11 am -0500, Sam Varshavchik wrote: >You're forgetting the fact that a single message may have multiple >recipients, and adding an X-Originally-To header, which will be seen by all >recipients of the message, will lead to confusion.
That's a point. The confusion would only arise though if there were multiple recipients on the local machine. However... Multiple BCC deliveries to one host require an equal number of distinct SMTP sessions, since the BCC recipient is specified via the envelope RCPT TO: and that can only be one address, correct? Therefore, this header could be named X-Original-BCC (or somesuch) and applied in the case that the envelope recipient does not match any of the To or Cc addresses. Even better though, could this whole situation be resolved by simply providing more information in the Received header? For example, on your message to which I am replying the last Received line is this: Received: from mx-outbound.sourceforge.net (mx-outbound.sourceforge.net [66.35.250.223]) by basil.zygoat.ca with esmtp; Fri, 31 Dec 2004 07:12:09 -0500 id 00018CCA.41D54219.00007F1B If this instead read "... by basil.zygoat.ca for [EMAIL PROTECTED] with esmtp ..." that would precisely give the missing information. My understanding was that there was no canonical format for Received lines, so this would pose no problem. If I'm wrong, then another header (X-Envelope-To or whatever) would fill the bill. Am I still missing something? -ben -- Ben Kennedy, chief magician zygoat creative technical services 613-228-3392 | 1-866-466-4628 http://www.zygoat.ca ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
