Re: [Mailman-Users] Newer postfix: unused parameter: mailman_destination_recipient_limit=1
Le 2012-03-09 20:28, Larry Stone a écrit :
On Fri, 9 Mar 2012, Tanstaafl wrote:
Hi all,
I've had this parameter defined in my postfix ever since it was
first set up (not by me), and most everything I read online says it
should be there.
But, the newer versions of postfix now provide warnings for unused
parameters, and that is what I'm getting for this one parameter:
myhost : Fri Mar 09, 13:16:12 : ~
# postconf -n | grep mailman
alias_maps = hash:/etc/mail/aliases,
hash:/var/lib/mailman/data/aliases
virtual_alias_maps = ${mysql}/vam.cf,
hash:/var/lib/mailman/data/virtual-mailman
postconf: warning: /etc/postfix/main.cf: unused parameter:
mailman_destination_recipient_limit=1
myhost : Fri Mar 09, 13:16:26 : ~
#
Anyone have any idea why? Am I indeed not using it? I'd rather not
just comment it out and test without some confirmation first, since
this is a production box.
transport_destination_recipient_limit is a Postfix parameter that is
specific to the named transport. If you don't have a transport named
mailman, then mailman_transport_destination_recipient is indeed
unused.
-- Larry Stone
lston...@stonejongleux.com
this depend version the postfix
ks3 ~]# 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
--
http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xC2626742
gpg --keyserver pgp.mit.edu --recv-key C2626742
http://urlshort.eu fakessh @
http://gplus.to/sshfake
http://gplus.to/sshswilting
http://gplus.to/john.swilting
https://lists.fakessh.eu/mailman/
This list is moderated by me, but all applications will be accepted
provided they receive a note of presentation
--
Mailman-Users mailing list Mailman-Users@python.org
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
Re: [Mailman-Users] Newer postfix: unused parameter: mailman_destination_recipient_limit=1
On Mar 9, 2012, at 3:17 PM, ml wrote: this depend version the postfix ks3 ~]# 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 lston...@stonejongleux.com http://www.stonejongleux.com/ -- Mailman-Users mailing list Mailman-Users@python.org 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
Re: [Mailman-Users] Newer postfix: unused parameter: mailman_destination_recipient_limit=1
* Larry Stone lston...@stonejongleux.com: 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. Yep. If no mailman transport, then mailman_destination_recipient_limit is unused. If there is a mailman transport, then mailman_destination_recipient_limit is used. Yep. 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. Yep. -- Ralf Hildebrandt Charite Universitätsmedizin Berlin ralf.hildebra...@charite.deCampus Benjamin Franklin http://www.charite.de Hindenburgdamm 30, 12203 Berlin Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155 -- Mailman-Users mailing list Mailman-Users@python.org 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
[Mailman-Users] Newer postfix: unused parameter: mailman_destination_recipient_limit=1
Hi all,
I've had this parameter defined in my postfix ever since it was first
set up (not by me), and most everything I read online says it should be
there.
But, the newer versions of postfix now provide warnings for unused
parameters, and that is what I'm getting for this one parameter:
myhost : Fri Mar 09, 13:16:12 : ~
# postconf -n | grep mailman
alias_maps = hash:/etc/mail/aliases, hash:/var/lib/mailman/data/aliases
virtual_alias_maps = ${mysql}/vam.cf,
hash:/var/lib/mailman/data/virtual-mailman
postconf: warning: /etc/postfix/main.cf: unused parameter:
mailman_destination_recipient_limit=1
myhost : Fri Mar 09, 13:16:26 : ~
#
Anyone have any idea why? Am I indeed not using it? I'd rather not just
comment it out and test without some confirmation first, since this is a
production box.
Thanks...
Charles
--
Mailman-Users mailing list Mailman-Users@python.org
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
Re: [Mailman-Users] Newer postfix: unused parameter: mailman_destination_recipient_limit=1
On Fri, 9 Mar 2012, Tanstaafl wrote:
Hi all,
I've had this parameter defined in my postfix ever since it was first set up
(not by me), and most everything I read online says it should be there.
But, the newer versions of postfix now provide warnings for unused
parameters, and that is what I'm getting for this one parameter:
myhost : Fri Mar 09, 13:16:12 : ~
# postconf -n | grep mailman
alias_maps = hash:/etc/mail/aliases, hash:/var/lib/mailman/data/aliases
virtual_alias_maps = ${mysql}/vam.cf,
hash:/var/lib/mailman/data/virtual-mailman
postconf: warning: /etc/postfix/main.cf: unused parameter:
mailman_destination_recipient_limit=1
myhost : Fri Mar 09, 13:16:26 : ~
#
Anyone have any idea why? Am I indeed not using it? I'd rather not just
comment it out and test without some confirmation first, since this is a
production box.
transport_destination_recipient_limit is a Postfix parameter that is
specific to the named transport. If you don't have a transport named
mailman, then mailman_transport_destination_recipient is indeed unused.
-- Larry Stone
lston...@stonejongleux.com
--
Mailman-Users mailing list Mailman-Users@python.org
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
