I have a question on this as well. I just tested this (we do NOT use
Exchange, only Postfix) and found:
- with a setting of "ALL" - BCC is indeed exposed for all mails.
- with a setting of "incoming and local" - BCC is not exposed - and
neither are the other recipients.
My test:
from both internal and external clients for my domain, I sent a message
to an internal user with a BCC to another. With "ALL" - the mails
included the headers that showed both recipients.
with "incoming and local" - I saw no headers for either recipient
with "incoming and local" - a message from Gmail had a single
intended-for header in each mail - showing the individual recipient.
The BCC target did not see the public target, nor the public target see
the BCC target.
Daniel
On 6/5/2017 8:33 AM, K Post wrote:
Your last email was quite helpful and is helping me to understand
better. Thank you again for that. *And I found a mistake in my
testing/understanding by retrying some things and re-reading what
you've already said multiple times.*
Please, bear with me through just a few more questions and point and
then I think we'll be done.
It's no question that Exchange is sending this info in the envelope,
but it's allowed to do so, we can't change that, nor can we change
what other external SMTP servers do.
And it's worse than "just" Exchange, email clients that send through
ASSP's smtp port also send a single message for multiple bcc recipients.
But, and this is important, _I must not have tested incorrectly_,
because when now *when I set AddIntendedFor to incoming and local, I
get exactly what you describe, the intended for line does NOT appear
in the email client, but does show up in the eml files.*
_17151 resolves the issue with Exchange and clients sending a single
message for multiple bcc recipients._ That's exactly what I want.
Maybe I didn't apply the changes when testing or something. Whatever
the case, this is quite relieving.
Just 2 more quick questions:
1) I think there's going to be serious misunderstanding by people
reading the GUI as to the AddIntendedFor options. Option 0, disabled,
is clear, don't ever add the headers. Option 3, all is also clear,
always add the headers.
But what is being tested for "outgoing" vs "incoming and local"
I'm sure this question sounds completely stupid to you, but I don't
understand your options.
2) You previously mentioned that having the mail stream differ from
the stored eml is bad, or at least I interpreted it that way. It
seems like with the incoming/local only option for AddIntendedFor, the
stream and stored file could be different. I don't see a problem with
this, but I'm worried that you said there could be. Could you explain?
Thanks again for your patience.
Ken
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test
