Search results for "user unknown in local recipient table" - Mailman-users

After importing my old databases, the mail local_recipient map is suddenly not working any more

by Wikinaut

After importing old databases everythimng looks fine now. But the mail local_recipient maps are not working (/etc/postfix/main.cf looks fine, as before, and postfix was restarted). Mails to test(a)example.org rejected with Error 550 Recipient address rejected: User unknown in local recipient table /* as in your installation guide */ transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp local_recipient_maps = $alias_maps hash:/var/lib/mailman3/data/postfix_lmtp relay_domains = hash:/var/lib/mailman3/data/postfix_domains The files appears to be present: /var/lib/mailman3/data# dir 4 -rw-rw---- 1 mailman mailman 339 Oct 20 21:13 postfix_domains 8 -rw-r----- 1 mailman mailman 12288 Oct 20 21:13 postfix_domains.db 4 -rw-rw---- 1 mailman mailman 2714 Oct 20 21:13 postfix_lmtp 12 -rw-r----- 1 mailman mailman 12288 Oct 20 21:13 postfix_lmtp.db What else is needed to get the list-addresses working and not rejected? It worked before the import.

2 years, 1 month

Re: Unable to get Postfix to bounce messages to non-existent lists

by skenny＠scss.tcd.ie

Thanks Mark Sapiro and Stephen J. Turnbull for your responses. Re the output of mailq - this was initially confusing (to me anyway). The diagnostic for the message stuck in the queue was "connection timed out", but the IP listed was the Postfix mail server's not Mailman's. At a guess, Postfix was trying to send the message to Postfix's local domain after it failed to LMTP it over to the Mailman server, and was unable to do that too. Since I posted yesterday, I hit upon a solution that seems to work ... I set relay_recipient_maps to the same value as transport_maps, so that the relevant config lines now look like this: transport_maps = regexp:/var/mailman-data/postfix_lmtp local_recipient_maps = $alias_maps relay_domains = regexp:/var/mailman-data/postfix_domains relay_recipient_maps = regexp:/var/mailman-data/postfix_lmtp This seems to have the desired effect (and, I hope, no unintended consequences). If I fire a message at a non-existent list now, I get an immediate bounce message in my mail client - "Recipient address rejected: User [nonexistent-list(a)lists.scss.tcd.ie] unknown in relay recipient table". No longer is the message loitering in the Postfix queue. The Postfix documentation for relay_recipient_maps says "Optional lookup tables with all valid addresses in the domains that match $relay_domains. [...] Technically, tables listed with $relay_recipient_maps are used as lists: Postfix needs to know only if a lookup string is found or not, but it does not use the result from the table lookup." For transport_maps, it says "Optional lookup tables with mappings from recipient address to (message delivery transport, next-hop destination). " Postfix does what we want now: bounce the message is the list name isn't found in relay_recipient_maps, forward it on to the Mailman server via LMTP (transport_maps setting) if it is. Re Stephen J. Turnbull's comment about the patch allowing Postfix to query Mailman's database and more, I think I'll hold off for the moment, but good to know. We will reconfigure when it makes it into an official release (we're using Maxking's Docker images). As ever I'm really grateful for your taking the time to respond, many thanks. Kind regards.

1 year, 9 months

Re: configuring postfix local recipient table

by Odhiambo Washington

