Mailman: Difference between revisions

From Wildsong
Jump to navigationJump to search
Brian Wilson (talk | contribs)
mNo edit summary
Brian Wilson (talk | contribs)
mNo edit summary
Line 24: Line 24:


== Move a list from a different server ==
== Move a list from a different server ==
== Spam control ==
I am using postgrey (installed from Ubuntu package).
Home page http://postgrey.schweikert.ch/
See http://www.howtoforge.com/greylisting_postfix_postgrey
Postgrey simply sends a message back on first connection refusing email and saying "come back later". It then creates a database (whitelist) entry and if the server connects to try again, lets it through.
You can whitelist or blacklist anyone manually.
/etc/postgrey/whitelist_clients
/etc/postgrey/whitelist_recipients
Local (internal) mail is unaffected.
You can monitor the lists

Revision as of 19:18, 27 February 2011

Some tips on using mailman

I am using the standard Ubuntu package. This means things are symlinked from the normal places in /var to where they are really installed in /usr

User.group = list.list not the usual mailman.mailman

Various config files including mm_cfg.py are in /etc/mailman I am using postfix as the MTA

Pipermail is installed

master.cf has this /usr/lib/mailman/bin/postfix-to-mailman.py

Notes in mailman docs

Integrating Postfix with Mailman

Create a list

http://hupi.org/cgi-bin/mailman/create

Move a list from a different server

Spam control

I am using postgrey (installed from Ubuntu package).

Home page http://postgrey.schweikert.ch/

See http://www.howtoforge.com/greylisting_postfix_postgrey

Postgrey simply sends a message back on first connection refusing email and saying "come back later". It then creates a database (whitelist) entry and if the server connects to try again, lets it through.

You can whitelist or blacklist anyone manually.

/etc/postgrey/whitelist_clients
/etc/postgrey/whitelist_recipients


Local (internal) mail is unaffected.

You can monitor the lists