[Mailman-Users] Re: Writing to list bounces with 'user doesn't exist'
It sounds like you still have a working postfix+dovecot setup. :-) Yes, I suppose so! But I keep poking at it so much, I worry :) Indeed I wouldn't expect dovecot to know any such user, so I'm not sure what step I've missed... In my postfix main.cf I have: Unfortunately, you've left out the critical information: dovecot routing. Clearly, dovecot has a relatively high-priority routing for local traffic, and it's sucking up everything addressed to your host before Mailman gets a whack at it. There are several possibilities, so it doesn't make sense for me to guess. Hmm, the dovecot-related settings in main.cf seem to be: ``` mailbox_transport = lmtp:unix:private/dovecot-lmtp smtpd_sasl_auth_enable = yes smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth smtpd_sasl_local_domain=$myhostname smtpd_sender_login_maps = hash:/usr/local/etc/postfix/smtpd_sender_login_maps.txt virtual_transport = lmtp:unix:private/dovecot-lmtp ``` Do those give a clue? Sean -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/ Member address: arch...@jab.org
[Mailman-Users] Writing to list bounces with 'user doesn't exist'
Sean McBride writes: > So I have/had a working postfix+dovecot setup, and then I installed > mailman2. It sounds like you still have a working postfix+dovecot setup. :-) > Indeed I wouldn't expect dovecot to know any such user, so I'm not > sure what step I've missed... > > In my postfix main.cf I have: Unfortunately, you've left out the critical information: dovecot routing. Clearly, dovecot has a relatively high-priority routing for local traffic, and it's sucking up everything addressed to your host before Mailman gets a whack at it. There are several possibilities, so it doesn't make sense for me to guess. > In my mm_cfg.py I have: This isn't a problem yet. The fact that DEFAULT_EMAIL_HOST and $myorigin are not in $mydestination looks like a potential problem to me, but we'll deal with any issues here once you get mail into the pipes that go to Mailman. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Sourcehttps://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/ Member address: arch...@jab.org
[Mailman-Users] Writing to list bounces with 'user doesn't exist'
Hi all, So I have/had a working postfix+dovecot setup, and then I installed mailman2. It largely works. The web interface works, I can create lists, list creation emails are sent to the admin (me), but trying to write to a list (as a member) fails with a bounce. My maillog shows: ``` May 12 12:19:48 hostname postfix/lmtp[83792]: ED07A32156: to=, relay=mx.example.com[private/dovecot-lmtp], delay=0.6, delays=0.59/0/0/0.01, dsn=5.1.1, status=bounced (host mx.example.com[private/dovecot-lmtp] said: 550 5.1.1 User doesn't exist: testl...@example.com (in reply to RCPT TO command)) ``` Indeed I wouldn't expect dovecot to know any such user, so I'm not sure what step I've missed... In my postfix main.cf I have: ``` mydomain = example.com myhostname = mx.example.com mydestination = $myhostname localhost.$mydomain localhost myorigin = $mydomain virtual_alias_maps = hash:/usr/local/etc/postfix/virtual-aliases, hash:/usr/local/mailman/data/virtual-mailman alias_maps = hash:/etc/aliases, hash:/usr/local/mailman/data/aliases ``` In my mm_cfg.py I have: ``` MTA = "Postfix" POSTFIX_STYLE_VIRTUAL_DOMAINS = ['example.com'] DEFAULT_EMAIL_HOST = 'example.com' DEFAULT_URL_HOST = 'mailman.example.com' VIRTUAL_HOSTS.clear() add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) ``` Any clues would be greatly appreciated. Thanks, Sean -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/ Member address: arch...@mail-archive.com
[Mailman-Users] Re: Writing to list bounces with 'user doesn't exist'
On 5/12/25 12:41, Sean McBride wrote: Hmm, the dovecot-related settings in main.cf seem to be: mailbox_transport = lmtp:unix:private/dovecot-lmtp This sends all local deliveries to dovecot before consulting aliases. smtpd_sasl_auth_enable = yes smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth smtpd_sasl_local_domain=$myhostname smtpd_sender_login_maps = hash:/usr/local/etc/postfix/smtpd_sender_login_maps.txt virtual_transport = lmtp:unix:private/dovecot-lmtp and this sends all virtual mailbox deliveries to dovecot. I'm not sure if this trumps virtual_alias_maps, but it doesn't matter because virtual_alias_maps will map a virtual alias list address to a local address in alias_maps and mailbox_transport will send that to dovecot. I can't recall if there is a resolution to a MM 2.1 configuration with dovecot, but this search https://mail.python.org/archives/search?mlist=mailman-users%40python.org&q=dovecot may turn something up. I think the answer, if there is one, is to somehow configure dovecot to be aware of the mailman lists and route those addresses to mailman. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/ Member address: arch...@mail-archive.com
[Mailman-Users] Re: Writing to list bounces with 'user doesn't exist'
On 2025-05-12 at 15:41:56 UTC-0400 (Mon, 12 May 2025 15:41:56 -0400) Sean McBride is rumored to have said: It sounds like you still have a working postfix+dovecot setup. :-) Yes, I suppose so! But I keep poking at it so much, I worry :) Indeed I wouldn't expect dovecot to know any such user, so I'm not sure what step I've missed... In my postfix main.cf I have: Unfortunately, you've left out the critical information: dovecot routing. Clearly, dovecot has a relatively high-priority routing for local traffic, and it's sucking up everything addressed to your host before Mailman gets a whack at it. There are several possibilities, so it doesn't make sense for me to guess. Hmm, the dovecot-related settings in main.cf seem to be: ``` mailbox_transport = lmtp:unix:private/dovecot-lmtp smtpd_sasl_auth_enable = yes smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth smtpd_sasl_local_domain=$myhostname smtpd_sender_login_maps = hash:/usr/local/etc/postfix/smtpd_sender_login_maps.txt virtual_transport = lmtp:unix:private/dovecot-smtp ``` Do those give a clue? virtual_transport definitely looks wrong, but I can't tell you what it should be without full 'postconf -Mf' and 'postconf -nf' output and maybe more details about why you have a "dovecot-smtp" transport defined using lmtp at all. E.g. On all my Mailman boxes with postfix "virtual_transport = virtual" but that's also the default, so presumably you've done something different. -- Bill Cole b...@scconsult.com or billc...@apache.org (AKA @grumpybozo@toad.social and many *@billmail.scconsult.com addresses) Not Currently Available For Hire -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/ Member address: arch...@mail-archive.com
[Mailman-Users] Re: Writing to list bounces with 'user doesn't exist'
Guy, Thanks for your reply. In /usr/local/mailman/data/virtual-mailman I have entries like: te...@example.com test9 test9-ad...@example.comtest9-admin and in /usr/local/mailman/data/aliases I have entries like: test9: "|/usr/local/mailman/mail/mailman post test9" test9-admin: "|/usr/local/mailman/mail/mailman admin test9" I believe I'm pointing to both those files with virtual_alias_maps and alias_maps as quoted below. Thanks, Sean On 12 May 2025, at 20:05, Guy B. Purcell wrote: Do you actually have the alias for testl...@example.com in either of your aliases files (most probably should be /usr/local/mailman/data/aliases)? The only way postfix will know what to do with that address is via an alias directing it to call a MM function that posts the message to the list. Despite my better judgement, I’m still on v2 & such an entry looks like: testlist: “|/path_to_mailman/mail/mailman post testlist” Been *many* years, but IIRC the docs note how to set those up properly & it was a manual process (but once you have the set for one list, copy/pasta + a little search/replace will get you the rest). -Guy On 2025 May 12, at 10:08, Sean McBride wrote: Hi all, So I have/had a working postfix+dovecot setup, and then I installed mailman2. It largely works. The web interface works, I can create lists, list creation emails are sent to the admin (me), but trying to write to a list (as a member) fails with a bounce. My maillog shows: ``` May 12 12:19:48 hostname postfix/lmtp[83792]: ED07A32156: to=, relay=mx.example.com[private/dovecot-lmtp], delay=0.6, delays=0.59/0/0/0.01, dsn=5.1.1, status=bounced (host mx.example.com[private/dovecot-lmtp] said: 550 5.1.1 User doesn't exist: testl...@example.com (in reply to RCPT TO command)) ``` Indeed I wouldn't expect dovecot to know any such user, so I'm not sure what step I've missed... In my postfix main.cf I have: ``` mydomain = example.com myhostname = mx.example.com mydestination = $myhostname localhost.$mydomain localhost myorigin = $mydomain virtual_alias_maps = hash:/usr/local/etc/postfix/virtual-aliases, hash:/usr/local/mailman/data/virtual-mailman alias_maps = hash:/etc/aliases, hash:/usr/local/mailman/data/aliases ``` In my mm_cfg.py I have: ``` MTA = "Postfix" POSTFIX_STYLE_VIRTUAL_DOMAINS = ['example.com'] DEFAULT_EMAIL_HOST = 'example.com' DEFAULT_URL_HOST = 'mailman.example.com' VIRTUAL_HOSTS.clear() add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) ``` Any clues would be greatly appreciated. Thanks, Sean -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/ Member address: g...@extragalactic.net -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/ Member address: arch...@jab.org
