Thus spake Mark Sapiro:
Did you restart Mailman after installing the python-dns package?
I think this was the problem---I forgot to restart Mailman after
installing python-dns. It took a few days after asking about this
before I got any further posts which would trigger From munging, but
now I
Thus spake Mark Sapiro:
On 05/28/2014 05:41 AM, Joel Uckelman wrote:
I'm running the just-released RPM for 2.1.18 on Fedora 20. I have the
python-dns package installed, which I read was required for DMARC
checks.
The required package is dnspython. This is not the same as PyDNS
Thus spake Mark Sapiro:
On 05/28/2014 10:28 PM, Stephen J. Turnbull wrote:
Mark Sapiro writes:
If there are no 'DMARC' entries in Mailman's logs, it most likely means
the imports I show above didn't succeed in the python that Mailman is
using, in which case
Thus spake Mark Sapiro:
On 05/29/2014 03:03 AM, Joel Uckelman wrote:
Do you still think that given what I found above?
Did you restart Mailman after installing the python-dns package?
I think so, but I have no way of checking now.
Yes, I still think that. If you did restart Mailman
Thus spake Mark Sapiro:
What do you get on the local machine from
dig txt _dmarc.yahoo.com
[uckelman@one Mailman]$ dig txt _dmarc.yahoo.com
; DiG 9.9.4-P2-RedHat-9.9.4-12.P2.fc20 txt _dmarc.yahoo.com
;; global options: +cmd
;; Got answer:
;; -HEADER- opcode: QUERY, status: NOERROR, id:
Last week I upgraded to Mailman 2.1.18 in order to get the DMARC
workarounds new in that version. I set dmarc_moderation_action for my
list to Munge From and waited to see what would happen. Despite that I
seem to still be having DMARC bounces, as this morning I got 22 Bounce
action notifications
Thus spake Joel Uckelman:
Yesterday I upgraded Mailman to 2.1 and started to notice the following
problem: The List-archive headers in messages coming from my lists all look
like this:
List-archive: /archives
while before they looked like this, e.g.:
List-archive: http
Yesterday I upgraded Mailman to 2.1 and started to notice the following
problem: The List-archive headers in messages coming from my lists all look
like this:
List-archive: /archives
while before they looked like this, e.g.:
List-archive: http://lists.ellipsis.cx/archives/hosers-talk/
What's
Hello,
I've searched the archives, the FAQ and google and couldn't find the answer
to this question. So, any help is appreciated.
I'm moving our lists from Majordomo to Mailman and have set up a test list
where I've sent some test messages from several different e-mail accounts. I
I've been having a problem with archiving that has me puzzled:
One of my list's archives displays in each message's From header the user's
address followed by his name in parentheses. Another of my list's archives
displays the list address in the From field in place of the user's address,
For one of my lists, I have show member addrs so they're not recognizable
as email addrs set to no, and if I do a dump of that lists' db, I see
that obscure_addresses = 0. But when I look at the archives, all of the
From headers show up like this:
From: [EMAIL PROTECTED] (Joel Uckelman)
when
11 matches
Mail list logo
