[Mailman-Users] 2.1.18 internal documentation suggestions

[Mark Sapiro]

On 04/30/2014 11:58 PM, Stephen J. Turnbull wrote:

> Why not just deprecate
> list_is_from in favor of dmarc_moderation_action?
> 


I don't think I can for two reasons. One is technical.
dmarc_moderation_action is unreliable. If the DNS lookup times out, the
message is assumed unaffected by DMARC. This could be reversed, and in
any case, I plan to make the timeouts an mm_cfg.py setting, but I think
this is an issue. It also requires installation of the 3rd party
dnspython package, and if that's not there, all messages pass. I did
build a test into configure so it will error out if dnspython isn't
installed. None of these is a show stopper for this feature, but some
may just want to apply whatever action to all messages.

The other is social. My largest and highest traffic production list is
the discussion list for my bicycle club.

If I could, I would set dmarc_moderation_action to Reject with a gentle
suggestion to find another ESP to post from, but I can't. One particular
member of the board of directors is a very vocal and not very technical
Yahoo user who I think would have a fit if her mail were "singled out"
for differing treatment, even if only that hers was munged and mine
wasn't. I have tried in the past to programmatically hold or reject "me
too" posts and others that have way more quoted that original material.
(Almost everyone top posts and quotes the entire message being replied
to.) I was forced by a few vociferous complainers who got the boards
attention to back off.

Anyway, my point is list owners don't always have the freedom to do
whatever they want. If their list serves an organization, the policies
of that organization can override good sense.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan