On Sat, 2021-12-25 at 11:55 -0500, William Oliver wrote:

Another data point.  When Ichange the port number in mailman.cfg, the error changes to reflect it.  When I change the port to 8055, I get:

The mail system

<"lmtp:[mail.libertyfp.org]:8055"@libertyfp.org> (expanded from <fplist@libertyfp.org>): unknown user: "lmtp:[mail.libertyfp.org]:8055@libertyfp.org"

Also, mail works fine outside of the mailing list.

On Sat, 2021-12-25 at 10:29 -0800, Mark Sapiro wrote:

This is the issue.

See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.ht... for information on configuring Postfix with mailing lists in a virtual domain.

Thanks, at least that changed the error  :-)

Clearly that was the problem, but it uncovered a new one -- the mailman vmap doesn't seem to be created.  In the installation docs, it says about /opt/mailman/mm/data/postfix_vmap:

 "If this is done and the configured MTA is Postfix, Mailman will create an additional /path-to-mailman/var/data/postfix_vmap file with mappings from the example.com addresses to the corresponding addresses in the alias_domain and will use the alias_domain in the other files. "

But, alas, I get a "temporary lookup failure" which isn't all that helpful.  However, if I wander over to /var/logs/syslog, I see:

Dec 25 15:18:23 libertyfp postfix/smtpd[20248]: error: open database /opt/mailman/mm/var/data/postfix_vmap.db: No such file or directory Dec 25 15:18:23 libertyfp postfix/smtpd[20248]: connect from localhost[::1] Dec 25 15:18:23 libertyfp postfix/trivial-rewrite[20252]: error: open database /opt/mailman/mm/var/data/postfix_vmap.db: No such file or directory Dec 25 15:18:23 libertyfp postfix/trivial-rewrite[20252]: warning: hash:/opt/mailman/mm/var/data/postfix_vmap is unavailable. open database /opt/mailman/mm/var/data/postfix_vmap.db: No such file or directory Dec 25 15:18:23 libertyfp postfix/trivial-rewrite[20252]: warning: virtual_alias_domains: hash:/opt/mailman/mm/var/data/postfix_vmap: table lookup problem Dec 25 15:18:23 libertyfp postfix/trivial-rewrite[20252]: warning: virtual_alias_domains lookup failure Dec 25 15:18:23 libertyfp postfix/trivial-rewrite[20252]: warning: hash:/opt/mailman/mm/var/data/postfix_vmap is unavailable. open database /opt/mailman/mm/var/data/postfix_vmap.db: No such file or directory Dec 25 15:18:23 libertyfp postfix/trivial-rewrite[20252]: warning: virtual_alias_domains: hash:/opt/mailman/mm/var/data/postfix_vmap: table lookup problem Dec 25 15:18:23 libertyfp postfix/trivial-rewrite[20252]: warning: virtual_alias_domains lookup failure Dec 25 15:18:23 libertyfp postfix/smtpd[20248]: NOQUEUE: reject: RCPT from localhost[::1]: 451 4.3.0 <billo@billoblog.com>: Temporary lookup failure; from=<mailman@libertyfp.org> to=<billo@billoblog.com> proto=ESMTP helo=<mail.libertyfp.org> Dec 25 15:18:23 libertyfp postfix/smtpd[20254]: error: open database /opt/mailman/mm/var/data/postfix_vmap.db: No such file or directory

and on and on.  This looks like a clue to me -- that mailman3 did not automagically make postfix_vmap.db.   

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...

Sigh.  That's enough for today.  I'm off to eat Christmas turkey.

Thanks for all your help this morning.

billo

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@libertyfp.org': (550, b'5.1.1 <redacted@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@libertyfp.org>: Recipient address rejected: User unknown in virtual alias table; from=<redacted2@libertyfp.org> to=<redacted@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@libertyfp.org>: Recipient address rejected: User unknown in virtual alias table; from=<root@localhost.local> to=<redacted@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@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@libertyfp.org>: Recipient address rejected: User unknown in virtual alias table; from=<redacted2@libertyfp.org> to=<redacted@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@libertyfp.org>: Recipient address rejected: User unknown in virtual alias table; from=<root@localhost.local> to=<reacted@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@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@libertyfp.org' EMAIL_HOST_PASSWORD = 'passwd'

