On Wed, Dec 10, 2008 at 09:00:37PM +0100, Tomas Pospisek wrote: > On Wed, 10 Dec 2008, Lionel Elie Mamane wrote: >> On Wed, Dec 10, 2008 at 08:45:31PM +0100, Tomas Pospisek wrote:
>>> IMHO the bug reported in #396537 some 2 years ago doesn't apply any more. >>> I've followed the instructions in /usr/share/doc/mailman/README.Exim4.Debian >>> but they are - as far as I can see - bogus as well. >> The setup you describe does not play well with multiple virtual email >> domains. It will - as far as Exim is concerned - put every mailing >> list in every domain, which will lead to errors in mailman (unless you >> configure [EMAIL PROTECTED] as aliases for the list in every list >> for each virtual domain served by that Exim. > All right, I stand corrected. However, what is not described in the > README is what should go into the MAILMAN_HOME/data/aliases File? > How does it look like? Could you describe that? It is automatically generated by Mailman; that is the effect of "MTA='Postfix'" (and putting all mailman email domains in POSTFIX_STYLE_VIRTUAL_DOMAINS). It contains things like: # LOOP ADDRESSES START [EMAIL PROTECTED] mailman-loop # LOOP ADDRESSES END for every domain configured in mailman, and # STANZA START: list.name # CREATED: Sun May 23 19:00:51 2004 [EMAIL PROTECTED] list.name [EMAIL PROTECTED] list.name-admin [EMAIL PROTECTED] list.name-bounces [EMAIL PROTECTED] list.name-confirm [EMAIL PROTECTED] list.name-join [EMAIL PROTECTED] list.name-leave [EMAIL PROTECTED] list.name-owner [EMAIL PROTECTED] list.name-request [EMAIL PROTECTED] list.name-subscribe [EMAIL PROTECTED] list.name-unsubscribe # STANZA END: list.name for every mailing list known to mailman. Actually, most of this stuff is ignored by Exim4; all it looks for is a line whose left-hand-side is "[EMAIL PROTECTED]" when routing the email addresses [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], etc. It ignores the right-hand-side and it ignores the other additional lines. I had as a plan to fork off Mailman's Postfix support into a "minimal" Exim support (that is, recognise MTA='Exim' in mm_cfg.py) that would generate that file with just: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] etc, instead of all the extra unused things, but I never got round to it; works like that, so never became a priority. > (I do not understand how the condition line finds out that to which > domain a list belongs to) When routing email address [EMAIL PROTECTED] (or [EMAIL PROTECTED] or [EMAIL PROTECTED] or ...), it looks in that file for a line that starts with "[EMAIL PROTECTED]" and then whitespace or a ":" or end-of-line. -- Lionel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
