- Mailman-users - lists.mailman3.org

Postorius admin/user guide
by Florin Pasăre Nov. 8, 2024

Nov. 8, 2024

Hello, We're trying to update mailman to version 3 from version 2, and I can't seem to find some non-technical guide for Postorius, something like an owners manual for all the configurations available in Postorius. Is there such a thing? Thank you, Florin

3 2

Members (and moderators) can't view the list of members.
by mrl＠psfc.mit.edu Nov. 7, 2024

Nov. 7, 2024

I installed Mailman 3 almost 2 years ago. I only now noticed that members of a mailing list can't view the list of members. Even moderators can't see the list. Only Owners. The error message is "You do not have permissions to visit this page." Mailman Core Version GNU Mailman 3.3.8 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.10.12 (main, Jun 11 2023, 05:26:28) [GCC 11.4.0] Postorius Version 1.3.8 Any ideas? I did make a few "minor" changes to the code, but hopefully it didn't cause this problem. What file(s) contains the code that checks for permissions? Or maybe there is a config file? I also notice by default, for all users, in their "Global Mailman Preferences", the default setting for "Hide Address" is "Yes". How can I change that to be "No". And can I reset that setting for all my present users? Thanks. - Mark

2 1

How to keep virtualenv install secure?
by Lichtinger, Bernhard Nov. 7, 2024

Nov. 7, 2024

Hi, I am looking for some advice: If we use the virtualenv install method, how does one keep track of security updates for all the installed dependencies? I can think of: - Upgrade regularly all installed packages inside the virtualenv. This might break mailman3 if there are incompatible updates. - Try to track all dependencies and check if there are security updates published. This might be impossible to achieve. - Security updates are so rare, we do not need to bother. ;) Thanks, Bernhard

3 2

Abusive user creation - ideas for mitigating
by Andy Smith Nov. 7, 2024

Nov. 7, 2024

Hi, My mailman3.auth_users table contains 131 rows, of which 113 of them were created in the last week. All of these users have a 10 character long random string of lowercase letters as their chosen username. Their email addresses are all over the place. I only noticed this was happening because an unusual number of the subscription confirmation messages were bouncing back to me as postmaster, and I saw the unlikely user names. I matched up some of the date_joined timings with logs of HTTP POST to /mailman/accounts/signup and every single one so far was a unique IP address. So I am not going to get very far with firewalling. Does anyone have any suggestions what I can do to avoid this? Specifically what I would like to avoid is sending a confirmation email to these potentially innocent addresses. … Hmm, actually I've just noticed that all of them are Tor exit nodes. Looks like I could probably autogenerate an Apache ACL that lists all Tor exit nodes and bans them from posting to /mailman/accounts/signup. Thanks, Andy

2 3

Backup and restore a single list
by sherin＠raidm.com Nov. 6, 2024

Nov. 6, 2024

Hello, I am new to mailman3 . I am looking for the procedure to backup and restore a single mailing list from mailman3. If any one know the procedure or the documentation , please point me

3 7

Where to find disabled members?
by Bill Oliver Nov. 5, 2024

Nov. 5, 2024

Now that I have mailman running smoothly, I'm having to deal with a few other issues. When I changed vendors for my vps, my vendor gave me a static IP address that was apparently run by Satan himself. The ip address is -- or was -- on a number of blacklists. I have spent the past couple of weeks going through various appeals processes to get whitelisted, and I think I'm in good shape. In the meantime, a fair number of subscribers have been disabled. When I look at Postorius -> Settings -> Bounce processing, I see all of the policies I can play with, but I don't see how to a) See who is disabled, and b) un-disable them by hand or... do I just have to wait seven days for them to automatically get un-disabled? Thanks! billo

2 2

member appears twice in list - how?
by Jose Bernal Nov. 5, 2024

Nov. 5, 2024

