Mailman_integration

PostfixAdmin doesn't have a "direct" integration of any mailinglist manager.

There is also a security restriction in postfix that forbids virtual aliases in a database pointing to a pipe/program (instead of a mail address).

However, there are some ways to integrate mailman - it's quite simple and works ;-)

The examples below assume you want to create the mailinglist listname@example.com.

redirect mailman aliases to @lists.example.com

The first method is to run mailman on a lists.example.com domain and to add aliases that redirect to listname*@lists.example.com on the domain where the list appears to be.

Pro

• mailman aliases visible in PostfixAdmin
• no need to edit the mailman config if you need a list on another domain

Cons

• aliases for listname@example.com -> listname@lists.example.com have to be added manually (or with a script)

Configuration

• /etc/postfix/main.cf

  • add a domain like lists.example.com in mydestination
  • add hash:/var/lib/mailman/data/aliases to alias_maps
  • restart postfix

• create the list in mailman (on the lists.example.com domain)

  /usr/lib/mailman/bin/newlist -l de -u "lists.example.com" -e "example.com" "listname"

note that the listname must be unique to the whole server - you can't have listname@example.com and listname@domain.tld

• add redirects in PostfixAdmin:
  • listname@example.com -> listname@lists.example.com
  • listname-request@example.com -> listname-request@lists.example.com
  • [same for the other mailman aliases]

You can add the aliases in PostfixAdmin manually or by using the CLI.

using Mailman virtual domains

The second method is using Mailman's virtual domain support.

Pro

• no need to manually add aliases

Cons

• mailman aliases not visible in PostfixAdmin (someone could accidently create overlapping aliases)
• you need to edit the mailman config if you need a list on another domain

Configuration

See http://list.org/mailman-install/postfix-virtual.html for information how to configure this.