Re: BCC in message to pickup folder is NOT "blind"
- From: "Sanford Whiteman" <swhitemanlistens-software@xxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 20 Feb 2008 16:01:07 -0500
Microsoft acknowledged this as a bug in other SMTP server versions such
as that provided with IIS on Windows 2000 and Exchange Srvr. 4.0. Those
products were patched to address this VERY SAME issue.
I think you're mixing different issues. Do not worry about a patch.
(Exchange 4.0?!?)
Again, you are the mail client. You do not technically submit over
SMTP, but the special x- headers are interpreted as RFC 821 envelope
variables, not RFC 822 header variables:
x-sender = RFC 821 MAIL FROM:
x-receiver = RFC 821 RCPT TO:
Before ever posting my question here I read both RFC 821 and 822
[http://www.faqs.org/rfcs/rfc821.html
http://www.faqs.org/rfcs/rfc822.html]
Neither of these documents seems to address "x-sender" or "x-receiver" --
what you term "pickup headers."
As I said, these are special non-standard headers (note the x-) that
are supported only in the IIS SMTP Pickup feature. While they appear
to be part of the RFC 822 content, they are actually just placeholders
for data normally supplied via TCP port 25. When you craft a message
to place in \Pickup, you can add special headers which _simulate_ RFC
821 envelope data, even though envelope data is usually only seen at
the SMTP protocol level. By using these headers, you can create
messages that have different envelope (true) and header (apparent)
recipients. That's exactly what tou get from BCC:.
More to the point, is there a BCC pickup header?
x-receiver.
I can get "x-sender" and "x-receiver" to work within a txt message dropped
in the pickup folder, but I still can NOT figure out the syntax for BCC.
You mention "RFC 821 envelope variables" . . . RFC does not even mention
BCC. Is THAT where my problem stems from?!
Bcc: users are users that DO appear in the SMTP envelope -- and thus
do receive copies of the message -- but DO NOT appear in the message
headers in transit.
FWIW, "!=" may be unclear to those NOT schooled in C++, C# or JScript.
To avoid unambiguity for the legions of VB.Net coders out there you may
wish to ALSO write <> or simply "not equal."
Look, but if a "coder" doesn't know what != means, I'm not giving
them a leg up. :)
NON-coders... that's a different point, and perhaps I could be less
symbolic.
--Sandy
------------------------------------
Sanford Whiteman, Chief Technologist
Broadleaf Systems, a division of
Cypress Integrated Systems, Inc.
------------------------------------
.
- References:
- Re: BCC in message to pickup folder is NOT "blind"
- From: Sanford Whiteman
- Re: BCC in message to pickup folder is NOT "blind"
- From: Sanford Whiteman
- Re: BCC in message to pickup folder is NOT "blind"
- From: fbachofner
- Re: BCC in message to pickup folder is NOT "blind"
- Prev by Date: Re: SMTPSVC Warnings 4000 & 4006
- Next by Date: IIS Smarthost not relaying to exchange
- Previous by thread: Re: BCC in message to pickup folder is NOT "blind"
- Next by thread: Messages getting stuck in queue folder
- Index(es):
Relevant Pages
|
