Make our lives easy: There are 3 files: mailman.cfg, settings.py, and main.cf.
We expect that from these files: /etc/postfix/main.cf /etc/mailman3/mailman.cfg /etc/mailman3/settings.py For each file, do "egrep -v '^$|^.*#' filename". You should then obfuscate any sensitive details in the output and share the contents of the file.
On Wed, Apr 30, 2025 at 8:01 PM Alexander Inzinger-Zrock via Mailman-users < mailman-users@mailman3.org> wrote:
Am 30.04.25 um 15:36 schrieb Stephen J. Turnbull:
Did you set var_dir or layout in mailman.cfg? If not, you may have an alternate var_dir which is either the current directory when you start Mailman or possibly /var/tmp/mailman. That is also where "mailman aliases" will put the postfix aliases (in the "data" subdirectory).
It seems i set both *facepalm* while doing [1] and then adding changes according to [2]:
In mailman.cfg i have:
[paths.here] var_dir: /opt/mailman/mm/var
but also
[mailman] layout: local
also checking via mailman conf:
''mailman conf -s mailman | grep layout''
Output: [mailman] layout: local
''mailman conf -s | grep var_dir:''
Output:
[paths.dev] var_dir: $cfg_file/../.. [paths.fhs] var_dir: /var/lib/mailman [paths.here] var_dir: /opt/mailman/mm/var [paths.local] var_dir: /var/tmp/mailman
so i have empty logs at /opt/mailman/mm/var/logs and populated log files under /var/tmp/mailman/logs
If i recall correctly, setting layout: local is the suggested way to do for virtualenv install [2], so deleting
[paths.here] var_dir: /opt/mailman/mm/var
in mailman.cfg should be the next step (what i did).
Restarting my services gave me the warnings again, but these are (we remember) wrong paths (hash:/opt/mailman/mm/var/data/postfix_lmtp).
so i looked under /var/tmp/mailman/data and here we have populated files:
-rw-rw---- 1 mailman mailman 268K Feb 19 12:51 mailman.db -rw-rw---- 1 mailman mailman 377 Apr 30 18:01 postfix_domains -rw-r----- 1 mailman mailman 12K Apr 30 18:01 postfix_domains.db -rw-rw---- 1 mailman mailman 1.8K Apr 30 18:01 postfix_lmtp -rw-r----- 1 mailman mailman 12K Apr 30 18:01 postfix_lmtp.db
Now - before changing the /etc/postfix/main.cfg - there is the question that brings us almost back to the start:
With respect to [2]:
"If you are installing Mailman from source (or using Pip), it is recommended to use paths.local."
and [3]:
" transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp local_recipient_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains
[…]
local_recipient_maps = proxy:unix:passwd.byname $alias_maps hash:/path-to-mailman/var/data/postfix_lmtp "
**what is the recommended place to put the files to?**
I believe it to be /var/tmp/mailman/data according to
[mailman] layout: local
and that the above specific /opt/mailman -part is just a leftover from former times (the second and more generic part with /path-to-mailman indicates that to me).
If my assumption is correct i would create an issue + merge-request for the docs.
lg aiz
https://docs.mailman3.org/en/latest/config-core.html#configuring-filesystem-...
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...
This message sent to odhiambo@gmail.com
-- 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]