Re: [Mailman-Developers] [Mailman-checkins] SF.net SVN: mailman: [8100] trunk/mailman/Mailman/MTA/Postfix.py

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Nov 23, 2006, at 7:32 AM, tkikuchi@users.sourceforge.net wrote:
I haven't tried this diff yet, but are you sure that you need the
alias settings if you've got a transport_maps setting? I thought
that I tested using fully qualified alias names in the transport map
and not needing alias file entries unless you wanted site-wide or
across-all-domain aliases, e.g. noreply@.
I'll have to test this again, but it would be great that if you're
using LMTP via transport maps, you don't also need alias file settings.
- -Barry
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRWXppXEjvBPtnXfVAQKtSQP+LZJj+k/tRGznbOUP93I6ShSgHIbWoyy7 O9Bf6Y8a4gw4ru31MDDfNeYU3/0PRr+LLEqD5oAD1iTNPwojdUOSwOuzNkvAwyZy MIyIkH8LRX/Xj91ye8+JHqdin9ZV3Wh5j0DjXPTM5iBihK7rYrk+7qkyYsgOBm7j Qt9OAUitS0s= =kEaT -----END PGP SIGNATURE-----

Well, I'm testing on debian/postfix-2.1.5, which may be old, but the postfix returns 550 if I set up with transport map only. But, additional test on my site revealed that using virtual map resulted in pipe command and not lmtp. :-( I'll test it more on this weekend.
-- Tokio Kikuchi, tkikuchi@is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/

Hi,
After all, you are right, Barry.
Tokio Kikuchi wrote:
I've committed in trunk and here is the basic configuration for Postfix virtual host environment. We need no indivual entries for transport file. You may have to run bin/genaliases if LMTP_ONLY_DOMAINS is updated though.
Postfix configuration main.cf +------------------------------------------------- |# dom1 is the main hostname. |# dom2 is not here |mydestination = dom1.example.com |# You need aliases for noreply address |alias_maps = hash:/etc/aliases | hash:/usr/local/mailman/data/aliases |# for persons in dom2 domain |virtual_alias_maps = hash:/etc/postfix/virtual |# everything else is in transport |transport_maps = hash:/usr/local/mailman/data/transport +------------------------------------------------- /etc/postfix/virtual +------------------------------------------------- |# if you want to deliver to a real person in dom2 |user@dom2.example.com dom2user +------------------------------------------------- /usr/local/mailman/data/aliases +------------------------------------------------- |noreply: /usr/local/mailman/data/owner-bounces.mbox +------------------------------------------------- /usr/local/mailman/data/transport +------------------------------------------------- |# This file is automatically generated |noreply@dom1.example.com local:noreply |... etc. |# dom2 is for mailman only (except in /etc/postfix/virtual) |dom2.example.com lmtp:localhost:8025 |# list transports follow. |list@dom1.example.com lmtp:localhost:8025 |... etc. +-------------------------------------------------
etc/mailman.cfg (Defaults.py) +------------------------------------------------- |USE_LMTP = Yes |add_runner('LMTPRunner') |add_domain('dom2.example.com', 'www2.example.com') |LMTP_ONLY_DOMAINS = ['dom2.example.com'] |# Use this domain only for mailman mailing list. |# You should write postfix 'virtual' file for other persons |# in this domain. +-------------------------------------------------
-- Tokio Kikuchi, tkikuchi@is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Nov 25, 2006, at 9:28 PM, Tokio Kikuchi wrote:
Hi Tokio,
Yes, I think this is looking really good. I think I see what you're
doing: you use a single transport entry to catch all aliases in a
domain, and any overrides for that domain go in a virtual file.
Correct? That seems nicer than having to write every alias in the
transport file.
I'm not quite ready to update to your revision though. I'm currently
trying again to convert to SQLAlchemy for all list data and I'm in
the middle of that process. I'd like to commit these changes to the
trunk, but if it looks too radical then I might create a short lived
branch for that work. I'm going to try to not completely break the
trunk. ;)
Thanks,
- -Barry
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRWuznXEjvBPtnXfVAQK4gAQAqtP1HPBAYwzECsyHQpuZt7YhAh9/yONX t0b0lFAlPcqnAYaIaI+UlLfPUPzebc93tJGyktuUSc7csAwn3TgZAR/ttn/wEqi/ ZNAVrYPEHMvm+5pSizURRgzlS/i9+UaEjgvINZaqr8DyRhVRp0BlugrIGDCTfUC8 Ve+fG2+wZUU= =aPCl -----END PGP SIGNATURE-----

