- Mailman-users - lists.mailman3.org

hello， Discussion on how to subscribe to the mailing list
by 朱超 Jan. 18, 2023

Jan. 18, 2023

Hi, When I subscribe the email list in Subscription Policy is confirm, Some problems happen in here： 1.Some mail mua reject send the confirm the message, because the length of recipient is too long. for exmaple: requirements-confirm+9605556e0b35a5da280c1de0d34a3e6f770f8ea5@domain, and the mail mua reject to modify about this. 2.It is inconvenient for users to use. Many people will mistakenly think that after clicking the subscribe button, it will be successful, and they will not process the email. Regarding the discussion on the subscription method of the mailing list, should we consider optimizing the subscription method of the mailing list, for example: 1. use the method of sending a verification code to subscribe by email，When you receive the verification code sent by the mailing list and fill it in again, you can subscribe successfully。 2. use the email to send a connection to confirm the subscription，People click the link to be redirected to a confirmation page to subscribe to the email。

4 12

mailman-web causing constant 100% cpu load of mysqld
by Johannes Rohr Jan. 16, 2023

Jan. 16, 2023

Dear all, with mailmanweb running, the CPU load of mysqld constantly hovers around 100% In /var/log/mysql/errors.log I see repeatedly: 2023-01-13 17:22:42 27198 [Warning] Aborted connection 27198 to db: 'mailman_core' user: 'mailman' host: 'localhost' (Got an error reading communication packets) 2023-01-13 17:27:43 29621 [Warning] Aborted connection 29621 to db: 'mailman_core' user: 'mailman' host: 'localhost' (Got an error reading communication packets) This also seems to affect other services such as dovecot which rely on mysql and at times can't connect to it. Does anyone have a suggestion what to do about this? Cheers, Johannes

2 1

Error Logging - what changed with the New Year releases?
by Odhiambo Washington Jan. 15, 2023

Jan. 15, 2023

Apart from all the defaults in settings.py (derived from gitlab), I also have this line: LOGGING['handlers']['file']['filename'] = '/opt/mailman/mm/var/logs/mailmanweb.log' Before the New Year releases of MM3, I used to get errors written to this file. Not anymore after I updated to the New Year releases. Another thing that I have realized is that prior to the New Year releases, I would get an error logged to that file and also mailed to me. I don't think that I have changed anything in settings,py related to logging. I have been trying to get signup with Twitter working. This used to generate an error that was both logged and emailed, but that isn't happening anymore. I have enabled other social auth providers (in settings.py) which I haven't configured in the admin panel. I expect that tying to use these on Postorius would generate an error that is logged and mailed to admin, but that too is not happening. Just checking out what might have changed - or if I am going nuts :-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 5

Moderation request reminders
by Allan Hansen Jan. 14, 2023

Jan. 14, 2023

Hi all, I and my moderators are getting daily moderation request reminders. Is there a way to set them to be weekly instead? I looked around in the UI for it but did not see it. It started with my latest server upgrade. As list owner I get 50+ of these messages every morning and my modertors each get only one, but don't like it. I still don't see a link for my moderators to see the membership lists even though the lists are set to allow it. Is that among the planned bug fixes? Yours, Allan

2 1

Cross-List and Domain based sender whitelisting ( accept_these_nonmembers )
by Patrick Brückner Jan. 13, 2023

Jan. 13, 2023

Hi everyone, one of our servers that was running a mailman2 instance just crashed this afternoon, so we decided to take the leap and migrate to 3, and I have to say it worked pretty well, the lists seem to be back. What I can't seem to find is the option to whitelist senders based on a domain AND on membership on a different list. The lists are operated for a smallish university and all the professors need to be allowed to send to the students list, without being member of that list. That was possible with mailman2 by just whitelisting the university domain. Also, in the past we allowed all members of the all-students list to post to any of the dorm-lists (this is mainly used for party announcements so it is not a must have), but I wanted to ask anyways, if there was a chance to allow this feature again. According to the docs, the accept_these_nonmembers option exists (https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…) but none of my lists have that set after the migration - the field is not even there when accessing the REST API. Do I need to enable something? Has that feature been added just recently, and we are missing out (since we are using the apt packages from ubuntu)? Thanks in advance, Patrick

4 7

About the sender of the mailing list receiving an auto-reply email
by 朱超 Jan. 13, 2023

Jan. 13, 2023

Hi, When I use the mailing list to send emails, I receive an automatic reply email, Is there a better way to block similar automatic reply emails? From: Tom

2 1

Error from - /opt/mailman/mm/bin/django-admin runjobs hourly
by Odhiambo Washington Jan. 12, 2023

Jan. 12, 2023

I have received the following error message from the hourly cron run: <quote> /opt/mailman/mm/bin/django-admin: line 7: 7475 Killed django-admin $@ </quote> I have looked at my log files, but could not find any clue. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 1

mailman.log file owned by 'list' user
by Mike Wertheim Jan. 12, 2023

Jan. 12, 2023

