Search results for "sapiro" - lists.mailman3.org

[MM3-users] Re: Problem getting Mailman3 to work with Ubuntu 24.04.1 LTS

by Mark Sapiro

On 9/12/24 20:52, sebensteg(a)cod.edu wrote: > Hello everyone, > > We have been using Mailman3 for over a year and half. We upgraded from Ubuntu 22.04.5, where it was working fine, to Ubuntu 22.04.1. Since then, mailman3 won’t work. When we tried to start it immediately after the upgrade, we got this error: > > 024-09-12T23:08:04.322353+00:00 weather1 systemd[1]: Starting mailman3.service - GNU Mailing List Manager... > 2024-09-12T23:08:04.935569+00:00 weather1 mailman[23628]: SystemError: type psycopg2.extensions.ReplicationConnection has the Py_TPFLAGS_HAVE_GC flag but has no traverse function See https://github.com/psycopg/psycopg2/issues/1598 ... > But yet, we have this installed: > > venv mailman@weather1:~$ pip install psycopg2-binary > Requirement already satisfied: psycopg2-binary in ./venv/lib/python3.12/site-packages (2.8.6) > > Any advice on how to get this working again would be GREATLY appreciated! Try pip install --upgrade psycopg2-binary -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 2 weeks

[MM3-users] Re: Deliverability and Spam Filtering

by Mark Sapiro

On 1/30/20 1:58 PM, Tom @ Gather wrote: > Interesting! Does the `in` queue also work for emails to subaddresses like > foo-owner, etc? Or is it only for list posts? -bounces goes to bounces -confirm, -join, -leave (and their synonyms -subscribe and -unsubscribe) and -request go to command -owner goes to in. But there's more to it that that. There's also things put in the metadata in the queue entry such as mail to -owner sets to_owner = True > Relatedly, why is `list_id` a required parameter? Isn't that information > contained in the email? Possibly not. The recipient list is the envelope recipient which may or may not be in the message headers - it could be a Bcc to the list. Thus, listid needs to be set in the metadata as well. You need to look at mailman/runners/lmtp.py and emulate what it does. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: Mailman Suite installation on CentOS 7

by Mark Sapiro

On 11/8/21 4:18 AM, Kimmo L wrote: > Hello! > > I want to install fresh Mailman, which is combined with hyperkitty+postorius. After checking documentation i found, that Mailman Suite is perfect for me. > But i have some misunderstandings about installation. I only found this part in documentation, which explains how to clone and start using Mailman Suite (https://docs.mailman3.org/en/latest/devsetup.html#run-the-mailman-suite-com…) > > But am i correct, that before doing so, i need to install mailman core, mailman client, django-mailman3 ? > Or what would be the correct steps to build up my first Mailman Suite on CentOS? The docs you want to look at are https://docs.mailman3.org/en/latest/#the-pre-installation-guide and https://docs.mailman3.org/en/latest/install/install.html. There is also information at https://wiki.list.org/x/17891998 and in docs linked from thefirst paragraph thereof. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

[MM3-users] Re: Messages not picking up header or footer template

by Mark Sapiro

On 2/26/23 13:04, benjamin(a)tougshire.com wrote: > > I can see the entry in the database with the uri: http://localhost:8000/mailman3/api/templates/list/testing.comms.sdcvirginia… > > I can do a wget on that uri and download a copy of the footer, and it looks right > > But when I send a message to the list and the message is forwarded, the footer isn't on the messages that members receive > > Looking at mailman.log, I cannot see any attempt to access the footer. I can see connections to the REST API (config, roster/owner, roster/moderator) that correspond to the time I sent the message Can you see an attempt to GET /mailman3/api/templates/list/testing.comms.sdcvirginia.org/list:member:regular:footer in your web server's logs? Is there anything in Django's log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

[MM3-users] Re: Social signup?

by Mark Sapiro

On 3/15/23 05:08, Duane Raymond wrote: > > I'll jump over to the developers list when I start this (I'm about to > travel for a week to run an annual event in Oxford - so the far removed > from programming)...but which chatGPT suggested so far was > > 1. Extending postorius/signups.html with a loop to get the configured > social login providers PLUS adding a csrf_token field to the form > 2. Modifying postorius/views.py (which doesn't seem to exist but there > is a postorius/views folder) - so perhaps this is views/urls.py This is not what you want to do for this. The changes need to be in django-mailman3, not postorius. I have attached a patch which might work for you. I think it is good, but some of the wording is stuff that may not be appropriate. See what you think. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: unrequested unsubscription

by Mark Sapiro

On 6/14/23 19:40, Mike Wertheim wrote: > I have a Mailman 3 email list, running on Mailman 3.3.3 on Debian 11. > > A few of the list members are reporting that they received Email Address > Unsubscription Confirmation emails, but claim that they never requested to > be unsubscribed. (All are Gmail users. but they might be coincidental, > since most list members are Gmail users.) > > Has anyone seen this behavior before? Any ideas on what might be happening? Yes. This is someone sending an email `leave` or `unsubscribe` command for the user in question. This may be malicious, i.e. someone doesn't like a user's posts and tries to unsubscribe them, or it may be just spam of some sort. the user should just ignore the email. Beyond that, there's not much you can do unless you can identify from mail logs the source of the requests. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

[MM3-users] Re: Disable Sign-up per domain

by Mark Sapiro

On 7/31/25 23:00, Mark wrote: > > The traceback does suggest that the SITE does not exist... Yes. Please confirm that the issue only occurs with the modified /opt/mailman/venv/lib/python3.11/site-packages/django_mailman3/views/user_adapter.py and does not occur with the original .../user_adapter.py. Also, prior to installing the modified /opt/mailman/venv/lib/python3.11/site-packages/django_mailman3/views/user_adapter.py did you have ACCOUNT_ADAPTER = 'django_mailman3.views.user_adapter.DisableSignupAdapter' in your settings or did you only add that with the modified .../user_adapter.py I.e., I'm trying to determine if there is some issue with the modified ../user_adapter.py or if the issue does not involve the modification, but rather just the setting of ACCOUNT_ADAPTER Also, when does this error occur? Does it occur an all web access to the site or only on access to the accounts/signup page? and does the host in the https request make a difference? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

12 hours, 37 minutes

[MM3-users] Re: Mailing lists sometimes do not honor moderation_action of non-members

by Mark Sapiro

On 11/3/19 6:58 PM, Alan So wrote: > Are there any pointer of documentation that I can clear all _these_nonmembers settings by updating the databases directly or using mailman shell? I am not so familiar with mailman shell though. We expect list owners use moderation_action only for members and non-members. $ bin/mailman shell -l test.example.com Welcome to the GNU Mailman shell The variable 'm' is the test.example.com mailing list >>> m.accept_these_nonmembers = [] >>> m.hold_these_nonmembers = [] >>> m.reject_these_nonmembers = [] >>> m.discard_these_nonmembers = [] That will just blindly clear them all. If you want to see what you're clearing, you could do things like >>> if m.accept_these_nonmembers: ... m.accept_these_nonmembers ... m.accept_these_nonmembers = [] ... which if the list's accept_these_nonmembers is non-empty will display it and then set it empty. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

[MM3-users] Re: Docker-Setup: example.com in test mails

by Mark Sapiro

On 2/24/22 13:30, Bjoern Franke via Mailman-users wrote: > Hi, > >> >> >> Exactly what messages are you referring to? I don't understand `test >> mails testing for bounces`. >> > > I mean the messages created by > > [mta] > verp_probes: yes I thought that might be what you meant, but you said > To our confusion, test mails testing for bounces are sent from example.com > > From: Mailman mailman(a)example.com > To: Mailman Bounces mailman-bounces(a)example.com > Verp probes are always addressed to the bouncing user, never to mailman-bounces(a)example.com unless mailman-bounces(a)example.com is a list member with bouncing deliveries. They are also from listname-bounces+<token>@example.com, not mailman(a)example.com. I don't know what messages you are looking at, but they don't seem to be verp probes. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: Restore/export existing Mailman lists + hyperkitty archives on a new server

by Mark Sapiro

On 9/15/22 01:22, Kimmo L wrote: > Hi Mark! > > I forwarded the same shunted file to you as well, which i sent to Steve. Thanks. I got it and will look further. > About that no "Message-ID" error - Basically it still occurs in mailman.log file even if some other list has been used. And our other lists does not use this "anonymous list" option. Those errors should result in the affected messages being saved as *.pck files in Mailman's var/archives/hyperkitty/spool/ directory. Possibly there is only one such 'bad message' which is retried each time there is a new post resulting in the same error. How many such files are there? If only one, please send me that one too. Also, these can be examined with `mailman qfile`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

[MM3-users] Re: Using the API to create nonmembers with a different moderation action than the list default

by Mark Sapiro

On 6/6/24 11:36 PM, Perry Kollmorgen wrote: > Hi, > > My next challenge is to script the setup of a bunch of nonmembers who have a moderation action of accept (or maybe defer) whilst the list itself has a nonmember action of hold. > > This is due to a relatively heavy use of nested lists, and have a fair number of people who might possibly send to all lists, and are important enough they wouldn't want to be manually allowed each time even if it only once. Note that beginning with Mailman 3.3.10 (not yet released) you can put things like @list2@example.com in accept_these_nonmembers of list1(a)example.com to accept posts from non_members who are members of list2(a)example.com. See https://gitlab.com/mailman/mailman/-/merge_requests/1154 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 1 month

[MM3-users] Re: Log Owner/Moderator actions ban address matching.

by Mark Sapiro

On 5/1/25 04:02, Stephen J. Turnbull wrote: > Odhiambo Washington via Mailman-users writes: > > > So this issue can be addressed by making Postorius to log user logins, > > right? > > However, I don't have the patch :) > > I would guess it's probably possible to get Django to do this, quite > possibly using standard configuration to do so. I just don't know > where to look offhand. Postorius can't log logins because it's not Postorius (or HyperKitty) that does the logging in. It is django-allauth. You can see the `Last Login` info for a user in the Django admin web UI under Authentication and Authorization -> Users django-mailman3 does have some involvement with logging in and it might be possible to add logging there, but I don't offhand know where. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months

[MM3-users] Re: DKIM signatures with message footers or subject prefixes

by Mark Sapiro

On 3/12/22 12:20, Stanisław Findeisen via Mailman-users wrote: > On Fri, Mar 11, 2022 at 10:41:00AM -0800, Mark Sapiro wrote: >> Also, your outgoing MTA should DKIM sign the mail on the way out. With that and the above setting, the outgoing message will have only your >> valid DKIM signature and no prior Authentication-Results:. > > Ok, you mean after replacing the From address with the list address, right? > I can see no way (or sense) to DKIM sign arbitrary From: addresses. Your DKIM signature only says you sent the mail and if the signature validates, the mail hasn't been modified since you signed it. I.e. validation of the signature is a statement to the recipient that the mail received is what you sent. That's all. If the domain of the From: address doesn't align with your domain, the signature won't help with DMARC, but that's a separate issue and why we have DMARC mitigations suck as replacing the From: with the list address. > This actually works quite good: the recipient just gets 2 DKIM signatures. The original one is broken, the MTA-generated one (after writing my list address into From) is OK. This is good enough even for ProtonMail (no red warning). And your rewriting the From: is only necessary for DMARC. If the ProtonMail red flag is only because there was no valid DKIM signature, you shouldn't need to rewrite From:. If it is because of DMARC, you do. > What about this list (mailman-users). It looks this one also has From address replacement + conditional DMARC mitigation. And remove_dkim_headers: no. Correct? This list has DMARC mitigation action = Replace From: and DMARC Mitigate unconditionally = No and remove_dkim_headers: no. We DKIM sign all outgoing mail from lists.mailman3.org. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: LMTP on unix socket

by Mark Sapiro

On 10/20/19 3:55 PM, Hristo Venev via Mailman-users wrote: > How do I configure mailman to use a unix socket for lmtp connections? > Setting > > [mta] > incoming: mailman.mta.null.NullMTA > lmtp_host: /path/to/socket > > does not work. Mailman still tries to create a TCP socket. You can't do this. Mail Delivery is to Mailman's lmtp runner which uses the LMTP class in aiosmtpd <https://aiosmtpd.readthedocs.io/en/latest/> to create an LMTP server which listens for tcp connection on lmtp_host:lmtp_port. You would have to modify mailman/runners/lmtp.py to listen on a unix socket. The docs imply the aiosmtpd.controller.Controller class has a make_socket() method which "allows subclasses to customize the creation of the socket before binding" which I suppose could be used to create a unix socket, but mailman/runners/lmtp.py currently doesn't make use of that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

[MM3-users] Re: HyperKitty async tasks runner: systemd qcluster service fails eventually

by Mark Sapiro

On 12/5/19 6:17 AM, actionmystique(a)gmail.com wrote: > I think I have a lead: after having removed ```Restart=always``` which masked the details about the systemd service failure, I get: ...> Dec 05 15:04:06 samsung4-ubuntu django-admin[1199893]: File "/usr/lib/python3.7/logging/config.py", line 571, in configure > Dec 05 15:04:06 samsung4-ubuntu django-admin[1199893]: '%r' % name) from e > Dec 05 15:04:06 samsung4-ubuntu django-admin[1199893]: ValueError: Unable to configure handler 'file' ... > ... > 'file':{ > 'level': 'INFO', > #'class': 'logging.handlers.RotatingFileHandler', > 'class': 'logging.handlers.WatchedFileHandler', > ### 'filename': os.path.join(BASE_DIR, 'logs', 'mailmansuite.log'), > 'filename': '/var/log/mailman3/mailmansuite.log', Does the mailman user, 'list' or whatever you have for User=<user> and Group=<group> in the systemd service file have permission to create/write /var/log/mailman3/mailmansuite.log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

[MM3-users] Re: MM3 shunting mails

by Mark Sapiro

On 12/5/19 1:40 PM, ikemulder(a)hotmail.com wrote: > > In the script I am filtering for 'mhonarc' ListArchivers, since the duplicate ListArchivers always seem to be mhonarc archivers. > > If this is not the appropriate place, please let me know - I would like to get to the bottom of this :). I see you've also filed <https://gitlab.com/mailman/mailman/issues/657>. Thank you for that. We are as puzzled as you are by this. It would help if you could detect this duplication when it happens and try to get more information. The problem is I can't see how to do that. I would start by adding some logging to the patch_put method of the ListArchivers class in mailman/rest/lists.py to log the list and the request. Then when you see the duplicate, you can check this log to see if anything suspicious happened just prior to that? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: Disable archives per list

by Mark Sapiro

On 2/25/21 1:57 AM, Bernd Wurst wrote: > > Can I as the server admin disable archiving (or set other list options) > in a way that the list admin can not change it via postorious? As the server admin, you can enable/disable archivers sitewide. See <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.…> et seq. Note that the prototype archiver, if enabled, stores messages in the file system in maildir format. Normally a list admin can select which of the enabled archivers is active for that list via Postorius. To prevent this, you would have to modify Postorius. It would be easy enough to just remove settings from the relevant templates. > Can I have custom archiver settings per list or per domain > (customer-specific hyperkitty)? I'm not sure what you mean by "custom archiver settings", but other than enable/disable and public/private, probably not. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: auto-away notices as bounces

by Mark Sapiro

On 8/24/21 11:17 AM, Andreas Barth wrote: > > Well, the mail adress got disabled, and the user got warning mails > ("Your subscription for list mailing list has been disabled"). As none > of the list owners did that, I don't think there is any other > explanation. Please note that individualsation was enabled, so all > mails are sent out with per-subscriber mail envelope address, which > then makes bounce detection quite straight-forward. If by 'individualsation was enabled' you mean messages were VERPed, there could be a bug here. There are a couple of considerations. First the vacation responder should not respond to list messages. See <https://www.rfc-editor.org/rfc/rfc5230.html#section-4.6>. That said, bounce processing should treat even a VERPed message as unrecognized if it doesn't look like some kind of DSN. This may not be the case in MM 3. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] Re: Emergency moderation and clearing out a lot of held messages

by Mark Sapiro

On 4/28/22 12:31, bob B via Mailman-users wrote: > sorry that makes sense, users not senders, but what is the setting for the sender? I have emergency moderation on a list, and if someone sends to the list they get this message: > ************************** > Your mail to 'maillistalpha(a)XXXX.com' with the subject > test > Is being held until the list moderator can review it for approval. > The message is being held because: > Emergency moderation is in effect for this list > Either the message will get posted to the list, or you will receive > notification of the moderator's decision. > ****************************************************** > > Can I turn this off for a list? As you suggested in your OP, set "Notify users of held messages" to No. Is that not working? It should. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: Walk-thru for Ubuntu Bionic Mailman 3 Full setup

by Mark Sapiro

On 7/8/22 9:16 AM, kisner(a)live.com wrote: > > Just out of curiosity and to try to improve the doc I can do this a little later. But I can tell you for sure the pip install psycopg2-binary<2.9 command failed for me on Ubuntu 22.04 and Debian 11.3. I'm not saying it's *not* me, and I don't know when the last time that doc was updated but I couldn't get it to work on a few different distros. The issue is when you do ``` pip install psycopg2-binary<2.9 ``` your shell (sh, bash, zsh or whatever) interprets `<2.9` as an input redirection and probably says something like `2.9: No such file or directory`. You need to do something like ``` pip install psycopg2-binary\<2.9 ``` or ``` pip install 'psycopg2-binary<2.9' ``` I'll update the doc. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

[MM3-users] Re: Is there a way to find out when a user subscribed to a list

by Mark Sapiro

On 4/17/24 15:14, Mark wrote: > You can query the mailman database ... > > select email, registered_on,verified_on from mailman.public.address > where email = 'mmasoudf(a)aaas.org' > > > On 2024-04-18 03:19, Mohsen Masoudfar wrote: >> Hi, >> We need to find out when a specific user joined a list. Is there a way >> to get this information? Querying the database in that way is not reliable. Yes, it is correct that the user has both a user record and an address record, and the user record has a created_on date and the address record has both registered_on and verified_on dates, but those are only the creation/verification dates for those records. They are not necessarily the date that that user/address subscribed to any list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

[MM3-users] Re: Held messages showing a reason not in English on the Postorious

by Mark Sapiro

On 6/25/24 20:13, Alan KT So (ITSC) wrote: > We just notice a held message from a user's list showing the held reason in Ukrainian, but the interface is in US English and the list's preferred language is English (USA). We could not repeat the issue. What can be the reason behind? > > [cid:image001.png@01DAC7B9.AF2B0400] I'm assuming the image that content filtering removed was a screen shot of the held message view in Postorius. was the sender of the message a list member with preferred language Ukranian? There may be an issue here. The line at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/chains/hold.py… calls format_reasons which will translate the reasons in whatever the current language context is. It should probably explicitly specify the list's preferred language. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 1 month

[MM3-users] Re: Header settings and Gmail

by Mark Sapiro

On 7/29/24 12:25, erik(a)dante.de wrote: > > As a preventive measure, it helps to use DMARC mitigation action with “Replace From: with list address” and “ DMARC Mitigate unconditionally ”. But now some users are unhappy with the From header " Username via Test-liste <test(a)test-liste.org>". They would rather have their email address in it. If your Mailman core version is >=3.3.9 you can add `^.*(a)gmail\.com` to dmarc_addresses (DMARC addresses in Postorius) to apply the mitigation to gmail.com addresses instead of unconditionally, but this won't help your gmail users. > Is there a solution with which Google delivers the mailing list messages without complaining, but the sender email address is also in the “From:”? No. This is just one example of Google/gmail behaving oddly. gmail.com publishes a DMARC policy of none, yet they require incoming email From: the gmail.com domain to pass DMARC -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] Re: no mails to list members

by Mark Sapiro

On 1/4/19 6:49 AM, Thomas Stein wrote: > > While we`re at it. Is /var/lib/mailman3/templates/lists/$listname the right location for customized templates? There are multiple ways to reference templates, but just putting them in that location should work. > Should > I name the template list:member:generic:footer.txt or list_member_generic_footer.txt? Your list was created with an older version of import21. That version named the templates it stored with underscores rather than colons and set the URI for that template to use the underscore name. Thus, without changing the URI for the template, you need to continue to use the underscore name for those templates, but for other templates, you can use the name with colons and not worry about the URI. > Is there some documentation > what variables i can put in those templates? See <https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/templates.ht…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 6 months

[MM3-users] Re: Delete Django profiles not signed up to a list

by Mark Sapiro

On 2/8/21 1:22 AM, r.woithe(a)callassoftware.com wrote: > Hello, > > i did try the script and unfortunately there is a problem. The script is deleting django-users are not member,nonmember ... of any lists.But thats not the point. Its ok if a user want to be only a django-user to see the archives and work with them. If a user sign's up for an account at /accounts/signup/ and then confirms her address, she will then be a Mailman user with a user and an address record even though not a member of any lists. > The script should delete django-users who dont confirm your email address. Change one line in the script from ``` if mm_user is None or len(list(mm_user.memberships.members)) == 0: ``` to ``` if mm_user is None: ``` And it will do what you want. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: moderation notices for list-owner being redirected to mailman address

by Mark Sapiro

On 2/9/22 16:12, Philippe B wrote: > Ah, thanks for that. > > I've done `owner.preferences.delivery_status = DeliveryStatus.enabled` for those 2 lists. > > Is there an easy way to find out all the other owners that don't have `<DeliveryStatus.enabled: 1>` ? ``` $ bin/mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> for mlist in getUtility(IListManager).mailing_lists: ... for admin in mlist.administrators.members: ... if admin.delivery_status != DeliveryStatus.enabled: ... print(f'List: {mlist.list_name}, ' ... f'Admin: {admin.address.email}, ' ... f'Role: {admin.role}, ' ... f'Status: {admin.delivery_status}') And optionally, ... admin.preferences.delivery_status = DeliveryStatus.enabled ... print('Enabled.') ... (output here) >>> commit() >>> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: Restore/export existing Mailman lists + hyperkitty archives on a new server

by Mark Sapiro

On 8/5/22 07:02, Kimmo L wrote: > > The only concern I've observed and I'm trying to solve right now is with memory. Not sure whats consumes the memory gradually, so that it will start consume also swap memory and eventually you can find"OSError: write error" entries in uwsgi-error.log or "django.request Internal Server Error: /hyperkitty/" in mailmanweb.log > Do i need to modify my uwsgi.ini configuration maybe ? > Server has 2CPU and 5GB RAM. We have seen reports of memory leaks, but no solutions. We do not see these issues on any of the production servers we manage. The server that hosts this lists has 4GB RAM and that seems fine for a server doing just Mailman. Our servers use gunicorn, not uwsgi, so this could be a uwsgi issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[MM3-users] Re: Badsignature on uwsgi-error.log

by Mark Sapiro

On 3/20/24 14:25, Helio Loureiro wrote: > Hi, > > I keep receiving a lot of errors like this: > > --- Logging error --- > Traceback (most recent call last): ... > "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", > line 55, in unsign > raise BadSignature('Signature "%s" does not match' % sig) > django.core.signing.BadSignature: Signature "F6V0Dr_SvBsx5-cY8vcvLXrX8tA" > does not match ... > > The api_key on mailman-hypperkitty.cfg, SECRET_KEY and MAILMAN_ARCHIVE_KEY > on setting.py are the same. Of those three, the api_key on mailman-hypperkitty.cfg and MAILMAN_ARCHIVE_KEY must match. SECRET_KEY is different. It is a Django thing and has nothing to do with the others. See https://docs.djangoproject.com/en/5.0/ref/settings/#secret-key If you changed it, that's the issue. If you know what it was previously, you could set the previous value in SECRET_KEY_FALLBACKS, see https://docs.djangoproject.com/en/5.0/ref/settings/#secret-key-fallbacks -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

[MM3-users] Re: Bulk delivery status change?

by Mark Sapiro

On 11/10/24 08:34, Odhiambo Washington via Mailman-users wrote: > On Sun, Nov 10, 2024 at 7:16 PM Stephen Daniel <swd(a)pobox.com> wrote: > >> Mistakes were made, and for while every single outbound email bounced. >> I've fixed the mistakes, but now in my largest and most active email list, >> every single user's delivery status is "Disabled by Bounces". >> >> Is there a way to bulk fix this? Or do I have to go into each user, one at >> a time, and fix them? > > Please see this thread: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… The script in that post does all lists. For a single list see https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… but note that the command line ``` $ shell -l list(a)example.com ``` should be ``` $ mailman shell -l list(a)example.com ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 3 weeks

[MM3-users] Re: Language confusion in held mail notifications

by Mark Sapiro

On 9/22/21 2:16 AM, Henrik Rasmussen wrote: > I just upgraded from Mailman 3.2.0 (La Villa Strangiato) to Mailman 3.3.4 (Tom Sawyer) - Docker Mailman v0.3.12. As the language is not possible to set, and the default language is English, I set my user profile to Spanish and the list config to German, to figure out where the changes would take affect. > > After sending a mail to the list as the moderated list user, the resulting notification returned to the users email address is mostly in German, but the reason indicated is in Spanish "El mensaje proviene de un miembro moderado". I am unable to duplicate this in Mailman 3.3.5rc1. I set the list's language to German and a moderated user's language to Spanish. The held message notice to the user was entirely in Spanish and the notice to the admin was entirely in German. User Notice --------------------------------------------------- Date: Thu, 23 Sep 2021 17:12:50 -0700 From: test-bounces(a)msapiro.net To: mark(a)msapiro.net Subject: Su mensaje a test(a)msapiro.net espera la aprobación del moderador Su mensaje a la lista 'test(a)msapiro.net' con el asunto A test message Ha sido retenido hasta que el moderador de la lista pueda revisarlo y aprobarlo. El mensaje está siendo retenido por: El mensaje proviene de un miembro moderado O bien el mensaje será enviado a la lista, o bien recibirá una notificación con la decisión del moderador. --------------------------------------------------------------- Owner Notice -------------------------------------------------- Date: Thu, 23 Sep 2021 17:12:50 -0700 From: test-owner(a)msapiro.net To: test-owner(a)msapiro.net Subject: Der Beitrag test(a)msapiro.net von mark(a)msapiro.net muss genehmigt werden [-- Attachment #1 --] [-- Type: text/plain, Encoding: base64, Size: 0.5K --] Ihre Einwilligung als Administrator*in ist für folgende Nachricht an die Mailingliste nötig: Liste: test(a)msapiro.net Absender: mark(a)msapiro.net Betreff: A test message Die Nachricht wurde aus folgenden Gründen zurückgehalten: Die Nachricht kommt von einem moderierten Mitglied Besuchen Sie die Administrations-Seiten, um die Nachricht anzunehmen oder abzulehnen. [-- Attachment #2 --] [-- Type: message/rfc822, Encoding: 7bit, Size: 0.8K --] Date: Thu, 23 Sep 2021 17:12:48 -0700 From: Mark Sapiro <mark(a)msapiro.net> To: test(a)msapiro.net Subject: A test message User-Agent: Mutt/1.9.4 (2018-02-28) Give this a try. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan [-- Attachment #3 --] [-- Type: message/rfc822, Encoding: 7bit, Size: 0.9K --] Date: Thu, 23 Sep 2021 17:12:50 -0700 From: test-request(a)msapiro.net Subject: confirm b903b34955e0268e33b011ff9c9ccb7667dce4f2 Wenn Sie auf diese Nachricht antworten und den Subject: Header unverändert lassen wird Mailman die zurückgehaltene Nachricht verwerfen. Tun Sie dies, wenn es sich bei der Nachricht um Spam handelt. Wenn Sie auf die Nachricht antworten und einen Approved: Header mit dem Listenkennwort einfügen, wird Nachricht für die Veröffentlichung auf die Liste genehmigt. Der Approved: Header kann auch in der ersten Zeile des Textes der Antwort erscheinen. --------------------------------------------------------------- -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

[MM3-users] Re: hyperkitty.views.mailman Could not archive the email with message-id '<snip>': A string literal cannot contain NUL (0x00) characters

by Mark Sapiro

On 3/11/21 12:59 PM, Gilles Filippini wrote: > Hi, > > I have this error message repeating endlessly into the mailman-web logs. > The related list is an open one on which we receive spam sometimes. I > understand these emails can me malformed and cause this error. How to > deal with them? They can't stay forever at the hyperkitty door. The message is queued at `var/archives/hyperkitty/spool/`. The files in that directory are Python pickles. You can examine them with the `mailman qfile` command and delete the spam ones. You will also find log messages in `var/logs/mailman.log` with tracebacks, but presumably you know that as one such is the Subject: of this message. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users] Re: Default setting for Delivery status

by Mark Sapiro

On 10/10/22 15:31, Mark Dale via Mailman-users wrote: > > Where and how do I set the default setting of "Delivery status" to be > "Enabled". It already is. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/core/constants… > I'm not seeing any clues in mailman3-web/settings.py > > At the moment, a new subscriber is neither "Enabled" or "Disabled". That's because the member's list based preferences for that list are not set, so we fall back to address based preferences if set and finally to global preferences where Delivery status is enabled. Log in to Postorius and select Mailman settings from the dropdown on the upper right at your user name to see more. New list members don't have and list based preferences for that list and just fall back to their address based preferences or global preferences. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: Message getting held due to max number of recipients and maximum message size

by Mark Sapiro

On 9/22/23 11:37, Wong, Wesley wrote: > > Currently, the settings are set to 0 for both settings on the list so I am not sure where mailman is getting the default settings. Is this default hard coded somewhere in the Mailman core? The version of Mailman running is 3.3.6. This is very strange. Are you certain the list's settings are 0? Are there possibly two lists in different domains or otherwise similar names and you are looking at the wrong one? The only place where the defaults are set is in mailman/styles/base.py and this only affects the default settings for a new list. The values in the ``` Message has more than 10 recipients The message is larger than the 40 KB maximum size ``` messages come from the list's settings. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

[MM3-users] Re: configuring postfix local recipient table

by Mark Sapiro

On 4/29/25 00:17, Alexander Inzinger-Zrock via Mailman-users wrote: > [Status] > > Suggestion: > > It seems, we are wasting to much time with a probably messed up system. > I suggest, that i do as initially suggested [1] and start over with a > reinstall. > > Last idea before that would be to > > 1. delete the files: > > -rw-r--r-- 1 mailman mailman 0 Mar 21 11:58 postfix_domains > -rw-r--r-- 1 mailman mailman 12K Mar 24 11:44 postfix_domains.db > -rw-r--r-- 1 mailman mailman 0 Mar 21 11:58 postfix_lmtp > -rw-r--r-- 1 mailman mailman 12K Mar 24 11:44 postfix_lmtp.db > > 2. restart services > > 3. test if programms make new files > > 4. report to mailinglist > > Would that be of interest to someone? Yes. Also, is there anything in Mailman's logs from the time you ran `mailman aliases`? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months

[MM3-users] Re: New releases

by Mark Sapiro

On 6/9/20 1:05 AM, Danil Smirnov wrote: > On Tue, 9 Jun 2020 at 00:05, Mark Sapiro <mark(a)msapiro.net> wrote: > >> After you upgraded did you run these django-admin commands? >> ``` >> django-admin collectstatic --clear --noinput --verbosity 0 >> django-admin compress >> django-admin compilemessages >> django-admin migrate >> ``` >> These 4 commands should be run after every update to Postorius, >> HyperKitty or django_mainlman3. >> > > Hm, interesting... Could you point me to some related docs please? The documentation is weak and should be updated, but see <https://docs.mailman3.org/en/latest/upgrade-3.2.html#migration-steps> > To upgrade, I've just bumped app versions in my Dockerfiles, built and > restarted... > Mailman-core worked right away with no issues. > Mailman-web (Hyperkitty) failed with the error: > > ---------- > ERROR 2020-06-08 19:46:41,942 14 django.request Internal Server Error: > /hyperkitty/ > Traceback (most recent call last): > File "/usr/lib/python3.6/site-packages/compressor/base.py", line 282, in > precompile > mod = import_module(mod_name) > File "/usr/lib/python3.6/importlib/__init__.py", line 126, in > import_module > return _bootstrap._gcd_import(name[level:], package, level) > File "<frozen importlib._bootstrap>", line 994, in _gcd_import > File "<frozen importlib._bootstrap>", line 971, in _find_and_load > File "<frozen importlib._bootstrap>", line 953, in _find_and_load_unlocked > ModuleNotFoundError: No module named 'sassc -t compressed {infile} > {outfile}' ... > I've fixed the error by removing the older file which is > /opt/mailman-web-data/static/hyperkitty/libs/bootstrap/stylesheets/_bootstrap.scss > > After that everything seems to be working fine. I'm not sure about the above error. 'sassc -t compressed {infile} {outfile}' is defined in `settings` COMPRESS_PRECOMPILERS, but it is a command to be run as part of `django-admin compress`, not a module to be imported. Possibly running `django-admin compress` before starting Hyperkitty would have avoided this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

[MM3-users] Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive

by Mark Sapiro

On 3/2/21 1:55 PM, David Partain via Mailman-users wrote: > On Tue, 2021-03-02 at 13:43 -0800, Mark Sapiro wrote: >> >> Unless you want to remove the Ubuntu package and install everything >> with >> pip, you need to just stick with what you have that at least partly >> works and we'll try to determine how to fix the utf8mb4 issue. > > Hi Mark, > > You're a very patient soul. Thank you. > > Yes, I'm resigned to exactly that. The archives when folks send emojis > will break, but that's just life. Mail will get sent. Heck, I guess I > could edit the file in /var/lib/mailman3/archives/hyperkitty/spool to > get rid of the emoji in the worst case... You would need to do that, because once one of the `emoji` messages gets into /var/lib/mailman3/archives/hyperkitty/spool, I think no further messages are archived because mailman_hyperkitty tries to process the queued messages first and throws the exception. But, it's still not clear to me whether you have removed the settings_local.pyc and restarted uWSGI or whatever interfaces to Django. > Once I've migrated my 1500 mailing lists (this weekend) to the server, > I'll think about how to get a new server set up that I can shift to and > I'll install that with pip, since that'll clearly give me something > more supportable. > > Is Ubuntu 20.04 a reasonable platform for that? Yes it is. FWIW, this list runs bleeding edge Mailman 3 on an Ubuntu 14.04 server (yes we should upgrade), the only issue being that we needed to install Python 3.6 (the latest at the time) from source because the native Python 3 was 3.4 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users] Re: Time Zone Issue in Postorius

by Mark Sapiro

On 2/4/22 09:48, Andy Summers wrote: > Hello, > > I'm encountering an error that sounds similar to this previous thread: > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > I've tried setting my TIME_ZONE to 'UTC' in my settings.py and > settings_local.py files (and restarting Mailman), but when I check the > datetime for a held message in Postorius, the datetime seems to be > pushed +8 hours unexpectedly. > > My Postorius account time zone is set to "US/Pacific". The appropriate setting for Django is always `TIME_ZONE = 'UTC'`because the time passed from Mailman core is a naive datetime.datetime object and is actually UTC. This should then display the time in your account timezone since Postorius 1.3.4. See https://gitlab.com/mailman/postorius/-/merge_requests/531 If this isn't working in Postorius >=1.3.4, it's a Django issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: Templates do not work

by Mark Sapiro

On 4/28/22 02:50, Eggert Ehmke wrote: > I created some templates in Postorius to get > personalized notifications when there are > moderator requests. The notifications I get seem to > be the standard texts. When I look into mailman/ > mm/var/templates > the directory is empty. Nevertheless, the templates I > create in Postorius seem to be stored (where?), they > just do not work. As Steve said the templates are stored in the database. I suspect the issue is and incorrect value for `POSTORIUS_TEMPLATE_BASE_URL` in your Django settings. This is used to construct the URI to retrieve the template. The URI is stored in the `template` table in the database. It is normally just `http(s)://host.name/` If this is the issue, after correcting the setting and restarting the web service, you will need to delete and re-enter the template in Postorius to correct the `template` table entry. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: combine postorius and hyperkitty into one Apache vhost

by Mark Sapiro

On 12/29/22 05:51, Wolfgang Rosenauer wrote: > Hi, > > I'm in the process to set up a new mailman3 site. > (Migrating from mailman2) > > There are RPMs for my distribution which integrate postorius and > hyperkitty with uwsgi. I think you'll be much happier if you don't use the distro's RPMs which are probably out of date and instead follow <https://docs.mailman3.org/en/latest/install/virtualenv.html>. Those instructions use uWSGI as a WSGI interface, but Gunicorn <https://gunicorn.org/> is what is used on the site supporting this list. The advantages of Gunicorn are it's already installed as a dependency of Mailman core, and it's what the Mailman developers are more familiar with. I'll work on updating <https://docs.mailman3.org/en/latest/install/virtualenv.html> to include Gunicorn as an alternative. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 7 months

[MM3-users] Re: Internal Server Error, Need 2 values to unpack in for loop; got 1

by Mark Sapiro

On 7/11/24 11:06 AM, Elias Rudberg wrote: > Hello! > > I am using mailman3 (version 3.3.8) and it mostly works fine, but > sometimes (usually several times every day) the error below appears. > > Any suggestions for what could be done about this? ... > Here is what the error message looks like: > ------------------------------------------- > > [Django] ERROR (EXTERNAL IP): Internal Server Error: > /mailman3/postorius/lists/ > > Internal Server Error: /mailman3/postorius/lists/ > > ValueError at /postorius/lists/ > Need 2 values to unpack in for loop; got 1. Can you get the page at /mailman3/postorius/lists/ and /mailman3/postorius/lists/?all-lists If those are OK, look in your web server access logs for `GET /mailman3/postorius/lists/` messages with the same timestamp as those errors. Is there some bogus query fragment on those? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] Re: Django Internal Server Error on held_messages

by Mark Sapiro

On 3/24/22 04:02, Hasan Berkay Çağır via Mailman-users wrote: > Hello, > > We've been running a Mailman3 instance with Debian 10's official package: > > Mailman Core Version: GNU Mailman 3.2.1 (La Villa Strangiato) > Mailman Core API Version: 3.0 > Mailman Core Python Version: 3.7.3 (default, Jan 22 2021, 20:04:44) [GCC 8.3.0] > > For some reason, and only on some lists, when we try to see held messages on Postorius, we get an error message "An error occurred while processing your request." and the following error email: > > """ > Internal Server Error: /postorius/lists/list.example.com/held_messages As Andrew suggests, you will probably find exceptions with tracebacks in Mailman core's mailman.log. This is probably /var/log/mailman/mailman.log in the Debian package. If you find such and you can't determine the problem from them, post one here. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: Error while Approving a Post Through Email

by Mark Sapiro

On 12/14/22 01:45, Stephen J. Turnbull wrote: > Alex A.J. writes: > > line 1132, in identify_record > > raise exc.UnknownHashError("hash could not be identified") > > passlib.exc.UnknownHashError: hash could not be identified > > Dec 13 17:01:41 2022 (2677611) SHUNTING: > > 1670931101.6040337+d5806b00b2b9d03f25db396639f66f3a26516178 > > This looks like maybe you have the wrong password? > > Maybe Mark or Abhilash has a more concrete suggestion, I've never used > the Approved header with Mailman 3. I don't have more time to look at this now, but I think it's a bug. This patch ``` --- a/src/mailman/rules/approved.py +++ b/src/mailman/rules/approved.py @@ -140,6 +140,7 @@ class Approved: mpw = mlist.moderator_password else: mpw = mlist.moderator_password.decode('utf-8') + mpw = config.password_context.encrypt(mpw) is_valid, new_hash = config.password_context.verify(password, mpw) if is_valid and new_hash: # Hash algorithm migration. ``` may fix it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 7 months

[MM3-users] Re: 404 on fresh install (Debian11)

by Mark Sapiro

On 3/23/23 08:42, Odhiambo Washington wrote: > On Thu, Mar 23, 2023 at 6:13 PM thomas--- via Mailman-users < > mailman-users(a)mailman3.org> wrote: > >> Thanks both of you. I didn't know Debian11 version is out of date. I will >> try using pip. >> > No. Debian 11 is _not_ out of date. It's just that the preferred and easy > to support installation method is using the virtualenv. The Debian stable mailman packages definitely ARE out of date. bullseye (stable) has Mailman core 3.3.3 and django-mailman3 1.3.5 (current releases are 3.3.8 and 1.3.9 respectively) It is unclear what Postorius and HyperKitty versions are in mailman3-web 0+20200530-2. bookworm (testing) and sid (unstable) do have current versions of Mailman core and django-mailman3 and possibly mailman3-web 0+20200530-2.1 has current Postorius and HyperKitty, but those are generally not the Debian packages that most users would install. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: Postfix SMTP REJECT non-subscribers

by Mark Sapiro

On 7/10/24 12:26 AM, Matthew Blissett via Mailman-users wrote: > > With Mailman 2, I have configuration and scripts to reject non-members > from posting to lists _during the SMTP connection_. This is better than > bouncing (no backscatter), better than discarding messages (the user > finds out) and better than moderation (spammy messages aren't forwarded > to external email systems). > > > The configuration and scripts are described here: > https://code.launchpad.net/~jimpop/mailman/check_subscriber > > > Is anything like this built-in to Mailman 3? I cannot find it in Gitlab. No. nothing similar is built in to Mailman 3, but it shouldn't be difficult to implement. It could be done with a milter as in the above implementation, or it could be done by modifying the _handle_RCPT function in mailman/runners/lmtp.py to check if the sender is a member of the recipient list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] Re: mail stuck in "out" queue

by Mark Sapiro

On 12/10/24 07:44, pdw(a)mythic-beasts.com wrote: > > The messages were constantly re-appearing in the "out" queue with different file names (I assume they were going via the retry queue). First check to ensure there are no files in Mailman's var/templates/ directory that are not readable by the Mailman user. That can cause this issue. > After multiple restarts trying to get some debug information, the hard loop seems to have stopped recurring, and the messages are sat in the "shunt" queue. They've not been delivered to recipients, but they are in the hyperkitty archive. The shunted messages should have a SHUNTING entry with an exception and traceback in mailman.log. If there were files unreadable by Mailman in Mailman's var/templates/ directory and you have corrected that, you can move the shunted messages back to their original queue with `mailman unshunt`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 3 weeks

[MM3-users] Re: mailman3 on new Debian 12 installation, got ssl apache working on all URLs except /mailman3

by Mark Sapiro

On 3/31/25 06:26, Philip Bondi wrote: > My /etc/mailman3/urls.py is empty. > > Should I, like it indicates in https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > cp /opt/mailman/venv/lib/python3.11/site-packages/mailman_web/urls.py /etc/mailman3/urls.py > chown mailman:mailman /etc/mailman3/urls.py > and add to /etc/mailman3/settings.py > > ROOT_URLCONF = 'urls' You can do all of that, but it's probably unnecessary. What is in /opt/mailman/venv/lib/python3.11/site-packages/mailman_web/urls.py? compare it to https://gitlab.com/mailman/mailman-web/-/blob/master/mailman_web/urls.py > After completing above, https://systemdatabase.ca/mailman3 still gives > Service Unavailable It appears that https://systemdatabase.ca/postorius works so the issue is almost certainly that your urls.py is missing path('mailman3/', include('postorius.urls')), -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months

[MM3-users] Re: Relay Access Denied

by Mark Sapiro

On 7/22/25 10:25 AM, jkoral(a)luc.edu wrote: > Here is what I have in postfox_lmtp. Do I need to add another line for joetest(a)lists.luc.edu as well? > > joetest(a)listservnew.luc.edu lmtp:[127.0.0.1]:8024 > joetest-bounces(a)listservnew.luc.edu lmtp:[127.0.0.1]:8024 > joetest-confirm(a)listservnew.luc.edu lmtp:[127.0.0.1]:8024 > joetest-join(a)listservnew.luc.edu lmtp:[127.0.0.1]:8024 > joetest-leave(a)listservnew.luc.edu lmtp:[127.0.0.1]:8024 > joetest-owner(a)listservnew.luc.edu lmtp:[127.0.0.1]:8024 > joetest-request(a)listservnew.luc.edu lmtp:[127.0.0.1]:8024 > joetest-subscribe(a)listservnew.luc.edu lmtp:[127.0.0.1]:8024 > joetest-unsubscribe(a)listservnew.luc.edu lmtp:[127.0.0.1]:8024 If you want to address the lists @lists.luc.edu, the list names should be, e.g. joetest(a)lists.luc.edu, not joetest(a)listservnew.luc.edu. If you want to be able to use either domain for list mail, that's more involved. If you want this, say so and as I have time I can make suggestions., but I suspect you really only want to use the lists.luc.edu domain. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 week, 3 days

[MM3-users] Re: Installation Questions [Installation}

by Mark Sapiro

On 11/3/24 11:31, Arte Chambers via Mailman-users wrote: > Hello everyone, > > I'm running Ubuntu 24.10 and following the Virtualenv instructions > <https://docs.mailman3.org/en/latest/install/virtualenv.html#setup-mailman-u…>. > When creating the mailman user per the instructions I find that the mailman > user doesn't have sufficient permissions to do things later in the > installation such as creating files in /etc. What steps should I take to > ensure that the mailman user has the correct permissions to install the > Mailman app. We should probably cover this in the docs, but for /etc/mailman3, you should do ``` sudo mkdir /etc/mailman3 sudo chown mailman:mailman /etc/mailman3 sudo chmod 755 /etc/mailman3 ``` Then you can create all the subordinate files as the mailman user. For other things like the systemd service and the postfix and web server configs, you need to do them as root (via sudo). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 4 weeks

[MM3-users] Re: Mail configuration

by Mark Sapiro

On 03/23/2018 10:05 AM, Darren Smith wrote: > > We have been told that "warming up" the IP is the way to go - that is, > cutting over just some of the traffic a little at a time. So what I am > looking for is a way for all mail on our domain to be sent to our current > mailman installation, and based on some configuration (certain mailing > lists?) certain emails being sent out to the list subscribers will first be > forwarded to the new server and be sent from the new IP address. > > Does that make sense? > > Does anyone know a way that mailman/postfix can be configured to accomplish > this? Is this Mailman 3 or Mailman 2.1? The Mailman side of this would be different depending on which. If it's Mailman 2.1, a better list is mailman-users(a)python.org <https://mail.python.org/mailman/listinfo/mailman-users> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 4 months

[MM3-users] Re: Fresh installation mailman3-suite via "pipx" - any experiences yet?

by Mark Sapiro

On 1/25/24 12:20, Odhiambo Washington wrote: > On Thu, Jan 25, 2024 at 4:43 PM Wikinaut <mail(a)tgries.de> wrote: > >> I recently found the "pipx" wrapper very useful and wanted to ask you if >> this could be facilitate the fresh installation of the mailman3-suite. >> Has anyone in the list already experiences installing mailman and >> mailmanweg through "pipx"? ... > > if pipx doesn't create a virtual > environment, then there is no difference with installing MM3 using apt! pipx apparently does create virtual environments. See https://pipx.pypa.io/stable/comparisons/ The thing there that concerns me is "pipx replaces a subset of pip's functionality; it lets you install cli applications but NOT libraries that you import in your code." What does this say about the multiple dependencies that we install. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

[MM3-users] Re: Question: What happens if I delete a user from all lists and that user is sole owner of some list?

by Mark Sapiro

On 4/3/24 04:07, David Partain via Mailman-users wrote: > > I might have been able to manage them using the command line on the old > installation, but there is no 'mailman delmembers' on that box. There is bin/remove_members. > My question is: If one of these users is the sole owner of a list, what > will happen? Will the user be deleted and that list now owner-less? > Will mailman refuse to delete that user until I add a new owner? The `mailman delmembers` command deletes only members, i.e those with MemberRole member. It does not delete owners, moderators or nonmembers. You may also be interested in the script at https://www.msapiro.net/scripts/clean_users.py -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

[MM3-users] Re: Mailman3 Issue

by Mark Sapiro

On 7/13/18 7:10 AM, jon.kokko(a)us.fujitsu.com wrote: > I've gone through a few iterations of recreating the domains with the same result. > > After the commented header, my postfix_domains contains: > > <empty line> > domain.org<single whitespace>domain.org > <empty line> OK. Apparently the first sentence of the OP in this thread, "For some weird reason, the file /mailman/var/data/postfix_domains has a whitespace added to every mail domain.", doesn't apply in your case and may have been unrelated to the actual issue throwing the exception. The "KeyError" is also misleading. In the OP traceback at least that comes during error handling of the original exception. See the line During handling of the above exception (HTTP Error 500: b'A server error occurred. Please contact the administrator.'), another exception occurred: You need to look in mailman.log to see if you can find more info about the '500'. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years

[MM3-users] Re: Invalid FilterAction: discard. Treating as discard

by Mark Sapiro

On 6/6/19 6:02 AM, Henrik Rasmussen wrote: > > Still, attachments (PDF) is removed by Mailman. I as the list admin to send a new mail, but hold it back, to see what type it is. You have to add the MIME types for the attachments you want kept the the list's pass_types. You need to do this via mailman shell or REST as it isn't currently exposed in Postorius. Here's an example from a list that wants to accept PDFs as well as word processing and spreadsheet documents. Note that nappdf and x-pdf are uncommon PDF subtypes that I have seen. ['multipart', 'message/rfc822', 'text/plain', 'text/html', 'application/pdf', 'application/nappdf', 'application/x-pdf', 'application/rtf', 'application/vnd.oasis.opendocument.spreadsheet', 'application/vnd.openxmlformats-officedocument.spreadsheetml.sheet', 'application/vnd.ms-excel', 'application/vnd.oasis.opendocument.text', 'application/vnd.openxmlformats-officedocument.wordprocessingml.document', 'application/msword' ] -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 1 month

[MM3-users] Re: Chinese characters in list name shows question mark (?)

by Mark Sapiro

On 10/23/19 5:22 PM, Franklin Weng wrote: > > Franklin Weng 於 2019/10/24 上午8:05 寫道: >> >> What may be possible wrong that I couldn't see Preferred Language >> settings in the web interface? > > I got it. It is implemented in postorius 1.2.5 but my Debian buster > contains 1.2.4-1 for now. Actually, there is no 1.2.5. The next release after 1.2.4 is 1.3.0, but you can still set preferred_language for the list using the REST API or mailman shell. For example in mailman shell $ mailman shell -l zh-l10n.lists.linux.org.tw Welcome to the GNU Mailman shell The variable 'm' is the zh-l10n.lists.linux.org.tw mailing list >>> m.preferred_language <Language [en] English (USA)> >>> m.preferred_language = 'zh_TW' >>> m.preferred_language <Language [zh_TW] Chinese (Taiwan)> >>> commit() -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

[MM3-users] Re: Migration from 2.1 to 3

by Mark Sapiro

On 12/20/19 7:26 AM, brunol(a)agro.uba.ar wrote: > Hi, > > I am in the process to migrate an old 2.1 installation to 3.2.1 (Debian 10.1) > Following the 2.1 to 3 docs: > - Create a new list > - Use the import21 command > The command runs successfully (at least no errors in stdout). There is a problem when sending an email to the newly imported list, the message never get send to the members. I do get moderation emails, and if i do a mass subscribe, the welcome email is received by the new members. Are you saying that when a post is sent to the list, it is held for moderation, and when you approve it, it is not delivered? Or are the moderation messages from some other lists? Are there any non-digest members with delivery enabled? Is the MTA (which MTA) delivering the message to Mailman's REST runner? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

[MM3-users] Re: I like your style, but what is it?

by Mark Sapiro

On 1/26/21 9:12 PM, Stephen Willey Mats Mats wrote: > > How do I get a dump of list settings for each style. See <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/styles/base.py> and <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/styles/default…>. > Thanks, > steve > > p.s. the search on https://mailman.readthedocs.io/en/latest/README.html gives results but every link needs to have ‘projects/mailman/‘ removed from the url to work. Or have its domain changed from `mailman.readthedocs.io` to `docs.mailman3.org`. If you start at <https://docs.mailman3.org/en/latest/> or just go to <https://docs.mailman3.org/projects/mailman/en/latest/README.html>, I think everything works. Granted, search from <https://mailman.readthedocs.io/en/latest/README.html> should work too, but I'm not sure offhand whether its a Sphinx or a Read the Docs issue or how to fix it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: Mailman 3 api php

by Mark Sapiro

On 03/14/2017 05:24 AM, david.terni(a)gmail.com wrote: > Hi, > I apologize if this is't the right place but I don't understand how connect mailman 3 with api and php/CURL. It's possibile to do it? I tried to use the same url used with mailman2 but doesn't work. Mailman 3 is completely different from Mailman 2 in this respect. While it would be possible to use php/CURL to post to Postorius analagously to posting to the Mailman 2 web UI, this is not how it is done. Mailman 3 core exposes a RESTful api on localhost. Both Postorius and HyperKitty use this UI to communicate with the core and you should too. Start at <http://mailman.readthedocs.io/en/release-3.0/src/mailman/rest/docs/basic.ht…>. The "Previous" link will take you to the section on Addresses and the "Next" links will take you through the rest of the REST api. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 4 months

[MM3-users] Re: Upgrade path

by Mark Sapiro

On 08/08/2017 04:42 AM, David Krantz wrote: > > What is the rekommended way to upgrade to the newest version? (newest > _usable_ version, of course)? Is it docker-only with a migration from > the current solution to a docker based? If so, any ideas or pointers > on how to go about this? You may find this wiki article helpful <https://wiki.list.org/x/17891998>. I started with bundler on both this (lists.mailman3.org) and the mail.python.org installs, but have been updating from the heads of the various gitlab branches since very early on. At the moment, these installations are somewhat ahead of the 3.1 release, but I am not updating as the latest core has dropped Python 3.4 support, and I haven't yet installed Python 3.5 or 3.6 on these (Ubuntu 14.04) servers. (I will probably install 3.6 from source at some point.) Please feel free to ask here if you have more specific questions. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 11 months

[MM3-users] Re: Welcome Message

by Mark Sapiro

On 4/16/19 9:18 AM, brian(a)emwd.com wrote: > Thanks Mark. I added the POSTORIUS_TEMPLATE_BASE_URL to my settings: > > /opt/mailman/web/settings_local.py > > Now I get the following errors: ... > requests.exceptions.SSLError: HTTPSConnectionPool(host='mailman3.emwd.com', port=443): Max retries exceeded with url: /postorius/api/templates/list/testlist.mailman3.emwd.com/list:user:notice:welcome (Caused by SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:841)'),)) > Apr 16 15:38:44 2019 (28) 172.19.199.3 - - "POST /3.1/members HTTP/1.1" 500 59 > > I am confused by the SSL errors. I have a valid SSL certificate installed on mailman3.emwd.com. These errors occur whether the POSTORIUS_TEMPLATE_BASE_URL is using http or https. I'm confused too. What happens if you just do in a python3 interactive session >>> import requests >>> response = requests.get('https://mailman3.emwd.com/postorius/api/templates/list/testlist.mailman3.em…') and if you get this far >>> response.status_code >>> response.text -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 3 months

[MM3-users] Re: Hyperkitty issue(s)

by Mark Sapiro

On 5/28/20 3:00 PM, brylon(a)oit.rutgers.edu wrote: > > I seem to have archives working on posts now, however, during my troubleshooting I moved away some archives/hyperkitty/spool/*.pck files and was wondering if/when I put them back is there a django-admin/hyperkitty command to run and process those again? (and if not I'm pretty confident the next post to any list? would slurp them all into hyperkitty anyway?) Your confidence is not misplaced. Every time mailman_hyperkitty receives a post from Mailman to be archived, it first tries to reprocess all the messages queued in archives/hyperkitty/spool/. There is no Django command because neither Django nor HyperKitty is directly involved. This is all mailman_hyperkitty which is a shim between Mailman and HyperKitty. Mailman talks to mailman_hyperkitty directly via the configured mailman_hyperkitty.Archiver class ``` [archiver.hyperkitty] class: mailman_hyperkitty.Archiver ``` and mailman_hyperkitty talks to HyperKitty via the API at the base_url configured in mailman-hyperkitty.cfg. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: File "/usr/lib/python2.7/httplib.py", line 1148, in getresponse raise ResponseNotReady()

by Mark Sapiro

On 10/7/20 12:39 AM, r.woithe(a)callassoftware.com wrote: > Hallo, > cause of we import our lists from mailman 2.1 to mailman3 as Alex Schuilenburg did, i did take a look in hyperkitty_sender and find an address like it is discribed above ( "firstname surename"@... ); i did insert,update and delete this address. > Now the sync is working and all is fine. Good. I'm glad you solved it. > Well, excuse my ignorance; cause of i have import the patch and set the logging level to debug but i could not find any more detailed error messages into the log files. I don't know why the patch didn't work. It should have produced warning level messages in the Django log as configured in settings(_local).py. Anyway, the issu is solved and you can remove the patch. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: Customising hyperkitty and postorius

by Mark Sapiro

On 11/18/20 5:16 PM, peter(a)chubb.wattle.id.au wrote: > > Hi, > I've put up a mailman3 instance, with hyperkitty enabled, and > imported all my mailman2.1 archives -- it all seems to be > working. > > How do I now customise the look and feel of my site? > > In particular, I'd like to render archived emails with a > monospace font, and I'd like to change the colour scheme and > styles of all the pages to match other pages on the same website. HyperKitty will display a message in monospace if you click the 'A' icon at the bottom of the message. I don't know offhand how you would make that the default. For styles, they are mostly SCSS in the directory hyperkitty/static and CSS in the directory postorius/static/postorius. I think you'd have to find the relevant styles and edit them. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: Error Logging - what changed with the New Year releases?

by Mark Sapiro

On 1/14/23 01:19, Odhiambo Washington wrote: > 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. Nothing in those releases per se would affect this. This is Django and django-allauth. Perhaps when you updated the Mailman packages, you also updated these dependencies. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] Re: Configure new list via REST API - trying to add moderators

by Mark Sapiro

On 9/11/24 14:32, Andy Matthews wrote: > One quick follow up. I'm making a subscribe request for a moderator. I'm passing in list_id, subscriber, and role (moderator). The request is returning a 201 response, but when I shell into the mailman server and inspect the list directly it shows there are no moderators. I've confirmed the list id, and I can see a list of regular members, but when I use the command line, the only version of the query which shows members is the default: `mailman members <list name>`. Does `mailman members <list name> --role moderator` show the moderator? The following works for me: ``` curl -urestadmin:restpass \ --request POST \ -H 'Content-Type: application/json' \ --data-binary '{"list_id": "list.example.com", "subscriber": "someone(a)example.com", "role": "moderator"}' \ http://localhost:8001/3.1/members ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 3 weeks

[MM3-users] Re: Re-send subscription response and file permission error in queue

by Mark Sapiro

On 9/11/20 2:18 PM, Mark Sapiro wrote: > On 9/8/20 10:56 PM, accounts-mailman(a)holbrook.no wrote: >> A user sent subscription request to the `..-join@` address of a list. Email domain wasn't set up properly, so response got rejected. Now, if the user tries to send another request, no reponse comes back. In the log I find a python stack trace saying subscription already pending. >> >> ``` >> Sep 08 10:32:44 2020 (19918) Traceback (most recent call last): >> File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 171, in _one_iteration >> self._process_one_file(msg, msgdata) >> File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 264, in _process_one_file >> keepqueued = self._dispose(mlist, msg, msgdata) >> File "/usr/lib/python3/dist-packages/mailman/runners/command.py", line 196, in _dispose >> mlist, msg, msgdata, parts, results) >> File "/usr/lib/python3/dist-packages/mailman/commands/eml_membership.py", line 104, in process >> ISubscriptionManager(mlist).register(subscriber) >> File "/usr/lib/python3/dist-packages/mailman/app/subscriptions.py", line 520, in register >> list(workflow) >> File "/usr/lib/python3/dist-packages/mailman/app/workflow.py", line 69, in __next__ >> return step() >> File "/usr/lib/python3/dist-packages/mailman/app/subscriptions.py", line 227, in _step_sanity_checks >> raise SubscriptionPendingError(self.mlist, self.address.email) >> mailman.interfaces.subscriptions.SubscriptionPendingError >> ``` > > > I'll look at this when I get some time. I'm still catching up after > being off line for 12 days. This exception should also send a response to the user's email saying "User <user(a)example.com has a pending subscription for list(a)example.net" Was this sent? To fix, >> How can I remove the pending subscription, or re-send the response email? > > In Postorius, pull down Subscription Requests and select Pending > Confirmation and delete the request. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: Five Year Old Issue

by Mark Sapiro

On 3/13/21 8:07 PM, Brian Carpenter wrote: > Any chance to get this implemented in time for the next Mailman 3 core > release? > > https://gitlab.com/mailman/mailman/-/issues/19 > > It's been 5 years. It's not simple. The issue is delivery_mode is an attribute of the member, and when an email join command is processed, there is no member yet because the request is waiting confirmation so join processing can't just set the delivery_mode. It would require an additional argument to the ISubscriptionManager interface register() method for the delivery mode and then carrying that with the subscription workflow until there is actually a member to apply it to. And tests have to be written for all of that. That's not to say that it shouldn't be fixed, just that it's not something that can be knocked out in an hour. Anybody care to take it on? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users] Re: Issue converting table charset to utf8mb4 on mysql

by Mark Sapiro

On 3/23/24 12:14, Helio Loureiro wrote: > So the question is whether it is possible to change the types in this table. > > MariaDB [mailman3]> desc pendedkeyvalue; > +-----------+----------------+------+-----+---------+----------------+ > | Field | Type | Null | Key | Default | Extra | > +-----------+----------------+------+-----+---------+----------------+ > | id | int(11) | NO | PRI | NULL | auto_increment | > | key | varchar(255) | YES | MUL | NULL | | > | value | varchar(20000) | YES | MUL | NULL | | > | pended_id | int(11) | YES | MUL | NULL | | > +-----------+----------------+------+-----+---------+----------------+ > 4 rows in set (0.001 sec) > > key and value are varchar. Can any of them be changed to text instead? > Perhaps even both? I wouldn't bother. The keys and values in the pendedkeyvalue table should all be OK as latin1. That's why that table wasn't included in the migration at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/database/alemb… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

[MM3-users]Re: Request for assistance for fresh install of Mailman 3.0.3 and Python 3.4

by Mark Sapiro

On 05/28/2016 02:19 PM, Rubén Rivero Capriles wrote: > > (please note that I earlier replied this by email, as I notice that it doesn't show up on the list website I am reposting. Hopefully it won't be repeated. I've been looking through archive posts and some are double. Would be interesting to check if my reply from half an hour ago will eventually get posted. If it gets, my apologies!) Your initial reply was sent to the list members. It should have been archived, but it wasn't. That is my fault as I was experimenting with a Python 3 version of mailman.client which didn't work and then for a short time I had stopped the web services but not the core, and your post arrived during that window and was unable to be archived. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 2 months

[MM3-users] Re: [Mailman-Developers] Mailman 3.1 beta coming soon

by Mark Sapiro

On 12/10/2016 12:52 AM, Barry Warsaw wrote: > > Please do rebase and if you can, remilestone the MR to 3.1. We'll get it in. Done. There is one "temporary" commit in my MR to work around <https://github.com/sphinx-doc/sphinx/issues/3212> and get "docs" to pass. >> I can also work on Postorius. Also in this vein I have a question. >> Should the DMARC settings be added to the Alter Messages tab in the List >> Settings view or would it be better to have a separate DMARC Mitigations >> tab. > > My gut reaction is to add a separate DMARC Mitigations tab, but Florian and > Terri have final say I think. I have a WIP MR at <https://gitlab.com/mailman/postorius/merge_requests/194> that adds a tab. Maybe Florian and Terri can look at that and chime in. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 7 months

[MM3-users] Re: Log rotation

by Mark Sapiro

On 04/10/2018 03:04 PM, Darren Smith wrote: > > 1) Has anyone come up with a good log rotation strategy that doesn't > necessitate a restart of the service? I think Abhilash has answered this, but for completeness, here's what I use on lists.mailman3.org which uses nginx and gunicorn Mailman's logs /opt/mailman/mailman-bundler/var/logs/*.log { missingok sharedscripts su mailman mailman postrotate /opt/mailman/mailman-bundler/bin/mailman reopen &>/dev/null || true if [ -r /opt/mailman/mailman-bundler/var/gunicorn.pid ]; then PID=`cat /opt/mailman/mailman-bundler/var/gunicorn.pid` kill -s USR1 $PID fi endscript } mailman-web log /var/log/mailman-web/*.log { missingok notifempty delaycompress su mailman mailman } And here's mail.python.org with apache and mod_wsgi Mailman's logs /opt/mailman/mailman-bundler/var/logs/*.log { missingok sharedscripts su mailman mailman postrotate /opt/mailman/mailman-bundler/bin/mailman reopen &>/dev/null || true endscript } mailman-web log /var/log/mailman-web/*.log { missingok notifempty delaycompress su mailman mailman } -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 3 months

[MM3-users] Re: Splitting hosts: mta&core vs postorius

by Mark Sapiro

On 6/20/20 7:24 PM, Ruth Ivimey-Cook wrote: > > ... the Body of reply, with the JSON text: > > { > "start": 0, > "total_size": 1, > "entries": [ > { > "alias_domain": null, > "description": null, > "mail_host": "ch-bc.org.uk", > "self_link": "http://0.0.0.0:8870/3.1/domains/ch-bc.org.uk", > "http_etag": "\"5d474f0be89222e6122b6dc375a18ff01190419d\"" > } > ], > "http_etag": "\"c6f15186189ff5cf5b67f2d06dcf4ea97ea447a9\"" > } All these self_link references are generated from self.api.path_t which is a reference to (in the case of 3.1) <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/core/api.py#L6… which gets the host portion from config.webservice.hostname, i.e. the value of hostname in the webservice section of mailman.cfg, and actually <sigh>, looking back at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> that's exactly where you said you set it to 0.0.0.0. Change that to greyarea-post -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

[MM3-users] Re: Email to list owner on list creation only sent when using mailman create --notify command

by Mark Sapiro

On 6/9/24 5:26 PM, Perry Kollmorgen wrote: > Hi, > > This is only a minor issue, however as a nicety for new list owners I am hoping there is work around or something I have missed. > > I have the following file: templates/domains/<fqdn_listname/en/domain:admin:notice:new-list.txt > > When I use the mailman create command with the --notify option the new owners receives an email with the correct template info from the above file. > > However when I use mailmanclient python bindings or Postorius to create an list, there is no email sent. This is a bug. Currently only `mailman create` sends this notice, but as you note, list creation via rest should do it too. I have created https://gitlab.com/mailman/mailman/-/issues/1156 for this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 1 month

[MM3-users] Re: Mailing list welcome message won't update

by Mark Sapiro

On 1/9/25 13:58, via Mailman-users wrote: > > I have updated the welcome message for a mailing list by directly updating the file at: > file:///var/lib/mailman3/templates/lists/[redacted].lists.[redacted].org.au/en/list:user:notice:welcome > > I then restarted theses services: mailman3, mailman3-web and nginx. > > But when I test subsribe to the mailing list, the welcome message does not update. > > GNU Mailman 3.1.1 (Between The Wheels) > Postorius Version 1.1.2 These are extremely old - over 7 years. This may have something to do with the issue. There may be an issue in that the template table in the database is saying to look elsewhere. What do you get for a database query like ``` SELECT uri FROM template WHERE name = 'list:user:notice:welcome' AND context = '[redacted].lists.[redacted].org.au'; ``` where `[redacted].lists.[redacted].org.au` is the actual list-id. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 3 weeks

[MM3-users] Re: Installation problem: Ubuntu 18.10 mailman3-full. EMAIL_HOST_USER

by Mark Sapiro

On 2/4/19 6:30 PM, worik wrote: > Friends > > I am installing on a fresh ubuntu 18.10 using mailman3-full. > > Following http://docs.mailman3.org/en/latest/config-web.html after > http://docs.mailman3.org/en/latest/config-core.html and I have got to > point where I am a bit stumped. > > I have to set EMAIL_HOST_USER and EMAIL_HOST_PASSWORD > > I am unsure what I should use here. What sort of user? First of all, your primary resource for support of this package should be the packager, i.e. Debian. That said, presumably these are used to set smtp_user and smtp_pass in Mailman's config. These are described as: > # How to connect to the outgoing MTA. If smtp_user and smtp_pass is given, > # then Mailman will attempt to log into the MTA when making a new connection. > smtp_host: localhost > smtp_port: 25 > smtp_user: > smtp_pass: -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 5 months

[MM3-users] Re: Cannot setup announce-only mailing list

by Mark Sapiro

On 1/30/20 5:42 AM, Alberto Granzotto wrote: > > Of course, I want to keep this mailing list "read only" for members, and > I want only selected people to post to that mailing list. > > Any idea on how to achieve that? There is only one difference between the `Discussion` and `Announce` list styles, and that is for an `Announce` list, the `allow_list_posts` attribute is set to `False`. In turn, all that does is cause the List-Post: header to be set to NO rather than the list posting address. There is a discussion at <https://wiki.list.org/x/4030685> of how to set up an announce list for Mailman 2.1. Most of this translates straightforwardly to Mailman 3, although not all the relevant settings are exposed in Postorius. In short, you need to set this up manually using things like moderation settings and custom templates for the welcome message. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: mailman not starting, status is active (exited)

by Mark Sapiro

On 8/19/20 10:26 AM, Ricardo Kleemann wrote: > Hi, > > After quite a long time with no issues, I’ve started having a problem where mailman won’t start and I don’t see any clear error message Is this Mailman 3 or Mailman 2.1? If Mailman 2.1, the appropriate list in mailmain-users(a)python.org <https://mail.python.org/mailman3/lists/mailman-users.python.org/>. The usual cause of Mailman not starting in either case is a stale master lock. In either case, the locks are in a directory named locks/ in Mailman's hierarchy. In the Mailman 3 case if that directory contains files master.lck and master.lck|hhhh|pppp|tttttt (hhhh is the host name, pppp is a PID and tttttt is a timestamp) and the PID pppp is not running on the host, just remove those files. For Mailman 2.1, its the same except the names are master-qrunner master-qrunner.hhhh.pppp -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

[MM3-users] Re: Alias for a list name

by Mark Sapiro

On 10/6/23 09:49, Lars Bjørndal wrote: > > To run mm 3 through Postfix, I use local_recipient_maps and > transport_maps. > > What I want to achieve, is alias medlem(a)list.saf-org.no to > saf-medlem(a)list.saf-org.no > > I tried to put > > medlem(a)list.saf-org.no: saf-medlem(a)list.saf-org.no > > and get the following error when running newaliases: > > postalias: warning: /etc/aliases, line 231: name must be local > > Is it possible to do this aliasing in a simple way? If list.saf-org.no is a local domain, i.e. in mydestination, the alias would be medlem: saf-medlem(a)list.saf-org.no or more simply medlem: saf-medlem If list.saf-org.no is not a local domain it needs to be a Postfix virtual (alias or mailbox) domain and you need a virtual_alias_maps with an entry like medlem(a)list.saf-org.no saf-medlem(a)list.saf-org.no -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: Issue with mailman auto subscription

by Mark Sapiro

On 8/20/24 2:45 AM, Francisco Paco López wrote: > > I migrated my mailman 2 instance to mailman 3 some months ago. Some users have been reporting lately that auto subscriptions don't work anymore. In the affected list both the Subscription and un subscription policies are open, which means that normally a user that sends a "subscribe" mail automatically subs to the list. This works fine for users that have been subscribed in the past but not for new users. The latter get a mail stating that a confirmation is needed ("Your confirmation is needed to join the XXXX(a)my.lists.com mailing list"). I see nothing out of the ordinary in the mailman.log file and co. In Mailman 3 addresses need to be verified. Even if a list's subscription policy is open, if the request is from an unverified address, a confirmation request is sent to verify the address. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 1 week

[MM3-users] Re: Mailing list welcome message won't update

by Mark Sapiro

On 1/21/25 20:26, via Mailman-users wrote: > > I also found that the actual file containing the welcome message and footer message does not have the .txt extension for my dev instance. The files will not be used unless they have the .txt extension. You need to rename them to add the .txt extension. > root@mailman-dev:/var/lib/mailman3/templates/lists/[redacted].mailman-dev.dev.aws.[redacted].org.au/en# ll > total 12 > drwxr--r-- 2 mailman operations 4096 Jan 22 14:14 ./ > drwxr--r-- 3 mailman operations 4096 Oct 1 13:50 ../ > -rwxr--r-- 1 mailman operations 0 Oct 1 13:50 list:member:regular:footer* > -rwxr--r-- 1 mailman operations 506 Jan 22 14:12 list:user:notice:welcome* > > What is that * at the end of the file name mean? It means the file is executable. It shouldn't be so you can change the mode from rwxr--r-- to rw-r--r-- -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 1 week

[MM3-users] Re: What to backup?

by Mark Sapiro

On 5/27/19 3:05 PM, Alain Kohli wrote: > Thank you, that's perfect! For anyone that might stumble upon this, I > had to make two minor adjustments to automate it. > snipped because formatting was off. > > # I couldn't run it with '--run' and if you pipe it into 'mailman > shell' # I needed this or the loop above wouldn't execute. pass It won't run with --run as I wrote it because `mailman shell` only predefines the various interface names and getUtility when entering interactive mode. To use --run, you need to import those. I have attached msgs_del.py which will run with --run. It incorporates the test for msg not None (thank you), makes a minor variable name change (file -> fn) and adds a print of the number of files removed. It has my path to var/messages hard coded, so that may need to be changed. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

[MM3-users] Re: Out runner not sending emails, stuck on recvFrom.

by Mark Sapiro

On 10/20/21 11:03 AM, 01ste02(a)gmail.com wrote: > My mta is logging a connection, which times out every three minutes. The strace for the out runner shows the following: > ... > connect(21, {sa_family=AF_INET, sin_port=htons(465), sin_addr=inet_addr("127.0.0.1")}, 16) = 0 > recvfrom(21, > > And the mailman smtp-log shows: > > Oct 20 19:58:04 2021 (1262375) <163474270655.1243104.7078333516263200191@xxx> delivery to xxx@xxx failed with code 444, Connection unexpectedly closed > Oct 20 19:58:04 2021 (1262375) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7f219bf93310> > Oct 20 19:58:04 2021 (1262375) Connecting to 127.0.0.1:465 Is the local MTA listening on 127.0.0.1:465? If so, is some firewall blocking that connect? We are waiting for a response from the MTA to the connect and it never comes, Even if [mta] settings like smtp_user: smtp_pass: smtp_secure_mode: smtp_verify_cert: smtp_verify_hostname: are somehow not correct or appropriate, we don't seem to be getting that far. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Re: Still unable to get mailman3 working on Ubuntu 20.04 LTS

by Mark Sapiro

On 1/3/22 2:44 AM, Michael Heseltine wrote: > > But that did not change anything, I still get the following error message when running "/opt/mailman/mm/bin/mailman-post-update" in the venv: ... >> File "/opt/mailman/mm/venv/lib/python3.8/site-packages/compressor/conf.py", line 115, in configure_url >> if not value.endswith('/'): >> AttributeError: 'NoneType' object has no attribute 'endswith' That code is ``` def configure_url(self, value): # Uses Django's STATIC_URL by default if value is None: value = settings.STATIC_URL if not value.endswith('/'): raise ImproperlyConfigured("URL settings (e.g. COMPRESS_URL) " "must have a trailing slash") return value ``` which is basically saying you have no setting for STATIC_URL, but https://gitlab.com/mailman/mailman-suite/blob/master/mailman-suite_project/… sets it, so I don't know what the issue is. What does ``` grep STATIC /opt/mailman/mm/settings* ``` show? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: How to see the admin password reset in docker with mailman3

by Mark Sapiro

On 4/6/23 13:48, bob B via Mailman-users wrote: > I am setting up a new environment of Mailman3 in docker. I understand I have to reset the password to set the password for admin. I go to forget the password, in the GUI and I put in the address I have listed in the docker-compose.yaml and I never get the email. I look at the mail log on the host and I do not see the smtp connections. I assume Django is not using the docker host but sending the mail directly?? > > Basically, where can I see the password email rest mail logs to make sure an email was sent out and where it is going? I can't answer that question, but you can set an admin user and password with the django admin createsuperuser command. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 3 months

[MM3-users] Re: Help needed to create filters that were working in Mailman 2.

by Mark Sapiro

On 6/20/23 11:04 PM, mrl(a)psfc.mit.edu wrote: > How do I make a filter that if it matches, it accepts the message and doesn't check the remaining filters? > > I could do this using the anti-spam filters in mailman 2, as there was a Accept option. > > But there is no Accept option in Mailman 3 (that I can find). > > I tried using "Default antispam action", but that didn't stop the rest of the filters from being applied. The default action for "Default antispam action" is "hold" but you can change that to "accept" by setting ``` jump_chain: accept ``` in the [antispam] section of mailman.cfg, however current Postorius offers "Accept immediately (bypass other rules)" as a choice for the Header Filters action. Does yours not? What is your Postorius version? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

[MM3-users] Re: Tracking from gravatar

by Mark Sapiro

On 2/14/19 2:31 PM, worik wrote: > Privacy badger reports one tracker (for which it disables cookies) on my > Mailman installation. It is: > > secure.gravatar.com > > What is this for and how do I get rid of it? If you go to <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/> and look around the archives you will see that all users have some sort of graphic image associated with them. In many cases such as yours, the image is just a rudimentary silhouette, but others have a picture or other graphic. Those are things the user has published at gravatar.com. You can disable them by setting GRAVATAR_SECURE_URL = '' in your local settings. See <https://github.com/twaddington/django-gravatar> Setting the URL to the null string is not completely satisfactory as there will still be a 'missing image' where the image used to be, but it should remove references to secure.gravatar.com. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 5 months

[MM3-users] Re: Rendering HTML for moderation

by Mark Sapiro

On 10/28/19 1:37 AM, Gila Halpern wrote: > Hi, new member here doing some research for my boss. Does Mailman 3 allow > HTML rendering in the moderation queue, or only plain text? I'm asking > because our list mod doesn't have time to check each image in a submission > individually, so we currently don't allow images, but the boss wants to > allow them. Postorius displays only plain text of a held message with HTML and images shown as attachments, and clicking an HTML attachment link will download the HTML and what happens depends on the browser, but if there are image parts referenced in the HTML, they will be separate links to download and won't render along with the HTML. However, is the list is set to notify the moderators of held messages, the notice will imclude the entire message which should render properly in the moderator's MUA. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

[MM3-users] Re: mailman web spamming uwsgi error log.

by Mark Sapiro

On 6/29/21 8:44 AM, Sarah H wrote: > from the Django settings the log is here: > > Make sure that this directory is created or Django will fail on start. > LOGGING['handlers']['file']['filename'] = '/opt/mailman/web/logs/mailmanweb.log' > > but the only new entry in the log is from when I attempted to run the runjobs as the wrong user and the log entries for unable to connect to DB from when the uwsgi log filled the drive and the db process died, which is what originally alerted me to the issue. The catching of the "MailingList.DoesNotExist" exception and logging "MailingList with name xxx does not exist" was recently added and will be released in HyperKitty 1.3.5. Apply the patch to hyperkitty/tasks.py from https://gitlab.com/mailman/hyperkitty/-/merge_requests/341/diffs which should replace the uwsgi-error.log entries with the one line entries in mailmanweb.log. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

[MM3-users] Re: config incoming email in my domain cpanel

by Mark Sapiro

On 08/03/2017 10:42 AM, Rafael Mora wrote: > > I've found the MX records on my cpanel but how do I redirect the emails > going to my list to my private server? You have to configure the MTA that is the MX for the domain to relay the mail to the Mailman server. > I still don't get it. What if I just suscribe the members and then send the > email to the suscribers the thing is that the email has to be received by > mailman in order to resend it to the list suscribers right? If all you want to do is send mail that you generate, you can use mailman inject to deliver the mail to Mailman on the local machine. The drawback of not being able to receive mail from the outside is Mailman won't receive bounce DSNs from remote servers. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 11 months

[MM3-users] Re: Walk-thru for Ubuntu Bionic Mailman 3 Full setup

by Mark Sapiro

On 4/11/19 6:40 PM, brian(a)emwd.com wrote: > > Also Kelly are you sure this is correct: > > "There are two configuration files that have a key in them that must match for Hyperhitty to authorize and be able to store archives (the paths should be as follows): > /etc/mailman3/mailman-hyperkitty.cfg (set the api_key without any quotes) > /etc/mailman3/mailman-web.py (set the ‘SECRET_KEY’ - include single quotes around the key)" > > It was the MAILMAN_ARCHIVER_KEY that I needed to make sure it was being matched by the API key in mailman-hyperkitty.cfg. I believe the SECRET_KEY setting has nothing to do with the auth errors that Hyperkitty was displaying. Yes. SECRET_KEY is used internally within Django. See <https://docs.djangoproject.com/en/2.1/ref/settings/#secret-key>. It is the MAILMAN_ARCHIVER_KEY setting that must match the api_key setting in mailman-hyperkitty.cfg (modulo quoting). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 3 months

[MM3-users] Re: How to configure a mailing list?

by Mark Sapiro

On 3/10/20 6:44 AM, Patrick Ben Koetter wrote: > Greetings, > > I do have mailman 3 installed via virtualenv and it is up an running. Now I'd > like to create a mailing list, but I can't find any instructions how I should > do this. > > Is there a resource online I missed? If not, can anyone on this list tell me > how to do it preferrably using a command line tool? There is a bin/mailman command in your venv. It needs to be run with a -C option pointing to your mailman.cfg. I use a wrapper like #!/bin/bash exec /opt/mailman/mm/venv/bin/mailman \ -C "/opt/mailman/mm/mailman.cfg" \ $@ Give the mailman command with no args for a list of sub-commands and ultimately mailman create --help for instructions on creating a list. See <https://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/commands…> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

[MM3-users] Re: FILTER_VHOST = True doesn't work fine with alias_domain

by Mark Sapiro

On 2/18/22 09:53, Élodie BOSSIER via Mailman-users wrote: > > Now, I need to find how to set it automatic when I will add a new list. > Perhaps I could do it with an an SQL command if there are no bash > command ? I will check with "mailman create" and the --domain argument. Part of adding a new list is specifying the domain. If it's one of the existing domains, i.e., ml.franceserv.fr, or ml.viticreation.fr, that's all that needs to be done. e.g. `mailman create newlist(a)ml.franceserv.fr`. If it's a new domain, you need to add the domain to the django_site table perhaps directly or via the django admin UI and then after `mailman create newlist(a)new.domain` you may need to edit the domain via Postorius' domains view to specify the correct Web Host. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: Question about whitlisting a domain for specific mailing list

by Mark Sapiro

On 3/30/23 08:55, Zaheer Abbas wrote: > Hi All, > > I need to whitelist a domain for a specific mailing list on your platform. > Only *(a)example.com email addresses should be allowed to post messages to > this list. > > Could you please provide me with documentation or instructions on how to > achieve this? I have already searched the knowledge base and user manuals > without success. In Postorius Header filters add a filter with Header = from, pattern = ^.*(a)(?!example\.com(\W|$)) and Action as desired. That pattern will match anything in a From: header which contains an @ followed by anything other than example.com and a non-alphanumeric or the end of string. I.e., things that won't match are for example xxx(a)example.com xxx(a)example.com> xxx(a)example.com yyy Things that will match are for example xxx(a)other.domain xxx(a)example.comp -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: Internal Server Error: /archives/

by Mark Sapiro

On 11/29/24 7:51 AM, Christian via Mailman-users wrote: > What is this error and how can I fix it please? Running Debian 4.19.316-1 ... > Request Method: GET > Request URL: https://lists.domedoman.ie/archives/?sort=active%22%27! ... > Traceback (most recent call last): > None ... > GET: > sort = 'active"\'!' Some remote user has requested `https://lists.domedoman.ie/archives/?sort=active"'!` The `"'!` appended to the sort=active query fragment caused the error. This sort of thing happens when bots and script kiddies crawl your web site. You can find the request in your web server logs for more information about where it came from, but the bottom line is this will happen from time to time and it's not an indication that anything is broken. It would be possible to harden HyperKitty to defend against malformed URLs like this, but without a traceback it is not clear where to do it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months

[MM3-users] Re: MTA setup

by Mark Sapiro

On 12/22/24 20:10, Arte Chambers via Mailman-users wrote: > I'm not sure how to check mailmans shunt queue. `ls var/queue/shunt` > I'm not seeing any errors in mailman logs > > There are several .pck files in Mailman's > var/archives/hyperkitty/spool/ These are message that failed to archive. There should be messages in mailman.log about these failures indicating what the issue is. > I can send email from the server using mail utilities as long as the "from > email address" contains the server's domain name. I also notice that in > this MM3-Users list the "from" email shows senders(a)emailaddress.com VIA > mailman3.org. I'm wondering if I've missed something that would allow my > server to behave this way. In the list's Settings -> DMARC Mitigations set DMARC mitigation action to Replace From: with list address and set DMARC Mitigate unconditionally to Yes. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 1 week

[MM3-users] Re: Syncing Real Name between user account and membership

by Mark Sapiro

On 12/31/20 2:52 AM, Andreas Barth wrote: > > I think it would be useful (for others who try it) to have just these > snippets somewhere (also as examples what could be achived by mailman > shell). I'm happy to add them myself if possible, but the > wiki seems to be mailman 2 centric? > > What would be the appropriate place then? The wiki <https://wiki.list.org/> is an appropriate place. It only seems to be Mailman 2 centric because it's been around in one form or another for over 20 years and during much of that time, there was no Mailman 3 at all. There is also a new FAQ section at <https://docs.mailman3.org/en/latest/faq.html>, the source for which is at <https://gitlab.com/mailman/mailman-suite-doc/-/blob/master/source/faq.rst>. Merge requests to add to that are also welcome. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: Setting up on ubuntu server 22.04

by Mark Sapiro

On 10/3/23 06:00, Kyriakos Terzopoulos wrote: > > However, I cannot find the mailman/setup.py anywhere in order to patch it, > since the installation was done through pip from here: > https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… > > Maybe I can try upgrading python from 3.10 to 3.11 and re-install Upgrading Python won't help. There is currently an incompatibility issue when following https://docs.mailman3.org/en/latest/install/virtualenv.html because that doc is based on the head of the GitLab branch, but `pip install mailman3` installs the 3.3.8 released version of core and the latest 6.1.0 version of importlib_resources and these are incompatible. There are two ways to fix this. The easy way is to downgrade importlib_resources in your venv with ``` pip install importlib_resources\<6.0 ``` The slightly more complex way is to upgrade mailman core to 3.3.9b1 from GitLab with ``` pip install -U git+https://gitlab.com/mailman/mailman.git ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: Thread IDs on messages incrementing per reply?

by Mark Sapiro

On 10/18/23 15:06, Thomas Ward via Mailman-users wrote: > Is there a way to oerhaps custom-plugin my way through to set this up as > an integration into Core? And specify the custom handler process or > such to allow that integration? I see that there are ways to code > plugins into existence so it may be a custom-processor plugin or such > for this purpose. The issue is Mailman core would have to keep track of the message-ids and thread number of all prior posts to know whether the current post is a reply to some other post or not. You would need a new database table or some other mechanism to keep track of this and then you may need to keep everything forever because you can't know that there won't be a future post in reply to some very old post. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: hyperkitty web site

by Mark Sapiro

On 4/28/20 9:40 AM, Gelpi Andrea wrote: > > If in django administration I rename that site it works. > > But having more than one domain this is not a solution. > > what i need is to separate different domains > > https:/website1/mailman3/hyperkitty shows some lists > https:/website2/mailman3/hyperkitty shows other lists There are issues with FILTER_VHOST. See <https://gitlab.com/mailman/postorius/-/issues/394> for the Postorius issue. This will be fixed for Postorius in the next release. For HyperKitty, the issue is <https://gitlab.com/mailman/hyperkitty/-/issues/254>. This is not yet fixed. Currently, if FILTER_VHOST is True, HyperKitty only shows lists in the index for which the list's domain matches the domain in the accessing url with a leading 'www.' stripped. E.g. list(a)example.com will only show on the index if the accessing URL's host is example.com or www.example.com, but not if it is say lists.example.com. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: installing mailman3 core

by Mark Sapiro

On 5/29/20 7:49 AM, Ralf Wiegand wrote: > https://docs.mailman3.org/en/latest/install/install.html > > I was following this "official" page. There is no word on "pip install > mailman" as an alternate choise? > > There is also a reference in regards to "Virtualenv Installation > <https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst…>, > recommended for Production" ... why is this recommended? Does the "pip > install mailmail" install a production environment I can trust? I didn't write that page, but I think it is saying that for production, installing in a virtualenv is preferred over installing globally, and not that it is necessarily preferred over installing a Docker container or a distro package. However, if you actually read the Virtualenv Installation document, you will see under Installing Mailman Core <https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-mail…> it says to install Mailman core via `pip install mailman` in the virtualenv. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: [Django] ERROR (EXTERNAL IP): Service Unavailable

by Mark Sapiro

On 3/1/21 12:58 PM, dancab(a)caltech.edu wrote: > Ok, thanks. I'll need to reproduce what happened somehow. > > Any suggestions on how to clear this "held message" notification from the database? > > If necessary I can just re-initialize everything but it would be helpful to know if there's just a row I could drop. I would d delete rows from 3 tables. I would first SELECT * from message WHERE path = 'XC/DU/XCDUNGGCTVSN7RGCW5F3WXM5T2WEHCCJ'; then SELECT * from pendedkeyvalue WHERE type = 'id AND value = <the id of the message table>; Then SELECT * from pendedkeyvalue WHERE pended_id = <the pended_id from above>; This should return 2 rows, the type = id from above and a type = 'held message' Then I would delete the row from the pended table with id = that pended_id and the two rows from the pendedkeyvalue table and the row from the message table. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: List Migration from MM2.1 -> MM3

by Mark Sapiro

On 8/14/22 11:04, Odhiambo Washington wrote: > So I thought I have everything running. Fresh install of MM3 on > Ubuntu-22.04. > > I have created a list in postorius - it has the same name as my old list in > MM2. > > [image: MM3.png] Your image didn't make it through content filtering. What is the fully qualified name of the list > mailman@lists:~$ /opt/mailman/mm/venv/bin/mailman import21 skunkworks(a)lists.my.co.ke /var/list/lists/skunkworks/config.pck > Usage: mailman import21 [OPTIONS] LISTSPEC PICKLE_FILE > Try 'mailman import21 -h' for help. > > Error: No such list: skunkworks(a)lists.my.co.ke Apparently the list you created is not named skunkworks(a)lists.my.co.ke > What am I missing? The Mailman 3 list skunkworks(a)lists.my.co.ke including that exact domain must exist in order to import to it. Try /opt/mailman/mm/venv/bin/mailman create skunkworks(a)lists.my.co.ke -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[MM3-users] Re: Hyperkitty shows "<" as <

by Mark Sapiro

On 4/4/23 09:53, Andreas Schamanek wrote: > > Hi fellow Hyperkitties, > > I migrated from Mailman 2 to 3 and imported my 1st list via `manage.py > hyperkitty_import` to Hyperkitty 1.3.4 (the Debian package), but that > might not even be relevant to my problem: > > All "<" and ">" in old and new messages are shown as "<" and ">" > in message views _however_ they are shown correctly in overview > abstracts e.g. at //server/mm3/hyperkitty/list/testlist@server/latest I don't think I've ever seen this. Certainly it is not the case on this list with either current messages such as those in this thread <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> or in old threads on the mailman-users(a)python.org list imported with hyperkitty_import such as https://mail.python.org/archives/list/mailman-users@python.org/thread/A2DCH… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 3 months

[MM3-users] Re: mm3 installation question

by Mark Sapiro

On 3/5/24 1:52 PM, advorkin(a)cs.princeton.edu wrote: > > I went with the apache/uswgi configuration. The site is up and running, but if I click Postorius, it gets redirected to https://mysite.com/postorius/lists and I get not found error message. > > The same goes for Lists and Archives. Compare your urls.py to <https://gitlab.com/mailman/mailman-web/-/blob/master/mailman_web/urls.py?re…>. Some of the `path` settings are probably not in the same order as in that file. The ``` path('mailman3/', include('postorius.urls')), path('archives/', include('hyperkitty.urls')), ``` settings should come after the ``` path('postorius/', include('postorius.urls')), path('hyperkitty/', include('hyperkitty.urls')), ``` settings (unfortunately, mailman-web 0.0.8 has these in the wrong order). Or you can just delete the 'postorius/' and 'hyperkitty/' ones or you can add ``` ProxyPass "/postorius" "http://127.0.0.1:8000/postorius" ProxyPass "/hyperkitty" "http://127.0.0.1:8000/hyperkitty" ``` to your Apache config. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

[MM3-users] Re: Join a Mailman 3 list?

by Mark Sapiro

On 6/2/25 10:55, Cathryn McGuire wrote: > Hi, > > We’re currently hosted by EMWD who upgraded the Mailman 2 cPanel/Python and have been unable to resolve the issues we’re experiencing. > > We would like to join a Mailman 3 list to see how it all looks and works. > > Do you have any recommendation? Welcome to the mailman-users(a)mailman3.org list. As far as your EMWD migration from cPanel Mailman 2.1 to Mailman 3 is conerned, I think you'll find little if any change as far as email posting to the list and email from the list is concerned, but EMWD has their own proprietary web UI for list management and archiving, so the web UI at EMWD is quite different from that for this list. I'm not sure if we can help with the issues you're having, but if you tell us what they are, we can try. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 4 weeks

[MM3-users] Re: out queue backlog and delivery rate

by Mark Sapiro

On 3/25/22 16:17, dancab(a)caltech.edu wrote: > > Mail delivery is continuing at a snails pace and it is now 4 hours behind. > > I noticed that the system isn't overloaded either via CPU or Memory. It's just slowly "working on it". > > Are there rate limits that can be tuned for Mailman queues such as the "out" queue? Could this be IO related somehow? I'd expect there to be a CPU spike in that case. There are things that can be done. One big performance killer is MTA recipient checks during SMTP from Mailman. Look too at the various hits at <https://wiki.list.org/?action=fullsearch&value=performance&titlesearch=Titl…>. These are written for older Mailman, but the MTA advice is relevant. One thing you can do is enable an alternate SMTPD port in the MTA with minimal checking and configure Mailman to use that port. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: Remove PDF attachents

by Mark Sapiro

On 3/4/20 7:42 AM, Eduardo Costa via Mailman-users wrote: > Hello, > > How do I configure the list to remove attachments of type pdf and others. You need to set the list's filter_types and or pass_types. For example, to filter out everything except HTML and plain text, collapse alternative parts and convert remaining HTML to plain text, you would set filter_content = True collapse_alternatives = True convert_html_to_plaintext = True pass_types = ['multipart', 'text/plain', 'text/html'] The first 3 of these can be set in Postorius -> Settings -> Alter Messages, but the last has to be set in mailman shell as in $ /opt/mailman/mm/bin/mailman shell -l list(a)example.com Welcome to the GNU Mailman shell m. The variable 'm' is the list(a)example.com mailing list >>> list(m.pass_types) [] >>> m.pass_types = ['multipart', 'text/plain', 'text/html'] >>> list(m.pass_types) ['multipart', 'text/plain', 'text/html'] >>> commit() -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

[MM3-users] Re: Mailman3 throws 500 error (unicode encode) when loading held messages in Postorius

by Mark Sapiro

On 9/6/20 3:39 PM, Simon Handfield via Mailman-users wrote: > Thanks for your advice, Stephen. > > As I've removed the file from the shunt queue I don't believe that file is causing the 500 error any more. > > I've confirmed the error is not cached in the browser. > > If the issue does not reside in the shunt queue (no other files indicate parse errors when checking via command line) are there any other places I should look for data that is addressed by that page? As Steve said, messages in the shunt queue have nothing to do with the held messages view in postorius. Held messages are in Mailman's var/messages/ directory and referenced by entries in the message table in the database which in turn are referenced by entries in the pendedkeyvalue table. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: Problem with list creation

by Mark Sapiro

On 9/16/20 8:25 AM, Pawel Grzywaczewski wrote: > > We increased timeout in mailman.cfg > ``` > [gunicorn] > workers: 4 > timeout: 900 > ``` This doesn't do it. In order to pass configuration settings to the REST gunicorn servers, you need to put in mailman.cfg ``` [webservice] configuration: /path/to/gunicorn.cfg ``` and then put settings like these ``` [gunicorn] workers: 4 timeout: 900 ``` in /path/to/gunicorn.cfg. Some settings, but only hostname, port and workers can be put in mailman.cfg, but in the [webservice] section, not in a [gunicorn] section. See <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/rest/gunicorn.…> for more detail. > And we increased timeout in nginx > > ``` > http { > > # MODIF UNICORN > proxy_connect_timeout 300s; > proxy_read_timeout 300s; > # MODIF UNICORN > > ``` nginx is not involved. These are not proxied requests through nginx. They are requests to Mailman's REST API which use a separate gunicorn server. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: where is manage.py for migration?

by Mark Sapiro

On 11/26/20 6:50 AM, Dan Langille wrote: > Hello, > > I am following https://docs.mailman3.org/en/latest/migration.html and I'm trying to "Migrate the list archives from Mailman 2 to Mailman 3 by running the following command": > > [mailman@mailman ~]$ python manage.py hyperkitty_import -l biking(a)lists.example.org /usr/local/mailman/archives/private/biking.mbox > python: can't open file 'manage.py': [Errno 2] No such file or directory > > Is the documentation correct? I cannot locate manage.py in the code: That refers to the Django manage.py script. It's name and location depends on how you installed Postorius and HyperKitty. Have you installed those and set up a Django project? There are sample manage.py files in both postorius/example_project/ and hyperkitty/example_project/ as well as mailman-suite/mailman-suite_project/, however, depending on how things are installed, the Django admin interface could be named manage.py, django-admin or something else. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: Disabled by bounce

by Mark Sapiro

On 2/2/23 18:19, Allan Hansen wrote: > Mark, > > I can see your argument here, but if a 'Disabled by bounce' subscription is enabled, it would require just looking at that particular subscription and set the bounce count to 0, so that the next bounce (before staleness) does not disable it again. We are talking about two different issues here. One issue is not resetting the bounce score to zero when (or before) a disabled by bounce user's delivery is enabled. This is https://gitlab.com/mailman/mailman/-/issues/1061 and I'm working on it. The other issue is not resetting the user's bounce score when it goes stale as opposed to when another bounce is received and the score is stale. Other than the fact that one might be misled by seeing a non-zero bounce score which is stale, there are no other issues from waiting for a bounce to reset a stale score. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

[MM3-users] Re: [migration] to a another server - one year database apparently lacks fields for newer mailman3/django suite

by Mark Sapiro

On 10/20/23 14:04, Wikinaut wrote: > I also solved this issue. > How? > > By adding columns to two tables in the database mailman3web: > > alter table hyperkitty_mailinglist add column archive_rendering_mode varchar(255) default null; > alter table socialaccount_socialapp add column `provider_id` varchar(200) NOT NULL; > alter table socialaccount_socialapp add column `settings` longtext CHARACTER SET utf8mb4 COLLATE utf8mb4_bin NOT NULL CHECK (json_valid(`settings`)); The proper fix is just to run `mailman-web migrate`. See https://docs.mailman3.org/en/latest/install/virtualenv.html#run-database-mi… You should also run that and `mailman-web collectstatic` `mailman-web compress` and `mailman-web compilemessages` any time you do any kind of update. See https://docs.mailman3.org/en/latest/install/virtualenv.html#collect-static-… et. seq. Running `mailman-web migrate` at this point may fail because of the changes you made manually. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: 120 gmail users removed from lists !

by Mark Sapiro

On 10/24/23 11:51 AM, info(a)joergschulz.de wrote: > Am 24. Oktober 2023 um 18:07 schrieb "Yvan ♞" <elemac(a)free.fr>: > >> >> I add an SPF entry on my web hosting, domain name: "v=spf1 mx ptr >> include:_spf.google.com -all" and it seems to fix the problem. >> > Smart. As I understand above statement, it allows the google servers to send out emails for your domain. Not sure you want that. But you're right, mailman will eventually pick up the -all for the google addresses and apply the DMARC mitigation to google originating messages. Is this assumption correct? Wrong. Mailman in conditionally applying DMARC mitigations considers only the DMARC policy if any of the From: domain. Whether or not an outgoing message might be rejected for DMARC policy or any other reasons has no automatic effect on the application of DMARC mitigations to subsequent messages. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: List description as sender

by Henrik Rasmussen

Yes, but even the Settings -> Alter Messages -> Anonymous list is set to No, the 'anonymous_list': is still True. That is my problem, I think. -- Henrik Rasmussen her(a)adm.ku.dk University of Copenhagen, Danmark -----Oprindelig meddelelse----- Fra: Mark Sapiro <mark(a)msapiro.net> Sendt: 24. september 2018 15:54 Til: mailman-users(a)mailman3.org Emne: [MM3-users] Re: List description as sender On 9/24/18 4:00 AM, Henrik Rasmussen wrote: > Mark Sapiro wrote: >> On 09/17/2018 01:04 AM, Henrik Rasmussen wrote: >> I think your choices are: >> >> 1) Don't configure the list as anonymous. > > I've just tested it on a list which was imported from Mailman 2, but changing the list to announced doens't seem to affect the From: ... > 'anonymous_list': True, Set anonymous_list False. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

6 years, 10 months

[MM3-users] Re: Any known limit of number of lists that one can be owner/member of?

by Mark Sapiro

On 5/14/19 6:34 PM, Alan So wrote: > Thanks for your explanation. Just verified with a normal user and notice that no lists will be shown when all is selected since all lists are not advertised. I thought that for a user with that issue (as owner of more than 50 lists) at least her subscription or lists with her as owner will be shown. I understand it can be confusing because "all" is one of the "roles" in the "Filter by Role" dropdown, but the unfiltered "all-lists" view is generated differently from the other filtered views and only shows unadvertised lists to a site admin (superuser). That's also why the all-lists view is paginated (and can show more than 50 lists) and the other roles are not. We will be fixing that part. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

[MM3-users] Re: Mailman shell tutorial

by Mark Sapiro

On 6/11/19 6:00 PM, Andrew Bernard wrote: > > I have this going, and it is great. But I recall seeing something called > mmclient or similar which has simple commands like show user, show lists, > and so on. Is that still available? Are you thinking of the mailman command itself? Things like `mailman lists` and `mailman users`. Try running the `mailman` command itself with no arguments to see a list of sub-commands and then `mailman sub-command --help` to get the details of a particular subcommand. > Now knowing how mailman shell works, anybody could write their own commands, > but I don't want to reinvent wheels. I don't know what it is you are trying to accomplish, but yes, you can create scripts which you run via `mailman shell -run ...`, but is there something specific you are trying to do that is not currently available via the `mailman` command or the Postorius wb UI? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 1 month

[MM3-users] Re: Help with troubleshooting mailman3 DNS lookups

by Mark Sapiro

On 2/23/21 3:11 PM, Simon Handfield via Mailman-users wrote: > However when messages are sent to mailman3 lists we're still seeing hits on the old DNS servers. > > I have tried to find a config that references the old servers but have not been able to find one. Because Mailman doesn't directly access DNS. As far as I know, there are only two pieces in Mailman core that indirectly access DNS. DMARC mitigations look up sending domain DMARC policy via the dnspython package <https://pypi.org/project/dnspython/> and if you have enabled ARC signing in Mailman via [ARC] enabled: yes it uses authheaders <https://pypi.org/project/authheaders/> I don't know what these packages might be looking at to see the old servers, but as far as I know, nothing else is doing DNS lookups. The modules that invoke these are mailman/rules/dmarc.py and mailman/handlers/arc_sign.py. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: Filter who can send on mailman3 list?

by Mark Sapiro

On 4/7/21 1:32 AM, Marcus Granath wrote: > > Sorry, but actually I can not find any "Users dropdown" to select "Non-Members" at any Postorius in my web interface. :-( It's one of the various tabs across the top of the page. What Postorius version is this? Seversal versions back, I think it was called `members` rather than `users`. In current Postorius, the tabs are Info Subscription requests Held messages Users Templates Settings Mass operations Ban List Header filters Delete As I said, `Users` used to be `Members` and `Templates` was added at some point, but that's the general idea. > Maybe, could it be that I am actually not the admin of the mailman3 server, I'm "just" the admin of my mailman-list - so just admin for my mailman-list and not for the mailman server? As Steve said, the list admin should see all those. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

[MM3-users] Re: High memory usage

by Mark Sapiro

On 2/15/22 08:11, Stephen Daniel wrote: > TL;DR: quite likely your system has plenty of memory and is operating > normally. ... > On Tue, Feb 15, 2022 at 5:28 AM Prasanth Nair <prasanth.nair(a)linaro.org> > wrote: > >> Hi, >> >> We are having an issue with high memory usage on our Mailman3 server. >> Initially, our server had 16GB RAM and the memory usage went up from 5% to >> 92% within a week. So, we increased the memory capacity to 32GB RAM and we >> can see that the memory usage is going up in the same pattern. >> >> Any idea why it is happening? or any suggestions? Just for reference, mail.python.org supports 231 MM 2 lists and 182 MM 3 lists with 16 GB of ram and no swap. The server that supports this list and also the www.list.org web site has 4 GB of ram and no swap. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: Migrated from MM2 to MM3, all is well except *one* list

by Mark Sapiro

On 8/27/22 1:20 PM, Scott Courtney wrote: > Hello, all > > I have migrated a multi-list server from MM2 to MM3, on Debian 11, and > migrated about half a dozen lists with fairly large archives. > Absolutely everything has been working for a couple of months, but I > am still unable to get one specific list to send mail to its > subscribers. Of course, the first place I started was the logs, but > that's the problem -- even with logging turned up, it appears to be > failing silently as it connects to the MTA. See the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… You probably ran `mailman import21` for that list as root or some other non Mailman user (`list` with Debian packages) causing that list's templates to be unreadable by Mailman. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[MM3-users] Re: problem configuring mailman3 on debian bullseye

by Mark Sapiro

On 3/15/23 09:55, Odhiambo Washington wrote: > On Wed, Mar 15, 2023 at 7:10 PM Servizio Informatico U.I.C.I. Sezione > territoriale di Brescia <servizioinformatico(a)uicibrescia.it> wrote: > >> Hi, >> >> I created a template but after some tests I deleted it. >> >> Now I created only a standard list without modifying any templates. >> >> So they are the standard templates coming with the distribution. I did not >> change also the language >> > Maybe you can start by deleting any templates in postorius_emailtemplate > table in the DB? There shouldn't be any, but if the issue is with accessing postorius templates, that might make it worse. If you want only the system default templates, you could do this database query to remove any non-defaults: DELETE FROM templates; That will ensure that you aren't accessing Postorius for any templates. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: missing graphics in Postorius

by Mark Sapiro

On 12/7/21 4:01 PM, David Newman wrote: > On 12/7/21 11:17 AM, Mark Sapiro wrote: >> Add '127.0.0.1' to ALLOWED_HOSTS anyway. > > Done, thanks. > > Given that DNS works fine on this host, with localhost and 127.0.0.1 > resolving backward and forward, this seems like a bug. Shouldn't the > resolver be able to recognize localhost without hard-coding an address? It's probably a bug, but if so, it's a Django bug and not anything Mailman can do anything about. ... >> Assuming you have >> ``` >> STATIC_ROOT = '/opt/mailman/web/static' >> ``` >> in your /etc/mailman3/settings.py file, you may need to create that >> directory if it doesn't exist. You shouldn't need to manually create >> the /opt/mailman/web/static/postorius directory if the >> /opt/mailman/web/static directory exists and is writable/searchable by >> the Mailman user. > > Yes, that was it. Thanks. > > Previously you'd pointed out what you considered an error in the venv > docs, with the workaround to manually create the /opt/mailman/web > directory [1]. I think the same issue applies here, and also that > /opt/mailman/web and subdirectories need to be owned by the mailman user. I don't recall what I said about that but near the end of the Initial Configuration section at https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-configu… it says ``` Make sure that the logging path is created. You can run mkdir -p /opt/mailman/web/logs to create the path. ``` I added ``` Also make sure the ``STATIC_ROOT`` directory is created. ``` after that. As far as things being owned by the mailman user, early in the doc at https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-setup there is a note that says ``` Make sure that you are running commands as mailman user from here forth. Setup Mailman user. ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Re: Auth question

by Mark Sapiro

On 03/31/2017 01:06 AM, David Krantz wrote: > On Fri, Mar 31, 2017 at 9:29 AM, Simon Hanna <simon.hanna(a)serve-me.info> wrote: >> On 03/31/2017 08:10 AM, David Krantz wrote: >>> I think that would correspond to this line in urls.py >>> >>> url(r'^$', RedirectView.as_view(url=reverse_lazy('hyperkitty.views.index.index'))), >> Yes, that's the culprit. Replace it with the following: >> >> url(r'^$', RedirectView.as_view(url=reverse_lazy('hk_root'))), >> You can also update whatever guide you were using... > > Great, will try that! I don't know whether I can update the guide. > It's the one referenced earlier in this thread named something like > setup experience of mailman 3 in production. Yes, that comes from "https://wiki.list.org/DOC/Mailman%203%20installation%20experience", specifically the attachment urls.py. The interesting thing is that works for me both at <https://lists.mailman3.org/> and <https://mail.python.org/mm3/>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 4 months

[MM3-users] Re: WEB UI fail to reply and create new thread

by Mark Sapiro

On 12/18/20 10:26 AM, Milan P. Stanić wrote: > > Sending mail by mail clients works and mails are sent to subscribers > properly. > Most other 'things' works but we have problem with reply to posts and > creating new threads using web ui. When replying to post with web ui it > says that the everything is ok and post is sent but post doesn't arrive > to mailing list. Same happens with creating new thread. > > Our debug says "KeyError: 'display_fixed'" but we are not sure what > should be changed/fixed/set for this problem. > Attached is excerpt from debug log. I don't think that exception is the problem. See <https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/lib/posting.…> for whit I think might be the issue. I.e., Hyperkitty won't send the mail if DEBUG = True -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: Bounce Problems

by Mark Sapiro

On 2/23/21 2:25 AM, M4tze wrote: > If I understand the settings correctly, bounce_info_stale_after = 7d > means that any bounce received > 7d ago are not counted (which would be > intuitive). But it doesn't work that way. It means that the user's bounce info is ignored/discarded if the user hasn't received a bounce within the last bounce_info_stale_after days. I.e it is bounce_info_stale_after and not bounces_stale_after. > It seems, that there must be a 7d gap between the last > bounce received and a new bounce to get the score reset to 1. Is my > interpretation right? Is this intentional? Can this be changed? Yes, this behavior is intentional and no, it won't be changed. Consider a list that gets fewer than five posts per week. While default settings probably aren't appropriate for this list, with default settings, if we discarded bounces older than 7 days, an address that bounced every post would never be disabled. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: can't get mail into mailman3 in docker

by Mark Sapiro

On 8/6/21 6:26 AM, bob B wrote: > > But when I send a message, the docker host machine in /var/log/email/ shows "connection refused" & "lost connection" to mailman-core port 8024 > > > ************************************ > 2021-08-06T09:08:41.885213-04:00 dockerhost postfix/cleanup[109782]: D630B3083ED0: message-id=<4805A7DC-E100-4851-B1BB-E6C1806568A1(a)sender.com> > 2021-08-06T09:08:41.896943-04:00 dockerhost postfix/qmgr[105559]: D630B3083ED0: from=<USER(a)sender.com>, size=8308, nrcpt=1 (queue active) > 2021-08-06T09:08:41.949022-04:00 dockerhost postfix/lmtp[109783]: connect to localhost[::1]:8024: Connection refused > 2021-08-06T09:08:41.974225-04:00 dockerhost postfix/lmtp[109783]: D630B3083ED0: to=<test(a)mailman-docker.###.####>, relay=localhost[127.0.0.1]:8024, delay=0.11, delays=0.05/0.02/0.04/0, dsn=4.4.2, status=deferred (lost connection with localhost[127.0.0.1] while receiving the initial server greeting) The Connection refused is from trying to connect to localhost at IPv6 ::1. Then Postfix tries 127.0.0.1, gets connected and then Mailman's LMTP runner closes the connection. There may be more info from aiosmtpd in Mailman's smtp.log. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] Re: How to edit default 'Reject (with notification)' message

by Mark Sapiro

On 5/26/23 7:57 AM, Zaheer Abbas wrote: > > I have created a template with the option, "Notice sent to a poster when > their message has been rejected by the list’s moderator." but it only works > if message acceptance is set to 'Hold for Moderation' and then the > moderator rejects the post manually. > > Is there any source file, which I can modify to replace the default > rejection text mentioned above? The template you want is described in Postorius as [list.user.notice.rejected] Notice sent to a poster when their message has been rejected automatically You can set it in Postorius per list or per domain or you can set it sitewide by putting it in Mailman's var/templates/site/en/list.user.notice.rejected.txt and if you do that, be sure the Mailman user has access to read it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: Button unsubscribe

by Mark Sapiro

On 12/7/18 7:22 AM, erlonmz(a)hotmail.com wrote: > how to put a button unsubscribe in the message together with the part > > " LIST mailing list -- LIST@domain > To unsubscribe send an email to LIST-leave@domain' > > I want to put this button in the emails to the users unsubscribe. it would already send the confirmation tolkien. > > my question is, has some place where generated tolkien is saved in mailman files? No. The confirmation token is not generated until the unsubscribe request is received so there's no way to know it in advance. Further, a button requires HTML and the list's footer is plain text. Finally, one-click unsubscribe without confirmation is dangerous. People forward list messages to others and even reply to the list without removing the one-click unsubscribe link and then wonder why they get removed from the list. At least with confirmation, they only wonder why they got a confirmation request. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 7 months

[MM3-users] Re: Template for Password Reset Email

by Mark Sapiro

On 11/14/24 13:57, Mark wrote: > > I have a list and user account set with French as the preferred language. > > Most message emails (such as the Welcome email) all arrive in French, > but not the Password Reset email (shown below) - it arrives in English. > > I'm guessing that there may not be an .mo file for it. This message comes from django-allauth. there is a French message catalog for it. These are in site-packages/allauth/locale/fr/LC_MESSAGES and should be good. You can always run `django-admin compilemessages` to update all the .mo files for all the projects. However, the issue is probably that Django doesn't get the language context from the list's preferred language. In fact, the password reset is not in a list context at all. See https://docs.djangoproject.com/en/5.1/topics/i18n/translation/#how-django-d… for how it determines the language to serve. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 2 weeks

[MM3-users] Re: Mailman shutting down Hyperkitty: Request too large

by Mark Sapiro

On 1/31/25 11:01, Arte Chambers via Mailman-users wrote: > Thanks, this was helpful. It was a message I sent to the list that was just > an image attachment with no body text. I noticed this other thread > about messages > with attachments, without text discarded silently > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>. > I am attaching the pickle file hoping that it helps anyone researching this > issue. I think the underlying issue is the same as in that thread. While your message has mime structure multipart/mixed multipart/alternative text/plain <- empty text/html image/jpeg If you have content filtering Collapse alternatives = yes, it will become multipart/mixed text/plain <- empty image/jpeg after collapsing alternatives and that will trigger the error. See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… for a patch (not yet tested) that I think will fix this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months

[MM3-users] Re: Migration from old server to new server failed

by Mark Sapiro

On 2/16/24 07:12, Helio Loureiro wrote: > - start mailman3 and mailman-3web > - run mailman3-web migrate You should run mailman3-web migrate when mailman-3web is not running. > django.db.utils.OperationalError: (1050, "Table > 'hyperkitty_mailinglist_moderators' already exists") > > I tried to drop the table, but then it complained about another one. I > dropped all the complained tables and as result hypperkitty never > started. So I went back to see why the first error happened. The errors occurred because you had recently added tables in your database so they couldn't be added by the migrations. Dropping the tables was the correct thing to do. Did you ultimately successfully run all the migrations? When you say `hypperkitty never started`, what exactly does that mean? What happens when you try to access the archives? Can you access postorius? Are any errors logged in mailman3-web's log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

[MM3-users] Re: sync_members via email

by Mark Sapiro

On 1/20/25 13:45, kbaumann(a)chicagoiww.org wrote: > I can use email to get a list of members: > > To: mylist-request(a)lists.theserver.org > Subject: who (password) The password argument is Mailman 2.1 only. If provided for Mailman 3 it will result in an error Unrecognized or invalid argument(s): (password) > Any chance that a sync_members could be accomplished in a similar fashion? Looks like it's only available from the console, but I'm asking anyway to be sure. You are correct, there is no email sync members function. The issue for this is authentication. As far as the who command is concerned, the only authentication is whether the sender is authorized to see the result. In the case of a spoofed sender, no harm is done as the result will be sent to the sender address. The same method could not be used for syncing members because if the sender were spoofed, the syncing would be done. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 1 week

[MM3-users] Re: mailman-core installation on debian stretch/maria-db

by Mark Sapiro

On 03/10/2018 01:53 PM, Wolfgang Bock wrote: > > Hi, > > I need your help: I installed mailman3 on a debian stretch environment > and faced following problems. How? Did you install <https://packages.debian.org/stretch-backports/mailman3-core>? If so, these are probably issues with the Debian package. You may find <https://gitlab.com/mailman/mailman/issues/455> to be of interest. If you installed Mailman some other way, How? > 1. On "mailman start" I got the error message: > Starting Mailman's master runner > /usr/bin/python3: can't open file '/sbin/master': [Errno 2] No such file > or directory Where is it? What does 'which master' show? > 2. connection to maria-db > In debian stretch maria-db is running. In my mailman.cfg I set: > [database] > class: mailman.database.mysql.MySQLDatabase > url: > mysql+pmysql://#username#:#user-pawo#@localhost/#databasename#?charset=utf8&use_unicode=1 should that be mysql+pymysql ? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 4 months

[MM3-users] Re: Member Issue Discovered

by Mark Sapiro

On 10/29/20 5:17 AM, Brian Carpenter wrote: > > On 10/29/20 4:27 AM, Alex Schuilenburg via Mailman-users wrote: >> On 29/10/2020 01:57, Brian Carpenter wrote: >>> With Mailman 3, every list owner has the ability to remove a reply in >>> a thread, a complete thread, and even the entire archives. That is a >>> welcome difference from MM2 in my opinion. >> >> A very welcome difference, only I don't see this option in the web >> interface of my debian 3.2.1 installation. Is this a shell only >> option, 3.3 feature or configuration option I have missed? > It is not a shell option. It can be done via Hyperkitty but I am not > sure when that feature showed up. Actually, with current HyperKitty, only site admins can remove messages or threads or the archive. The ability for list owners to do it is <https://gitlab.com/mailman/hyperkitty/-/issues/261>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: Hyperkitty Error Curiosity

by Mark Sapiro

On 11/11/20 4:18 PM, Brian Carpenter wrote: > > Some sort of auto-discard procedure after a number of retries? Is it > possible to detect a message with a null characters and automatically > discard them? Do such messages make it into the thread table? The message has been delivered to the list, but it is not archived. The list post has an Archived-At: header with a URL, but the message isn't there at all. The only way to get it archived is to correct the message defect. Thus, I don't think it's good to just discard the message at that point. I'm fine with moving out of or not queueing it in the first place in var/archives/hyperkitty/spool, but I think it should be preserved somewhere, say in var/archives/hyperkitty/bad, and along with that, some kind of notice sent to the site admin so bad messages don't just accumulate without being seen. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: Maximum number of recipients Setting

by Mark Sapiro

On 4/3/21 1:45 PM, Brian Carpenter wrote: > I have run several tests. It looks like on the 'Maximum number of > recipients' setting, a 2 means 1. If I set it to 2, I can have the > listname(a)listdomain.com only. If I have a CC, it comes to me for > moderation. If I set it to a 3, I can send out to > listname(a)listdomain.com plus a CC. If I set it to 3 and add 2 CC's plus > the listname(a)listdomain.com address, it comes to me for moderation. I understand it's confusing, but it's been that way since the beginning of Mailman 2.1. The docs at <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rules/docs…> say "For backward compatibility, the message must have fewer than the maximum number of explicit recipients." I agree the description in Postorius could be clarified see <https://gitlab.com/mailman/postorius/-/issues/515>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

[MM3-users] Re: Mailman3 Setup

by Mark Sapiro

On 6/5/22 06:26, George R. Kasica wrote: > Hello: > > I'm in the process of setting up Mailman3 on Ubuntu 20.04. I have the following Environment, and please ask if I left something needed out: > Postfix > Apache2 > MySQL > Mailman3 (all 3 bits mailman3, mailman3-web, python-mailman-hyperkitty) > The install SEEMS to have worked, but I'm looking for a guide for setup now. I used to run 2.1 about 18 months ago, but the server failed, and I never reinstalled it. I figured now, with a newish Ubuntu 20.04LTS Server, I'd go the mailman3 route...I've seen MANY posts of issues getting MM3 working with 20.04. Should I go back to 2.1, or what is the best way to get mailman-3 configured? You should definitely go with Mailman 3. The docs are at https://docs.list.org/ (redirects to https://docs.mailman3.org/en/latest/) I suggest you start by looking at https://docs.mailman3.org/en/latest/install/virtualenv.html -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

[MM3-users] Re: Importing mbox files into archive defect with lines with From

by Mark Sapiro

On 9/19/23 2:25 AM, Alex Schuilenburg via Mailman-users wrote: > > Prefixing the line with '>' allows the hyperkitty_import to partially succeed - partially as the line and everything below it is omitted from message in the archive. Presumably because the archiver thinks the remainder is a quote which it omits? > > Prefixing with a single whitespace was the best work-around, since the renderer ignores it when viewing the message from the archive. As discussed earlier in this thread, issues with unescaped 'From ' lines in message bodies exist because of the format of *nix mbox files where lines beginning with 'From ' are message separators by definition. Escaping such lines by prefixing them with `>` is a defacto standard. As far as this causing HyperKitty to ignore the rest of the message is concerned, I do not see that with current HyperKitty. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Mark Sapiro

On 10/21/22 09:56, Onyeibo Oku wrote: > On Fri, 21 Oct 2022 09:52:03 -0700 > Mark Sapiro <mark(a)msapiro.net> wrote: > >> Can you successfully start mailman (or run any mailman commands) >> with, e.g. ``` >> /opt/mailman/venv/bin/mailman start >> >> or >> >> /opt/mailman/venv/bin/mailman info >> ``` >> without activating the venv? >> > > Yes. All those are working without activating venv. On my test installation with /etc/systemd/system/mailman3.service installed per https://docs.mailman3.org/en/latest/install/virtualenv.html#starting-mailma… systemctl start|stop|status mailman3 all work. Assuming ``` python3 -c 'from pkg_resources import load_entry_point' ``` (not in your venv) returns no error, try replacing /opt/mailman/venv/bin/mailman with ``` #!/opt/mailman/venv/bin/python3 # EASY-INSTALL-ENTRY-SCRIPT: 'mailman==3.3.5','console_scripts','mailman' __requires__ = 'mailman==3.3.5' import re import sys from pkg_resources import load_entry_point if __name__ == '__main__': sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0]) sys.exit( load_entry_point('mailman==3.3.5', 'console_scripts', 'mailman')() ) ``` Or in yours posted at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… replace everything from the first `try:` through `globals().setdefault(...)` with ``` from pkg_resources import load_entry_point ``` and see if that helps. Actually, if I replace mine with yours, it still works with systemctl, but this may be dependent on the python version (mine is 3.8.10). I'm really only guessing here, but this in your traceback ``` Oct 19 19:52:03 mail.server.tld mailman[782]: File "/opt/mailman/venv/bin/mailman", line 25, in importlib_load_entry_point Oct 19 19:52:03 mail.server.tld mailman[782]: return next(matches).load() Oct 19 19:52:03 mail.server.tld mailman[782]: StopIteration Oct 19 19:52:03 mail.server.tld systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE ``` seems to say that the `return next(matches).load()` is raising `StopIteration` and that is the issue, so removing that stuff from /opt/mailman/venv/bin/mailman may help. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: From address of subscription notifications

by Mark Sapiro

On 2/26/19 2:11 PM, worik wrote: > > When I subscribe some body to to a list I on I get a notification that > says it comes from changeme(a)example.com > > As far as I can tell no subscribers are getting mail with that, so this > is not a crises. But it is untidy and I cannot find where to change it. > > SERVE_FROM_DOMAIN is set in the mailman-web/environment section of > docker-compose.yaml (I am using the docker distribution...) You set it in your mailman.cfg. As it says in mailman/config/schema.cfg > [mailman] > # This address is the "site owner" address. Certain messages which must be > # delivered to a human, but which can't be delivered to a list owner (e.g. a > # bounce from a list owner), will be sent to this address. It should point to > # a human. > site_owner: changeme(a)example.com -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 5 months

[MM3-users] Re: how to delete a list member using the Linux command line

by Mark Sapiro

On 6/19/20 7:29 AM, Mike Wertheim wrote: > I have Mailman 3.2.1 installed (on Debian Linux), using exim4 as the MTA. > > I have been trying to figure out how to use the Linux command line to add > members to a list and delete members from a list, but am having trouble > with deleting. The --delete option to `mailman members` was introduced in Mailman 3.3.0. Your version doesn't have it. Note that as of the next (3.3.2) release, the --add, --delete and --sync options to `mailman members` are deprecated in favor of new `mailman addmembers`, mailman delmembers` and `mailman syncmembers` commands. It should be possible for you to install the current versions of all of these without upgrading just by copying the `cli_*members.py` files from <https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/commands> to the `mailman/commands/` directory in your current installation. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

[MM3-users] Re: Mysterious Bounces Being Logged

by Mark Sapiro

On March 26, 2021 2:08:01 PM PDT, Brian Carpenter <brian_carpenter(a)emwd.com> wrote: > >I would think any mail administrator for a mailman server would want to > >know why bounces are happening. I never saw this issue with Mailman 2. >Did it exist? No. Mailman 2.1 always included the DSN in notices to the admin. >Is the patch going to make it to the next version of Mailman 3 core? No. I don't think it's generally useful. It's use is too obscure. >Are >there any plans to make bounce processing more transparent to server >admins so we can troubleshoot delivery issues? Absolutely. At first MM3 wasn't processing bounces at all. A GSOC student did the bulk of the current implementation and we were happy to get that even though this piece was missing. We know we need it. If you don't think we're working fast enough, you can submit a merge request or dock our pay. -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

4 years, 4 months

[MM3-users] Re: URL-lines in templates get folded

by Mark Sapiro

On 10/18/22 10:45, Frank Steinberg wrote: > > > The folding appears in the raw message sent by Mailman and put into the users INBOX. > > I thought there could be a kind of filter in Mailmans mailout processing that cares for line breaks in order to not exceed approx. 75 chars per line? Some but not all templates are wrapped at column 70 by the function at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/stri…. Those that are wrapped are: list:admin:action:subscribe list:admin:action:unsubscribe list:admin:notice:pending list:user:notice:goodbye list:user:notice:hold list:user:notice:no-more-today list:user:notice:probe list:user:notice:refuse list:user:notice:warning list:user:notice:welcome Others are not. For those that are wrapped, there are techniques to avoid wrapping. In particular, lines beginning with whitespace aren't wrapped so if you put your long URL preceded by a space, all on one line it won't wrap. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: Make archives private by default

by Mark Sapiro

On 5/11/23 12:03 PM, mrl(a)psfc.mit.edu wrote: > Hi - I imported mailman 2 mailboxes which were private. Settings show them to be private, but they are not. It's possible to view them without being logged in. Should that be happening? No. I don't know what the issue is, but if Postorius shows the list's Archive policy as Private archives HyperKitty should not allow a non-logged in user to view that archive. > Can someone point to me the documentation on mailman.cfg features? I.e., I read on this mailing list that one can set archives for new lists to be private using: > > [styles] > default: private-default That's correct. > But where can I find that and other features? Thanks. I don't think there is a good doc on this, but https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.… has a fair amount of documentation in comments. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: Is there a way to see all the list's held messages

by Mark Sapiro

On 10/15/22 02:47, Martin Lorenz wrote: > Mark Sapiro wrote: >> On 10/11/22 07:04, bob B via Mailman-users wrote: > [...] >> run mailman' mean you are an admin of the server on which it is >> installed? If so, you can do this in mailman shell, but what do you > > in my case: yes > >> want to see? I.e., just a summary by list of subject, sender and hold >> reason > > how would I do this? For example, a `mailman shell` interaction like this ``` $ /opt/mailman/mm/bin/mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> for mlist in getUtility(IListManager): ... requests = IListRequests(mlist) ... first = True ... for request in requests.held_requests: ... key, data = requests.get_request(request.id) ... if first: ... first = False ... print(mlist.list_id) ... print(f"""\ ... Sender: {data['_mod_sender']} ... Subject: {data['_mod_subject']} ... Date: {data['_mod_hold_date']} ... Reason: {data['_mod_reason']} ... """) ... ``` > Additional question: how would I set/change the owner of a number of lists identifyable by a regular expression? Something like this: ``` >>> import re >>> newowner = 'newowner(a)example.com' >>> user_manager = getUtility(IUserManager) >>> # get the address record for the new owner >>> address = user_manager.get_address(newowner) >>> # create one if necessary >>> if address is None: ... user = user_manager.create_user(newowner) ... address = list(user.addresses)[0] ... >>> for mlist in getUtility(IListManager): ... if not re.search('the criterion', mlist.list_id): ... continue ... # remove existing owners --- for owner in mlist.owners.members: ... owner.unsubscribe() ... # add new owner ... mlist.subscribe(address, MemberRole.owner) ... >>> commit() >>> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

[MM3-users] Re: Gmail/Fetchmail in Mailman3?

by Mark Sapiro

On 06/23/2018 02:48 PM, Bill Christensen wrote: > > Our Mailman2 setup uses Fetchmail to retrieve list mail from our > accounts on Gmail. > > Is there a similar setup for Mailman3? Delivery to Mailman is different in Mailman 3. What are you currently doing with Fetchmail? If you are doing something like getting the mail from google and delivering it via SMTP to an MTA on the Mailman server, that should still work for MM 3. If Fetchmail is piping it to a command like "| /path/to/mail/mailman post listname" that won't work in Mailman 3. Mailman 3 gets mail via its own LMTP server (which it calls a runner). Mail is normally delivered to an MTA which is configured to relay the mail via LMTP to the localhost port that Mailman is listening on. So Fetchmail can eithr deliver to the MTA and let the MTA relay to Mailman or deliver directly to Mailman's LMTP port. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 1 month

[MM3-users] Re: Office365 posts shunted (authres.core.SyntaxError)

by Mark Sapiro

On 9/17/20 2:41 PM, brylon(a)oit.rutgers.edu wrote: > > [1] I currently applied this hack to get around the syntax error... > > $ diff -u venv/lib/python3.6/site-packages/mailman/handlers/validate_authenticity.py.ORIG venv/lib/python3.6/site-packages/mailman/handlers/validate_authenticity.py > --- venv/lib/python3.6/site-packages/mailman/handlers/validate_authenticity.py.ORIG 2020-09-16 14:23:03.565482574 -0400 > +++ venv/lib/python3.6/site-packages/mailman/handlers/validate_authenticity.py 2020-09-17 13:17:09.296409626 -0400 > @@ -70,10 +70,12 @@ > > if config.arc.trusted_authserv_ids and (AUTH_RESULT_HEADER in msg): > header = '{}: {}'.format(AUTH_RESULT_HEADER, msg[AUTH_RESULT_HEADER]) > - authserv_id = AuthenticationResultsHeader.parse(header).authserv_id > - if authserv_id in config.arc.trusted_authserv_ids: > - return header > - > + try: > + authserv_id = AuthenticationResultsHeader.parse(header).authserv_id > + if authserv_id in config.arc.trusted_authserv_ids: > + return header > + except: > + log.exception('AR header failed to parse for message: %s', msg['Message-ID']) > > @retry(Timeout, NUM_TIMEOUT_RETRIES) > def authenticate(msg, msgdata): I think that's fine. Also, you should look at <https://gitlab.com/mailman/mailman/-/issues/765>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: spanish localization

by Mark Sapiro

On 2/14/21 3:21 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > I did some exploration this morning (Spain time) in the weblate > statistics and archives and I found that the changes done from > Victoriano and me were recorded. I did a screencopy of all that if > someone has any doubt about it. I downloaded this files: > > -rw-r--r-- 1 1002 wheel 11037 Feb 14 10:57 gnu-mailman-django-mailman3-es.po > -rw-r--r-- 1 1002 wheel 34511 Feb 14 10:54 gnu-mailman-hyperkitty-es.po > -rw-r--r-- 1 1002 wheel 143758 Feb 14 10:51 gnu-mailman-mailman-es.po > -rw-r--r-- 1 1002 wheel 104997 Feb 14 10:49 gnu-mailman-postorius-es.po > > The thing is that they differ from the .po installed via pip upgrade. > Mostly, as said, postorius, hyperkitty and django_mailman3. The latest packages in PyPI (pip) were released on Feb 2 except for django-mailman3 which was released on Jan 15. They don't include updates after those dates. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: Change 'from' server for outgoing messages

by Mark Sapiro

On 3/11/23 16:44, Benjamin Goldberg wrote: > > BTW the errors that I had been getting were, at first: > response exception: (450, b'The from.email must be verified. The from.email must be verified.') > but later changed to: > response exception: (450, b'Sorry, please try again. 429 Too many requests.') > > I had assumed both errors were being generated by MailerSend but now I'm not sure Yes, they are from your smtp_host which was mailersend Both those are retryable and will be retried by Mailman to a point. I suggest if you want to use mailersend that in Postorius DMARC Mitigations you set DMARC mitigation action to Replace From: with list address and DMARC Mitigate unconditionally to yes. That will ensure all posts are From: the list address and will probably avoid the 'The from.email must be verified. The from.email must be verified.' error. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: How to process emails with Mailman3?

by Mark Sapiro

On 3/10/25 12:24 AM, Kyle Lahnakoski wrote: > > When I add a user (like myself) I get a welcome email from all- > request(a)mymaillist.org. When I respond, the mail arrives in the S3 > bucket, but I do not know how to give it to mailman3. The "inject" > command will not work because there is no "all-request" mailing list. > > > How do I feed these administrative mails to mailman3? You can use `inject` with something like ``` /opt/mailman/venv/bin/mailman inject -f <somefile> -q command all(a)mymaillist.org ``` but > I have tried netcat the email to the ?LMTP? port, but it fails: this is the better way. The issue is you are not using `nc` correctly. When you do $ nc localhost 8024 < /tmp/pbTw1oqmV1rZtHXV707Jcov264hr you are telling nc to take commands from the file /tmp/pbTw1oqmV1rZtHXV707Jcov264hr. You need to give it a command to send the file. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 3 weeks

[MM3-users] Re: How to Increase outgoing mail volume for Mailman 3

by Mark Sapiro

On 11/10/20 12:30 PM, Brian Carpenter wrote: > Hello everyone, > > We had a new client come on board that brought a list that had the > largest out-going mail volume that I have ever dealt with. So I did what > any sane server administrator would do that is running Mailman 3: I ran > to Mark Sapiro for help! Here is what the Sage of all things Mailman > counseled me to do: Thank you <blush> > 1. Disabled VERP delivery. VERP can help improve mail delivery by > delivering 1 message per SMTP transaction (I think I got that right). > Using VERP is counter-productive as it can seriously delay outgoing mail > delivery for a high-volume list. So you can use something like the > following in the MTA section of your mailman.cfg: Actually, I mentioned VERP, but I don't think I recommended disabling it. Also note that these settings: > [mta] > verp_confirmations: no > verp_personalized_deliveries: no > verp_delivery_interval: 0 are the defaults. Further, verp_confirmations is a holdover from MM 2.1 and has no effect, although prior to Mailman 3.3.2 confirmations were sent with `confirm <token>` as the Subject: and beginning with Mailman 3.3.2, confirmations are sent with `Your confirmation is needed ...` as the Subject:. Actually, I think enabling VERP with [mta] verp_delivery_interval: 1 is generally a good idea for more reliable bounce detection. > 2. I configured Mailman 3 to run 4 outgoing runners. The default is 1. > This action was the game changer. It allows Mailman to handle 4 incoming > messages at a time instead of 1. My client's incoming list volume was > high enough where it was overwhelming the single outgoing runner. Here > is what I added to the mailman.cfg file: > > [runner.out] > instances: 4 > > Doing this step immediately solved the backlog in var/queue/out. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: DMARC Munging

by Mark Sapiro

On 1/26/20 4:43 PM, Allan Hansen wrote: > All, > > The munged From: header in MM3 still says > 'name' via ‘listname’ <‘listaddress’> > > This caused me and my subscribers a lot of grief in MM2: > Some mail clients use the first part up to the From for future key-ahead for new email to ’name’, hiding the address, so what they think is a personal message for ’name’, instead goes to the entire list. Red faces all around. > > Stephen Thurnbull earlier suggested further munging by replacing the list address in the From: header like this: > > 'name' via ‘listname’ <‘whoopsieaddress’> > > Which will return an automated reply explaining the issue. I like this option. How can I get that in? You can file an issue at <https://gitlab.com/mailman/mailman/issues>. That will at least get it on the table, but there are no guarantees as to if/when it would be implemented. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: Apple Mail encoding again

by Mark Sapiro

On 4/21/22 04:53, tlhackque via Mailman-users wrote: > > Note that MailMan is encapsulating a multipart/signed message in a > multipart/mixed in order to append it's footer, and reports that it > removed the signature part of the multipart/signed. This makes the > signed message format invalid. So at least, MM3 needs to handle signed > messages better: either include the signature or remove the signature > headers (an unwrapping exercise to convert the message to unsigned)... > Note that this can be recursive where a signed message contains a > message/rfc822 part that contains a signed message, that.... This was an issue with Mailman's content filtering for the mailmanusers(a)mailman3.org list. Pass types was: multipart message/rfc822 text application/pgp-signature So the application/x-pkcs7-signature part was removed. I have just updated Pass types to: multipart message/rfc822 text application/pgp-signature application/x-pkcs7-signature to not remove application/x-pkcs7-signature parts going forward. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: Recently active discussions - Hyperkitty

by Mark Sapiro

On 6/3/24 8:55 AM, Sam Darwin wrote: > > Try this: > > systemctl reload mailman3-web > or > systemctl restart mailman3-web > > The "Recently Active Discussions" listing is refreshed! That fixes it. > > --- > > Related issue, #2 > > On the "Recently Active Discussions" page, click on a message, a test message, and then "Delete this thread". It's deleted. > > Now "Recently Active Discussions" hangs. A spinning icon, indefinitely. In the logs file: "hyperkitty.models.thread.Thread.DoesNotExist: Thread matching query does not exist." > Re-running recent_threads_cache, and restarting Django, fixes it. However in production you wouldn't want to wait 24 hrs, and also manually restart the web. As you say, these issues may be related. The latter is already reported at https://gitlab.com/mailman/hyperkitty/-/issues/504 and as it says there, I am unable to duplicate it; it may be related to which database manager you use. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 1 month

[MM3-users] Re: when on particular person sends a message to the list dozens of OTHER users have their bounce score incremented

by Mark Sapiro

On 8/30/24 14:34, Ken Alker wrote: > I just found and then changed the "Settings/Alter Messages/Replay goes > to list" from "No Munging" to "Reply goes to list" to combat the reply > issue I mentioned above. I suppose this means that if someone sent a > specific Reply-to: in their original email, it gets overwritten. I > suppose there is no perfect solution. If `Reply goes to list` is set to `Reply goes to list`, the list posting address is added to the Reply-To: header. I.e., if there is a Reply-To: in the incoming message, The resultant Reply-To: contains the original plus the list posting address unless `First strip Reply-To` is `Yes` in which case it contains only the list posting address. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 3 weeks

[MM3-users] Re: MM2 to MM3 Archives Loading

by Mark Sapiro

On 12/4/24 12:45, Joshua Bushe wrote: > > This link is an example you sent earlier: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/ > > This link is above is the page where i can't see any of my lists outputs on my mailman3 gui. All i visually see is three loading icons spinning. Also, mark said it will only show threads with post in the last 30 days. so i made a test list and made a new thread and still the problem persists. Still see the three loading icons spinning. I've manually added the test list and also did it through the gui. Same outcome. We've seen issues like this before? Are you running the django cron tasks <https://docs.mailman3.org/en/latest/install/virtualenv.html#cron-jobs-for-m…>. Sometimes the `daily` jobs fix this. Also if you haven't done so, restarting the WSGI server (uWSGI, gunicorn, Apache mod_wsgi) may help. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 4 weeks

[MM3-users] Re: Problem with perms on /etc/mailman3/mailman.cfg while following https://docs.list.org/en/latest/install/virtualenv.html on new mailman3 Debian 12 installation

by Mark Sapiro

On March 25, 2025 1:20:22 AM GMT+07:00, Philip Bondi <pjbondi(a)systemdatabase.com> wrote: > >The instructions https://docs.list.org/en/latest/install/virtualenv.html#installing-mailman-… do not say what to do with existing file. > >root@shackleton12:~# ls -alF /etc/mailman3/mailman.cfg >-rw-r--r-- 1 root list 11119 Mar 20 11:45 /etc/mailman3/mailman.cfg > >Should we move the /etc/mailman3/mailman.cfg out of the way and create new file as user and group mailman:mailman ? How did that file get there? It looks like at some point you installed the Debian package. If you are following <https://docs.list.org/en/latest/install/virtualenv.html you shouldn't install the Debian package. In any case, just remove the file. Probably it's best to remove the Debian package completely and start over. -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

4 months, 1 week

[MM3-users] Re: content filtering in version 3.1

by Mark Sapiro

On 5/11/21 8:45 PM, Simon Handfield via Mailman-users wrote: > Hi everyone, > > I'm sorry to resurrect this thread from so long ago but it appeared to provide exactly the answer I was looking for, trying to manage pass_types in 3.1.1 on Ubuntu 18.04. > > GNU Mailman 3.1.1 (Between The Wheels) > > Unfortunately when I run: > > ./bin/mailman shell -l [list address] > > I receive: > > usage: mailman [-h] [-v] [-C CONFIG] > {help,aliases,conf,create,digests,import21,info,inject,lists,members,qfile,remove,reopen,restart,shell,start,status,stop,unshunt,version,withlist} > ... > mailman: error: unrecognized arguments: -l > > Can anyone advise how I can use the -l switch to manage this setting for a list? Older versions of Mailman core did not support the -l/--listspec option for mailman shell. They expected the listname as an argument as in ``` mailman shell list(a)example.com ``` What does ``` mailman shell --help ``` show in your case? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

[MM3-users] Re: FW: [Django] ERROR (EXTERNAL IP): Internal Server Error: /user-profile/

by Mark Sapiro

On 10/16/21 9:52 AM, Christian Stalberg via Mailman-users wrote: > When I go to https://.../admin/ I get a Django Administration screen and in > the upper right hand corner I see > > WELCOME, <username>. VIEW SITE / CHANGE PASSWORD / LOG OUT And my point was if you go to Users under Authentication and Authorization you should find that alekos.pantazis is a user. If you go to your own https://www.grizz.org/user-profile/ page, do you see a gravatar to the right of the Username, First name, Last name boxes, and does going there produce the same error in the logs. If that's all OK, then I don't know what produced the original error, but I think you can ignore it. If that produces the same error in the logs, then something is wrong with your django-mailman3 installation, but I don't know what. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Re: 500 error on Held Messages page

by Mark Sapiro

On 9/20/22 14:50, Dan Caballero wrote: > > 2022-09-20 14:44:17 [FALCON] [ERROR] GET /3.1/lists/jewishlife(a)caltech.edu/held?count=10&page=1 => Traceback (most recent call last): > File "falcon/app.py", line 365, in falcon.app.App.__call__ > File "/opt/mailmanve/lib/python3.9/site-packages/mailman/rest/post_moderation.py", line 182, in on_get > resource = self._make_collection(request) > File "/opt/mailmanve/lib/python3.9/site-packages/mailman/rest/helpers.py", line 182, in _make_collection > entries = [as_dict(resource) for resource in collection] > File "/opt/mailmanve/lib/python3.9/site-packages/mailman/rest/helpers.py", line 182, in <listcomp> > entries = [as_dict(resource) for resource in collection] > File "/opt/mailmanve/lib/python3.9/site-packages/mailman/rest/post_moderation.py", line 173, in _resource_as_dict > assert resource is not None, resource > AssertionError: None This is most likely a race condition between two browsers, one of which handles the held message while the other is getting the held messages. Check Mailman's access.log entries with time stamps around 2022-09-20 14:44:17. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

[MM3-users] Re: (venv) mailman-web migrate (as explained) fails with "django.core.exceptions.ImproperlyConfigured: allauth.account.middleware.AccountMiddleware must be added to settings.MIDDLEWARE"

by Mark Sapiro

On 10/19/23 13:15, Wikinaut wrote: > > However myserver/mailman3 page is throwing > > Erfolgreich als Admin angemeldet. > Something went wrong >>>> HTTP Error 401: REST API authorization failed > > Even when the API keys are unchanged from my previous installation. Any idea what can be wrong here? what does the command `mailman info` show for REST credentials? The defaults for these are REST credentials: restadmin:restpass set by admin_user: restadmin admin_pass: restpass in the [webservice] section of mailman.cfg and the corresponding defaults for Django settings are: MAILMAN_REST_API_USER = 'restadmin' MAILMAN_REST_API_PASS = 'restpass' If you have something different, is it set in both mailman.cfg and settings.py? Is there more information in /opt/mailman/mm/var/logs/mailman.log or /opt/mailman/web/logs/mailmanweb.log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: Immediate notification to the administrator

by Mark Sapiro

On 11/2/23 07:48, Stephen J. Turnbull wrote: > > Until then, here's the crontab template distributed with Mailman 3.2.2: > > # At 8AM every day, mail reminders to admins as to pending requests. > 0 8 * * * @PYTHON@ -S @prefix@/cron/checkdbs > # > # At 9AM, send notifications to disabled members > 0 9 * * * @PYTHON@ -S @prefix@/cron/disabled > # > # Noon, mail digests for lists that do periodic delivery. > 0 12 * * * @PYTHON@ -S @prefix@/cron/senddigests > # > # Every 5 mins, try to gate news to mail. > */5 * * * * @PYTHON@ -S @prefix@/cron/gate_news > # > # At 3:27am every night, regenerate the gzip'd archive file. Only > # turn this on if the internal archiver is used and > # GZIP_ARCHIVE_TXT_FILES is false in mm_cfg.py > 27 3 * * * @PYTHON@ -S @prefix@/cron/nightly_gzip This Mailman 3.2.2 cron/crontab.in.in file is is an artifact from Mailman 2.1. Nothing there is relevant to any Mailman 3 version -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

[MM3-users] Re: Changes in Django admin interface are not syncing to postorius gui /database

by Mark Sapiro

On 11/9/24 05:32, ulf.rapphahn(a)offis.de wrote: > Hello, > I have the lasted version of mailman3 in an fresh venv installation and I am testing it for our upcoming migration from v2.1. > > When I add a new list in the django admin interface this list will never appear in postorius (vice versa it works). Because the mailing lists in the Django admin interface are HyperKitty Lists, not Mailman lists. When you create a list in Postorius or Mailman core, this is a Mailman list. A corresponding HyperKitty list will also be created if hyperkitty is one of the active archivers for the list so you see it in Django. When you create a list in Django, it is only a HyperKitty list and will be visible in HyperKitty, but no Mailman list is created so the list is not in Mailman/Postorius. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 3 weeks

[MM3-users] Re: (Custom) Plugins: Proper file path(s) for adding a handler?

by Mark Sapiro

On 10/24/23 3:56 PM, Thomas Ward via Mailman-users wrote: > > When I DO NOT have the module loaded in the configuration, `mailman > shell` works. Since that was functional, I went into the shell and > executed this: > > > from mailman_customizations.hooks import MailmanCustomizations > > This worked fine, but obviously importing the class doesn't necessarily > *activate* the class. So something is up with how I'm *supposed* to > activate the plugin in the config, and we know that it's visible to > Mailman in its shell, but it can't autoload it. I'm past the limit of my knowledge here and only stabbing in the dark, but what happens after you import it. Can you instantiate it, e.g. ``` instance = MailmanCustomizations() dir(instance) ``` I'm not saying this should succeed, just that it may possibly provide useful information. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: Show number of subscribers

by Mark Sapiro

On 6/28/19 3:19 AM, andrew.bernard(a)gmail.com wrote: > Would there be a way to show the number of subscribers to a list in the web UI? > > The number of participants per message is great, but this would be good too. My users seem very interested in this number. I guess they want to know how big the audience is that is reading their posts. I don't know how difficult it would be to add this to HyperKitty, and I'm not sure how useful it would be in general. HyperKitty is an archiver. It deals with archiving posts. It knows who has sent a post, but doesn't know or care if that person is, was or will be a member of the list. Postorius knows who the list members are and this information should be available to list members or the world depending on the list's member_roster_visibility setting, but see <https://gitlab.com/mailman/postorius/issues/369>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 1 month

[MM3-users] Re: Cannot show archives

by Mark Sapiro

On 9/26/19 5:48 PM, Qiuhong.Su 蘇秋紅 wrote: > Hi all, > > After I setup mailman3 and run mailman-suite, I can do: > > 1. Register user > > 2. Login > > 3. Create new Domain > > 4. Create new List > > 5. Subscribe to the list > When I try to send email to the list by run command: echo “test email” | mail –s “test email” test(a)example.com > User test can receive this email, but I cannot find it on Archives, and other members cannot receive this email too. You say "User test can receive this email". Is test(a)example.com a user or the list's posting address? If you are saying that test(a)example.com should be the list's posting address, but the mail is instead delivered to the user test(a)example.com, you have not set up your MTA to properly deliver list mail to Mailman. See <https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

[MM3-users] Re: Confirmation emails to Users has wrong domain name (example.com!)

by Mark Sapiro

On 9/29/21 9:50 AM, Odhiambo Washington wrote: > 1. Confirmation emails to Users has wrong domain name (example.com!) > <https://docs.mailman3.org/en/latest/faq.html#id1> > <https://docs.mailman3.org/en/latest/faq.html#confirmation-emails-to-users-h…> > > This happens when your reverse (SSL) proxy isn’t setting up the correct > headers when proxying requests. Fix this by setting the right > proxy_set_header directives: ... > How is this supposed to be mitigated in Apache when using WSGI? > > My config: > > WSGIDaemonProcess hyperkitty threads=25 python-path=/usr/local/mailman > user=mailman group=mailman > WSGIPythonHome "/usr/local" > WSGIProcessGroup hyperkitty You are using mod_wsgi and not proxying at all, so this is not relevant in your case. Are you actually seeing this issue? If so, it might be related to https://docs.mailman3.org/en/latest/faq.html#the-domain-name-displayed-in-h… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

[MM3-users] Re: Apache Configuration for Subdomain

by Mark Sapiro

On 7/26/22 14:20, Mail Person wrote: > Ok, progress with tinkering some. Using the below configuration I can manually navigate to lists.example.com/mailman3/postorius/lists/ and all is working fine. If I go to lists.example.com/mailman3 it for some reason redirects to lists.example.com/mailman/postorius/lists/ which generates a 404. This is a uWSGI issue. > ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost Others have found that changing this to ``` ProxyPass /mailman3/ unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ ``` fixes it. Note the added slashes after `mailman3` and `localhost`. See this thread https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > Going to lists.example.com also hits a 404. Here > RewriteEngine on > RewriteCond %{SERVER_NAME} =lists.example.com [OR] > RewriteCond %{SERVER_NAME} =www.lists.example.com > RewriteRule ^ https://%%7BSERVER_NAME%7D%%7BREQUEST_URI%7D [END,NE,R=permanent] You're redirecting http to https, but have you defined a VirtualHost for port 443? Just copy your <VirtualHost *:80> block to a <VirtualHost *:443> block. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

[MM3-users] Re: URLs in moderation messages

by Mark Sapiro

On 3/3/23 01:55, Tim Cutts wrote: > > I’ve clearly got something wrong in my configuration, but I can’t work out what. > > All my URLs seem to have the “mailman3” part duplicated, i.e. > > Https://example.com/mailman3/mailman3/lists > > Is where I have to go to get a list of my mailing lists, which just doesn’t seem right. > > In my settings.py file I have: > > POSTORIUS_TEMPLATE_BASE_URL = 'https://example.com/mailman3/' > > If I change the value of this to just https://example.com/ it doesn’t change this, That setting has nothing to do with your issue. It only determines the base part of the URL that's used to retrieve templates set in Postorius. What is your web server configuration? This is probably where the problem lies. See https://docs.mailman3.org/en/latest/install/virtualenv.html#nginx-configura… for a suggested nginx config and https://docs.mailman3.org/en/latest/install/virtualenv.html#apache-configur… for Apache. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: clicking on a username when viewing a thread results in "Page not found"

by Mark Sapiro

On 6/26/23 12:20 AM, Ken Alker wrote: > If I click on a username when viewing a thread, it returns "Page not found" then "This page either doesn't exist, or it moved somewhere else.". Any idea why this may be happening? This is a problem. That link goes to, e.g., https://example.com/archives/users/<user_id>/. What do you get if you strip the user_id and just go to what https://example.com/archives/users/ translates to on your system? You should get a page saying ``` Not implemented This feature has not been implemented yet, sorry. ``` If you get a 404, there is an issue with your web server configuration or maybe your top level urls.py. > Also, why is it that some usernames are not clickable (ie. black text with no hyperlink)? I'm not sure without research. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

[MM3-users] Re: Displaying addresses in emails from a Mailman 3 installation

by Mark Sapiro

On 7/4/25 11:08, Steve Brown via Mailman-users wrote: > Yes, I intended to post to the list. I now see that if I use the archives > to post (as I'm doing now), I have to use "reply all". On my Outlook, it's > the other way around. If I want to reply off-list, I have to click on > reply all and then remove the list address. Sorry. I only use the Gmail > address for a few limited purposes. I don't understand. When I reply from HyperKitty, the reply just goes to the list whether I enter the reply in the web UI or "Use email software". There is no "reply all" option and no way to reply to the poster other than using the "Use email software" method and manually adjusting the recipient addresses. Is this not the case with you? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 weeks

[MM3-users] Re: Handling of Mail from non-subscribers

by Mark Sapiro

On 5/8/20 4:42 PM, Peter Adebahr via Mailman-users wrote: > > I have a fresh setup of MM3 on Ubuntu 20, installed by apt-get. It seems > to be running fine so far, except for some (to me) strange behaviour: > > When posting to the list as a non-subscriber, I see the mail coming in > on mailman's smtp.log, then it vanishes. No notice of this mail being > hold is sent to the sender, no notice to the moderator, and logging into > Postorius as owner of the list, it is not showing up in "Held messages" > > "Hold for moderation" has been set. Set in "Default action to take when a non-member posts to the list"? If that is the case, find the non-member in Users -> Non-Members and look at the Non-member Options link. What is the "Administration options Moderation" setting? for that non-member? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: How To Install Mailman 3 on Debian 10 (Complete Guide)

by Mark Sapiro

On 2/27/21 4:36 AM, Stephen J. Turnbull wrote: > > As far as I know the "emoji" problem (MySQL doesn't handle Unicode > characters outside of the Basic Multilingual Plane by default) is > still present. Given that emoji are now in use by pretty much > everybody and easily accessible on most platforms, this default is > unfortunate. However, I believe this is a server-wide setting, so I > am dubious that Mailman should force the "full Unicode" setting on. > (Anybody who knows feel free to correct me.) As far as I know, the `OPTIONS {'charset': 'utf8mb4}` setting in the `DATABASES` definition for mysql (see <https://gitlab.com/mailman/mailman-suite/-/blob/master/mailman-suite_projec…>) will fix this issue. Although, one user may be currently having this issue where the `OPTIONS` setting doesn't fix it <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: Username being set to givenname for socialaccount login

by Mark Sapiro

On 9/22/21 11:22 AM, cfarley(a)iastate.edu wrote: > I have a new mailman3 install setup with Okta as a social application. This is working well for logins and data comes through as expected, but for some reason the username is being set at to a lowercase version of the given_name. The Extra data on the social users in the admin interface looks good, so I don’t think it’s a problem with the attributes coming from Okta. > > We have tried a number of variations on the below setting, but that all of them other than the default of “username” end up with the username being empty. > ACCOUNT_USER_MODEL_USERNAME_FIELD = “email” > > Any direction would be welcome. This is an issue for Django allauth <https://django-allauth.readthedocs.io/en/latest/index.html>. Mailman has no control over this. The username is part of Django's login and is not used by Mailman at all. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

[MM3-users] Re: eccentric setup question

by Mark Sapiro

On 3/21/23 02:05, Jeff Berry wrote: > > The problem we're having is that if the mailman domain of the list is listserver.domain.com then spamfilters start to flag the mail since it looks like spoofing/malformed headers and so on. If the mailman domain is just domain.com then postfix rejects it with an unknown local recipient error. I though I might be able to just tweak the incoming mail headers in postfix via header_checks but that's not working, either because I've got the wrong check or it's the wrong approach, or both. > > postfix relay_domains might do it, I think, but if it maps listserver.domain.com to domain.com that would break the listserver domain mailing lists (I think). Is Postfix on the mailman server set up per https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… and did you run `mailman aliases` to regenerate mappings after changing Exchange to relay to list(a)domain.com? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: Mailman3-Web lots of database queries

by Mark Sapiro

On 11/17/18 8:36 AM, Stefan Tatschner wrote: > Hey! > > I recently set up a mailman3 instance and it works quite nice. I use > the debian packages from buster. After running the thing for a few > days, I realized an unexpected network load (my postgres database is on > a separate machine). Turning the postgres log on revealed that mailman3 > constantly queries the database: > > [...] > 2018-11-17 16:33:15.417 UTC [8304] mailman3web@mailman3web LOG: statement: SELECT "django_q_ormq"."id", "django_q_ormq"."key", "django_q_ormq"."payload", "django_q_ormq"."lock" FROM "django_q_ormq" WHERE ("django_q_ormq"."key" = 'default' AND "django_q_ormq"."lock" < '2018-11-17T16:32:15.385901+00:00'::timestamptz) LIMIT 1 ... > > Is this behaviour intended? No. This is not normal. This is apparently coming from Django qcluster. At least it is qcluster that uses the django_q_ormq table, but these repeated queries are not normal, at least I don't see them in the sites I administer. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 8 months

[MM3-users] Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive

by Mark Sapiro

On 2/25/21 6:32 AM, David Partain via Mailman-users wrote: > > In /etc/mailman3/mailman.cfg I see: > > > class: mailman.database.mysql.MySQLDatabase > > url: mysql+pymysql://mailman3:NopeNotPastingThat@localhost/mailman3?charset=utf8&use_unicode=1 > > > Should I change the latter to be something like: > > > url: mysql+pymysql://mailman3:NopeNotPastingThat@localhost/mailman3?charset=utf8mb4&use_unicode=1 Yes, either make it charset=utf8mb4 or I think dropping the charset= option altogether will use the database default, however I'm not clear why this would be the issue as this only controls how Mailman core accesses the database, and your issue is with HyperKitty/Django and its access is controlled by the DATABASES setting in Django's settings which you say do specify 'charset': 'utf8mb4' in OPTIONS. Also, it seems Mailman core is not even using the same database - i.e. `mailman3` whereas Django's is `mailman3web`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: Hyperkitty on Debian 12

by Mark Sapiro

On 3/25/24 07:58, Markus Grandpre wrote: > Dear list members, > > when following the instructions to migrate list archives from Mailman21 > to Mailman3 (see [1]), I face the following problem: > > # python3 manage.py hyperkitty_import -l mailman21-migration-test-04 > /var/mailman21/testlist.mbox > python3: can't open file '/var/mailman21/manage.py': [Errno 2] No such > file or directory > > and have no clue, where to find the right <manage.py> file. The command This depends on how you installed Mailman 3. You may or may not want `python3 manage.py` at all. The required command could be something like `django-admin` or `mailman-web`. Also the `#` prompt indicates you may be running as root. Mailman related commands should be run as the Mailman user (could be `mailman` or `list` or ... depending again on how you installed Mailman). Running as root can create files owned by root that later can't be read by the Mailman user. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

[MM3-users] Re: Exception in the HyperKitty archiver: 'utf-8' codec can't encode characters

by Mark Sapiro

It turns out this error is caused by a non-ascii character in a prologue section of the email. When the message gets parsed into a mailman.email.message.Message objectand then flattened to a string, the non-ascii in the prologue gets converted to unicode surrogates which causes problems in subsequent processing. The bug report has moved twice in the process of diagnosing and fixing this - from https://gitlab.com/mailman/hyperkitty/-/issues/301 to https://gitlab.com/mailman/mailman-hyperkitty/-/issues/25 to https://gitlab.com/mailman/mailman/-/issues/732 The fix is in core and is quite simple. ``` --- a/src/mailman/email/message.py +++ b/src/mailman/email/message.py @@ -55,7 +55,8 @@ class Message(email.message.Message): except (KeyError, LookupError, UnicodeEncodeError): value = email.message.Message.as_bytes(self).decode( 'ascii', 'replace') - return value + # Also ensure no unicode surrogates in the returned string. + return email.utils._sanitize(value) @property def sender(self): ``` See https://gitlab.com/mailman/mailman/-/merge_requests/665 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

[MM3-users] Re: Rejection Reason for refusing a subscription request

by Mark Sapiro

On 3/27/21 2:08 PM, Brian Carpenter wrote: > I was testing out the process of rejecting an incoming subscription > request. Choosing the reject option for a moderated subscription request > does send out a rejection notice but it gives no reason for the > rejection. ... > Is there a place somewhere in Postorius to provide a rejection reasons > for moderated subscription requests? Does Mailman 3 core provide this > via its REST api but it is just not revealed in Postorius yet? It's in Postorius since 1.3.3. If in the held message view, you click the subject of a held message, you get a popup dialog the shows the message with options to also show headers or the raw message. There is also a dropdown t=o set the poster's moderation action and a box for a reject reason if you click the reject button in the dialog. Do you not see this? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users] Re: List Migration from MM2.1 -> MM3

by Mark Sapiro

On 8/15/22 00:32, Odhiambo Washington wrote: > > Apparently so, because: > mailman@lists:~$ /opt/mailman/mm/venv/bin/mailman lists > No matching mailing lists found > mailman@lists:~$ > > Which is surprising, given this: https://imgur.com/a/LPrh42K Postfix is talking to a different Mailman core. > root@lists:/home/wash# su - mailman > mailman@lists:~$ /opt/mailman/mm/venv/bin/mailman create > skunkworks(a)lists.my.co.ke > sh: 1: /usr/sbin/postmap: not found > sh: 1: /usr/sbin/postmap: not found > Traceback (most recent call last): ... > RuntimeError: command failure: /usr/sbin/postmap > /opt/mailman/var/data/postfix_lmtp, 127, Key has expired > command failure: /usr/sbin/postmap /opt/mailman/var/data/postfix_domains, > 127, Key has expired > > Now that wants Postfix, while I don't use Postfix, but Exim as the MTA. In the [mta] section of mailman.cfg, put ``` incoming: mailman.mta.exim4.LMTP configuration: python:mailman.config.exim4 ``` See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[MM3-users] Re: MM attaches mime-attachments to mail as text file since update to 3.3.8

by Mark Sapiro

On 1/23/23 22:50, Stefan Bauer wrote: > Dear Mark, > > thank you for your time. > > Here are the lists settings and an example mail attached. > > Filter content: NO > Filter types: EMPTY > Pass types: EMPTY > Pass extensions: EMPTY > Collapse alterantives: YES > Convert html to plaintext: NO > > Thunderbird is showing the mail "correct". Outlook does show the > attachments as attachments. So Filter content is NO so Mailman isn't doing any content filtering. All it is doing is adding headers and footers if any, and if the original message is other than a single text/plain part, these will be added as separate MIME text/plain parts. For a discussion on why this is done, see https://wiki.list.org/x/4030707 which is written for MM 2.1, but which applies at least generally to MM 3. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] Re: Held messages not delivered after approval

by Mark Sapiro

On 7/30/25 07:27, Stephan Krinetzki wrote: > Hi all, > > I'm running into an issue with Mailman 3. Mails sent to a list are being held due to moderation settings — which is expected — but after approving them, they are not delivered to list members. Are there any regular members with delivery enabled? ``` mailman members --regular --nomail enabled LISTSPEC ``` > The message does not end up in the shunt queue, and nothing is delivered. > > Here's what I see in the Mailman log: > > Jul 30 16:12:23 2025 (213300) HOLD: mm(a)lists.example.com post from sender(a)sub.example.com held, message-id=<20250730141221.5VVrn%sender(a)sub.example.com>: The message is not from a list member > Jul 30 16:12:39 2025 (213338) held message approved, message-id: <20250730141221.5VVrn%sender(a)sub.example.com> This is expected. Is there anything relevant in Mailman's smtp.log? Do any posts to this list get delivered, e.g., posts which aren't held. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 days, 6 hours

[MM3-users] Re: Where do I find the bounced messages?

by Mark Sapiro

On 12/20/22 02:29, Sörös Zoltán wrote: > Greetings, > I am running several lists under mailman3. I am getting notifications > about users being put on nomail because of their bounces - but I can > find no way to actually see the bounced messages. > > Do mailman3 store the received bounces? Where? They are stored in the message store in the database but only temporarily. > Is there any setting to forward these bounces to the list owner? There are two relevant settings. These are exposed in Postorius -> Settings -> Bounce Processing. They are: Notify owner on bounce increment - sends a notice to the owner including the DSN when a user's bounce score is incremented, but to a value less than the bounce threshold. Notify owner on disable - sends a notice to the owner including the DSN when a member's subscription is automatically disabled due to the bounce threshold being reached. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 7 months

[MM3-users] Re: messages with attachments, without text discarded silently

by Mark Sapiro

On 1/31/25 17:38, Mark Sapiro wrote: > On 1/31/25 12:14, Schulz wrote: >> ---- >> these are the first lines of the .eml: >> >> MIME-Version: 1.0 >> Date: Tue, 28 Jan 2025 19:31:15 +0000 >> Content-Type: multipart/mixed; >> boundary="6efe513a-b2f8-47e5-ace0-b3b6aa5a056c-1" >> From: "J. Schulz" <js(a)jslz.de> >> Message-ID: <17def72e63ed443458a88ec892a17fe01b8a287c(a)jslz.de> >> TLS-Required: No >> Subject: empty, but another att >> To: it(a)freie-dorfschule.de >> >> --6efe513a-b2f8-47e5-ace0-b3b6aa5a056c-1 >> Content-Type: text/plain; charset="utf-8" >> Content-Transfer-Encoding: quoted-printable >> >> >> --6efe513a-b2f8-47e5-ace0-b3b6aa5a056c-1 >> Content-Type: application/pdf; name="someExample.pdf" >> Content-Disposition: attachment; filename="someExample.pdf" >> Content-Transfer-Encoding: base64 >> >> JVBERi0xLjcKJcOkw7zDtsOfCjIgMCBvYmoKPDwvTGVuZ3RoIDMgMCBSL0ZpbHRlci9GbGF0 >> ZURlY29kZT4+CnN0cmVhbQp4nC2NTQvCMBiD7++vCHjz0L7t1q2DMXAfgoeBg4Ln4TpRULEU >> 9OdbRB4SCISEhcKb5C7E6zqfI9qxoxcYLFhbmMoIXRrYXAlbKARPpy0eNKSWPAa/PsN9jtEv >> G83Of2Jdy7E79OCmafv/UCJcqHVkCmFRlsmzCm6B3CsohltrVqw545wNF0llSjZRNe5Gg6Pp >> 9zfhC14SKM4KZW5kc3RyZWFtCmVuZG9iagoKMyAwIG9iagoxNTMKZW5kb2JqCgo3IDAgb2Jq >> Cjw8L0xlbmd0aCA4IDAgUi9GaWx0ZXIvRmxhdGVEZWNvZGUvTGVuZ3RoMSA5MDc2Pj4Kc3Ry >> ZWFtCnic5Vh9dFPHlb/zniTLH1iSP4RtGd4zwh9gW7ItTIAa/LAtYbDBso1BAgJ6lmQkYkta >> SbZj0haTJoGYzyaEtEnOhuajTQgJz5AcTEqBLbs9yTZp04/ddje00G6a3Z4mkO02Pd3TYO+d >> 0bP5aJKes2f/2yfPmzv3zr33N/feGWmcjA8GIQtGgQfJPyDH5s3K1APAWwAkxz+UFPsiGgfS >> VwG4V/pi2weeOLPlDwCawwBpr27vH+n7k+ZkC0AWNm0sFJQD8rtQCWB6FW0sDiHjyRvHdTj+ >> AMfzQwPJe/+Fe00DkGPEsbk/6pdbtKMoz6mg4wH53lhCU8/jWMKxGJEHgu+9/ I see the issue. Mailman's content filtering sees this multipart message as having two parts, the first of which is empty, so it tries to recast the message as a single part message containing only the second part. The problem is this code only works if the second part is a text/* part. Here it decodes the base64 encoded pdf and tries to recast it as unicode text which works for text/* parts with a declared charset, but not for non-text parts. This patch is untested, but I think it will fix the issue. ``` --- a/src/mailman/handlers/mime_delete.py +++ b/src/mailman/handlers/mime_delete.py @@ -221,7 +221,7 @@ Replaced multipart/alternative part with first alternative. def reset_payload(msg, subpart): # Reset payload of msg to contents of subpart, and fix up content headers - if subpart.is_multipart(): + if subpart.is_multipart() or subpart.get_content_maintype() != 'text': msg.set_payload(subpart.get_payload()) else: cset = subpart.get_content_charset() or 'us-ascii' ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months

[MM3-users] Re: Error after HyperKitty 1.3.x upgrade

by Mark Sapiro

On 6/29/20 1:38 AM, Florian Schulze wrote: > Hi! > > After upgrading to HyperKitty 1.3.x I get the following error for qcluster: > > File ".../lib/python3.7/site-packages/django_q/cluster.py", line 300, > in pusher > task = SignedPackage.loads(task[1]) > File ".../lib/python3.7/site-packages/django_q/signing.py", line 31, > in loads > serializer=PickleSerializer) > File ".../lib/python3.7/site-packages/django_q/core_signing.py", line > 38, in loads > return serializer().loads(data) > File ".../lib/python3.7/site-packages/django_q/signing.py", line 44, > in loads > return pickle.loads(data) > AttributeError: Can't get attribute 'process_task_result' on <module > 'hyperkitty.tasks' from > '.../lib/python3.7/site-packages/hyperkitty/tasks.py'> > > How do I recover from that? It seems like there are still persisted > tasks in the qcluster queue using the old code from 1.2.x with the old > locking implementation. Have you stopped ans started qcluster since upgrading? Are you running the Django periodic jobs? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

[MM3-users] Re: Include receipant address as a variable

by Mark Sapiro

On 6/5/22 07:57, chucka(a)blackforest-co.com wrote: > No joy. I'm hosted on Dreamhost and I think they run MM2 (maybe 1?) I can get the header to show up in the email, however > Warning: The following illegal substitution variables were found in the msg_header string: user_email > In the header I have https://mysite/NL.php - works > https...php?xyz - works > https...php?$user_email - kicks back to ?%(user_email)s - and gives the Warning - > ...pdf.php?%(user_delivered_to)s > > OH OH OH user_delivered_to works WOOP! WOOP! WOOP! Dreamhost's Mailman is 2.1 and the appropriate list for Mailman 2.1 is mailman-users(a)python.org <https://mail.python.org/mailman3/lists/mailman-users.python.org/>. Had you posted there in the first place, I would have known you were dealing with Mailman 2.1 and I would have been able to answer with Mailman 2.1 information. In any case, it seems you've worked it out so that's good. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

[MM3-users] Re: dmarc mitigation debug

by Mark Sapiro

On 5/31/23 21:26, Thomas Krichel wrote: > > Hi gang! > > I have a list with > > DMARC mitigation action "Replace From: with list address" > DMARC Mitigate unconditionally "Yes". > > But list posts still have the poster's From:, breaking DMARC. How can > I debug this? For a start, I looked in my sqlite database. Changes > on the web interface list settings seem to be correctly applied to > the database. But I don't see a "munge_from" in the fields of > a list in the database. `munge_from` is not a field name. `munge_from` is a value = 1 of DMARCMitigateAction which is stored in the dmarc_mitigate_action field. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/interfaces/mai… There's really not any logging that would help with this unless there were some exception involved, but that would shunt the message, not deliver it. What are the full headers of the post received from the list? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: migratng from 3.2.2 Debian packages to 3.3.8 source install - web server question

by Mark Sapiro

On 6/24/23 8:09 PM, Ken Alker wrote: > > I sent a reply to my original email this morning but when I view it in > the web archives, it see that it didn't get threaded with my original > email. I hope this one does. I wonder why the original did not. This one was properly threaded. I too noticed that the thread was split, but I didn't examine the headers of the reply as I received it, so I can't say why, but threading is done by In-Reply-To: headers. Possibly the header in the reply was missing or didn't reference the Message-ID: of the original. All I can say is the database has an empty in_reply_to value for the message at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… In any case I have joined the split thread. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

[MM3-users] Re: Moderate mails from owner

by Mark Sapiro

On 4/8/19 4:44 AM, Henrik Rasmussen wrote: > I finally received the right mail from the user. I am sorry for the delay. > > The mail from the list does actually not contain any X-Mailman-Rule-Misses: nor X-Mailman-Rule-Hits: This is quite strange. There are no 'X-Mailman' headers which might be exchange removing all 'X-' headers other than its own, but while there are some 'List-' headers, there is no 'List-Id:' header which Mailman always adds. Can you try to get an example message from the list that was sent to a non-outlook/exchange user. Perhaps you could subscribe a gmail or other non-microsoft managed address to the list. I note the MX for your email domain is ku-dk.mail.protection.outlook.com, so that probably won't do. However, one thing to check is the list's Header filters settings. Is there a filter there that could match the owner's email with action accept? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 3 months

[MM3-users] Re: New releases

by Mark Sapiro

On 9/11/20 7:30 AM, brylon(a)oit.rutgers.edu wrote: > > $ ./bin/django-admin compress --trace > Compressing... Traceback (most recent call last): > File "/opt/mailman/mm/venv/lib/python3.6/site-packages/compressor/base.py", line 282, in precompile > mod = import_module(mod_name) > File "/opt/mailman/mm/venv/lib64/python3.6/importlib/__init__.py", line 126, in import_module > return _bootstrap._gcd_import(name[level:], package, level) > File "<frozen importlib._bootstrap>", line 994, in _gcd_import > File "<frozen importlib._bootstrap>", line 971, in _find_and_load > File "<frozen importlib._bootstrap>", line 953, in _find_and_load_unlocked > ModuleNotFoundError: No module named 'sass -t compressed {infile} {outfile}' You have something like COMPRESS_PRECOMPILERS = ( ('text/x-scss', 'sass -t compressed {infile} {outfile}'), ('text/x-sass', 'sass -t compressed {infile} {outfile}'), ) in your Django settings. You either need to install ruby-sass or install sassc if it isn't already installed and for sassc change the above to COMPRESS_PRECOMPILERS = ( ('text/x-scss', 'sassc -t compressed {infile} {outfile}'), ('text/x-sass', 'sassc -t compressed {infile} {outfile}'), ) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: at the finish line of mailman3 docker, but can't sign in.

by Mark Sapiro

On 7/30/21 10:47 AM, bob B wrote: > > Basically once I have docker installed, and mailman3 up and no lists are available, How do I setup or/and sign in as admin? I'm not sure what the actual command would be do run the django-admin interface in the docker image, but from below, it looks like it's `mailman-web`. Run `mailman-web createsuperuser` to create an admin ID. > Also In docker how can I test sending mail? the command "mailman-web sendtestemail youremailid@domain" from the mailman-web container does not work. This command tries to send the mail via SMTP to localhost port 25. > How can I make sure my containers can send and receive mail? The MTA should be listening on port 25 and that need to be visible in the mailman-web container. See <https://asynchronous.in/docker-mailman/#setting-up-your-mta> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

[MM3-users] Re: Walk-thru for Ubuntu Bionic Mailman 3 Full setup

by Mark Sapiro

On 7/8/22 8:28 AM, kisner(a)live.com wrote: > > I tried to follow that guide ( https://docs.mailman3.org/en/latest/install/virtualenv.html ), but I couldn't get it to work. I'd have to try it again to see where it broke. One thing that I got past was I had to change: > > (venv)$ pip install wheel mailman psycopg2-binary<2.9 > > to > > (venv)$ pip install wheel mailman psycopg2-binary==2.8.6 > > and that got me past that part, I don't understand why that would make a difference since the latest psycopg2-binary<2.9 is 2.8.6 > but hyperkitty/mailman-web pip install has components that failed to install. I'm not sure why, someone smarter than me could probably have figured it out, but as written it wasn't working for me. If you do try again, post the specific issues/error messages and we will try to help. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

[MM3-users] Re: Importing mailman 2 shows member's "Moderation Action" = "Default processing". But new members show = "None". Why

by Mark Sapiro

On 5/25/23 6:48 PM, mrl(a)psfc.mit.edu wrote: > Thanks. However, the list I imported, did have as it's default, to hold new members to be moderated. Therefore, shouldn't import21, set imported moderated members, to also be the list default? If the imported user's MM 2.1 mod bit is off, the user will be imported with moderation action = default processing which mimics MM 2.1's action for an unmoderated member. If the imported user's MM 2.1 mod bit is on, the user will be imported with moderation action set according to the MM 2.1 lists Privacy options... -> Sender filters -> member_moderation_action. The list's default_member_moderation together with member_moderation_action is used to set the MM 3 list's Default action to take when a member posts to the list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: List description as sender

by Mark Sapiro

On 09/17/2018 01:04 AM, Henrik Rasmussen wrote: > It is the description in the Settings -> List Identity -> Description that is used in the list overview https://list.example.com/postorius/lists/ and also as the "From:" in the mails sent to the subscribers. And it is only the From: in posts delivered to the list members if the list is anonymous. Otherwise the From: is that from the original post to the list or possibly a mumged version thereof in the case of DMARC mitigations. I think your choices are: 1) Don't configure the list as anonymous. 2) Make the list's Description what you think is appropriate for the display name part of the From: header. 3) Modify mailman/handlers/cleanse.py to use something else in the From: header of anonymized posts. 4) Submit an RFE at <https://gitlab.com/mailman/mailman/issues/new> asking for the solution you want and possibly a merge request implementing it. 5) Live with it as is. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 10 months

[MM3-users] Re: Change language to welcome message in mailman3

by Mark Sapiro

On 7/29/20 2:00 PM, Massimo Zappalà wrote: > Hi Mark, > i've created the it templates from en. > I have make a merge request from the link that you posted before, but i was rejected because I am non a member of the project. How can I make a merge request? You need to fork Mailman Core <https://gitlab.com/mailman/mailman> into your own GitLab project space, make and commit your changes there and then submit a merge request to merge your branch back into the master. If that's what you did, I don't know what the issue is, but you can send the templates to me directly. > Anyway, I copied the files in the path indicated by you but the translated emails arrive only if I am an list administrator. Is this perhaps a permissions issue. The Mailmanuser needs to be able to read them. See <https://gitlab.com/mailman/mailman/-/issues/745> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: My Server is unable to connect to Mailman REST API few times

by Mark Sapiro

On 9/19/20 4:32 AM, Shashikanth Komandoor wrote: > > But I am trying to delete a list on an urgent basis. Because of which I am > getting the above said errors. I tried to delete > through the interface, through curl command and through "mailman shell" but > nothing led me to a > positive result. Is there any work around to delete the list ? What have you tried in Mailman shell? This should do it. $ mailman shell -l list.example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list.example.com mailing list >>> getUtility(IListManager).delete(m) >>> commit() So should just $ mailman remove list.example.com What happens if you do those? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: Setting for archiving multi email domains?

by Mark Sapiro

On 3/10/21 2:32 PM, Duane Raymond wrote: > > As for the potential bug in hyperkitty, I have been referencing the hyperkitty version of this thread as I was working the problem, and while I faintly remember seeing the loop in the email on my phone, when I was referencing the hyperkitty version of your email it was not there - even when expanding the quoted text....perhaps you see the same thing via hyperkitty? Essentially it removed part of the message that was intended to be seen. That's a known issue with the HyperKitty that is installed at mailman3.org and python.org due to the patch for markdown rendering <https://gitlab.com/mailman/hyperkitty/-/merge_requests/160>. This patch is superceded by <https://gitlab.com/mailman/hyperkitty/-/merge_requests/324>, but I haven't gotten around to trying that yet. If you look at the message view at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>, you'll see the missing part -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users] Re: Strange issue with bounce processing

by Mark Sapiro

On 9/12/23 10:16 AM, Dan Caballero wrote: > I have a somewhat related question. > > I monitor the Mailman runner processes via cron and restart based on a drop in the number of processes. As a result I've noticed that the bounces runner process becomes defunct at varying times. For example, the cron job restarted the Mailman processes early this morning and I can see the bounce runner process is currently defunct (Z state). It appears to have become defunct after about 3 hours of CPU time. There are some relevant issues on this, some of which are fixed. See https://gitlab.com/mailman/mailman/-/issues/?state=all&search=bounce%20runn… When the runner dies, the master watcher should restart it. See https://gitlab.com/mailman/mailman/-/issues/898, fixed (maybe) by https://gitlab.com/mailman/mailman/-/merge_requests/1094 which will be in Mailman 3.3.9. However, this doesn't address why it dies in the first place. You might find some info about the death in syslog. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

[MM3-users] Re: mailman-web compress - Invalid template socialaccount/login_cancelled.html

by Mark Sapiro

On 10/29/23 01:57, Odhiambo Washington wrote: > > Consequent upon this django-allauth issue and the previous issue > with psycopg2, how likely is it that new MM3 installations will suffer the > effects? As noted in other replies, the django-allauth issue has been fixed in 0.58.1 and should not be an issue for anyone installing Mailman at this point. Regarding your psycopg2 issue, it was apparently fixed when you upgraded from 2.8.6 to 2.9.9. Presumably you got 2.8.6 with the command ``` (venv)$ pip install wheel mailman psycopg2-binary\<2.9 ``` shown at https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-mail… Perhaps you didn't read the following paragraph which says in part "Currently Django>=2.2,<3.1 requires psycopg2-binary<2.9. See this issue. Later versions of Django will work with psycopg2-binary 2.9.x." That said, I don't know why there was an issue with psycopg2-binary=2.8.6. I have an installation with that version and it works. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: Not able to start mailman server

by Mark Sapiro

On 8/4/21 2:24 PM, Kartheek Reddy Bondugula wrote: > Hi, > > I am trying to start the mailman server on a mac according to the instructions given on the website as shown - What web site? A URL to the instructions you followed would help. > $(py3) git clone git@gitlab.com:mailman/mailman.git > $(py3) cd mailman > $(py3) python setup.py develop Rather than 'python setup.py develop', do 'pip install -e ./' > $(py3) mailman start > $(py3) cd .. > > But I run into the following problem - > > Starting Mailman's master runner > Generating MTA alias maps > /usr/local/Cellar/python(a)3.9/3.9.5/bin/python3.9: can't open file '/usr/local/opt/python(a)3.9/bin/master': [Errno 2] No such file or directory > > Can anyone help me out with this? There should be a `master` in the same bin/ directory as `mailman` which is probably not '/usr/local/opt/python(a)3.9/bin/' What does `mailman info` show? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

Search results for query "sapiro"