[Mailman-Developers] Postfix/virtual-mailman not compatible when using dedicated destination (like "localhost")

[Barry Warsaw]

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

On Dec 4, 2006, at 7:18 PM, Barry Warsaw wrote:

> On Dec 4, 2006, at 6:58 PM, Tokio Kikuchi wrote:
>
>> In mailman-2.2, Postfix.py is considerably patched from the current
>> version, especially making use of LMTP interface.  New configuration
>> output is summarized in
>>
>> http://mail.python.org/pipermail/mailman-developers/2006-November/
>> 019307.html
>> (you should convert back ' at ' -> '@')
>>
>> In this model, your '@localhost' corresponds to '@dom1.example.com'
>> and
>> all your list and personal maiboxes are to 'dom2.example.com'.  You
>> need
>> no individual listname(-subqueue) destination in
>> aliases/virtual/transport files.  Only one line
>> dom2.example.com lmtp:localhost:8025
>> in transport file.  You only have to manage /etc/postfix/virtual for
>> personal accounts.
>>
>> Is this suffice your needs?
>
> The other thing is that you'll get the individual -subqueue entries
> if you don't want to use LMTP_ONLY_DOMAINS (presumably because you
> can't create a separate subdomain for your lists).  Right?

I realize that in context, this is confusing.  In Mailman 2.2 if you  
don't use LMTP_ONLY_DOMAINS, you'll get the individual -subqueue  
entries in the transport file, but I believe you will not have name  
collisions because the same entries do not need to be added to the  
alias files.  LMTP delivery rocks!  (Thanks to Tokio :).

- -Barry

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

iQCVAwUBRXS8X3EjvBPtnXfVAQIXdgQAtcsB5O7Mpw4Q5ER6V3wf5Y5Db4ugoR2P
jq3Dk+UXTZZ+Uwa88r6X2qlR4GChfXp3CjGvwYcQUjhpP3R3PGHCznfQhANC+ZJH
kQtLyP9PIwrOT1eS3sVvgive5U93q7VuOONI0SX1ZFiVXBSUNYH5wOY8+x5QhlcI
Or5i+NPTvGM=
=SJTJ
-----END PGP SIGNATURE-----