DEFAULT_FROM_EMAIL = 'redacted2@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@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

On Sat, 2021-12-25 at 21:32 -0800, Mark Sapiro wrote:

Have you added an Alias Domain for your domain?

After doing that did you run mailman aliases or restart mailman to (re)generate the files.

postfix_domains     postfix_lmtp     postfix_vmap postfix_domains.db  postfix_lmtp.db  postfix_vmap.db

--

First, thanks for your patience. Two steps forward and one step back, here. I  have the interface running and I can create a list which *does* send messages to my test recipients.

To answer your question, yes, I did all that, and that generates postfix_domains and postfix_lmtp, but not postfix_vmap.   Here's what I got:

$more postfix_domains # AUTOMATICALLY GENERATED BY MAILMAN ON 2021-12-26 22:29:27 # # This file is generated by Mailman, and is kept in sync with the binary hash # file. YOU SHOULD NOT MANUALLY EDIT THIS FILE unless you know what you're # doing, and can keep the two files properly in sync. If you screw it up, # you're on your own.

libertyfp.org libertyfp.org

$more postfix_lmtp # AUTOMATICALLY GENERATED BY MAILMAN ON 2021-12-26 22:29:27 # # This file is generated by Mailman, and is kept in sync with the binary hash # file. YOU SHOULD NOT MANUALLY EDIT THIS FILE unless you know what you're # doing, and can keep the two files properly in sync. If you screw it up, # you're on your own. # Aliases which are visible only in the @libertyfp.org domain. testlist@libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-bounces@libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-confirm@libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-join@libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-leave@libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-owner@libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-request@libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-subscribe@libertyfp.org lmtp:[mail.libertyfp.org]:8024 testlist-unsubscribe@libertyfp.org lmtp:[mail.libertyfp.org]:8024

But no postfix_vmap.

However, let me ask another question first:

When running mailman3, do I need to set up a completely different virtual domain for it to run in?  My "real" domain name is libertyfp.org, and I'm trying to make mailman work on that domain, e.g. "testlist@libertyfp.org."  I'm starting to get the idea that I need to stick a completely different domain in there for the mailinglist. Which I can do -- I've got another two or three domain names to play with.  Is it a problem to run the mailinglist on the same domain that the machine sits on for its regular business?  A lot of the errors I'm getting seem to be from trying to do regular mail *and* the mailinglist on the same domain.

Now that I've installed all this stuff a couple of times, I can easily re-install for a second virtual domain, if that's what I should be doing.

But, on to what's not working now...

Unfortunately, I seem to have completely screwed the pooch on getting postfix/dovecot to play nicely with respect to *receiving* mail.

First, adding "virtual_alias_domains" (and putting libertyfp.org in it) and commenting out "virtual_mailbox_domains" resulted in postfix ignoring all my virtual mailboxes.  Mail still worked, but mail is now being sent to /home/<user>/Maildir instead of /home/vmail/libertyfp/<user>/Maildir -- which means that dovecot, which looks in the virtual mailboxes, is now unaware of new mail.  I suppose I could link /home/<user>/Maildir to /home/vmail/libertyfp.org/<user>/Maildir, but I suspect there will be problems and it's not a real fix.  But.. .a problem for another day.

Except...  the same thing is happening with the mailinglist.

In mailman3:

I set up a test list (testlist@libertyfp.org) and added two test users (one local and one on a different domain). They added just fine, and both received the welcome message.

However, when I replied, both messages bounced with the error that "testlist@libertyfp.org" was "user unknown in virtual alias table."

No problem, I thought. So I added:

testlist@libertyfp.org testlist

to /etc/postfix/virtual, and

testlist libertyfp.org/testlist/Maildir

