[Mailman-Users] Postfix, Mailman, and postfix-to-mailman.py trouble

Craig Stacey stace at mcs.anl.gov
Thu Oct 30 23:11:12 CET 2008


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Oct 30, 2008, at 4:25 PM, Stefan Förster wrote:

> Followup to myself:
>
> * Stefan Förster <cite+mailman-users at incertum.net> wrote:
>> * Craig Stacey <stace at mcs.anl.gov> wrote:
>>> master.cf:
>>> mailmancom   unix  -       n       n       -       -       pipe
>>>  flags=FR user=list argv=/www/lists.example.com/bin/postfix-to-
>>> mailman.py ${nexthop} ${user}
>>> mailmanorg   unix  -       n       n       -       -       pipe
>>>  flags=FR user=list argv=/www/lists.example.org/bin/postfix-to-
>>> mailman.py ${nexthop} ${user}
>>> mailmannet   unix  -       n       n       -       -       pipe
>>>  flags=FR user=list argv=/www/lists.example.net/bin/postfix-to-
>>> mailman.py ${nexthop} ${user}
> [...]
>>> All the docs specify you should put this line in main.cf:
>>>
>>> mailman_destination_recipient_limit = 1
>
> Did you do that?
>
> I.e., did you specify:
> mailmancom_destination_recipient_limit = 1
> mailmanorg_destination_recipient_limit = 1
> mailmannet_destination_recipient_limit = 1

This is precisely the magic we were missing.  I'm unfamiliar with that  
config line and has assumed the "mailman" portion of it was a mailman  
specific thing, not a transport thing.  This has solved our problem,  
thank you so much!


==
Craig



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAkkKMQEACgkQbVNGA3HOzQt9nACcDqr0JDgY/oIrf7si70dm1Aqy
fCEAnApvnIcbaRo8QmaFCsO31QQCyWAw
=cn4X
-----END PGP SIGNATURE-----


More information about the Mailman-Users mailing list