Dear Robert.
Thanks so much for your prompt answer. I am afraid this is not feasible, as this MTA is also serving other purposes, hence impacting not only the messages addressed to distribution lists, but actually all of them. Besides, we would not like to resort to relaying in mail servers we do not control for retries, as they may have so heterogeneous behaviours regarding how the subsequent attempts are dealt.
I would you to also please confirm whether there is a way to stop just Hyperkitty, or Django maintenance tasks. I would like you to please confirm whether the runners need the backend available just to deliver mails to the members of the distribution lists.
Many thanks for your time once more. Best regards.
-----"Robert Moody" <[1]robert@kneedrag.org> wrote: -----
To: [2]eugenio.jordan@esa.int From: "Robert Moody" <[3]robert@kneedrag.org> Date: 08/23/2021 06:09AM Cc: [4]mailman-users@mailman3.org Subject: Re: [MM3-users] Mailman backend maintenance task A simple solution would be to stop the MTA in front of mailman. That is assuming the MTA is only delivering to mailman and nothing else. This would force any mails being sent during the maintenance to queue up on the sending server and once the maintenance is done starting the MTA will allow mails that were queued on the sending MTAs to get delivered. Downside is mails will be delayed based on the sending servers retry settings. Get [5]BlueMail for Android On 23 Aug 2021, at 05:55, [6]eugenio.jordan@esa.int wrote:
Dear all. My apologies if the answer to this question is obvious, but I am pretty newbie for 3 version, and to be very honest I haven't had enough time yet to have a deep look into the documentation. Our customer is currently using PostGRESQL as backend, and we would like to perform some maintenance tasks, namely running vacuum full, or at least trying to rebuild hyperkitty_email primary key related index. We have been asked on the real impact of putting in place such initiative. Though the latter is related to archiving, I haven't found a way to stop just Hyperkitty or Django related processes other than stopping Mailman's core, hence preventing mails addressed to distribution lists from being delivered, could you please confirm if I am correct? Regarding the former, as far as I have read, the "mappings" lists -> addresses are stored just in the database, so if we run some kind of procedure or task like vacuum which will lock exclusively tables, or want anyway to have the database stopped for a cold backup or whatever, Mailman willl not work, that is, again the mails addressed to the distribution lists will not be delivered. Will you please confirm this point, too? Really wish we had a testing environment to have been able to check this ourselves and not bothering others, but unfortunately we lack it, and we need to provide an answer as soon as possible. Thanks a lot for your time. Best regards. __________________________________________________________________
Mailman-users mailing list -- [7]mailman-users@mailman3.org To unsubscribe send an email to [8]mailman-users-leave@mailman3.org [9]https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org /
This message is intended only for the recipient(s) named above. It may contain p roprietary information and/or protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received this e-mail in error, please notify the sender immediately. ESA applies appropri ate organisational measures to protect personal data, in case of data privacy queries, please contact the ESA Data Prot ection Officer (dpo@esa.int).
References
- mailto:robert@kneedrag.org
- mailto:eugenio.jordan@esa.int
- mailto:robert@kneedrag.org
- mailto:mailman-users@mailman3.org
- https://bluemail.me/
- mailto:eugenio.jordan@esa.int
- mailto:mailman-users@mailman3.org
- mailto:mailman-users-leave@mailman3.org
- https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org