On Wed, Apr 23, 2025 at 5:56 PM Alexander Inzinger-Zrock via Mailman-users < mailman-users(a)mailman3.org> wrote: > **System Key Data** > OS: Debian 12 > mailman: GNU Mailman 3.3.10 (Tom Sawyer) > Python: Python 3.11.2 (main, Nov 30 2024, 21:22:50) [GCC 12.2.0] > Method: Python Virtual Environment Installation > > > Ahoi, > > i am trying to configure a mailman3 instance > to replace a mailman2 installation (both on different hosts). > The mm3 instance is actually not reachable (Incoming) but can send > (Outgoing), > as is the desired state to be (we intend to swap IPs during change of > systems). > > A. Verify Incoming > > To verify that emails send to the MTA (postfix) get properly handled > and handed over to the mm3-instance i tried to substitute incoming email by > > a) swaks utility [1] (fail) > b) telnet utility [2] (fail) > c) command ''mailman inject'' [3] (success) > > With c) i copied a former generate testmail-file to the mm3-host > and injected it directly to my testlist (leaving out the MTA). > > With a) and b) i tried to hand over a testmail via CLI to the MTA (postfix) > what resulted in the error: > > "Recipient address rejected: User unknown in local recipient table" > > > B. /etc/postfix/main.cfg > > A search in mailman-users(a)mailman3.org archives [4] pointed me to the > configuration of postfix as MTA [5], especially settings with the > 'local_recipients_maps' parameter that should be set like [5]: > > local_recipient_maps = proxy:unix:passwd.byname $alias_maps > hash:/path-to-mailman/var/data/postfix_lmtp > > what i did / already had done. > > > C. aliasing, restarting services and test without , > > I then restarted postfix, rebuilt the postfix aliases (command > ''newaliases'') > and rebuilt the mailman aliases (command ''mailman aliases''), > even tried with space-separation instead of coma-separation [6], > testet again with same result. > > > D. empty /opt/mailman/mm/var/data/postfix_lmtp > > and then i just found out that my postfix_lmpt file was empty > (that i believe to be the the place from where the hastables take their > input). > > > Questions: > > 1. could somebody suggest a way, an entry should occur in postfix_lmtp? > 2. What would be the appropriate order to manually generate aliases? > first: postfix-command ''newaliases'' and > second: mailman-command ''mailman aliases'' > or reverse? > 3. finding traces [7] of a file called postfix.cfg > i can't find it (anymore) in the official installation instructions. > Is that file (still?) necessary regarding: > 3.1 parameter for default lookup table type > 3.2 pointing to command ''postmap'' > 4. to what user should the command ''postmap'' be available [8]? > > > Any pointer to manuals or examples i may have missed or ideas > on any of those 4 questions would be greatly appreciated. > There is just one definitive manual: https://docs.mailman3.org/en/latest/install/virtualenv.html If this is NOT what you followed, then my suggestion is you start over afresh and follow the steps without skipping anything. You can test Mailman3+Postfix with a phony domain name. As long as the domain name is local, deliveries to the list should happen. Try and apply the KISS principle. For instance, you could submit a post to Mailman by: echo "This is a test post" | mail -s " Testing ML Delivery" listname@phony-domain-name If submitted from an address you have subscribed to the list, you should see it in the archives of that list. Otherwise, you can see it in Postorius under held messages. The transaction details will be in mailman.log as well as your Postfix logfile. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

7 months, 2 weeks

MM3 Postfix FROM header issue

by Stephen J. Turnbull

