Hi,
After all, you are right, Barry.
Tokio Kikuchi wrote:
>>> - if config.USE_LMTP immediately after ALIASFILE add/remove; we need
>>> to keep alias settings because postfix rejects as unknown if
>>> not present.
>> 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. [EMAIL PROTECTED]
>
> 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.
>
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
|[EMAIL PROTECTED] dom2user
+-------------------------------------------------
/usr/local/mailman/data/aliases
+-------------------------------------------------
|noreply: /usr/local/mailman/data/owner-bounces.mbox
+-------------------------------------------------
/usr/local/mailman/data/transport
+-------------------------------------------------
|# This file is automatically generated
|[EMAIL PROTECTED] local:noreply
|... etc.
|# dom2 is for mailman only (except in /etc/postfix/virtual)
|dom2.example.com lmtp:localhost:8025
|# list transports follow.
|[EMAIL PROTECTED] 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, [EMAIL PROTECTED]
http://weather.is.kochi-u.ac.jp/
_______________________________________________
Mailman-Developers mailing list
Mailman-Developers@python.org
http://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives:
http://www.mail-archive.com/mailman-developers%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