Well, I'm testing on debian/postfix-2.1.5, which may be old, but the postfix returns 550 if I set up with transport map only. But, additional test on my site revealed that using virtual map resulted in pipe command and not lmtp. :-( I'll test it more on this weekend.
-- Tokio Kikuchi, tkikuchi@is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/

Hi,
After all, you are right, Barry.
Tokio Kikuchi wrote:
I've committed in trunk and here is the basic configuration for Postfix virtual host environment. We need no indivual entries for transport file. You may have to run bin/genaliases if LMTP_ONLY_DOMAINS is updated though.
Postfix configuration main.cf +------------------------------------------------- |# dom1 is the main hostname. |# dom2 is not here |mydestination = dom1.example.com |# You need aliases for noreply address |alias_maps = hash:/etc/aliases | hash:/usr/local/mailman/data/aliases |# for persons in dom2 domain |virtual_alias_maps = hash:/etc/postfix/virtual |# everything else is in transport |transport_maps = hash:/usr/local/mailman/data/transport +------------------------------------------------- /etc/postfix/virtual +------------------------------------------------- |# if you want to deliver to a real person in dom2 |user@dom2.example.com dom2user +------------------------------------------------- /usr/local/mailman/data/aliases +------------------------------------------------- |noreply: /usr/local/mailman/data/owner-bounces.mbox +------------------------------------------------- /usr/local/mailman/data/transport +------------------------------------------------- |# This file is automatically generated |noreply@dom1.example.com local:noreply |... etc. |# dom2 is for mailman only (except in /etc/postfix/virtual) |dom2.example.com lmtp:localhost:8025 |# list transports follow. |list@dom1.example.com lmtp:localhost:8025 |... etc. +-------------------------------------------------
etc/mailman.cfg (Defaults.py) +------------------------------------------------- |USE_LMTP = Yes |add_runner('LMTPRunner') |add_domain('dom2.example.com', 'www2.example.com') |LMTP_ONLY_DOMAINS = ['dom2.example.com'] |# Use this domain only for mailman mailing list. |# You should write postfix 'virtual' file for other persons |# in this domain. +-------------------------------------------------
-- Tokio Kikuchi, tkikuchi@is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Nov 25, 2006, at 9:28 PM, Tokio Kikuchi wrote:
Hi Tokio,
Yes, I think this is looking really good. I think I see what you're
doing: you use a single transport entry to catch all aliases in a
domain, and any overrides for that domain go in a virtual file.
Correct? That seems nicer than having to write every alias in the
transport file.
I'm not quite ready to update to your revision though. I'm currently
trying again to convert to SQLAlchemy for all list data and I'm in
the middle of that process. I'd like to commit these changes to the
trunk, but if it looks too radical then I might create a short lived
branch for that work. I'm going to try to not completely break the
trunk. ;)
Thanks,
- -Barry
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin)
iQCVAwUBRWuznXEjvBPtnXfVAQK4gAQAqtP1HPBAYwzECsyHQpuZt7YhAh9/yONX t0b0lFAlPcqnAYaIaI+UlLfPUPzebc93tJGyktuUSc7csAwn3TgZAR/ttn/wEqi/ ZNAVrYPEHMvm+5pSizURRgzlS/i9+UaEjgvINZaqr8DyRhVRp0BlugrIGDCTfUC8 Ve+fG2+wZUU= =aPCl -----END PGP SIGNATURE-----
participants (2)
-
Barry Warsaw
-
Tokio Kikuchi