On Thu, Oct 9, 2025 at 2:52 PM Sam Darwin <samuel.d.darwin@gmail.com> wrote:

Hi Odhiambo,

Here is an example, it would need to be adjusted to another environment:

root@lists:/etc/logrotate.d# cat mailman3-core

## ## This file is maintained by Ansible - CHANGES WILL BE OVERWRITTEN ##

/var/log/mailman3/*.log { weekly rotate 4 compress maxsize 100M missingok notifempty sharedscripts delaycompress postrotate su - list -s /bin/sh -c "/opt/mailman3/bin/mailman -C /etc/mailman3/mailman.cfg reopen" endscript }

Your MM3 installation is NOT standard. By 'standard,' I meant an installation that strictly conforms to https://docs.mailman3.org/en/latest/install/virtualenv.html.

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

On Thu, Oct 9, 2025 at 4:35 PM Sam Darwin via Mailman-users < mailman-users@mailman3.org> wrote:

...

Your MM3 installation is NOT standard.

It's a starting point. Modify the config, test it, and then submit a merge request. There are literally hundreds of open issues on all the gitlab repos, so contributions help.

Okay. I have tested and settled on the one below:

/opt/mailman/mm/var/logs/*.log {
    #weekly
    #rotate 4
    daily
    rotate 7
    compress
    maxsize 100M
    missingok
    notifempty
    sharedscripts
    delaycompress
    postrotate
        su - mailman -s /bin/bash -c "/opt/mailman/venv/bin/mailman -C
/etc/mailman3/mailman.cfg reopen"
    endscript
}

Thank you very much.

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