OK, I am sure I am almost there! I now have data/aliases and data/mailman-virtual functioning correctly, in that when lists are created or deleted, the appropriate alias entries are placed into these files. Thanks for getting me this far!
I have run into a further problem, however: When I send a message to a test list on the primary domain, it bounces with "[EMAIL PROTECTED] listname:unknown user". When I send a message to a test list on a virtual domain, it bounces with "[EMAIL PROTECTED] listname2:unknown user". Since aliases seem to be updating properly, this seems odd. Postfix is, I believe, properly connected to mailman, with (in main.cf): virtual_maps=hash:/usr/postfix/virtual, hash:/usr/local/mailman/data/virtual-mailman (NB I am assuming that I do not also update virtual_domain_maps) and: alias_database=hash:/etc/postfix/aliases, hash:/usr/local/mailman/data/aliases (NB I am assuming that I do not also update alias_maps) I think I have the mm_cfg.py right, too, with: MTA='Postfix' POSTFIX_STYLE_VIRTUAL_DOMAINS=['domain2'] add_virtualhost('www.domain2.org','domain2.org') added. Two final points: 1 - Before I tried setting up virtual domains, the system worked fine on a single domain, without any "unknown user" errors. 2 - Given the above, aliases for the special "mailman" list are contained in both /etc/postfix/aliases and /usr/local/mailman/aliases. This doesn't seem to make any difference, though I am unsure. I hope this is a clear explanation - any help much appreciated. Jon --- Mark Sapiro <[EMAIL PROTECTED]> wrote: > Jon Loose wrote: > > > >I did what was suggested below... > > > ... > > > >>If you now run bin/genaliases, it should create > the > >>data/aliases and > >>data/virtual-mailman files containing data for all > >>your lists, and run > >>the postalias and postmap commands to create the > .db > >>files. > > > ... > > > >yet, mailman created data/aliases, but not > >data/virtual-mailman. I made a vain attempt with > >"touch virtual-mailman", and then "genalias". This > >produced a virtual-mailman.db, but throws up errors > in > >the mail log because it is empty. > > > In order for virtual-mailman to be created/updated, > you must have a > list of virtual domains in mm_cfg.py like: > > POSTFIX_STYLE_VIRTUAL_DOMAINS = ['domain2', > 'domain3'] > > (see > <http://www.list.org/mailman-install/postfix-virtual.html> > for > what actually goes in this list - it could be just > one domain or two > as above or more), AND you must have one or more > Mailman lists with > host_name equal to one of the domains in > POSTFIX_STYLE_VIRTUAL_DOMAINS. Apparently you don't > have both of these > conditions. > > > >Also, I assume I create a list on the virtual > domain > >using newlist [EMAIL PROTECTED] ? > > > Yes, but contrary to intuition, domain2 in this case > must be the URL > host of the list, not the email host unless they are > the same. > > There are also options in later versions of newlist > to specify this > less counter-intuitively. See 'bin/newlist --help' > > -- > Mark Sapiro <[EMAIL PROTECTED]> The highway is > for gamblers, > San Francisco Bay Area, California better use > your sense - B. Dylan > > ___________________________________________________________ To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp