On 02/26/2009 09:41:40 AM, Brad Knowles wrote:
Mark Sapiro wrote:
SMTPHOST and SMTPPORT in mm_cfg.py.
That controls where you send to, but not what address Mailman binds
to when it sends to that host/port.
As it turns out I set SMTPHOST to 127.0.0.2, and instead of
the usual smtp line in /etc/postfix/master.cf I've these 3 lines:
mypublicip:smtp inet n - - - - smtpd
127.0.0.1:smtp inet n - - - - smtpd
127.0.0.2:smtp inet n - - - - smtpd
-o
local_header_rewrite_clients=permit_tls_clientcerts -o
relay_clientcerts=
The latter prevents address rewriting by requiring tls
authentication for rewriting and then preventing any
such authentication.
This is clunky. Postfix is much happier when such
"bad" address rewriting is triggered by the client's
IP.
Karl <k...@meme.com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
------------------------------------------------------
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
