Cédric Jeanneret wrote: > >I'm having big troubles with a special setup: > >one server, one domain (say foo.bar.com), virtual mailboxes (managed by >ldap), and a mailman > >I'm using postfix and dovecot for the "standard" mail part, and this >works well. My problem is for mailman: > >While trying to send email to my-l...@foo.bar.com, postfix tells me >this: > >Feb 23 09:49:25 sqdf3 postfix/smtpd[14760]: connect from myHost[myIP] >Feb 23 09:49:25 sqdf3 postfix/smtpd[14760]: 1CAECBE69AC: >client=myHost[myIP] >Feb 23 09:49:25 sqdf3 postfix/cleanup[14765]: 1CAECBE69AC: >message-id=<20120223084925.0B86537AAEF@mail.myhost> >Feb 23 09:49:25 sqdf3 postfix/qmgr[14759]: 1CAECBE69AC: >from=<me@myhost>, size=513, nrcpt=1 (queue active) >Feb 23 09:49:25 sqdf3 postfix/smtpd[14760]: disconnect from >myHost[myIP] >Feb 23 09:49:25 sqdf3 postfix/virtual[14766]: 1CAECBE69AC: >to=<|/var/lib/mailman/mail/mailman post my-l...@foo.bar.com>, >orig_to=<my-l...@foo.bar.com>, relay=virtual, delay=0.03, >delays=0.02/0/0/0.01, dsn=5.1.1, status=bounced (unknown user: >"|/var/lib/mailman/mail/mailman post my-l...@foo.bar.com")
So you have an alias in a virtual mapping. Aliases only work with 'local' delivery. [...] >transport_maps = hash:/etc/postfix/transport > >virtual_transport = virtual >virtual_transport_maps = hash:/etc/postfix/transport What is this for? >virtual_alias_maps = hash:/etc/aliases, >ldap:/etc/postfix/ldap-aliases.cf, hash:/etc/postfix/virtual /etc/aliases is not in the correct format for virtual_alias_maps. It should not be there. >virtual_alias_mbox = ldap:/etc/postfix/ldap-mbox.cf >virtual_mailbox_maps = ldap:/etc/postfix/ldap-accounts.cf >virtual_gid_maps = static:104 >virtual_minimum_uid = 8 >virtual_uid_maps = static:8 >virtual_mailbox_domains = foo.bar.com >virtual_mailbox_base = / >mailman_destination_recipient_limit = 1 >smtpd_sasl_type = dovecot > > >The virtual user delivery works just fine. Here's a sniped of my >transport hash: >my-l...@foo.bar.com mailman: So mail to my-l...@foo.bar.com should use a 'mailman' transport, presumably defined in master.cf as postfix_to_mailman.py. If you want to use this, there should be no aliases for Mailman at all there should only be transport maps entries of the form my-l...@foo.bar.com mailman: my-list-ad...@foo.bar.com mailman: my-list-boun...@foo.bar.com mailman: etc. A total of 10 per list since non-list mail for this domain should be handled by the 'virtual' transport. The FAQ at <http://wiki.list.org/x/ZoCj> may help. >@foo.bar.com virtual: > >Any help is welcome, if you need any other information regarding the >postfix configuration, please ask - I'm pretty sure it's obvious, but I >must be blind :(. > >Mailman version: 1:2.1.13-5 (on debian squeeze) >Postfix version: 2.7.1-1+squeeze1 >Dovecot version: 1:1.2.15-7 Please also see the FAQ at <http://wiki.list.org/x/OIDD>. -- 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 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org