to /etc/postfix/virtual-mailbox,

and I added testlist as a user:

$ adduser -m testlist

So, now mail from my list members goes to /home/testlist/Maildir, but not to the mailinglist.

I also have managed to get another *different* warning, and the "there ain't no vmap, newbie" error as well:

Dec 26 17:33:11 libertyfp systemd[1]: certbot.service: Consumed 1.041s CPU time. Dec 26 17:33:12 libertyfp postfix/smtpd[46453]: error: open database /opt/mailman/mm/var/data/postfix_vmap.db: No such file or directory Dec 26 17:33:12 libertyfp postfix/smtpd[46453]: error: unsupported dictionary type: #hash Dec 26 17:33:12 libertyfp postfix/smtpd[46453]: connect from billoblog.com[162.144.108.19] Dec 26 17:33:16 libertyfp postfix/trivial-rewrite[46479]: warning: do not list domain libertyfp.org in BOTH virtual_alias_domains and relay_domains Dec 26 17:33:16 libertyfp postfix/smtpd[46453]: warning: hash:/opt/mailman/mm/var/data/postfix_vmap is unavailable. open database /opt/mailman/mm/var/data/postfix_vmap.db: No such file or directory Dec 26 17:33:16 libertyfp postfix/smtpd[46453]: warning: hash:/opt/mailman/mm/var/data/postfix_vmap lookup error for "fplist@libertyfp.org" Dec 26 17:33:16 libertyfp postfix/smtpd[46453]: NOQUEUE: reject: RCPT from billoblog.com[162.144.108.19]: 451 4.3.0 <fplist@libertyfp.org>: Temporary lookup failure; from=<billo@billoblog.com> to=<fplist@libertyfp.org> proto=ESMTP helo=<billoblog.com>

That "you can't have both virtual_alias_domains" and "relay_domains" seems like it should be a clue.  But I don't' know what for.   Adding virtual_alias_domains really changed things...

Anyway, here's the part of the /etc/postfix/main.cf that I think is likely important.  Note that I comments out "virtual_mailbox_domains".

myorigin = localhost

mydestination = localhost, localhost.$mydomain alias_maps = /etc/aliases (which, by the way, just contains "postmaster:  root") home_mailbox= Maildir

# add to the end (add ssl support) smtpd_use_tls = yes smtp_tls_mandatory_protocols = !SSLv2, !SSLv3 smtpd_tls_mandatory_protocols = !SSLv2, !SSLv3 smtpd_tls_cert_file = /etc/letsencrypt/live/libertyfp.org/fullchain.pem smtpd_tls_key_file = /etc/letsencrypt/live/libertyfp.org/privkey.pem smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache

# add to the end (add virtual users) # if specify multiple domains, specify comma or space separated #virtual_mailbox_domains = libertyfp.org virtual_mailbox_base = /home/vmail virtual_mailbox_maps = hash:/etc/postfix/virtual-mailbox virtual_uid_maps = static:20000 virtual_gid_maps = static:20000

# mailman3 changes

owner_request_special = no always_add_missing_headers = yes 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 default_destination_recipient_limit = 30 default_destination_concurrency_limit = 15 virtual_alias_domains = hash:/etc/postfix/domains virtual_alias_maps = hash:/opt/mailman/mm/var/data/postfix_vmap #hash:/etc/postfix/virtual

Here's the postfix maps:

/etc/postfix/domains:

libertyfp.org   #

/etc/postfix/virtual:

fp145@libertyfp.org fp145 mailman@libertyfp.org mailman testlist@libertyfp.org testlist

/etc/postfix/virtual-mailbox:

mailman libertyfp.org/mailadmin/Maildir/ fp145@localhost libertyfp.org/fp145/Maildir/ testlist libertyfp.org/testlist/Maildir

On Sun, 2021-12-26 at 16:47 -0800, Mark Sapiro wrote:

On 12/26/21 3:06 PM, William Oliver wrote:

...

When running mailman3, do I need to set up a completely different virtual domain for it to run in?