I'm on Debian 11, trying to troubleshoot an installation of Mailman 3.3.3 that was done by someone else. Mailman is running as a non-privileged (non-root) user called 'xyz'. On the day that Mailman was installed, that non-privileged 'xyz' user was able to execute mailman commands successfully to create, view and modify lists. A couple of days later, when the 'xyz' user tried running those same mailman commands, they failed with this error: PermissionError: [Errno 13] Permission denied: '/var/log/mailman3/mailman.log' Doing "ls -l" on the file /var/log/mailman3/mailman.log showed this: -rw-r----- 1 list list 0 Jan 6 00:00 /var/log/mailman3/mailman.log When I did a 'ps' command, I saw that all of the mailman processes are running as user 'xyz'. No processes were running as the user 'list'. It seems that some process is rotating the mailman.log file at midnight, and the newly-created mailman.log is being owned by user 'list'. Can anyone explain why this is happening, and how to fix it?

4 3

Re: Docker or virtualenv?
by J.Schulz Jan. 10, 2023

Jan. 10, 2023

For Docker: just use the README on https://github.com/maxking/docker-mailman ; this should be enough for a basic setup. Eventually, you'll need to add some things to core/mailman-extra.cfg : ___ [mailman] site_owner: help(a)elternserver.de SMTP_MAX_RCPTS = 1 VERP_CONFIRMATIONS = Yes VERP_PASSWORD_REMINDERS = Yes VERP_PERSONALIZED_DELIVERIES = Yes VERP_DELIVERY_INTERVAL = 1 # [devmode] # enabled: yes # recipient: you(a)somewhere.com # # extra local settings for mailmen [mta] # NullMTA is just implementing the interface and thus satisfying Mailman # without doing anything fancy # outgoing: mailman.mta.null.NullMTA smtp_user: your_auth@your_MTA smtp_pass: supersecretpassword smtp_verify_hostname: yesorno smtp_secure_mode: starttls # or whatever # [logging.debug] [logging.smtp] level: warn ___ also, web/settings_local.py needs tweaking in some cases; the DJANGO_ALLOWED_HOSTS come from my docker-compose.yml ---- import os # see https://github.com/maxking/docker-mailman/issues/548 django_allowed_hosts = os.environ.get('DJANGO_ALLOWED_HOSTS') if django_allowed_hosts: ALLOWED_HOSTS = django_allowed_hosts.split(':') MAILMAN_WEB_SOCIAL_AUTH = [] SOCIALACCOUNT_PROVIDERS = { } DEBUG = False # see https://gitlab.com/mailman/mailman/-/issues/957 DEFAULT_AUTO_FIELD='django.db.models.AutoField' HAYSTACK_CONNECTIONS = { 'default': { 'ENGINE': 'xapian_backend.XapianEngine', 'PATH': "/opt/mailman-web-data/fulltext_index", }, } ----- Am 10.01.23 um 09:11 schrieb Odhiambo Washington: > Hi Jörg, > > Kindly share the link to the HOWTO, which you use to setup everything. > I just need to test. Perhaps I can use docker on Windows, no? > > On Mon, Jan 9, 2023 at 8:58 PM Jörg Schulz <info(a)joergschulz.de> wrote: > > I have a successful installation using docker, just updated to the > most > recent version - it runs along quite some other docker containers, so > there is a benefit when I want to switch machines. > > Am 07.01.23 um 12:02 schrieb Odhiambo Washington: > > On Sat, Jan 7, 2023 at 1:54 PM Johannes Rohr <johannes(a)rohr.org> > wrote: > > > >> I wanted to say "I have now chosen virtualenv". Sorry for the > confusion. > >> > > I have never tried docker, but soon I will. Just for the kicks. > > > > > > > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

1 0

SPF check fails for lists subdomain
by Jan Eden Jan. 9, 2023

Jan. 9, 2023

Hi, my question is not related to Mailman directly, apologies for using this list. I configured the DNS records for my base domain and my lists subdomain identically (the DMARC policy records are also identical, but not listed here): MX @ mail.eden.one TXT @ "v=spf1 mx ~all" MX lists mail.eden.one TXT lists "v=spf1 mx ~all" A mail 123.123.123.123 But both Yahoo and Google report different SPF results for the two domains: <policy_published> <domain>eden.one</domain> <adkim>s</adkim> <aspf>s</aspf> <p>quarantine</p> <pct>75</pct> </policy_published> <record> <row> <source_ip>123.123.123.123</source_ip> <count>3</count> <policy_evaluated> <disposition>none</disposition> <dkim>pass</dkim> <spf>pass</spf> </policy_evaluated> </row> <policy_published> <domain>lists.eden.one</domain> <adkim>s</adkim> <aspf>s</aspf> <p>quarantine</p> <pct>75</pct> </policy_published> <record> <row> <source_ip>123.123.123.123</source_ip> <count>2</count> <policy_evaluated> <disposition>none</disposition> <dkim>pass</dkim> <spf>fail</spf> </policy_evaluated> </row> What could possibly cause this difference? The SPF test also fails for a different base domain with the same MX and SPF records. - Jan

3 8