On 9/30/24 14:34, jkoral@luc.edu wrote:

Mark, thank you for the quick reply. We will most likely need to migrate the lists over a period of time. So the DNS cannot be changed at the moment. Both servers have different FQDNs. Any suggestions on what we can do?

If lists on the old and new servers have the same posting address domain you have to configure the incoming MTA on the old (MM 2.1) server to relay mail for the migrated lists to the new server.

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

On 9/30/24 14:44, jkoral@luc.edu wrote:

That makes sense. Are there instructions on how to do this?

It depends on the MTA. For Postfix you probably have a set of aliases for each of the form:

mailman: "|/path/to/mail/mailman post mailman" mailman-admin: "|/path/to/mail/mailman admin mailman" mailman-bounces: "|/path/to/mail/mailman bounces mailman" mailman-confirm: "|/path/to/mail/mailman confirm mailman" mailman-join: "|/path/to/mail/mailman join mailman" mailman-leave: "|/path/to/mail/mailman leave mailman" mailman-owner: "|/path/to/mail/mailman owner mailman" mailman-request: "|/path/to/mail/mailman request mailman" mailman-subscribe: "|/path/to/mail/mailman subscribe mailman" mailman-unsubscribe: "|/path/to/mail/mailman unsubscribe mailman"

You could change these, preferably in a separate aliases file so Mailman's genaliases won't overwrite them, to

mailman: mailman@new_server mailman-admin: mailman-admin@new-server mailman-bounces: mailman-bounces@new-server mailman-confirm: mailman-confirm@new-server mailman-join: mailman-join@new-server mailman-leave: mailman-leave@new-server mailman-owner: mailman-owner@new-server mailman-request: mailman-request@new-server mailman-subscribe: mailman-subscribe@new-server mailman-unsubscribe: mailman-unsubscribe@new-server

For exim, you would need to add another Mailman router ahead of the existing one which would match only the migrated lists and specify an smtp transport which relays to the new server.

Then once we are done migrating to the new server, then we can just change the DNS, correct?

Yes

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

Or can I just put the forwarding alias in /etc/aliases?

Thank you for all your help. It seems to be attempting to forward, but I don't think the new server is receiving messages. I can send out from the server, but it is just not taking delivery. Any suggestions for what I can look at. Also, this server is behind an F5 so it has a local IP address and a Virtual IP address. The virtual IP address has the fully qualified domain name.

Not sure if this means anything. This is the log from old server after trying to send. I edited the FQDN and IP though. Any thoughts? I think it may be the configuration of postfix on the new server though.

Oct 2 22:26:59 listservls01 postfix/smtp[139911]: B1FD27ED: to=<test@listservnew.example.com>, orig_to=<olivertest@lists.luc.edu>, relay=listservnew.example.com[x.x.x.x]:25, delay=0.01, delays=0/0/0.01/0, dsn=4.4.2, status=deferred (lost connection with listservnew.example.com[x.x.x.x] while receiving the initial server greeting) Oct 2 22:26:59 listservls01 postfix/smtpd[139918]: disconnect from mail-northcentralusazon11020123.outbound.protection.outlook.com[52.101.193.123]

HI Mark, I was off for a couple days. I have a feeling postfix is misconfigured because I see that port 25 is open. The server is not receiving mail at all. Are there any tips for things I can check. The logs are not showing much because the mail doesn't seem to reach it.

The old server is trying to send, but I end up getting an undeliverable message saying no connection could be made. I know port 25 is open because I can telnet to it. I'm wondering if I'm missing something in my configuration. Can you take a look? Thank you.