eboltz(a)lhtservices.com writes: > When I check the /var/log/mail.log without the > sender_canonical_maps setting enabled, The meaning of "canonical" here is that this is the original and universally acceptable accept-no-substitutes-or-aliases version of the sender's address. If you don't want to see it *literally everywhere* in the header of a message coming out of Postfix, you shouldn't put it in a canonical_map. > then the initial email sender is either rejected because 'Recipient > address rejected: User unknown in virtual alias table' Postfix is configured to relay only local senders to anywhere, or remote senders to local recipients and to relay_domains. This means that the list address doesn't look like a local address (I think it's a bad idea to set myhostname=localhost!) and it isn't in relay_domains (not sure why that might be if the postfix_domains file is present as a compiled .db), so the last try is virtual address (Postfix's way of delivering a possibly remote recipient address to a local recipient). You should use postconf to check that all of the my* variables are set sanely. > or '550-From header sender domain not verified (example.com) > 550-On your sending Verified senders page > 550 verify the sender domain or email to be allowed to send' Not sure where the "example.com" is coming from. If that is being set by the remote smtpd (smtp2go?), and isn't a hard-coded string, something's wrong either with your Postfix configuration or your test email -- that should be the envelope sender domain, which should be your host. The example.com domain actually exists, and I'm sure it doesn't allow you to send email! As others mention, you probably need to have a valid SPF record in your DNS for your host as well. > Here is my main.cf setup Check that both the .txt (produced by Mailman) and .db (produced by /usr/sbin/postmap) files exist for the postfix_lmtp and postfix_domains maps. The function that produces the .txt source is supposed to call postmap to generate the compiled .db database, you shouldn't need to do it by hand. But that's the only Mailman-specific reason for the "not in virtual address table" message. Postfix itself only looks at the .db file, it will not compile or even read the .txt. > transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp > local_recipient_maps = hash:/var/lib/mailman3/data/postfix_lmtp > relay_domains = hash:/var/lib/mailman3/data/postfix_domains Make sure there are no Mailman mailing lists in the aliases file. > alias_maps = hash:/etc/aliases > alias_database = hash:/etc/aliases As mentioned, this is not a good idea: > myhostname = localhost Steve

1 year, 11 months

Re: mail for lists.ccalternatives.org loops back to myself, then Recipient address rejected

by Stephen J. Turnbull

Christian Stalberg via Mailman-users writes: > Main.cf had > > transport_maps = > hash:/opt/mailman/mm/var/data/postfix_lmtp > local_recipient_maps = > hash:/opt/mailman/mm/var/data/postfix_lmtp > relay_domains = > hash:/opt/mailman/mm/var/data/postfix_domains This configuration produced the error message: /etc/postfix/main.cf and restarted Postfix -Now a new error message: <Deepadaptation(a)lists.ccalternatives.org>: host lists.ccalternatives.org[192.46.218.224] said: 550 5.1.1 <Deepadaptation(a)lists.ccalternatives.org>: Recipient address rejected: User unknown in local recipient table (in reply to RCPT TO command) Is that correct? > I then changed local_recipient_maps to > > transport_maps = > hash:/opt/mailman/mm/var/data/postfix_lmtp > local_recipient_maps = proxy:unix:passwd.byname $alias_maps > hash:/opt/mailman/mm/var/data/postfix_lmtp > relay_domains = > hash:/opt/mailman/mm/var/data/postfix_domains And this produces the same error, is that correct? I don't think this can affect the Mailman lists, because there should be no configuration related to them in proxy:unix:passwd.byname or $alias_maps. If you don't need them for non-Mailman processing, don't add them. > I then restarted postfix & mailman. When sending a message to the list I am > still getting the same error I had before The problem seems to be that the "Deepadaptation" list addresses are not in the postfix_lmtp file. Try 1. run the "mailman aliases" command, then 2. run the "postmap" command. These are usually run automatically, but it is the first thing to try if you have having this kind of trouble. The second thing, maybe you have to get the spelling (including upper/lower case) exactly right on the list name. Is the Deepadaptation list's mailbox spelled exactly "Deepadaptation" with exactly those upper- and lowercase letters in your Mailman list configuration? (Case differences are very unlikely to be the problem, however.)

3 years, 5 months

Confirmation email bounces because of listname+something@example.com

by thor.rustad＠gmail.com

I'm sure this is a small configuration error, but I have followed the instructions for mailman3 and postfix. Basically mailman works fine, but confirmation emails, when answered by the subscriber or would-be subscriber, fails because 'listname' (after the '+something' is stripped off) is not a local user. Also see my post to the postfix group: http://postfix.1071664.n5.nabble.com/address-extension-fails-for-mailman-td…. Mind you, the postfix local_recipient_maps=regexp:/path/postfix_lmtp will correctly match any of the lists, but once the <+something> is added to the listname, it fails. Note that I have configured a subdomain, klubb.domain.com, for my mailing lists. First, my postfix.cf: recipient_delimiter = + smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu) biff = no append_dot_mydomain = no readme_directory = no smtpd_tls_cert_file=/etc/letsencrypt/live/mailer.example.com/cert.pem smtpd_tls_key_file=/etc/letsencrypt/live/mailer.example.com/privkey.pem smtpd_use_tls=yes smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache smtpd_helo_restrictions = permit_mynetworks, permit_sasl_authenticated smtpd_sender_restrictions = permit_mynetworks, reject_non_fqdn_sender, reject_unknown_sender_domain smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, smtpd_tls_security_level = may smtp_tls_security_level = may smtp_tls_loglevel = 2 smtpd_tls_loglevel = 2 smtpd_relay_restrictions = permit_mynetworks, permit_sasl_authenticated, defer_unauth_destination mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 172.19.199.0/24 <public.ip>/32 myhostname = mailer.example.com mydomain = example.com alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases myorigin = mailer.example.com mydestination = klubb.$mydomain, localhost.$mydomain, localhost, $myhostname, $mydomain relayhost = mailbox_size_limit = 0 inet_interfaces = all inet_protocols = all compatibility_level = 2 transport_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp local_recipient_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp relay_domains = regexp:/opt/mailman/core/var/data/postfix_domains unknown_local_recipient_reject_code = 550 owner_request_special = no propagate_unmatched_extensions = canonical, virtual, alias, forward, include Here is the line in postfix mail.log where the valid listname+token is rejected: NOQUEUE: reject: RCPT from mail-lf0-f43.google.com[209.85.215.43]: 550 5.1.1 <abcliste-confirm+79ecdc9fe57e086b8e1335299ef5255d156b72db(a)klubb.example.com>: Recipient address rejected: User unknown in local recipient table; from=<me(a)mydomain.com> to=<abcliste-confirm+79ecdc9fe57e086b8e1335299ef5255d156b72db(a)klubb.example.com> proto=ESMTP helo=<mail-lf0-f43.google.com> Any help will be appreciated.

8 years, 2 months

Confirmation email bounces because of listname+something@example.com

by Thor Atle Rustad

I'm sure this is a small configuration error, but I have followed the instructions for mailman3 and postfix. Basically mailman works fine, but confirmation emails, when answered by the subscriber or would-be subscriber, fails because 'listname' (after the '+something' is stripped off) is not a local user. Also see my post to the postfix group: http://postfix.1071664.n5.nabble.com/address-extension-fails-for-mailman-td… . Mind you, the postfix local_recipient_maps=regexp:/path/postfix_lmtp will correctly match any of the lists, but once the <+something> is added to the listname, it fails. Note that I have configured a subdomain, klubb.domain.com, for my mailing lists. First, my postfix.cf: recipient_delimiter = + smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu) biff = no append_dot_mydomain = no readme_directory = no smtpd_tls_cert_file=/etc/letsencrypt/live/mailer.example.com/cert.pem smtpd_tls_key_file=/etc/letsencrypt/live/mailer.example.com/privkey.pem smtpd_use_tls=yes smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache smtpd_helo_restrictions = permit_mynetworks, permit_sasl_authenticated smtpd_sender_restrictions = permit_mynetworks, reject_non_fqdn_sender, reject_unknown_sender_domain smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, smtpd_tls_security_level = may smtp_tls_security_level = may smtp_tls_loglevel = 2 smtpd_tls_loglevel = 2 smtpd_relay_restrictions = permit_mynetworks, permit_sasl_authenticated, defer_unauth_destination mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 172.19.199.0/24 <public.ip>/32 myhostname = mailer.example.com mydomain = example.com alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases myorigin = mailer.example.com mydestination = klubb.$mydomain, localhost.$mydomain, localhost, $myhostname, $mydomain relayhost = mailbox_size_limit = 0 inet_interfaces = all inet_protocols = all compatibility_level = 2 transport_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp local_recipient_maps = regexp:/opt/mailman/core/var/data/postfix_lmtp relay_domains = regexp:/opt/mailman/core/var/data/postfix_domains unknown_local_recipient_reject_code = 550 owner_request_special = no propagate_unmatched_extensions = canonical, virtual, alias, forward, include Here is the line in postfix mail.log where the valid listname+token is rejected: NOQUEUE: reject: RCPT from mail-lf0-f43.google.com[209.85.215.43]: 550 5.1.1 < abcliste-confirm+79ecdc9fe57e086b8e1335299ef5255d156b72db(a)klubb.example.com>: Recipient address rejected: User unknown in local recipient table; from=< me(a)mydomain.com> to=< abcliste-confirm+79ecdc9fe57e086b8e1335299ef5255d156b72db(a)klubb.example.com> proto=ESMTP helo=<mail-lf0-f43.google.com> Any help will be appreciated. Thor

8 years, 2 months

Re: Newbie question 2: Rewriting issue for bounced emails

by William Oliver

On Sat, 2021-12-25 at 13:34 -0800, Mark Sapiro wrote: > On 12/25/21 12:42 PM, William Oliver wrote: > > > > Is there a "make-the-freaking-virtual- map-database" command in > > mailman3, or is this postfix thing? Should I just touch the thing > > and > > create an empty file? I'm a little scared to... The error message > > makes me think that it should be populated with something... > > > Did you add an Alias Domain (different from the Mail Host domain) to > the > entry for your domain? This is what triggers the creation of > postfix_vmap. > Well, I hope youi had/have/will have a great holiday. I just finished our dinner and I am now amusing myself by pretending to enjoy the Hallmark movies my wife is watching and debugging my mailman3 installation when she's not looking. It was either "The twelve cats of Christmas" or "Die Hard." I put my foot down and said we were watching Die Hard. So of course we are watching a movie about 12 kittens in a fire truck. In any case, I added a line for "virtual_alias_domains" in my main.cf for postfix. But it doesn't do anything, apparently, except generate another error line (see the syslog output below). So, just for a lark, I created an empty /opt/mailman/mm/var/data/postfix_vmap file and ran postmap on it to create a postfix_vmap.db file. Now, it no longer complains about there not being a postfix_vmap.db file. Instead it complains about it being empty. Here's what my mailmanweb.log has to say: smtplib.SMTPRecipientsRefused: {'redacted(a)libertyfp.org': (550, b'5.1.1 <redacted(a)libertyfp.org>: Recipient address rejected: User unknown in virtual alias table')} I redacted the name because this is supposed to be the admin account -- and it fails on login. So, here's syslog: Dec 25 19:08:49 libertyfp postfix/smtpd[44664]: connect from localhost[::1] Dec 25 19:08:49 libertyfp postfix/trivial-rewrite[44670]: warning: do not list domain libertyfp.org in BOTH virtual_alias_domains and virtual_mailbox_domains Dec 25 19:08:49 libertyfp postfix/trivial-rewrite[44670]: warning: do not list domain libertyfp.org in BOTH virtual_alias_domains and virtual_mailbox_domains Dec 25 19:08:49 libertyfp postfix/smtpd[44664]: NOQUEUE: reject: RCPT from localhost[::1]: 550 5.1.1 <redacted(a)libertyfp.org>: Recipient address rejected: User unknown in virtual alias table; from=<redacted2(a)libertyfp.org> to=<redacted(a)libertyfp.org> proto=ESMTP helo=<mail.libertyfp.org> Dec 25 19:08:49 libertyfp postfix/smtpd[44672]: connect from localhost[::1] Dec 25 19:08:49 libertyfp postfix/trivial-rewrite[44670]: warning: do not list domain libertyfp.org in BOTH virtual_alias_domains and virtual_mailbox_domains Dec 25 19:08:49 libertyfp postfix/smtpd[44672]: NOQUEUE: reject: RCPT from localhost[::1]: 550 5.1.1 <redacted(a)libertyfp.org>: Recipient address rejected: User unknown in virtual alias table; from=<root(a)localhost.local> to=<redacted(a)libertyfp.org> proto=ESMTP helo=<mail.libertyfp.org> Dec 25 19:08:49 libertyfp postfix/smtpd[44672]: disconnect from localhost[::1] ehlo=1 auth=1 mail=1 rcpt=0/1 rset=1 quit=1 commands=5/6 where "redacted2" is the name in settings.py for EMAIL_HOST_USER and DEFAULT_FROM_EMAIL and "redacted" is the address for "Mailman Suite Admin" I don't know where "root(a)localhost.local" comes from. OK, it didn't work when I just had virtual_mailbox_domains defined, and it didn't work when I had both defined, so I commented out virtual_mailbox_domains and just left virtual_alias_domains. That didn't help, either, though it got rid of the warnings in syslog: Dec 25 19:43:33 libertyfp postfix/smtpd[55192]: connect from localhost[::1] Dec 25 19:43:33 libertyfp postfix/smtpd[55192]: NOQUEUE: reject: RCPT from localhost[::1]: 550 5.1.1 <redacted(a)libertyfp.org>: Recipient address rejected: User unknown in virtual alias table; from=<redacted2(a)libertyfp.org> to=<redacted(a)libertyfp.org> proto=ESMTP helo=<mail.libertyfp.org> Dec 25 19:43:34 libertyfp postfix/smtpd[55199]: connect from localhost[::1] Dec 25 19:43:34 libertyfp postfix/smtpd[55199]: NOQUEUE: reject: RCPT from localhost[::1]: 550 5.1.1 <redacted(a)libertyfp.org>: Recipient address rejected: User unknown in virtual alias table; from=<root(a)localhost.local> to=<reacted(a)libertyfp.org> proto=ESMTP helo=<mail.libertyfp.org> Dec 25 19:43:34 libertyfp postfix/smtpd[55199]: disconnect from localhost[::1] ehlo=1 auth=1 mail=1 rcpt=0/1 rset=1 quit=1 commands=5/6 Here's my postfix configuration: alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases always_add_missing_headers = yes command_directory = /usr/sbin compatibility_level = 2 daemon_directory = /usr/lib/postfix/sbin data_directory = /var/lib/postfix debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin ddd $daemon_directory/$process_name $process_id & sleep 5 default_destination_concurrency_limit = 15 default_destination_recipient_limit = 30 header_checks = regexp:/etc/postfix/header_checks home_mailbox = Maildir/ inet_interfaces = all inet_protocols = all local_recipient_maps = proxy:unix:passwd.byname $alias_maps hash:/opt/mailman/mm/var/data/postfix_lmtp mail_owner = postfix mailq_path = /usr/bin/mailq mydomain = libertyfp.org myhostname = mail.libertyfp.org mynetworks = 127.0.0.0/8 10.0.0.0/24 mynetworks_style = host myorigin = $mydomain newaliases_path = /usr/bin/newaliases owner_request_special = no relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains sendmail_path = /usr/sbin/postfix smtp_tls_mandatory_protocols = !SSLv2, !SSLv3 smtpd_banner = $myhostname ESMTP smtpd_recipient_restrictions = permit_mynetworks, permit_auth_destination, permit_sasl_authenticated, reject smtpd_sasl_auth_enable = yes smtpd_sasl_local_domain = $myhostname smtpd_sasl_path = private/auth smtpd_sasl_security_options = noanonymous smtpd_sasl_type = dovecot smtpd_tls_cert_file = /etc/letsencrypt/live/libertyfp.org/fullchain.pem smtpd_tls_key_file = /etc/letsencrypt/live/libertyfp.org/privkey.pem smtpd_tls_mandatory_protocols = !SSLv2, !SSLv3 smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache smtpd_use_tls = yes transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp unknown_local_recipient_reject_code = 550 virtual_alias_domains = libertyfp.org virtual_alias_maps = hash:/opt/mailman/mm/var/data/postfix_vmap virtual_gid_maps = static:20000 virtual_mailbox_base = /home/vmail virtual_mailbox_maps = hash:/etc/postfix/virtual-mailbox virtual_uid_maps = static:20000 Here's my settings.py: # Mailman Web configuration file. # /etc/mailman3/settings.py from mailman_web.settings.base import * from mailman_web.settings.mailman import * #: Default list of admins who receive the emails from error logging. ADMINS = ( ('Mailman Suite Admin', 'redacted2(a)libertyfp.org'), ) # Postgresql database setup. DATABASES = { 'default': { 'ENGINE': 'django.db.backends.postgresql_psycopg2', 'NAME': 'mailman', 'USER': 'mailman', # TODO: Replace this with the password. 'PASSWORD': 'passwd', 'HOST': 'localhost', 'PORT': '5432', } } # 'collectstatic' command will copy all the static files here. # Alias this location from your webserver to `/static` STATIC_ROOT = '/opt/mailman/web/static' # Make sure that this directory is created or Django will fail on start. LOGGING['handlers']['file']['filename'] = '/opt/mailman/web/logs/mailmanweb.log' #: See https://docs.djangoproject.com/en/dev/ref/settings/#allowed-hosts ALLOWED_HOSTS = [ "localhost", # Archiving API from Mailman, keep it. "www.libertyfp.org", "libertyfp.org", "mail.libertyfp.org", "list.libertyfp.org", "127.0.0.1", "2.56.57.28" # "lists.your-domain.org", # Add here all production domains you have. ] #: Current Django Site being served. This is used to customize the web host #: being used to serve the current website. For more details about Django #: site, see: https://docs.djangoproject.com/en/dev/ref/contrib/sites/ SITE_ID = 1 # Set this to a new secret value. SECRET_KEY = 'passwd' # Set this to match the api_key setting in # /opt/mailman/mm/mailman-hyperkitty.cfg (quoted here, not there). MAILMAN_ARCHIVER_KEY = 'passwd' HAYSTACK_CONNECTIONS = { 'default': { 'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', 'PATH': os.path.join(BASE_DIR, "fulltext_index"), }, } # To be added to Django's settings.py EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'localhost' EMAIL_PORT = 25 EMAIL_HOST_USER = 'redacted(a)libertyfp.org' EMAIL_HOST_PASSWORD = 'passwd' DEFAULT_FROM_EMAIL = 'redacted2(a)libertyfp.org' SITE_ID = 2 Here's my mailman.cfg: /etc/mailman3/mailman.cfg [paths.here] var_dir: /opt/mailman/mm/var [mailman] layout: here # This address is the "site owner" address. Certain messages which must be # delivered to a human, but which can't be delivered to a list owner (e.g. a # bounce from a list owner), will be sent to this address. It should point to # a human. site_owner: redacted(a)libertyfp.org [database] class: mailman.database.postgresql.PostgreSQLDatabase url: postgres://redacted2:passwd@localhost/mailman [archiver.prototype] enable: yes # For the HyperKitty archiver. [archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /opt/mailman/mm/mailman-hyperkitty.cfg # And, create the /opt/mailman/mm/mailman-hyperkitty.cfg file containing # these settings uncommented #[general] #base_url: http://127.0.0.1:8000/archives/ #api_key: Secret_Hyperkitty_API_Key [shell] history_file: $var_dir/history.py [shell] history_file: $var_dir/history.py [mta] verp_confirmations: yes verp_personalized_deliveries: yes verp_delivery_interval: 1 incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: mail.libertyfp.org lmtp_port: 8024 smtp_host: mail.libertyfp.org smtp_port: 25 configuration: python:mailman.config.postfix recipient_delimiter = + unknown_local_recipient_reject_code = 550 owner_request_special = no Here's uwsgi.ini # /etc/mailman3/uwsgi.ini # [uwsgi] # Port on which uwsgi will be listening. #http-socket = 127.0.0.1:8000 http-socket = 0.0.0.0:8000 # If running uwsgi from the virtual environment ... virtualenv = /opt/mailman/venv/ module=mailman_web.wsgi:application # Add to python import path. pythonpath = /etc/mailman3/ # The default settings module. env = DJANGO_SETTINGS_MODULE=settings # Setup default number of processes and threads per process. master = true processes = 2 threads = 2 # Setup the django_q related worker processes. attach-daemon = /opt/mailman/venv/bin/mailman-web qcluster # Setup the request log. req-logger = file:/opt/mailman/web/logs/uwsgi.log # Log qcluster commands separately. logger = qcluster file:/opt/mailman/web/logs/uwsgi-qcluster.log log-route = qcluster uwsgi-daemons # Last log and it logs the rest of the stuff. logger = file:/opt/mailman/web/logs/uwsgi-error.log And, last but not least here's mailman-hyperkitty.cfg: [general] base_url: http://127.0.0.1:8000/archives/ api_key: passwd

3 years, 11 months

Re: Held messages not delivered after approval

by Stephen J. Turnbull

Krinetzki, Stephan writes: > Now in the mailman.log I see the HOLD messages and the approved > messages. The smtp.log logs just the incoming Mail, which seems to > be fine. By that you mean the incoming mail is fine? Or smtp.log is fine? smtp.log should include two (or more) lines for each successful post, like Jan 02 16:09:17 2025 (42985) <43007@turnbull> smtp to list-1(a)turnbull.jp for 1 recips, completed in 0.6027507781982422 seconds Jan 02 16:09:17 2025 (42985) <43007@turnbull> post to list-1(a)turnbull.jp from list-1-owner(a)turnbull.jp, 992 bytes, 1 failures Jan 02 16:09:17 2025 (42985) <43007@turnbull> delivery to list-1-owner(a)turnbull.jp failed with code 550, b'5.1.1 <list-1-owner(a)turnbull.jp>: Recipient address rejected: User unknown in local recipient table' (That last line shows an example of a failure report.) > Aug 05 10:21:05 2025 (217986) Cannot connect to SMTP server localhost on port 25 Postfix for some reason doesn't know about the alias "localhost" (it has something to do with trusting the DNS and not reading the /etc/hosts file). 127.0.0.1 works. I don't understand how any lists' posts get delivered at all with that. If it's postfix it's possible that the connection pool is exhausted intermittently (but that wouldn't explain why it's consistently impossible to post to a subset of lists). You can specify that connections from the loopback interfaces are less restricted. That might help. > Even after changing the smtp_host in mailman.cfg this error appears > randomly. Note that > Sadly the mail does not get delivered. :-( -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

4 months

OK, so I backed out completely and re-installed. Here's my *original* error. Should I modify virtual mailbox maps?

by Bill Oliver

OK, I think I was clearly in the phase of dealing with errors caused by my attempts to deal with previous errors. So I backed out and did a clean install. Again, the installl seemed to go without a problem. Then: 1) I set up a mailinglist (tradfp(a)forensicpath.us) for "old school" forensic pathologists to discuss cases. 2) I added a couple of users: oliver(a)billoblog.com on the same box as the mailinglist, though on different virtual domains, and william.oliver(a)knoxcounty.org, a local government domain not associated with my box. Results: The welcome message did not get delivered to either address. When I send email from those addresses to tradfp(a)forensicpath.us, I get the following error from both: Your message couldn't be delivered The message you sent to tradfp(a)forensicpath.us couldn't be delivered due to: Recipient email address is possibly incorrect. Further information 5.1.1 <tradfp(a)forensicpath.us>: Recipient address rejected: User unknown in virtual mailbox table If you sent this message to multiple addresses, you'll receive a notification like this for every one that didn't arrive. That is when I started going down the dovecot rabbit hole. Here's the (what I think is relevant) part of the mail.cf file: virtual_mailbox_domains = proxy:mysql:/etc/postfix/sql/mysql_virtual_domains_maps.cf virtual_mailbox_maps = proxy:mysql:/etc/postfix/sql/mysql_virtual_mailbox_maps.cf, proxy:mysql:/etc/postfix/sql/mysql_virtual_alias_domain_mailbox_maps.cf virtual_alias_maps = proxy:mysql:/etc/postfix/sql/mysql_virtual_alias_maps.cf, proxy:mysql:/etc/postfix/sql/mysql_virtual_alias_domain_maps.cf, proxy:mysql:/etc/postfix/sql/mysql_virtual_alias_domain_catchall_maps.c f virtual_mailbox_base = /var/vmail virtual_minimum_uid = 900 virtual_uid_maps = static:900 virtual_gid_maps = static:900 transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp local_recipient_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains In my previous attempt, I added hash:/opt/mailman/mm/var/data/postfix_lmtp to both virtual_mailbox_maps and virtual_alias_maps, but I haven't done that yet here. I thought I'd ask and make sure I should. Should that be my next step? Thanks, billo

1 year, 1 month

Mailman-users search results for query "user unknown in local recipient table"