[Mailman-Users] Searchable archive for mailman mailing-lists?

2017-01-16 Thread Fernando Gont
Folks, I was meaning to provide some option for searching our mailman mailing lists. Two questions: 1) Any open source recommendations for this? 2) In the past, we were providing this feature by mirroring the mailing-lists with google-groups, and thus using the googlegroups interface for

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

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

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

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

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

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

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