An issue with the postfix_domains directory creation and the mailman start command.
From Mark's reply of Jul 5, 2024, 3:18 PM:
RE: The mailman aliases command generates the postfix_domains and
postfix_lmtp files and calls the configured postmap_command (default
/usr/sbin/postmap) to create the .db files. mailman start also
generates these files by default.
1 [mailman3@somehost ~]$ ./venv/bin/mailman start
2 Starting Mailman's master runner
3 Generating MTA alias maps
4 [mailman3@somehost ~]$ sudo ls -l/opt/mailman3/mm/var/data/postfix_domains 5 ls: cannot access '/opt/mailman3/mm/var/data/postfix_domains': No such file or directory 6 [mailman3@somehost ~]$ ls -dl /opt/mailman3/mm/var/data/ 7 drwxr-xr-x. 2 mailman3 mailman3 6 Jul 5 13:38 /opt/mailman3/mm/var/data/
What should I do about lines 4-7? Thought it might be a permissions issue but it's owned by the correct user. Not sure that i missed any steps, suggestions appreciated.
On 2024-07-10 08:48, Keith Christian via Mailman-users wrote:
4 [mailman3@somehost ~]$ sudo ls -l/opt/mailman3/mm/var/data/postfix_domains 5 ls: cannot access '/opt/mailman3/mm/var/data/postfix_domains': No such file or directory 6 [mailman3@somehost ~]$ ls -dl/opt/mailman3/mm/var/data/ 7 drwxr-xr-x. 2 mailman3 mailman3 6 Jul 5 13:38 /opt/mailman3/mm/var/data/
What should I do about lines 4-7? Thought it might be a permissions issue but it's owned by the correct user.
My guess would be that mailman is using a different location for storing these files (aliases, domains, etc.)
One could search the system for where (if) the files were created with something like:
find / -name "postfix_domains"
Another (better?) thought would be to compare the [paths] pointed to by the "layout: ..." in /etc/mailman3/mailman.cfg to ensure it's pointing where you expect (in this case, /opt/mailman3/mm/var/data for data_dir).
As user mailman, running:
mailman conf
to double check the "layout: ..." that's in use.
Ron,
I ultimately have these layout files, due to what I've seen in the documentation. Not sure if these conflict with each other or if I need to create directories, these are in the /etc/mailman3/mailman.cfg listing below. layout: here layout: fhs layout: local
"Mailman info" to verify the mailman.cfg file in use: (venv) [mailman3@someserver ~]$ mailman info|cat -n 1 GNU Mailman 3.3.9 (Tom Sawyer) 2 Python 3.9.19 (main, May 16 2024, 08:45:40) 3 [GCC 8.5.0 20210514 (Red Hat 8.5.0-22)] 4 config file: /etc/mailman3/mailman.cfg 5 db url: postgresql://mailman3:not_the_password@localhost:5432/mailman3 6 devmode: DISABLED 7 REST root url: http://localhost:8001/3.1/ 8 REST credentials: restadmin:restpass
Here is the /etc/mailman3/mailman.cfg file: (venv) [mailman3@someserver ~]$ cat -n /etc/mailman3/mailman.cfg 1 # /etc/mailman3/mailman.cfg 2 [paths.here] 3 var_dir: /opt/mailman3/mm/var 4 5 [mailman] 6 layout: here 7 layout: fhs 8 layout: local 9 # This address is the "site owner" address. Certain messages which must be 10 # delivered to a human, but which can't be delivered to a list owner (e.g. a 11 # bounce from a list owner), will be sent to this address. It should point to 12 # a human. 13 site_owner: user@example.com 14 15 [database] 16 class: mailman.database.postgresql.PostgreSQLDatabase 17 #url: postgresql://mailman:MYPASSWORD@localhost/mailman 18 url: postgresql://mailman3:not_the_password@localhost:5432/mailman3 19 20 [archiver.prototype] 21 enable: yes 22 23 # For the HyperKitty archiver. 24 [archiver.hyperkitty] 25 class: mailman_hyperkitty.Archiver 26 enable: yes 27 configuration: /etc/mailman3/mailman-hyperkitty.cfg 28 29 [shell] 30 history_file: $var_dir/history.py 31 32 [mta] 33 verp_confirmations: yes 34 verp_personalized_deliveries: yes 35 verp_delivery_interval: 1 36
On Wed, Jul 10, 2024 at 1:40 PM Ron <admin@bclug.ca> wrote:
On 2024-07-10 08:48, Keith Christian via Mailman-users wrote:
4 [mailman3@somehost ~]$ sudo ls -l/opt/mailman3/mm/var/data/postfix_domains 5 ls: cannot access '/opt/mailman3/mm/var/data/postfix_domains': No such file or directory 6 [mailman3@somehost ~]$ ls -dl/opt/mailman3/mm/var/data/ 7 drwxr-xr-x. 2 mailman3 mailman3 6 Jul 5 13:38 /opt/mailman3/mm/var/data/
What should I do about lines 4-7? Thought it might be a permissions issue but it's owned by the correct user.
My guess would be that mailman is using a different location for storing these files (aliases, domains, etc.)
One could search the system for where (if) the files were created with something like:
find / -name "postfix_domains"
Another (better?) thought would be to compare the [paths] pointed to by the "layout: ..." in /etc/mailman3/mailman.cfg to ensure it's pointing where you expect (in this case, /opt/mailman3/mm/var/data for data_dir).
As user mailman, running:
mailman conf
to double check the "layout: ..." that's in use.
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 keith1christian@gmail.com
On 2024-07-10 12:14, Keith Christian via Mailman-users wrote:
5 [mailman] 6 layout: here 7 layout: fhs 8 layout: local
I don't know what happens when there are multiple entries for layout in there.
Try running this to see which one is active:
mailman conf | grep "layout:"
I get this:
[mailman] layout: here
And, in my /etc/mailman3/mailman.cfg file I have:
[paths.here] var_dir: /opt/mailman/mm/var bin_dir: $argv log_dir: $var_dir/logs data_dir: $var_dir/data ...
And, finally, I have this (can be slow on large disks):
find / -name "postfix_domains" 2>/dev/null /opt/mailman/mm/var/data/postfix_domains
Ron,
Ok I'll check this out, thanks!
On Wed, Jul 10, 2024, 13:26 Ron <admin@bclug.ca> wrote:
On 2024-07-10 12:14, Keith Christian via Mailman-users wrote:
5 [mailman] 6 layout: here 7 layout: fhs 8 layout: localI don't know what happens when there are multiple entries for layout in there.
Try running this to see which one is active:
mailman conf | grep "layout:"
I get this:
[mailman] layout: here
And, in my /etc/mailman3/mailman.cfg file I have:
[paths.here] var_dir: /opt/mailman/mm/var bin_dir: $argv log_dir: $var_dir/logs data_dir: $var_dir/data ...
And, finally, I have this (can be slow on large disks):
find / -name "postfix_domains" 2>/dev/null /opt/mailman/mm/var/data/postfix_domains
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 keith1christian@gmail.com
On Wed, Jul 10, 2024 at 11:05 PM Keith Christian via Mailman-users < mailman-users@mailman3.org> wrote:
Ron,
Ok I'll check this out, thanks!
Keith,
What would you lose if you deleted /opt/mailman3 and started afresh, by following https://docs.mailman3.org/en/latest/install/virtualenv.html ?
IMHO, trying to fix things your way is too costly in terms of the time you're investing on the installation.
-- 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]
Odhiambo,
I did exactly that late last week, and I'm further along since then than with the other two attempts to strictly follow the link above. I agree with you here: IMHO, trying to fix things your way is too costly in terms of the time you're investing on the installation. Another user mentioned there are a lot of detours in the otherwise good documentation. I'm going to spend a few more hours on this and if little progress I'll start over again. The next major part of this will be the import21 command which should prove very interesting.
Thanks for your suggestions.
On Wed, Jul 10, 2024 at 4:11 PM Odhiambo Washington <odhiambo@gmail.com> wrote:
On Wed, Jul 10, 2024 at 11:05 PM Keith Christian via Mailman-users <mailman-users@mailman3.org> wrote:
Ron,
Ok I'll check this out, thanks!
Keith,
What would you lose if you deleted /opt/mailman3 and started afresh, by following https://docs.mailman3.org/en/latest/install/virtualenv.html ?
IMHO, trying to fix things your way is too costly in terms of the time you're investing on the installation.
-- 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]
Ron, I get this:
1 (venv) [mailman3@somehost ~]$ mailman conf | grep layout
2 [mailman] layout: localI've added your paths to /etc/mailman3/mailman.cfg:
1 # /etc/mailman3/mailman.cfg
2
3 [paths.here]
4 var_dir: /opt/mailman3/mm/var
5 bin_dir: $argv
6 log_dir: $var_dir/logs
7 data_dir: $var_dir/data
8
9
10
11 [mailman]
12 layout: here
13 layout: fhs
14 layout: localI just stopped and started mailman to force a config file read: 1 (venv) [mailman3@somehost ~]$ ./venv/bin/mailman start 2 Starting Mailman's master runner 3 Generating MTA alias maps
Still, nothing in the data directory. 1 (venv) [mailman3@somehost ~]$ sudo ls -l /opt/mailman3/mm/var/data/postfix_domains 2 ls: cannot access '/opt/mailman3/mm/var/data/postfix_domains': No such file or directory 3 (venv) [mailman3@somehost ~]$ sudo ls -l /opt/mailman3/mm/var/data/postfix_lmtp 4 ls: cannot access '/opt/mailman3/mm/var/data/postfix_lmtp': No such file or directory
Once I get past the Postfix db files and other issues, I should be very close.
--------- Keith
On Wed, Jul 10, 2024 at 4:04 PM Keith Christian <keith1christian@gmail.com> wrote:
Ron,
Ok I'll check this out, thanks!
On Wed, Jul 10, 2024, 13:26 Ron <admin@bclug.ca> wrote:
On 2024-07-10 12:14, Keith Christian via Mailman-users wrote:
5 [mailman] 6 layout: here 7 layout: fhs 8 layout: localI don't know what happens when there are multiple entries for layout in there.
Try running this to see which one is active:
mailman conf | grep "layout:"
I get this:
[mailman] layout: here
And, in my /etc/mailman3/mailman.cfg file I have:
[paths.here] var_dir: /opt/mailman/mm/var bin_dir: $argv log_dir: $var_dir/logs data_dir: $var_dir/data ...
And, finally, I have this (can be slow on large disks):
find / -name "postfix_domains" 2>/dev/null /opt/mailman/mm/var/data/postfix_domains
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 keith1christian@gmail.com
On July 10, 2024 1:35:03 PM PDT, Keith Christian via Mailman-users <mailman-users@mailman3.org> wrote:
Ron, I get this:
1 (venv) [mailman3@somehost ~]$ mailman conf | grep layout 2 [mailman] layout: local
I've added your paths to /etc/mailman3/mailman.cfg:
1 # /etc/mailman3/mailman.cfg 2 3 [paths.here] 4 var_dir: /opt/mailman3/mm/var 5 bin_dir: $argv 6 log_dir: $var_dir/logs 7 data_dir: $var_dir/data 8 910 11 [mailman] 12 layout: here 13 layout: fhs 14 layout: local
Everything you put on lines 4-7 is irrelevant because line 14 overrides line 12. Remove lines 13 and 14.
-- Mark Sapiro <mark@msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.
participants (4)
-
Keith Christian -
Mark Sapiro -
Odhiambo Washington -
Ron