See, I knew PMDF was doing something overly correct. :) I'll agree that it's got a lot of nice options.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Larry Wahlers Sent: Thursday, June 23, 2005 8:04 AM To: Exchange Discussions Subject: RE: BCC woes - RESOLUTION! OK, kind and generous folks, somewhere between Andy and my PMDF list, we have resolution. Bottom line: It's Outlook's fault, but PMDF can fix it anyway. Here is the detail, from another smart email person on my PMDF list: ************************************ "RFC 822 messages are required to contain a recipient header in the message headers (To:, Cc:, or Bcc:) but if you send from Outlook with addresses just in the BCC field, Outlook puts no recipient headers in the message headers - it just puts the addresses in the envelope To: addresses. "How PMDF handles this is based on the configuration of the MISSING_RECIPIENT_POLICY option.dat option and/or missingrecipientpolicy channel keyword. "Its default is to populate the To: message header with the values from the To: envelope addresses which in many cases makes sense, but is lousy when the envelope addresses are BCC addresses. "Ideally Outlook needs fixing to stop this - only some versions of Outlook have the problem; others don't allow a blank To: field. Since there will be always broken versions of Outlook around, I'd suggest changing your MISSING_RECIPIENT_POLICY. We changed ours to 4, which gives "To: Recipients not specified:"." ************************************* Thanks to all you Exchange folks - you've been extremely patient, knowledgable, and generous with your time and expertise. Meanwhile, I made the change to PMDF mentioned above, recompiled, and did the same test with a couple Bcc: addresses and no To: or Cc: address. And here is what the To: line looks like at the recipient's end in both Gmail and Charter: Gmail: To: not specified <Recipients> Charter: To: Recipients not specified: Thanks to all, and to all a good morning! -- Larry Wahlers Concordia Technologies The Lutheran Church - Missouri Synod _________________________________________________________________ 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.
