transport map (postfix_lmtp) does not update - new lists not working
End of last year, I've re-installed mailman3 using the virtualenv installation method on ubuntu 20.04.
Since then, the transport map (/opt/mailman/mm/var/data/postfix_lmtp) has not been updated even though, new mailing lists were created. The old mailing lists, that existed before the re-installation work perfectly fine but those created after are not accessible. Because the entries for those new lists are missing in the transport map, postfix replies with a "mail for ... loops back to myself" error.
I'm quite sure, that I did all the steps in the documentation (except that I use a slightly different apache2 vhost configuration). I double checked on the cronjobs.
crontab -u mailman -e
@daily /opt/mailman/venv/bin/mailman digests --periodic @daily /opt/mailman/venv/bin/mailman notify
- * /opt/mailman/venv/bin/mailman-web runjobs minutely 0,15,30,45 * * * * /opt/mailman/venv/bin/mailman-web runjobs quarter_hourly @hourly /opt/mailman/venv/bin/mailman-web runjobs hourly @daily /opt/mailman/venv/bin/mailman-web runjobs daily @weekly /opt/mailman/venv/bin/mailman-web runjobs weekly @monthly /opt/mailman/venv/bin/mailman-web runjobs monthly @yearly /opt/mailman/venv/bin/mailman-web runjobs yearly
Any idea, what I could have missed???
Kind regards, Nils
On Mon, Jan 29, 2024 at 2:32 PM Nils <mailman@bugblatterbeast.de> wrote:
End of last year, I've re-installed mailman3 using the virtualenv installation method on ubuntu 20.04.
Since then, the transport map (/opt/mailman/mm/var/data/postfix_lmtp) has not been updated even though, new mailing lists were created. The old mailing lists, that existed before the re-installation work perfectly fine but those created after are not accessible. Because the entries for those new lists are missing in the transport map, postfix replies with a "mail for ... loops back to myself" error.
I'm quite sure, that I did all the steps in the documentation (except that I use a slightly different apache2 vhost configuration). I double checked on the cronjobs.
crontab -u mailman -e
@daily /opt/mailman/venv/bin/mailman digests --periodic @daily /opt/mailman/venv/bin/mailman notify
/opt/mailman/venv/bin/mailman-web runjobs minutelyAny idea, what I could have missed???
Kind regards, Nils
I am not any good with Postfix, nor am I an expert with MM3, but my thinking is that those files are updated by Mailman whenever you create a list. Postfix only reads them. Now the question lingering in my head is: How does Mailman know that it needs to create those files? I think that unless you tell Mailman - via mailman.cf - that you aren't using Exim or Sendmail or other MTA, then it assumes that you are using Postfix and so creates/updates those files. I am saying that because in my mailman.cfg I have this:
[mta] verp_confirmations: yes verp_personalized_deliveries: yes verp_delivery_interval: 1 verp_probes: yes incoming: mailman.mta.exim4.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: localhost smtp_host: localhost lmtp_port: 8024 smtp_port: 25 configuration: python:mailman.config.exim4 <============ I think this is probably what stops Mailman from creating those files on my server.
Looking at https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-mailm..., I do not see the line starting with "configuration", so I am taking it that Mailman core presumes Postfix by default. Now the other question is why would it NOT update those files whenever you create a new list? And I am thinking that maybe the permissions on that directory, or the initial files changed during your reinstall and so they could not be written to/updated.
This is just my guess. I am sure the proper explanation is on the way :-)
-- 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]
Thank you very much for your reply Odhiambo.
Sorry, it was all a mistake in my postfix configuration. Please forget it!
I forgot to update the pathes. They were still pointing to /var/lib/mailman.
Additionally I accidentally gave you wrong information. The transport map at /opt/mailman/mm/var/data/postfix_lmtp DID update.
Sorry for the confusion.
Kind regards, Nils
On 1/29/24 12:53, Odhiambo Washington wrote:
On Mon, Jan 29, 2024 at 2:32 PM Nils <mailman@bugblatterbeast.de> wrote:
End of last year, I've re-installed mailman3 using the virtualenv installation method on ubuntu 20.04.
Since then, the transport map (/opt/mailman/mm/var/data/postfix_lmtp) has not been updated even though, new mailing lists were created. The old mailing lists, that existed before the re-installation work perfectly fine but those created after are not accessible. Because the entries for those new lists are missing in the transport map, postfix replies with a "mail for ... loops back to myself" error.
I'm quite sure, that I did all the steps in the documentation (except that I use a slightly different apache2 vhost configuration). I double checked on the cronjobs.
crontab -u mailman -e
@daily /opt/mailman/venv/bin/mailman digests --periodic @daily /opt/mailman/venv/bin/mailman notify
- * /opt/mailman/venv/bin/mailman-web runjobs minutely 0,15,30,45 * * * * /opt/mailman/venv/bin/mailman-web runjobs quarter_hourly @hourly /opt/mailman/venv/bin/mailman-web runjobs hourly @daily /opt/mailman/venv/bin/mailman-web runjobs daily @weekly /opt/mailman/venv/bin/mailman-web runjobs weekly @monthly /opt/mailman/venv/bin/mailman-web runjobs monthly @yearly /opt/mailman/venv/bin/mailman-web runjobs yearly
Any idea, what I could have missed???
Kind regards, Nils
I am not any good with Postfix, nor am I an expert with MM3, but my thinking is that those files are updated by Mailman whenever you create a list. Postfix only reads them. Now the question lingering in my head is: How does Mailman know that it needs to create those files? I think that unless you tell Mailman - via mailman.cf - that you aren't using Exim or Sendmail or other MTA, then it assumes that you are using Postfix and so creates/updates those files. I am saying that because in my mailman.cfg I have this:
[mta] verp_confirmations: yes verp_personalized_deliveries: yes verp_delivery_interval: 1 verp_probes: yes incoming: mailman.mta.exim4.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: localhost smtp_host: localhost lmtp_port: 8024 smtp_port: 25 configuration: python:mailman.config.exim4 <============ I think this is probably what stops Mailman from creating those files on my server.
Looking at https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-mailm..., I do not see the line starting with "configuration", so I am taking it that Mailman core presumes Postfix by default. Now the other question is why would it NOT update those files whenever you create a new list? And I am thinking that maybe the permissions on that directory, or the initial files changed during your reinstall and so they could not be written to/updated.
This is just my guess. I am sure the proper explanation is on the way :-)
participants (2)
-
Nils -
Odhiambo Washington