No.

...

 My "real" domain name is libertyfp.org, and I'm trying to make mailman work on that domain, e.g. "testlist@libertyfp.org."  I'm starting to get the idea that I need to stick a completely different domain in there for the mailinglist.

No.

DNS or anywhere outside your server.

Have you actually set an alias domain in Postorius for the libertyfp.org domain. It doesn't matter what name it is as long as it isn't a real domain. A good choice is x.libertyfp.org. Have you set that or things like

testlist@libertyfp.org testlist@x.libertyfp.org testlist-bounces@libertyfp.org  testlist-bounces@x.libertyfp.org testlist-confirm@libertyfp.org testlist-confirm@x.libertyfp.org ... [snip]

Ah. I misunderstood you. I thought you meant that I had to tweak *postfix* to get this done. It's not that you weren't clear, it's that when I read the mailman3 instructions, I got the impression that *mailman* would set the alias domain automatically, so I was dead set on munging postfix.

This makes more sense, and I can back out of some of the changes I made in postfix, which for the last couple of rounds was mostly flailing about randomly -- I've heard that's often not a good admin strategy.

So.. if I need to do it myself, can you point me to what file I need to create/modify in the /opt/mailman/mm tree to set up the alias?

Thanks!

billo

On 12/26/21 6:19 PM, Mark Sapiro wrote:

Otherwise, you can do this in mailman shell, e.g.

$ mailman shell

Welcome to the GNU Mailman shell
Use commit() to commit changes.
Use abort() to discard changes since the last commit.
Exit with ctrl+D does an implicit commit() but exit() does not.

 >>> dm = getUtility(IDomainManager)
 >>> d = dm.get('example.com')
 >>> d.alias_domain = x.example.com
 >>> commit()

Ooops. That should be

d.alias_domain = 'x.example.com'

I.e., quoted

-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

On 12/27/21 1:36 PM, William Oliver wrote:

When I send a message to the list from *any* of these three, the mailman3 accepts it and attempts to broadcast it out. It is delivered sucessfully to the local email address, but it looks like there's a relaying problem with external addresses.

In the syslog snippet below, note that the fp145@libertyfp.org mail is delivered, but the mail to the recipients at billoblog.com get an "Access denied"

...>

Dec 27 15:33:26 libertyfp postfix/smtpd[419593]: NOQUEUE: reject: RCPT from mail.libertyfp.org[2.56.57.28]: 554 5.7.1 <billo@billoblog.com>: Recipient address rejected: Access denied; from=<testlist-bounces+billo=billoblog.com@libertyfp.org> to=<billo@billoblog.com> proto=ESMTP helo=<mail.libertyfp.org>

Dec 27 15:33:26 libertyfp postfix/smtpd[419593]: disconnect from mail.libertyfp.org[2.56.57.28] ehlo=1 mail=2 rcpt=1/2 data=1 rset=1 quit=1 commands=7/8

It appears that the MX for billoblog.com is not accepting mail from your server. Can you send non-mailman mail from this server to this address? If not, you need to contact billoblog.com to fin wht they are blocking your mail.

I tried changing the smtp port in mailman.cfg to 587, but that didn't change anything.

because the issue is not in delivery from Mailman to Postfix. It is in delivery from Postfix to billoblog.com.

-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

On 12/27/21 4:05 PM, William Oliver wrote:

Again, a quick DuckDuckGo search reveals that this has come up a couple of times. It required that I modify /etc/postfix/main.cf to add the non-localhost ip4 address of the box to the mynetworks line:

mynetworks = 127.0.0.0/8 10.0.0.0/24

to

mynetworks = 127.0.0.0/8 10.0.0.0/24 2.56.57.28

I assume that means that postfix uses localhost for regular mail, but mailman3 uses the 2.56.57.28 address.

Because you set

smtp_host: mail.libertyfp.org

in mailman.cfg. If you leave the default settings

smtp_host: localhost smtp_port: 25

you won't have this issue.

-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan