Re: [Mailman-Users] DMARC From munging: Keep original sender

[Ralf Jung]

Hi,

> On 05/01/2014 08:05 AM, Mark Sapiro wrote:
>> On 05/01/2014 07:54 AM, Ralf Jung wrote:
>>>
>>> I just noticed that stripping reply-to headers was enabled on the list
>>> in question, and that this is not the default (as I originally thought
>>> it was - I wasn't the one who initially set up these lists). Stripping
>>> happens after From munging, so this explains my issue. After disabling
>>> stripping, the original sender remains in the Reply-To.
>>
>> I *think* it works as you expect in 2.1.18rc3, but I'll have to double
>> check.
> 
> 
> In 2.1.18rc3 with first_strip_reply_to = Yes and reply_goes_to_list =
> Poster, the poster's From: address is in Reply-To:, but not for the
> other settings of reply_goes_to_list. I'm changing it for the final so
> the poster's From: address will always be in Reply-To: when from_is list
> is other than No.

Cool, thanks.

Kind regards
Ralf
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] DMARC From munging: Keep original sender

[Mark Sapiro]

On 05/01/2014 08:05 AM, Mark Sapiro wrote:
> On 05/01/2014 07:54 AM, Ralf Jung wrote:
>>
>> I just noticed that stripping reply-to headers was enabled on the list
>> in question, and that this is not the default (as I originally thought
>> it was - I wasn't the one who initially set up these lists). Stripping
>> happens after From munging, so this explains my issue. After disabling
>> stripping, the original sender remains in the Reply-To.
> 
> I *think* it works as you expect in 2.1.18rc3, but I'll have to double
> check.


In 2.1.18rc3 with first_strip_reply_to = Yes and reply_goes_to_list =
Poster, the poster's From: address is in Reply-To:, but not for the
other settings of reply_goes_to_list. I'm changing it for the final so
the poster's From: address will always be in Reply-To: when from_is list
is other than No.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] DMARC From munging: Keep original sender

[Ralf Jung]

Hi,

>> I just noticed that stripping reply-to headers was enabled on the list
>> in question, and that this is not the default (as I originally thought
>> it was - I wasn't the one who initially set up these lists). Stripping
>> happens after From munging, so this explains my issue. After disabling
>> stripping, the original sender remains in the Reply-To.
> 
> 
> The from_is_list description in 2.1.16 does say Reply-To: munging takes
> priority.

Indeed, I must have missed that.

> I *think* it works as you expect in 2.1.18rc3, but I'll have to double
> check.

Distribution packages as usual lack behind...

Kind regards
Ralf
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] DMARC From munging: Keep original sender

[Mark Sapiro]

On 05/01/2014 07:54 AM, Ralf Jung wrote:
> 
> I just noticed that stripping reply-to headers was enabled on the list
> in question, and that this is not the default (as I originally thought
> it was - I wasn't the one who initially set up these lists). Stripping
> happens after From munging, so this explains my issue. After disabling
> stripping, the original sender remains in the Reply-To.


The from_is_list description in 2.1.16 does say Reply-To: munging takes
priority.


> I would however argue that this is not expected - in particular, the
> text says that the Reply-To header of the "original message" is removed,
> which I read as: First the header is removed, then all the other
> processing is done.


I *think* it works as you expect in 2.1.18rc3, but I'll have to double
check.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] DMARC From munging: Keep original sender

[Ralf Jung]

Hi,

thanks for the fast reply.

>> Strange enough, I found code in Mailman/Handlers/CookHeaders.py which
>> adds the original sender to reply-to (which I was about to suggest), but
>> that header does not end up in the mail.
>> What I would expect to happen is (with from munging):
>> * reply_goes_to_list=0: The reply-to header contains the sender
>> * reply_goes_to_list=1: The reply-to header contains the sender (due to
>>   munging) and the list (due to replies going to the list)
>>
>> Is this a known problem? Am I doing something wrong? Any help would be
>> appreciated.
> 
> This is being addressed in MM 2.1.18, to be released shortly.

So what will be the new behaviour? I read through the release notes but
could not find anything applying to this particular issue.

I just noticed that stripping reply-to headers was enabled on the list
in question, and that this is not the default (as I originally thought
it was - I wasn't the one who initially set up these lists). Stripping
happens after From munging, so this explains my issue. After disabling
stripping, the original sender remains in the Reply-To.
I would however argue that this is not expected - in particular, the
text says that the Reply-To header of the "original message" is removed,
which I read as: First the header is removed, then all the other
processing is done.

Kind regards
Ralf
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] DMARC From munging: Keep original sender

[Mark Sapiro]

On 05/01/2014 05:46 AM, Ralf Jung wrote:
> 
> Strange enough, I found code in Mailman/Handlers/CookHeaders.py which
> adds the original sender to reply-to (which I was about to suggest), but
> that header does not end up in the mail.


It should.


> Is this a known problem? Am I doing something wrong? Any help would be
> appreciated.


The current release is 2.1.18rc3. The final will be released this
weekend. It works there. It should work in 2.1.16 as long as the list is
not fully personalized.

There are bugs fixed in 2.1.18rc3, but they don't seem relevant to your
case. See ,
 and
.

I'll try later today to duplicate this with 2.1.16.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] DMARC From munging: Keep original sender

[Lindsay Haisley]

On Thu, 2014-05-01 at 14:46 +0200, Ralf Jung wrote:
> I am currently experimenting with the From munging of Mailman (2.1.16)
> to make my lists DMARC-compliant. This is generally working, there is a
> problem though: I found no way so far to tell, from the mail that's
> ultimately delivered to the users, who was the original sender. No
> matter whether I set reply_goes_to_list to 0 or 1 (and unfortunately,
> many of my users request a 1 here :-/ ), the final mail contains no
> trace of the original sender except for its pretty-printed name.
> 
> Strange enough, I found code in Mailman/Handlers/CookHeaders.py which
> adds the original sender to reply-to (which I was about to suggest), but
> that header does not end up in the mail.
> What I would expect to happen is (with from munging):
> * reply_goes_to_list=0: The reply-to header contains the sender
> * reply_goes_to_list=1: The reply-to header contains the sender (due to
>   munging) and the list (due to replies going to the list)
> 
> Is this a known problem? Am I doing something wrong? Any help would be
> appreciated.

This is being addressed in MM 2.1.18, to be released shortly.

-- 
Lindsay Haisley   | "Everything works if you let it"
FMP Computer Services |
512-259-1190  |  --- The Roadie
http://www.fmp.com|

--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] DMARC From munging: Keep original sender

[Ralf Jung]

Dear all,

I am currently experimenting with the From munging of Mailman (2.1.16)
to make my lists DMARC-compliant. This is generally working, there is a
problem though: I found no way so far to tell, from the mail that's
ultimately delivered to the users, who was the original sender. No
matter whether I set reply_goes_to_list to 0 or 1 (and unfortunately,
many of my users request a 1 here :-/ ), the final mail contains no
trace of the original sender except for its pretty-printed name.

Strange enough, I found code in Mailman/Handlers/CookHeaders.py which
adds the original sender to reply-to (which I was about to suggest), but
that header does not end up in the mail.
What I would expect to happen is (with from munging):
* reply_goes_to_list=0: The reply-to header contains the sender
* reply_goes_to_list=1: The reply-to header contains the sender (due to
  munging) and the list (due to replies going to the list)

Is this a known problem? Am I doing something wrong? Any help would be
appreciated.

Kind regards
Ralf
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org