iis smtp nntp: I just learned about the supremely useful "pickup" feature of IIS' SMTP server.

Unfortunately, when I send a message with bcc recipient(s), such recipients
are SHOWN in the full headers of the message. That is, of course, completely
opposite the intended effect!

I have tried various formats to the addressing such as
BCC: <foo1@foo.com>,<foo2@foo.com>

and lowercase "bcc" and mixed "Bcc" and also only ONE bcc recipient.

No matter the variation, ALL recipients of the message (TO, CC, and BCC) can
see the BCC recipients if they examine the full headers.

This is on IIS running on Windows 2003, SP2 with all hotfixes

Can someone verify and tell me how to post a bugfix OR (better) tell me how
I am formatting the address information incorrectly?

[quoted text, click to view]

Think of your application -- the one crafting the messages and putting
them in \Pickup -- as the submitting mail client. If you don't want
info in the standard RFC 822 headers of messages you are submitting --
don't put it in the headers! True, _some_ mail servers will strip out
Bcc: headers and turn them into envelope recipients (which is what
mail clients do), but you can't assume that'll be the case.

If you want to specify RFC 821 sender/recipients, add these special
IIS Pickup headers:

x-sender:
x-receiver:

You can have multiple x-receivers.

--Sandy


------------------------------------
Sanford Whiteman, Chief Technologist
Broadleaf Systems, a division of
Cypress Integrated Systems, Inc.

Hi Sandy:

[quoted text, click to view]

OK, this actually makes quite a bit of sense!

[quoted text, click to view]

Are you saying that if, for example, I have two x-receivers, the 2nd will
NOT see the first in the headers of the message received by the 2nd?

This would at best only be a partial solution as I would like BCC recipients
to SEE the "TO" recipients but not vice versa.

I'll keep playing with this more and hope you can clarify your comments a
little more.

[quoted text, click to view]

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 =3D RFC 821 MAIL FROM:
x-receiver =3D RFC 821 RCPT TO:

[quoted text, click to view]

To: header !=3D RCPT TO: (unless you purposely set them to the same=

value).

--Sandy




------------------------------------
Sanford Whiteman, Chief Technologist
Broadleaf Systems, a division of
Cypress Integrated Systems, Inc.

Hi Sandy:


Sorry to seem obtuse, but I am not alone in this issue: on Google (and
similar) search, I fond dozens of people with the same problem.

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.

Does a similar patch need to be made for IIS on Windows 2003? Can someone
from MS comment on this thread?

[quoted text, click to view]

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."

Is there a document from which I can learn about such pickup headers?

More to the point, is there a BCC pickup header?

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?!


[quoted text, click to view]

I get that.

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."

Thanks for your (or anyone else's) ongoing help.

[quoted text, click to view]

I think you're mixing different issues. Do not worry about a patch.
(Exchange 4.0?!?)

[quoted text, click to view]

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:.

[quoted text, click to view]

x-receiver.

[quoted text, click to view]

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.

[quoted text, click to view]

Look, but if a "coder" doesn't know what !=3D 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.