Greetings.
I'm installing mailman 2.1.14 onto an Ubuntu server that previously had
mailman 2.1.13 installed, and it looks like the 2.1.13 install left some
virtual domain artifacts behind, namely:
/etc/postfix/transport, containing:
[my system's hostname] mailman:
... and the usual postifix transport lines in master.cf:
mailman unix - n n - - pipe
flags=FR user=list argv=/usr/local/mailman/bin/postfix-to-mailman.py
${nexthop} ${user}
I currently have no need for virtual domains, but was wondering:
- Is there any advantage besides being able to trivially enable virtual
domains, to maintaining a separate transport for mailman?
- What is the default transport that should be used by mailman 2.1.14 if
no virtual domains are needed -- smtp?
Thanks.
--
Richard Haas <[email protected]>
GnuPG public key ID: 1CB7F0E2
--
------------------------------------------------------
Mailman-Users mailing list [email protected]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