Here are the active settings in /etc/postfix/master.cf: # Postfix master process configuration file. For details on the format # of the file, see the master(5) manual page (command: "man 5 master" or # on-line: http://www.postfix.org/master.5.html). # # Do not forget to execute "postfix reload" after editing this file. # # ========================================================================== # service type private unpriv chroot wakeup maxproc command + args # (yes) (yes) (no) (never) (100) # ========================================================================== smtp inet n - y - - smtpd #smtp inet n - y - 1 postscreen #smtpd pass - - y - - smtpd #dnsblog unix - - y - 0 dnsblog #tlsproxy unix - - y - 0 tlsproxy # Choose one: enable submission for loopback clients only, or for any client. #127.0.0.1:submission inet n - y - - smtpd #submission inet n - y - - smtpd # -o syslog_name=postfix/submission # -o smtpd_tls_security_level=encrypt # -o smtpd_sasl_auth_enable=yes # -o smtpd_tls_auth_only=yes # -o local_header_rewrite_clients=static:all # -o smtpd_reject_unlisted_recipient=no # Instead of specifying complex smtpd_<xxx>_restrictions here, # specify "smtpd_<xxx>_restrictions=$mua_<xxx>_restrictions" # here, and specify mua_<xxx>_restrictions in main.cf (where # "<xxx>" is "client", "helo", "sender", "relay", or "recipient"). # -o smtpd_client_restrictions= # -o smtpd_helo_restrictions= # -o smtpd_sender_restrictions= # -o smtpd_relay_restrictions= # -o smtpd_recipient_restrictions=permit_sasl_authenticated,reject # -o milter_macro_daemon_name=ORIGINATING # Choose one: enable submissions for loopback clients only, or for any client. #127.0.0.1:submissions inet n - y - - smtpd #submissions inet n - y - - smtpd # -o syslog_name=postfix/submissions # -o smtpd_tls_wrappermode=yes # -o smtpd_sasl_auth_enable=yes # -o local_header_rewrite_clients=static:all # -o smtpd_reject_unlisted_recipient=no # Instead of specifying complex smtpd_<xxx>_restrictions here, # specify "smtpd_<xxx>_restrictions=$mua_<xxx>_restrictions" # here, and specify mua_<xxx>_restrictions in main.cf (where # "<xxx>" is "client", "helo", "sender", "relay", or "recipient"). # -o smtpd_client_restrictions= # -o smtpd_helo_restrictions= # -o smtpd_sender_restrictions= # -o smtpd_relay_restrictions= # -o smtpd_recipient_restrictions=permit_sasl_authenticated,reject # -o milter_macro_daemon_name=ORIGINATING #628 inet n - y - - qmqpd pickup unix n - y 60 1 pickup cleanup unix n - y - 0 cleanup qmgr unix n - n 300 1 qmgr #qmgr unix n - n 300 1 oqmgr tlsmgr unix - - y 1000? 1 tlsmgr rewrite unix - - y - - trivial-rewrite bounce unix - - y - 0 bounce defer unix - - y - 0 bounce trace unix - - y - 0 bounce verify unix - - y - 1 verify flush unix n - y 1000? 0 flush proxymap unix - - n - - proxymap proxywrite unix - - n - 1 proxymap smtp unix - - y - - smtp relay unix - - y - - smtp -o syslog_name=postfix/$service_name # -o smtp_helo_timeout=5 -o smtp_connect_timeout=5 showq unix n - y - - showq error unix - - y - - error retry unix - - y - - error discard unix - - y - - discard local unix - n n - - local virtual unix - n n - - virtual lmtp unix - - y - - lmtp anvil unix - - y - 1 anvil scache unix - - y - 1 scache postlog unix-dgram n - n - 1 postlogd # # ==================================================================== # Interfaces to non-Postfix software. Be sure to examine the manual # pages of the non-Postfix software to find out what options it wants. # # Many of the following services use the Postfix pipe(8) delivery # agent. See the pipe(8) man page for information about ${recipient} # and other message envelope options. # ==================================================================== # # maildrop. See the Postfix MAILDROP_README file for details. # Also specify in main.cf: maildrop_destination_recipient_limit=1 # #maildrop unix - n n - - pipe # flags=DRXhu user=vmail argv=/usr/bin/maildrop -d ${recipient} # # ==================================================================== # # Recent Cyrus versions can use the existing "lmtp" master.cf entry. # # Specify in cyrus.conf: # lmtp cmd="lmtpd -a" listen="localhost:lmtp" proto=tcp4 # # Specify in main.cf one or more of the following: # mailbox_transport = lmtp:inet:localhost # virtual_transport = lmtp:inet:localhost # # ==================================================================== # # Cyrus 2.1.5 (Amos Gouaux) # Also specify in main.cf: cyrus_destination_recipient_limit=1 # #cyrus unix - n n - - pipe # flags=DRX user=cyrus argv=/cyrus/bin/deliver -e -r ${sender} -m ${extension} ${user} # # ==================================================================== # # Old example of delivery via Cyrus. # #old-cyrus unix - n n - - pipe # flags=R user=cyrus argv=/cyrus/bin/deliver -e -m ${extension} ${user} # # ==================================================================== # # See the Postfix UUCP_README file for configuration details. # uucp unix - n n - - pipe flags=Fqhu user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient) # # Other external delivery methods. # #ifmail unix - n n - - pipe # flags=F user=ftn argv=/usr/lib/ifmail/ifmail -r $nexthop ($recipient) #bsmtp unix - n n - - pipe # flags=Fq. user=bsmtp argv=/usr/lib/bsmtp/bsmtp -t$nexthop -f$sender $recipient #scalemail-backend unix - n n - 2 pipe # flags=R user=scalemail argv=/usr/lib/scalemail/bin/scalemail-store ${nexthop} ${user} ${extension} #mailman unix - n n - - pipe # flags=FRX user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py ${nexthop} ${user}

And here are the setting I have in /etc/mailman3/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: user@example.com

[database] class: mailman.database.postgresql.PostgreSQLDatabase url: postgresql://mailman:PasswordEdited@localhost/mailman

[archiver.prototype] enable: yes

