Oliver Glueck wrote: > >I'm not sure about my malman installation. >I will show at first some facts: > >- LAN: our LAN domain is "intern.company.de" >- the mail server in the LAN: mail.intern.company.de >- on mail.intern.company.de is running open xchange on an UCS (unvention >corporate server, a debian) > >- our external domain is: company.com -> an email address is ><name>@company.com > and ....@company.de on the same server. > >- the internal open xchange has so three mail domains : >intern.company.de, company.com and company.de >- fetchmail is polling the emails from the external mail server > >- mailman is installed on the open xchange server 'mail.intern.company.de' > >My first mailing list is (after mailman) 'about-dummy'. >And /etc/postfix/virtual contains: >about-du...@company.com about-dummy >about-du...@company.de about-dummy >about-du...@intern.company.de about-dummy
These things shouldn't be in /etc/postfix/virtual. >My first try to receive an email from an external address to this list >is failed, because >I have to add 'about-du...@localhost' in virtual. After this entry, >the email >was received. >But why ....@localhost? I saw this in the log file, unknown mailbox >about-du...@localhost. This is not a Mailman issue. This is probably fetchmail that is delivering the message to about-du...@localhost. >For mailman I have no Idea about virtual_alias or virtual domains. >Only these two lines > IMAGE_LOGOS = '/icons/' > MTA = 'Postfix' >I have added to mm_cfg.py. Is this ok? With MTA = 'Postfix'. Mailman will maintain both aliases in /usr/local/mailman/data/aliases and virtual maps (if necessary?) in /usr/local/mailman/data/virtual-mailman, but you have issues that will probably preclude this from working. If fetchmail is going to deliver to addresses like listn...@localhost listname-boun...@localhost etc, and localhost is in mydestination as it appears to be, you only need aliases and not virtual maps. Thus both what you have in mm_cfg.py and what you have in main.cf looks OK. If you have mail being given to Postfix for listn...@company.com, you can add POSTFIX_STYLE_VIRTUAL_DOMAINS = ['company.com'] in mm_cfg.py and, assuming the list's email domain is company.com (see my reply to your other post), Mailman will generate virtual maps like listn...@company.com LISTNAME listname-boun...@company.com LISTNAME-bounces etc, in /usr/local/mailman/data/virtual-mailman and you need to add hash:/usr/local/mailman/data/virtual-mailman to virtual_maps in main.cf. If you actually need multiple domains for the same list in the virtual maps, Mailman won't do that automatically. >And in postfix? >Here a short cutout from main.cf: >---snip--- >myhostname = mail.intern.company.de >mydomain = intern.company.de >myorigin = /etc/mailname >smtp_helo_name = mail.intern.company.de >append_dot_mydomain = no >masquerade_domains = $mydomain >masquerade_exceptions = root >transport_maps = hash:/etc/postfix/transport, ldap:ldaptransport >mydestination = $myhostname.$mydomain, localhost.$mydomain, $mydomain, >localhost, $transport_maps >mynetworks = 127.0.0.0/8 >relay_domains = $mydestination >relayhost = www.company.de >canonical_maps = hash:/etc/postfix/canonical >virtual_maps = hash:/etc/postfix/virtual, ldap:ldapgroups, >ldap:ldapdistlist, ldap:ldapvirtual, ldap:ldapsharedfolderlocal >relocated_maps = hash:/etc/postfix/relocated >alias_maps = hash:/etc/aliases,hash:/usr/local/mailman/data/aliases >alias_database = hash:/etc/aliases >---snap--- and many LDAP entries from the open xchange installation. -- Mark Sapiro <m...@msapiro.net> 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