Re: [Mailman-Users] Recent trouble with DMARC Munging

2017-01-18 Thread Brian Carpenter
> The issues that have ired us are hosting services that appear to push > customer service off on cPanel or (worse ;-) us, and perceived lack of > cooperation from cPanel (I'm happy to say that era is long since past) > when hosting services and end users were coming to us for cPanel issues. > > I

Re: [Mailman-Users] Recent trouble with DMARC Munging

2017-01-18 Thread Barry Warsaw
On Jan 19, 2017, at 09:17 AM, Stephen J. Turnbull wrote: >As far as I can tell nobody in the Mailman crew has ever had a problem >with hosting services that support their customers using cPanel. It's >a great idea for that! cPanel also donated a VM for us to use in our CI process on GitLab, and

Re: [Mailman-Users] Recent trouble with DMARC Munging

2017-01-18 Thread Stephen J. Turnbull
Scott Neader writes: > Thanks for your support and understanding, Mark, and especially for > not making us feel bad or looking down upon us for utilizing such a > control panel system to support our customers and their myriad > needs. As far as I can tell nobody in the Mailman crew has ever h

Re: [Mailman-Users] Recent trouble with DMARC Munging

2017-01-17 Thread Scott Neader
On Tue, Jan 17, 2017 at 1:49 PM, Lindsay Haisley wrote: > Scott, I apologize to you, and to anyone else, if you feel that I was > looking down on you. It was not my intent. I have my opinions about > Linux and system administration, and they're not shared by everyone. > ... > Again, I'm sorry for

Re: [Mailman-Users] Recent trouble with DMARC Munging

2017-01-17 Thread Lindsay Haisley
On Tue, 2017-01-17 at 13:27 -0600, Scott Neader wrote: > Thanks for your support and understanding, Mark, and especially for not > making us feel bad or looking down upon us for utilizing such a control > panel system to support our customers and their myriad needs. Scott, I apologize to you, and

Re: [Mailman-Users] Recent trouble with DMARC Munging

2017-01-17 Thread Scott Neader
On 01/17/2017 08:57 AM, Lindsay Haisley wrote: > > This all underscores the problems of relying on other people's > > organization, and the resulting dependency on other people's confusion > > that comes from blind reliance on über-packages (especially proprietary > > über-packages) such as cPanel

Re: [Mailman-Users] Recent trouble with DMARC Munging

2017-01-17 Thread Mark Sapiro
On 01/17/2017 08:57 AM, Lindsay Haisley wrote: > > So inquiring minds want to know. Why is this a cPanel bug? Because cPanel provides Mailman and Python as part of their distribution. When they first upgraded to a Mailman that included DMARC mitigations based on DNS policy lookups, they included

Re: [Mailman-Users] Recent trouble with DMARC Munging

2017-01-17 Thread Lindsay Haisley
On Tue, 2017-01-17 at 07:40 -0500, Brian Carpenter wrote: > > > > Lindsay Haisley writes: > > > >  > I don't believe that the python DNS resolver module is a stock part of > >  > the python distribution. > > > > It is not, as of 3.6. Nor was it part of 2.6 or 2.7. Scott's original issue appare

Re: [Mailman-Users] Recent trouble with DMARC Munging

2017-01-17 Thread Brian Carpenter
> Lindsay Haisley writes: > > > I don't believe that the python DNS resolver module is a stock part of > > the python distribution. > > It is not, as of 3.6. > > -- cPanel has confirmed the bug and they are currently working on providing a f

Re: [Mailman-Users] Recent trouble with DMARC Munging

2017-01-17 Thread Stephen J. Turnbull
Lindsay Haisley writes: > I don't believe that the python DNS resolver module is a stock part of > the python distribution. It is not, as of 3.6. -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/

Re: [Mailman-Users] Recent trouble with DMARC Munging

2017-01-16 Thread Brian Carpenter
> Thanks, Mark. I'm opening a ticket with cPanel and will share the results > with the group. I appreciate you narrowing down the problem! > > - Scott > -- I opened a ticket a few hours ago. I also posted about this on the cPanel forums as I a

Re: [Mailman-Users] Recent trouble with DMARC Munging

2017-01-16 Thread Scott Neader
On Mon, Jan 16, 2017 at 9:37 PM, Mark Sapiro wrote: > On 01/16/2017 07:29 PM, Scott Neader wrote: > > On Mon, Jan 16, 2017 at 12:23 PM, Mark Sapiro wrote: > > > >> Also, in this case try > >> > >> python -c "import dns.resolver" > >> > >> to see if it reports any error. > >> > > > > Yes... not g

Re: [Mailman-Users] Recent trouble with DMARC Munging

2017-01-16 Thread Mark Sapiro
On 01/16/2017 07:29 PM, Scott Neader wrote: > On Mon, Jan 16, 2017 at 12:23 PM, Mark Sapiro wrote: > >> Also, in this case try >> >> python -c "import dns.resolver" >> >> to see if it reports any error. >> > > Yes... not good results: > > # python -c "import dns.resolver" > Traceback (most rece

Re: [Mailman-Users] Recent trouble with DMARC Munging

2017-01-16 Thread Scott Neader
On Mon, Jan 16, 2017 at 12:23 PM, Mark Sapiro wrote: > On 01/15/2017 08:58 PM, Scott Neader wrote: > > When yahoo.com or AOL.com users post to our > > lists, the Munging is not working. When I query for a DMARC record from > > the mail server, it can see the record, so I think it's not a resolve

Re: [Mailman-Users] Recent trouble with DMARC Munging

2017-01-16 Thread Lindsay Haisley
On Mon, 2017-01-16 at 19:24 -0500, Brian Carpenter wrote: > Meanwhile I get the following when I run " python -c "import > dns.resolver": > > Traceback (most recent call last): >   File "", line 1, in > ImportError: No module named dns.resolver > > Do I need to run that command in a certain dire

Re: [Mailman-Users] Recent trouble with DMARC Munging

2017-01-16 Thread Mark Sapiro
On 01/16/2017 04:24 PM, Brian Carpenter wrote: > > Meanwhile I get the following when I run " python -c "import > dns.resolver": > > Traceback (most recent call last): > File "", line 1, in > ImportError: No module named dns.resolver > > Do I need to run that command in a certain directory?

Re: [Mailman-Users] Recent trouble with DMARC Munging

2017-01-16 Thread Brian Carpenter
> On 01/16/2017 12:05 PM, Brian Carpenter wrote: > > > > I would also be interested if anyone has any answers or suggestions to this > > as we have seen the same issue on our mailman servers. > > > See > January/081821.html>. > Follow the s

Re: [Mailman-Users] Recent trouble with DMARC Munging

2017-01-16 Thread Mark Sapiro
On 01/16/2017 12:05 PM, Brian Carpenter wrote: > > I would also be interested if anyone has any answers or suggestions to this > as we have seen the same issue on our mailman servers. See . Follow the suggestions there and

Re: [Mailman-Users] Recent trouble with DMARC Munging

2017-01-16 Thread Brian Carpenter
> I'm using Mailman version 2.1.23. Since late 2014, I've been successfully > using the "Munge From" option under Privacy Options > Sender filters > > "Action to take when anyone posts to the list from a domain with a DMARC > Reject/Quarantine Policy." Mail from users using AOL, Yahoo and others

Re: [Mailman-Users] Recent trouble with DMARC Munging

2017-01-16 Thread Lindsay Haisley
On Mon, 2017-01-16 at 10:23 -0800, Mark Sapiro wrote: > Note that if you are seeing the > > DNS lookup for dmarc_moderation_action for list not > available > > messages, restarting Mailman may fix it. Also, in this case try > > python -c "import dns.resolver" > > to see if it reports any error

Re: [Mailman-Users] Recent trouble with DMARC Munging

2017-01-16 Thread Mark Sapiro
On 01/15/2017 08:58 PM, Scott Neader wrote: > > When yahoo.com or AOL.com users post to our > lists, the Munging is not working. When I query for a DMARC record from > the mail server, it can see the record, so I think it's not a resolver > issue. > > I'm really stumped... any pointers/ideas on

[Mailman-Users] Recent trouble with DMARC Munging

2017-01-16 Thread Scott Neader
I'm using Mailman version 2.1.23. Since late 2014, I've been successfully using the "Munge From" option under Privacy Options > Sender filters > "Action to take when anyone posts to the list from a domain with a DMARC Reject/Quarantine Policy." Mail from users using AOL, Yahoo and others with a D