- Mailman-users - lists.mailman3.org

"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

Do i need a mailman-hyperkitty.cfg file?
by Bill Oliver Oct. 30, 2024

Oct. 30, 2024

While trying to set up my new mailman installation in Ubuntu 22.04, which doesn't quite work yet, I decided to compare my config files with my Ubuntu 24.04 LTS installation, which does seem to work to the degree I've tested it. I noticed this little snippet in the settings.py file: # Set this to match the api_key setting in # /opt/mailman/mm/mailman-hyperkitty.cfg (quoted here, not there). MAILMAN_ARCHIVER_KEY = 'Secret_Hyperkitty_API_Key' Aha, I thought. I should have changed that. Then I noticed that I didn't even have a mailman-hyperkitty.cfg file, and I can't find mention of it in the venv instructions. I *have* installed mailman- hyperkitty during the "pip install mailman-web mailman-hyperkitty" step. I did a "find" on /opt/mailman, and it doesn't seem the file is there at all. Do I need this file? I found a template here: https://gitlab.com/mailman/mailman-hyperkitty/blob/master/mailman-hyperkitt… Do I need to copy and paste that in my installation? Thanks! billo

2 2

Welcome message issue
by Mohsen Masoudfar Oct. 29, 2024

Oct. 29, 2024

Good afternoon I have an issue with welcome message. A list owner is requesting to update the welcome message for only one of their lists. They are requesting to change the default text and insert additional URLs pointing to sites related to their list. I know there is a URI field that you may include a web page. But this doesn't work and gets ignored. - is there a mailman cli option to update the default template for a single list? I couldn't find it in WUI. I reviewed all parameters and variables of the list and couldn't find one that might be related to it. We are running an old version of Mailman 3. Thanks Mohsen

2 2

New installation, new issue: mailman3 migrate -- no module CommonMark
by Bill Oliver Oct. 27, 2024

Oct. 27, 2024

My Ubuntu 24.04 installation is working great, and I have a list running perfectly. I'm now trying to install mailman3 on an older server, this time runing ubuntu 22.04. I'm following the venv installation instructions again, but suddenly came up with a new error. I've made it to the "Run database migrations" section I run mailmanweb-migrate and get: (venv) mailman@mail:~$ mailman-web migrate Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.10/site- packages/django/template/backends/django.py", line 128, in get_package_libraries module = import_module(entry[1]) File "/usr/lib/python3.10/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1050, in _gcd_import File "<frozen importlib._bootstrap>", line 1027, in _find_and_load File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 688, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 883, in exec_module File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed File "/opt/mailman/venv/lib/python3.10/site- packages/postorius/templatetags/markdown.py", line 21, in <module> from readme_renderer import markdown as md_render File "/opt/mailman/venv/lib/python3.10/site- packages/readme_renderer/markdown.py", line 16, in <module> from CommonMark import commonmark ModuleNotFoundError: No module named 'CommonMark' The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/opt/mailman/venv/bin/mailman-web", line 8, in <module> sys.exit(main()) File "/opt/mailman/venv/lib/python3.10/site- packages/mailman_web/manage.py", line 87, in main execute_from_command_line(sys.argv) File "/opt/mailman/venv/lib/python3.10/site- packages/django/core/management/__init__.py", line 442, in execute_from_command_line utility.execute() File "/opt/mailman/venv/lib/python3.10/site- packages/django/core/management/__init__.py", line 436, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/opt/mailman/venv/lib/python3.10/site- packages/django/core/management/base.py", line 412, in run_from_argv self.execute(*args, **cmd_options) File "/opt/mailman/venv/lib/python3.10/site- packages/django/core/management/base.py", line 458, in execute output = self.handle(*args, **options) File "/opt/mailman/venv/lib/python3.10/site- packages/django/core/management/base.py", line 106, in wrapper res = handle_func(*args, **kwargs) File "/opt/mailman/venv/lib/python3.10/site- packages/django/core/management/commands/migrate.py", line 100, in handle self.check(databases=[database]) File "/opt/mailman/venv/lib/python3.10/site- packages/django/core/management/base.py", line 485, in check all_issues = checks.run_checks( File "/opt/mailman/venv/lib/python3.10/site- packages/django/core/checks/registry.py", line 88, in run_checks new_errors = check(app_configs=app_configs, databases=databases) File "/opt/mailman/venv/lib/python3.10/site- packages/django/core/checks/templates.py", line 60, in check_for_template_tags_with_the_same_name for module_name, module_path in get_template_tag_modules(): File "/opt/mailman/venv/lib/python3.10/site- packages/django/template/backends/django.py", line 105, in get_template_tag_modules for name in get_package_libraries(pkg): File "/opt/mailman/venv/lib/python3.10/site- packages/django/template/backends/django.py", line 130, in get_package_libraries raise InvalidTemplateLibrary( django.template.library.InvalidTemplateLibrary: Invalid template library specified. ImportError raised when trying to load 'postorius.templatetags.markdown': No mod ule named 'CommonMark' I know nothing about CommonMark. Since I've suffered the error cascade problem of trying to fix things and just making it worse, I stopped here. Can I ignore this error, or what can I do to fix it? Thanks! billo

2 5

501 Message has defects
by jgn1980＠gmail.com Oct. 25, 2024

Oct. 25, 2024

