Checking in on this, Thomas. Have I lost my mind again?
On Thu, May 25, 2017 at 10:29 PM, K Post <nntp.p...@gmail.com> wrote:
> 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 line to:
> 1) Be written to the mail file but NOT passed onto the mta stream?
> 2) Be removed from the stream sent to the MTA in the event of a resend?
>
> If things are broken, I'm sure we'll (ahem, Thomas) will work out a fix,
> but if this is the expected behavior, I think we've been giving away who
> bcc messages have been sent to all along. Consider changing the
> functionality??
>
>
>
> On Thu, May 25, 2017 at 9:30 PM, K Post <nntp.p...@gmail.com> wrote:
>
>> 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.com <-- regular to address
>>> rcpt to: gmailte...@gmail.com <-- the first bcc address
>>> rcpt to: gmailte...@gmail.com <-- the second bcc address
>>> data
>>> subject: test
>>> to: gmailclear.com
>>> from: m...@ourcharity.org
>>>
>>> test message
>>>
>>> .
>>>
>>>
>> The message will be received by gmailcl...@gmail.com with
>> X-ASSP-Intended-For: gmailcl...@gmail.com
>> X-ASSP-Intended-For: gmailte...@gmail.com
>> X-ASSP-Intended-For: gmailte...@gmail.com
>> in the message header, showing that test 1 and test 2 were bcc'ed - not
>> really blind....
>>
>> Is this expected behavior of AddIntendedForHeader? Do I have a setting
>> misconfigured somewhere?
>>
>> AddIntendedForHeader is really useful for outside mail that comes in to
>> us as a bcc only, where the recipient who we care about is bcc'ed. If we
>> don't use AddIntendedForHeader, then resends are a problem as is basic
>> diagnostics since the recipient doesn't appear in the to headers. It's
>> even useful when our users send through ASSP and bcc. But we can't take
>> the B out of bcc.
>>
>> *I'm guessing that I must have broken something on my end*, but I can't
>> figure out what. I also don't know how long this has been a problem, I'm
>> just happy that no important person has caught on yet...
>>
>>
>>
>> On Thu, May 25, 2017 at 7:25 PM, K Post <nntp.p...@gmail.com> wrote:
>>
>>> 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 <nntp.p...@gmail.com> 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 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 by personA would show
>>>>
>>>> X-ASSP-Intended-For: pers...@otherorg.com
>>>> X-ASSP-Intended-For: pers...@otherorg.com
>>>>
>>>> that's a problem. I haven't had time to dig deeper, but a quick test
>>>> to multiple gmail accounts show this to be true at least with our setup.
>>>>
>>>> FYI, mail is coming out of Outlook, into Exchange, then smarthost
>>>> forwarded to ASSP for sending on.
>>>>
>>>> I can't say that I've seen this before, nor to I know when it started
>>>> happening, but it's going on now.
>>>>
>>>> Pretty important I'd say. Am I missing something??
>>>>
>>>
>>>
>>
>
------------------------------------------------------------------------------
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
