On Mar 9, 2012, at 3:17 PM, ml wrote: > > this depend version the postfix > > > ks37777 ~]# postconf -n | grep mailman > alias_maps = hash:/etc/aliases , > hash:/etc/postfix/aliases,hash:/etc/mailman/aliases > mailman_destination_recipient_limit = 1 > virtual_alias_maps = hash:/etc/postfix/virtual,hash:/etc/mailman/aliases > > ok on my machine
While whether or not you get unused parameter warnings (and they are just warnings) depends on the Postfix version (the check was added in Postfix 2.9.0), whether or not mailman_destination_recipient_limit is used depends on whether or not you have defined a "mailman" transport in master.cf. If no mailman transport, then mailman_destination_recipient_limit is unused. If there is a mailman transport, then mailman_destination_recipient_limit is used. Postfix transports can be called anything you want to call them. There is nothing magic about a Postfix transport named "mailman" that ties it to GNU Mailman. So this is really a Postfix issue, not a Mailman issue. -- Larry Stone [email protected] http://www.stonejongleux.com/ ------------------------------------------------------ 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
