[Mailman-Users] Porting Issues

[Mark Sapiro]

Bill Tenny-Brittian wrote:
>
>We're running mailman 2.1.9.cp2 on a Linux server. We set up with
>PeertoPeer.net to filter our spam, which had become unmanageable. Because
>some spammers were sending directly to our IP, we changed the MX settings to
>go directly to PeerToPeer rather than through cPanel (mx). In addition, we
>changed our firewall smtp from 25.


See
<http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq06.011.htp>.


>It worked great and spam dropped to virtually zero, but all our mailing
>lists stopped working. They weren't caught in our spam trap (we can see
>what's captured) . they simply didn't go through. We reopened the MX
>settings and all our listServ emails shuffled through.
>
> 
>
>The question is, where do we change the settings in Mailman to allow the
>messages to be diverted to peertopeer and/or allow an alternate port from
>25?


The question is, where is the 'non-delivery' occurring? If the issue is
that the incoming post is not reaching Mailman, we would need more
information to know what is happening and what to do about it. Note
that changes to your MX and incoming mail routing should not affect
Mailman as long as list mail is ultimately delivered to the same local
MTA as before.

If posts are reaching Mailman, being archived but not going out, and
there are errors in Mailman's smtp-failure log, you probably need to
put

SMTPPORT = nnn

in mm_cfg.py where nnn is the port your outgoing MTA is listening on.

See
<http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.078.htp>
for some more information.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan