Now just hit one more slight snag, can no longer create new lists on the second-domain.org.
Fails with the Bug in Mailman version 2.1.5 - We're sorry, we hit a bug! Error. /var/log/mailman error shows: admin(14722): RuntimeError: command failed: /usr/sbin/postmap /etc/mailman/virtual-mailman (status: 1, Operation not permitted) I noticed that apache is now trying to own the virtual-mailman file in /etc/mailman, didn't notice that before. Changing the ownership to root:mailman doesn't work, when trying to create a list it fails and apache takes ownership back. Scott -----Original Message----- From: Mark Sapiro [mailto:[EMAIL PROTECTED] Sent: Friday, October 31, 2008 2:16 PM To: Scott Race Cc: mailman-users@python.org Subject: RE: [Mailman-Users] Mailman on multiple domains Scott Race wrote: >Thanks for the reply - so this will be a multiple mailman domain. >Currently list working on first-domain.org, trying to get it working on >second-domain.org. > >So yes, "Host name this list prefers for email" is correct as >second-domain.org. > >My mm_cfg.py looks like this: > > from socket import * > try: > fqdn = getfqdn() > except: > fqdn = 'mm_cfg_has_unknown_host_domains' > > DEFAULT_URL_HOST = fqdn > DEFAULT_EMAIL_HOST = fqdn > > # Because we've overriden the virtual hosts above >add_virtualhost > # MUST be called after they have been defined. > > add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) > add_virtualhost('www.first-domain.org', 'first-domain.org') > add_virtualhost('www.second-domain.org', >'second-domain.org') > > ############################################################## > # Put YOUR site-specific configuration below, in mm_cfg.py . # > # See Defaults.py for explanations of the values. # > > # Note - if you're looking for something that is imported from >mm_cfg, but you > # didn't find it above, it's probably in Defaults.py. > > POSTFIX_STYLE_VIRTUAL_DOMAINS = ['second-domain.org'] > > MTA = 'Postfix' > > >So, I might be getting somewhere now...so I have a virtual-mailman file >now, it's in /etc/mailman. I don't recall your telling us that this was a RedHat package. These things make a difference. It has the following entries: > ># LOOP ADDRESSES START >[EMAIL PROTECTED] mailman-loop ># LOOP ADDRESSES END > ># STANZA START: scott-test ># CREATED: Fri Oct 31 15:44:28 2008 >[EMAIL PROTECTED] scott-test >[EMAIL PROTECTED] scott-test-admin >[EMAIL PROTECTED] scott-test-bounces >[EMAIL PROTECTED] scott-test-confirm >[EMAIL PROTECTED] scott-test-join >[EMAIL PROTECTED] scott-test-leave >[EMAIL PROTECTED] scott-test-owner >[EMAIL PROTECTED] scott-test-request >[EMAIL PROTECTED] scott-test-subscribe >[EMAIL PROTECTED] scott-test-unsubscribe ># STANZA END: scott-test > >And the virtual-mailman.db is present and current (same date and time as >the virtual-mailman file). That's good. >So, getting closer, but a test to the list still bounces: >The following recipient(s) could not be reached: > > [EMAIL PROTECTED] on 10/31/2008 1:47 PM > There was a SMTP communication problem with the recipient's >email server. Please contact your system administrator. > <jdaarch.com #5.5.0 smtp;550 <[EMAIL PROTECTED]>: >Recipient address rejected: User unknown in virtual alias table> > > >At this point I'm wondering if since I'm using a second domain, I need >to include the first domain in the virtual domain config? Right now it >seems like only my second-domain is in the virtual config. That's probably not a problem. Does your main.cf virtual_alias_maps point to /etc/mailman/virtual-mailman where it is or does it point somewhere else. How about alias_maps? -- Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