I've got a list member showing up twice in a list (same email address). Can't use the GUI to remove the member from this list (get a 503 error) Screenshots attached, underlying database query reveals no duplicates. Wondering how this is possible or where else I should be looking to resolve this duplicate before I simply remove their entry from the members table altogether. Thank you, --------------------- José Bernal Web/Application Engineer Cell 541-228-8481 jbernal.web.dev(a)gmail.com ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: Screen Shot 2024-11-05 at 10.53.55 AM.png Content-Type: image/png Name: Screen Shot 2024-11-05 at 10.59.12 AM.png Replaced multipart/alternative part with first alternative.

2 1

"held for moderation" - alias domain details sought
by Greg Newby Nov. 5, 2024

Nov. 5, 2024

Hi friends. I've viewed this old thread: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… and documentation here: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… (and the Postfix docs it links to). Those documents don't seem to guide my situation, or maybe I just need a more specific example. The problem is that when messages are delivered to the alias domain, they are held for moderation. I.e., mail to the alias domain like testlist(a)domain.tld is held for moderation, but mail from the same subscribed, non-moderated user to testlist(a)lists.domain.tld is posted immediately without moderation. I wonder whether my main domain needs to be @domain.tld and my alias domain needs to be @lists.domain.tld - is that what I should try? Or, am I not setting up the alias domain correctly? Details: I'm writing to ask for advice so that mailman messages to address(a)domain.tld can also be sent to address(a)lists.domain.tld. There are various other non-Mailman addresses (local Unix accounts and aliases) handled by @domain.tld as well as @otherdomain.tld on the same server. I have a running 3.3.10 server (venv, using Postfix and PostgreSQL under Ubuntu 24.04LTS). The configured domain is of the form: lists.domain.tld and it's working ok. I put this in /etc/aliases and it seems to work, to forward messages from testlist(a)domain.tld to testlist(a)lists.domain.tld: testlist: testlist(a)lists.domain.tld I know it works because I see it in MM3's smtp.log and mailman.log, including a line like this in mailman.log: Oct 12 21:12:27 2024 (2560960) HOLD: testlist(a)lists.domain.tld post from gbnewby(a)petascale.org held, message-id=< CANLuyJZd8NNn5rOLe3XUhooG9F33U_7VOQXrS-7Z241koAV_Ww(a)mail.otherdomain.com>: Message has implicit destination And, indeed, the message is held for moderation. In the MM3 configuration panel for Domains ( https://lists.domain.tld/mailman3/domains/) I have put "domain.tld" in the "Alias domain" field. Thanks for any guidance. I appreciated seeing the recent threat about "redirecting -bounces replies" which also addresses alias domains. ~ Greg

3 4

The dread "relay access denied" error
by Bill Oliver Nov. 5, 2024

Nov. 5, 2024

