Ah! I took your command literally. So the problem is that my mm_cfg.py
seems to not be working. The resulting URL has the local FQDN not what I
specified. Here is my mm_cfg.py (sanitized):
# -*- python -*-
# Copyright (C) 1998,1999,2000,2001,2002 by the Free Software
Foundation, Inc.
#
# This
Dennis Putnam wrote:
Ah! I took your command literally. So the problem is that my mm_cfg.py
seems to not be working. The resulting URL has the local FQDN not what I
specified. Here is my mm_cfg.py (sanitized):
Did you run fix_url AFTER editing mm_cfg.py?
If so, what is the exact command you
Thanks again. I did not, I had to boot anyway for other reasons and I
thought that would be sufficient. Obviously not. In any case I had to
run check_perms a couple of times but it seems to be working OK now.
On 5/12/2012 9:53 AM, Mark Sapiro wrote:
Dennis Putnam wrote:
Ah! I took your command
On Thu, May 10, 2012 at 4:28 PM, Mark Sapiro m...@msapiro.net wrote:
DKIM signing is normally done in an outgoing MTA. SPF and reverse DNS
are DNS things, not Mailman.
In general, best practices for Mailman servers are the same as best
practices for sending mail in general.
Mailman does
David wrote:
I have DKIM implemented with opendkim and Postfix and messages sent out via
sendmail are signed properly.
However, messages sent out to the list's users by Mailman are not DKIM
signed. Any suggestions?
Is Mailman sending outgoing mail via your local Postfix.
These headers from
On Sun, May 13, 2012 at 12:51 AM, Mark Sapiro m...@msapiro.net wrote:
David wrote:
I have DKIM implemented with opendkim and Postfix and messages sent out
via
sendmail are signed properly.
However, messages sent out to the list's users by Mailman are not DKIM
signed. Any suggestions?
David wrote:
For a mailing list, would I have to expand my SigningTable in any way? My
opendkim SigningTable currently only has an entry for
*@list.example.com(which is associated with list._
domainkey.example.com).
But /var/log/mail.log shows a lot of entries like this:
no signing table match
