Best solution to fix the yahoo problem?
Thanks for the replies to my other post, and sorry that I didn't search the archives first, before posting.
In any event, I'm a unclear about the best solution (if there is one).
Is there a solution, that will only modify messages from domains that are like yahoo? I.e., only yahoo posts will be modified so that they will get delivered, but all the other other posts, will look like they presently do?
As a hack fix, could I simply modify my mailman code, so that @yahoo.com is changed to @yahooblah.com, in the From address?
- Mark
In any event, I'm a unclear about the best solution (if there is one).
My inclination is to refuse postings from addresses @yahoo.com, since accepting them will interfere with everyone's use of our list system.
The only issue for me is precisely how to implement it.
Joseph Brennan Columbia University I T
On 04/13/2014 01:59 PM, Joseph Brennan wrote:
In any event, I'm a unclear about the best solution (if there is one).
Mailman 2.1.16 and up already has the ability to either mung the From: header or wrap the original post in an outer message From: the list.
There is a minor bug in that this is also applied to posts to LIST-owner, but that is fixed for 2.1.18.
The major problem is it requires site configuration action to make this option available to list owners.
See the thread starting at <https://mail.python.org/pipermail/mailman-users/2014-April/076372.html> for lots of info.
See the post at <https://mail.python.org/pipermail/mailman-users/2014-April/076388.html> for links to the patches.
My inclination is to refuse postings from addresses @yahoo.com, since accepting them will interfere with everyone's use of our list system.
The only issue for me is precisely how to implement it.
Jim P's branch mentioned in his post at <https://mail.python.org/pipermail/mailman-users/2014-April/076383.html> is a general implementation for posts From: any domain with a reject DMARC policy.
We are talking about this at PyCon now. At sprints starting tomorrow, we will be working on enhancing the current options by merging at least ideas from Jim P's branch, and making the switches available to list owners by default, all with an eye to releasing this in 2.1.18 in weeks.
Also see the FAQ at <http://wiki.list.org/x/ggARAQ>.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark Sapiro writes:
Mailman 2.1.16 and up already has the ability to either mung the From: header or wrap the original post in an outer message From: the list.
The major problem is it requires site configuration action to make this option available to list owners.
Given that the whole site is at risk, should it be an option for list owners at all?
Jim P's branch mentioned in his post at <https://mail.python.org/pipermail/mailman-users/2014-April/076383.html> is a general implementation for posts From: any domain with a reject DMARC policy.
We are talking about this at PyCon now.
Good to hear, wish I could be there! I'll try to be in #mailman off and on 00:00 UTC to 15:00 UTC.
Steve
On Apr 14, 2014, at 11:03 AM, Stephen J. Turnbull wrote:
Given that the whole site is at risk, should it be an option for list owners at all?
This is a good point. It may make sense for the site admin to select whether some general DMARC mitigation approach is enabled for their lists or not, and then allow the list admins to select the approach that is least unpalatable for their users.
-Barry
On Sun, Apr 13, 2014 at 10:12 PM, Barry Warsaw <barry@list.org> wrote:
On Apr 14, 2014, at 11:03 AM, Stephen J. Turnbull wrote:
Given that the whole site is at risk, should it be an option for list owners at all?
This is a good point. It may make sense for the site admin to select whether some general DMARC mitigation approach is enabled for their lists or not, and then allow the list admins to select the approach that is least unpalatable for their users.
I agree, very valid point.
-Jim P.
participants (6)
-
Barry Warsaw -
Jim Popovitch -
Joseph Brennan -
Mark London -
Mark Sapiro -
Stephen J. Turnbull