Hi I'm using GNU Mailman 3.3.8 (Tom Sawyer) on debian 12, and I have this issue on a scheduled e-mail, every day: 2024-10-25T04:00:04.874081+01:00 XXXXXXX postfix/lmtp[29258]: CEB32100F44: to=<XXX(a)XXX.XX>, relay=localhost[127.0.0.1]:8024, delay=0.02, delays=0.01/0/0.01/0.01, dsn=5.0.0, status=bounced (host localhost[127.0.0.1] said: 501 Message has defects (in reply to end of DATA command)) I have already changed some settings on the postfix and list configurations, without success. Outlook 365 and gmail receive the email without issues. Does anyone have any idea of how I can fix this? Thanks,

2 1

Timeout error on anonymous subscribe
by vogt＠spamcop.net Oct. 25, 2024

Oct. 25, 2024

Hi, I am running a mailman 3.3.9 server (pip installation). It's working fine so far. However, I have problems setting a template. I set a '[list:user:action:subscribe]' template for a list with some simple text like "test1234". When someone wants to subscribe on the list page without creating an account, it takes five seconds until "HTTPSConnectionPool(host='lists.example.org', port=443): Read timed out. (read timeout=5)" appears on the page. The mail address has been added pending confirmation but no mail gets send. mailman.log shows just exceptions about the timeout itself: Sep 09 15:01:45 2024 (2070549) deque: do_confirm_verify Traceback (most recent call last): File "/opt/mailman/venv/lib64/python3.11/site-packages/urllib3/connectionpool.py", line 536, in _make_request response = conn.getresponse() ^^^^^^^^^^^^^^^^^^ ... requests.exceptions.ReadTimeout: HTTPSConnectionPool(host='lists.dkrz.de', port=443): Read timed out. (read timeout=5) [09/Sep/2024:15:01:45 +0200] "POST /3.1/members HTTP/1.1" 400 132 "-" "GNU Mailman REST client v3.3.5" The access log suggests that getting the template took 5s: ==> /opt/mailman/mm/var/logs/access.log <== 127.0.0.1 - - [09/Sep/2024:13:01:45 +0000] "GET /mailman3/api/templates/list/community.lists.example.org/list:user:action:subscribe HTTP/1.1" 200 8 "-" "python-requests/2.32.3" Running curl on that url returns immediately $ curl -v 'http://localhost:8000/mailman3/api/templates/list/community.lists.example.o…' I have captured the network traffic on localhost interface lo and I can see that the request is sent through the tcp connection and acknowledged. Then 5 seconds later the server (port 8000) sends a push data with the response and closes the connection with FIN. The data exchanged on the connection looks like this: GET /mailman3/api/templates/list/community.lists.example.org/list:user:action:subscribe HTTP/1.1 Host: lists.example.org User-Agent: python-requests/2.32.3 Accept-Encoding: gzip, deflate Accept: */* X-Forwarded-Proto: https X-Forwarded-For: 2001:638:1234:1224::111 X-Forwarded-Host: lists.example.org X-Forwarded-Server: lists.example.org Connection: Keep-Alive HTTP/1.1 200 OK Server: gunicorn Date: Mon, 09 Sep 2024 13:01:45 GMT Connection: close Content-Type: text/plain; charset=utf-8 X-Content-Type-Options: nosniff Referrer-Policy: same-origin Cross-Origin-Opener-Policy: same-origin X-Frame-Options: DENY Vary: Accept-Language, Cookie Content-Language: en Content-Length: 8 test1234 The timestamp 13:01:45 is the time of the timeout. The request started five seconds before that. It looks to me as if the connection/keepalive handling is not working properly or the server isn't pushing the response immediately, but it gets buffered until the 5s timeout. Occassionally, I have capture a requests, where the client side would send a FIN to the server and only then the server would send the http response with the final packets. Does anyone have an idea how I can fix this? Thanks, Gerald

3 9

User account issue after importing data from Mailman 2.x server
by dgoldsmith＠sans.org Oct. 24, 2024

Oct. 24, 2024

We finally migrated from Mailman 2.x to a Mailman 3.x several months ago. We have had some issues with people who are active list members not being able to login with their user creds and when trying to use the 'Forgot Password' link to reset, being told their user account does not exist. They can submit email to the list and get copied on other list traffic. I just started looking at a user and a list in both the Postorius and Django admin web UIs and found: - in Postorius: - list exists, has 20K plus subscribed members and has 3 list owners - user exists and is subscribed to this list - in Django: - in HyperKitty section - in the Mailing lists page, the list exists, no idea about members BUT it has 147 owners (also the same 147 moderators) - in the Emails page, there are 149K plus entries - in the Profiles page, there are 147 entries - in the Accounts->Email addresses page, there are only 155 entries - in the AUTHENTICATION AND AUTHORIZATION->Users page, there are 147 entries Should Mailman 3.x have created user accounts for everyone when importing the data from the old server? To correct the issue on a case by case basis, can I as a server admin do something via the web UI or CLI or do we need to remove the email address from the list and ask the person to create a new account using that address and to resubscribe to the specific list or other? Thanks, David Goldsmith

2 1

Logging subscribes/unsubscribes
by Brian Carpenter Oct. 22, 2024

Oct. 22, 2024

Does Mailman 3 log subscribes and unsubscribes for each list the way Mailman 2 did? Brian

5 7