# For the HyperKitty archiver. [archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /etc/mailman3/mailman-hyperkitty.cfg

[shell] history_file: $var_dir/history.py

[mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: 127.0.0.1 lmtp_port: 8024 smtp_host: localhost smtp_port: 25 configuration: python:mailman.config.postfix

On 10/10/24 1:55 PM, jkoral@luc.edu wrote:

The old server is trying to send, but I end up getting an undeliverable message saying no connection could be made. I know port 25 is open because I can telnet to it. I'm wondering if I'm missing something in my configuration. Can you take a look? Thank you.

Here are the active settings in /etc/postfix/master.cf: ... smtp inet n - y - - smtpd

This says port 25 is for smtpd and that's good.

And here are the setting I have in /etc/mailman3/mailman.cfg # /etc/mailman3/mailman.cfg

This is irrelevant as the message never gets to Mailman.

On 10/10/24 1:58 PM, jkoral@luc.edu wrote:

Here are the results from netstat:

tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 3876896/master

And Postfix master process is listening on port 25.

You say you can telnet to port 25. Can you do that from the old MM 2.1 server? Can you connect and receive the greeting and send EHLO hostname and get a good response?

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

On 11/13/24 18:44, jkoral@luc.edu wrote:

Now I am getting this error in mail.log. I have changed quite a few settings to try and not bother you anymore, but nothing seems to be working. Hopefully this will be an easy one for you. The unknown IP address is our F5 where the mail is coming through.

2024-11-13T20:31:15.988423-06:00 lstprdls01 postfix/smtpd[2261655]: connect from unknown[10.18.3.105] 2024-11-13T20:31:16.486460-06:00 lstprdls01 postfix/smtpd[2261655]: disconnect from unknown[10.18.3.105] ehlo=1 quit=1 commands=2 2024-11-13T20:31:18.246010-06:00 lstprdls01 postfix/smtpd[2261655]: connect from unknown[10.18.3.105] 2024-11-13T20:31:18.708146-06:00 lstprdls01 postfix/smtpd[2261655]: NOQUEUE: reject: RCPT from unknown[10.18.3.105]: 550 5.1.1 <joetest@listservnew.luc.edu>: Recipient address rejected: User unknown in local recipient table; from=<jkoral@luc.edu> to=<joetest@listservnew.luc.edu> proto=ESMTP helo=<CO1PR03CU002.outbound.protection.outlook.com> 2024-11-13T20:31:18.852290-06:00 lstprdls01 postfix/smtpd[2261655]: disconnect from unknown[10.18.3.105] ehlo=2 mail=1 rcpt=0/1 rset=1 quit=1 commands=5/6

What is joetest@listservnew.luc.edu? Is that a list? If so, is it mentioned in Mailman's var/data/postfix_lmtp and is that included in transport_maps and in local_recipient_maps in Postfix main.cf?

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

On 11/14/24 08:42, jkoral@luc.edu wrote:

joetest@listservnew.luc.edu is the list, but in postfix_lmtp, it is showing up as joetest@luc.edu. Where can I change that? I tried changing the domain and site, but it still has not changed.

The list has a mail_host attribute which is set when the list is created. Presumably, you created the list as joetest@luc.edu. You have to change the mail_host attribute of the list, but it may be easier to just delete it and create a new joetest@listservnew.luc.edu list. Then you can ignore everything below.

To change the mail_host for the list you can do a database query or use mailman shell.

The database query is

UPDATE mailinglist SET mail_host = 'listservnew.luc.edu' where list_name 
= 'joetest';

The `mailman shell interaction is

$ mailman shell -l joetest@luc.edu
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.
The variable 'm' is the list@example.com mailing list
 >>> m.mail_host = 'listservnew.luc.edu'
 >>> commit()

If you do either of the above to change the mail host, you probably need to do mailman aliases to regenerate the files for Postfix.

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

On 11/14/24 10:10, jkoral@luc.edu wrote:

I understand that now. I was able to delete it, re-create it and am now getting e-mails into the server. But now, it is not sending out to the e-mails that are subscribed to that list.

Will running mailman aliases fix that? Also, I don't see a mailman command, but am running mailman3 aliases. Does this process take while? It has been running for a couple minutes now.

No. mailman aliases will not affect delivery from Mailman to list members. mailman aliases should be almost instantaneous.

How did you install Mailman? If you followed our recommendations at https://docs.mailman3.org/en/latest/install/virtualenv.html there is no mailman3 command.

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

On 11/14/24 10:31, jkoral@luc.edu wrote:

Ah, you are right. I was able to run it from /opt/mailman/venv/bin/. I'm so confused on why it won't send out to the e-mail on the list now.

Look for shunted messages in Mailman's var/queue/shunt. Look for error messages in Mailman's var/logs/mailman.log. Check the ownership and permissions on everything in Mailman's var/templates/ directory if there is anything to ensure the Mailman user can read it.

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