I've been trying to avoid asking this question since "relay access denied" problems are usually pretty silly configuration errors that I should pick up. But I've been staring at this for three days and I'm stumped. Once again here's the scenario. I set up mailman3 on Ubuntu 24.04 and it's running without a hitch, particularly now that I added the appropriate archival commands. I decided to create a backup on an older server of mine running Ubuntu 22.04. The setup is almost identical except for domain names. Unfortunately, in the second setup, I'm getting "relay access denied" to senders/recipients outside the host domain. Things go fine to list members on the local machine. Mailman is successfully sending admin mail to mailman(a)bill-oliver.com Mail not using mailman works fine. The domain where everything works is billoblog.com. The domain I'm setting up is bill-oliver.com Here's the error in syslog (mirrored in mail.log) on bill-oliver.com trying to talk to list members oliver(a)billoblog.com and billo(a)billoblog.com:: Nov 1 21:24:52 mail postfix/smtpd[10193]: NOQUEUE: reject: RCPT from 162-144-108-19.bluehost.com[162.144.108.19]: 454 4.7.1 <oliver(a)billoblog.com>: Relay access denied; from=<tradfp-bounces+oliver=billoblog.com(a)bill-oliver.com> to=<oliver(a)billoblog.com> proto=ESMTP helo=<162-144-108- 19.bluehost.com> Nov 1 21:24:52 mail postfix/smtpd[10193]: disconnect from 162-144-108- 19.bluehost.com[162.144.108.19] ehlo=1 mail=2 rcpt=1/2 data=1 rset=1 quit=1 commands=7/8 Nov 1 21:24:52 mail postfix/smtpd[10193]: connect from 162-144-108- 19.bluehost.com[162.144.108.19] Nov 1 21:24:52 mail postfix/smtpd[10193]: NOQUEUE: reject: RCPT from 162-144-108-19.bluehost.com[162.144.108.19]: 454 4.7.1 <billo(a)billoblog.com>: Relay access denied; from=<tradfp-bounces+billo=billoblog.com(a)bill-oliver.com> to=<billo(a)billoblog.com> proto=ESMTP helo=<162-144-108-19.bluehost.com> Nov 1 21:24:52 mail postfix/smtpd[10193]: disconnect from 162-144-108- 19.bluehost.com[162.144.108.19] ehlo=1 mail=1 rcpt=0/1 rset=1 quit=1 commands=4/5 Nov 1 21:25:48 mail dovecot: auth-worker(10954): Debug: conn unix:auth- worker (pid=10903,uid=116): Disconnected: Connection closed (fd=-1) Nov 1 21:25:48 mail dovecot: auth-worker(10954): Debug: mysql(localhost): Connection finished (queries=1, slow queries=0) Nov 1 21:27:28 mail dovecot: auth: Debug: mysql: Connection finished (queries=0, slow queries=0) FYI, 162-144-108-19.bluehost.com is my ip address and bluehost.com is the VPS vendor. I don't know why that pops up, since the domain is bill-oliver.com. I assume it's VPS-related magic. Here are similar errors in /opt/mailman/mm/var/logs/smtp.log: Nov 01 21:22:46 2024 (1573) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Nov 01 21:22:46 2024 (1573) Peer: ('162.144.108.19', 51476) Nov 01 21:22:46 2024 (1573) ('162.144.108.19', 51476) handling connection Nov 01 21:22:46 2024 (1573) ('162.144.108.19', 51476) >> b'LHLO mail.bill-oliver.com' Nov 01 21:22:46 2024 (1573) ('162.144.108.19', 51476) >> b'MAIL FROM:<billo(a)billoblog.com> SIZE=1486 BODY=8BITMIME' Nov 01 21:22:46 2024 (1573) ('162.144.108.19', 51476) sender: billo(a)billoblog.com Nov 01 21:22:46 2024 (1573) ('162.144.108.19', 51476) >> b'RCPT TO:<tradfp(a)lists.bill-oliver.com>' Nov 01 21:22:46 2024 (1573) ('162.144.108.19', 51476) recip: tradfp(a)lists.bill-oliver.com Nov 01 21:22:46 2024 (1573) ('162.144.108.19', 51476) >> b'DATA' Nov 01 21:22:46 2024 (1573) ('162.144.108.19', 51476) >> b'QUIT' Nov 01 21:22:46 2024 (1573) ('162.144.108.19', 51476) connection lost Nov 01 21:22:46 2024 (1573) ('162.144.108.19', 51476) Connection lost during _handle_client() Nov 01 21:22:48 2024 (1574) <cbacd3866ebdfeeb706993996ba84e67f7db5ad9.camel(a)billoblog.com> recipients refused: {'oliver(a)billoblog.com': (454, b'4.7.1 <oliver(a)billoblog.com>: Relay access denied')} Nov 01 21:22:48 2024 (1574) <cbacd3866ebdfeeb706993996ba84e67f7db5ad9.camel(a)billoblog.com> recipients refused: {'billo(a)billoblog.com': (454, b'4.7.1 <billo(a)billoblog.com>: Relay access denied')} Nov 01 21:22:48 2024 (1574) <cbacd3866ebdfeeb706993996ba84e67f7db5ad9.camel(a)billoblog.com> smtp to tradfp(a)bill-oliver.com for 2 recips, completed in 0.27154111862182617 seconds Nov 01 21:22:48 2024 (1574) <cbacd3866ebdfeeb706993996ba84e67f7db5ad9.camel(a)billoblog.com> post to tradfp(a)bill-oliver.com from billo(a)billoblog.com, 1448 bytes, 2 failures Nov 01 21:22:48 2024 (1574) <cbacd3866ebdfeeb706993996ba84e67f7db5ad9.camel(a)billoblog.com> delivery to oliver(a)billoblog.com failed with code 454, b'4.7.1 <oliver(a)billoblog.com>: Relay access denied' Nov 01 21:22:48 2024 (1574) <cbacd3866ebdfeeb706993996ba84e67f7db5ad9.camel(a)billoblog.com> delivery to billo(a)billoblog.com failed with code 454, b'4.7.1 <billo(a)billoblog.com>: Relay access denied' Nov 01 21:24:11 2024 (1574) <173051065026.1640.13931339026208387550(a)162-144-108-19.bluehost.com> smtp to tradfp(a)bill-oliver.com for 1 recips, completed in 0.24669885635375977 seconds Nov 01 21:24:11 2024 (1574) <173051065026.1640.13931339026208387550(a)162-144-108-19.bluehost.com> post to tradfp(a)bill-oliver.com from tradfp-request(a)bill-oliver.com, 1222 bytes I have gone over my main.cf and master.cf a zillion times. Worse, I've compared them with the same files in the setup that works, and I can't find a significant error) though things are in a slightly different order. I don't know if I'm missing something big or am just a poor proofreader. Any ideas would be appreciated. Here's the obligatory main.cf and master.cf in /etc/postfix. I use dovecot and virtual domains and virtual mailboxex administered using postfixadmin. Here's the main.cf: # See /usr/share/postfix/main.cf.dist for a commented, more complete version # Debian specific: Specifying a file name will cause the first # line of that file to be used as the name. The Debian default # is /etc/mailname. #myorigin = /etc/mailname smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu) biff = no # appending .domain is the MUA's job. append_dot_mydomain = no # Uncomment the next line to generate "delayed mail" warnings #delay_warning_time = 4h readme_directory = no # See http://www.postfix.org/COMPATIBILITY_README.html -- default to 3.6 on # fresh installs. compatibility_level = 3.6 #Enable TLS Encryption when Postfix receives incoming emails smtpd_tls_cert_file=/etc/letsencrypt/live/mail.bill- oliver.com/fullchain.pem smtpd_tls_key_file=/etc/letsencrypt/live/mail.bill- oliver.com/privkey.pem smtpd_tls_security_level=may smtpd_tls_loglevel = 1 smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache #Enable TLS Encryption when Postfix sends outgoing emails smtp_tls_CApath=/etc/ssl/certs smtp_tls_security_level = may smtp_tls_loglevel = 1 smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache 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 myhostname = mail.bill-oliver.com alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases myorigin = /etc/mailname mydestination = $myhostname, localhost.$mydomain, localhost relayhost = mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 mail.bill- oliver.com bill-oliver.com lists.bill-oliver.com virtual_mailbox_limit = 0 mailbox_size_limit = 0 message_size_limit = 0 recipient_delimiter = + inet_interfaces = all inet_protocols = ipv4 #Enforce TLSv1.3 or TLSv1.2 smtpd_tls_mandatory_protocols = !SSLv2, !SSLv3, !TLSv1, !TLSv1.1 smtpd_tls_protocols = !SSLv2, !SSLv3, !TLSv1, !TLSv1.1 smtp_tls_mandatory_protocols = !SSLv2, !SSLv3, !TLSv1, !TLSv1.1 smtp_tls_protocols = !SSLv2, !SSLv3, !TLSv1, !TLSv1.1 mailbox_transport = lmtp:unix:private/dovecot-lmtp smtputf8_enable = no virtual_mailbox_domains = proxy:mysql:/etc/postfix/sql/mysql_virtual_domains_maps.cf virtual_mailbox_maps = proxy:mysql:/etc/postfix/sql/mysql_virtual_mailbox_maps.cf, proxy:mysql:/etc/postfix/sql/mysql_virtual_alias_domain_mailbox_maps.cf virtual_alias_maps = proxy:mysql:/etc/postfix/sql/mysql_virtual_alias_maps.cf, proxy:mysql:/etc/postfix/sql/mysql_virtual_alias_domain_maps.cf, proxy:mysql:/etc/postfix/sql/mysql_virtual_alias_domain_catchall_maps.c f hash:/opt/mailman/mm/var/data/postfix_vmap #virtual_transport = lmtp:unix:private/dovecot-lmtp virtual_mailbox_base = /var/vmail virtual_minimum_uid = 2000 virtual_uid_maps = static:2000 virtual_gid_maps = static:2000 policyd-spf_time_limit = 3600 smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination, check_policy_service unix:private/policyd-spf smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination # Milter configuration milter_default_action = accept milter_protocol = 6 smtpd_milters = local:opendkim/opendkim.sock non_smtpd_milters = $smtpd_milters unknown_local_recipient_reject_code = 550 ########################################### Here's the master.cf (comments deleted) : smtp inet n - y - - smtpd submission inet n - y - - smtpd -o syslog_name=postfix/submission -o smtpd_tls_security_level=encrypt -o smtpd_sasl_auth_enable=yes -o smtpd_tls_wrappermode=no -o smtpd_sasl_auth_enable=yes -o smtpd_relay_restrictions=permit_sasl_authenticated,reject -o smtpd_recipient_restrictions=permit_mynetworks,permit_sasl_authenticate d,reject -o smtpd_sasl_type=dovecot -o smtpd_sasl_path=private/auth smtps inet n - y - - smtpd -o syslog_name=postfix/smtps -o smtpd_tls_wrappermode=yes -o smtpd_sasl_auth_enable=yes -o smtpd_recipient_restrictions=permit_mynetworks,permit_sasl_authenticate d,reject -o smtpd_relay_restrictions=permit_sasl_authenticated,reject -o smtpd_sasl_type=dovecot -o smtpd_sasl_path=private/auth pickup unix n - y 60 1 pickup cleanup unix n - y - 0 cleanup qmgr unix n - n 300 1 qmgr tlsmgr unix - - y 1000? 1 tlsmgr rewrite unix - - y - - trivial-rewrite bounce unix - - y - 0 bounce defer unix - - y - 0 bounce trace unix - - y - 0 bounce verify unix - - y - 1 verify flush unix n - y 1000? 0 flush proxymap unix - - n - - proxymap proxywrite unix - - n - 1 proxymap smtp unix - - y - - smtp relay unix - - y - - smtp -o syslog_name=postfix/$service_name showq unix n - y - - showq error unix - - y - - error retry unix - - y - - error discard unix - - y - - discard local unix - n n - - local virtual unix - n n - - virtual lmtp unix - - y - - lmtp anvil unix - - y - 1 anvil scache unix - - y - 1 scache postlog unix-dgram n - n - 1 postlogd uucp unix - n n - - pipe flags=Fqhu user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient) policyd-spf unix - n n - 0 spawn user=policyd-spf argv=/usr/bin/policyd-spf Thanks, billo

2 2

How to fix: [Django] ERROR (EXTERNAL IP)
by Jigme Datse Nov. 2, 2024

Nov. 2, 2024

This feels like something that I should have working. I know I've not been attending to things all that well, so the thing that has happened, that's got us from, "possibly doing nothing," to throwing this error is that I went to update my mail server, and in the update, Mailman3 stopped working entirely (it was a variety of things), but now it's launching, and will load the main web interface... but Going to any of the list pages, gives the above Error. Well, not exactly the above error, Django is in square brackets. OK, that will work better for me with the how to fix. How to fix, probably isn't quite what I'm looking for, it's how to diagnose. The error tells me that the IP address is 127.0.0.1 and that 127.0.0.1 is in the ALLOWED_HOSTS. I *mostly* see this coming from Google, but when I go and look at the webpage, I get: normal page at /mailman3/lists/ But my lists, all give me... Something went wrong HTTP error 500: {"title": "500 Internal Server Error"} I've tried to figure out where to go from here, and right now I'm not making any progress, so I thought I'd ask here.

2 6