I'm sorry for the multiple emails on this, but I'm afraid that I'll forget
this thought if I don't mention it now. I'll try not to send any more
messages until I get a reply (or at least until morning!).
If this isn't the way it's supposed to work, wouldn't it be best for the
X-ASSP-Intended-For
I did a little bit of testing, this isn't exchange's fault as far as I can
tell. If I telnet to port 25 of the ASSP server from the inside and
manually do a send, the X-ASSP-Indended-For lines still appear.
telnet 127.0.0.1 25
> helo me
> mail from: m...@ourcharity.org
> rcpt to: gmailcl...@gmail
for now, I'll disable the AddIntendedForHeader option, but I will miss the
feature
On Thu, May 25, 2017 at 7:24 PM, K Post wrote:
> I just got a report for a user who bcc'ed a bunch of people on a message.
> She discovered that in the header, the X-ASSP-Intended-For line shows up in
> the re
I just got a report for a user who bcc'ed a bunch of people on a message.
She discovered that in the header, the X-ASSP-Intended-For line shows up in
the recipient's message. So if a message was sent to pers...@otherorg.com
and pers...@otherorg.com both as bcc, the headers in the message received
