[Mailman-Developers] [PATCH] for the notorious Sender header

[Barry Warsaw]

On Jun 30, 2010, at 05:14 PM, Malte S. Stretz wrote:

>Ah, sorry, seems like I was too quick with my merge proposal.  Gnn, now I 
>have to grok how to supersede it on lp.  I'll go and fix it.

Just push an update to your existing branch.  I believe LP will rescan your
branch and update the merge proposal appropriately.

>> I don't have a problem with including the patch in 2.1, except for the
>> Defaults.py.in
>> 
>> ALLOW_SENDER_OVERRIDES = Yes
>> 
>> If it were no, the feature would be entirely transparent to those who
>> didn't want it, essentially preserving the current situation for those
>> who took no action.
>
>Hmm.  The change is still fairly transparent I think, after an upgrade 
>there will just pop up an additional option for the list admins, 
>defaulting to the old value.  In the worst case it (theoretically) allows 
>the list admin to shoot himself or his users in the foot.  But nothing the 
>superadmin should be worried about (IMHO).

If it does get applied to 2.1.x, be sure this new option (both the
Defaults.py.in setting and the list admin option it enables) is clearly
discussed in the release notes.  I wonder if cPanel folks would ever read that
and enable it for their own users?

>> The problem with that is all those cPanel and service provider list
>> owners who would then not have access to the feature even if they were
>> aware and wanted it, so I think the default needs to be Yes which is
>> somewhat disruptive, but probably not excessively so considering the
>> potential benefit.
>
>As I am one of those cPanel users, trying to push this change down my 
>sysadmins throat the long way round, I'm in favor for Yes :)

:)
-Barry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/mailman-developers/attachments/20100630/ab3bb0a4/attachment.pgp>