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

[MM3-users] Re: Footer from templates not working - DB issue?

by Mark Sapiro

On 9/21/22 05:10, chris(a)mehl.one wrote: > Hi, > > I am running Mailman3 on Debian 11 with Apache and MariaDB. Single installation. > > When I edit a footer from the WebUI templates, it doesn't show in the messages. How is Mailman installed? If from the Debian packages, this may be a Debian issue, and you should contact Debian for assistance. > Could it be an issue with the related DB? If so - what do I need to change? I can't say without more info. Is the default footer added to messages? What do you get from the db query ``` SELECT * from template WHERE name = 'list:member:regular:footer'; ``` Assuming that returns a row with context of the list id, what is the uri and can you retrieve it? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

[MM3-users] Re: customized welcome message

by Mark Sapiro

On 12/7/23 12:46, Nils wrote: > I didn't try to include html. > It completely ignored the template I've created and sent the html source > of the parent domain. Which seems totally random to me. How and to what did you set the URL for the template? What does the database query SELECT uri FROM template WHERE name = 'list:user:notice:welcome'; show? >> I see no URI setting in Postorius Settings > Automatic Responses. What >> Postorius version is this? Any local mods? > It's Postorius Version 1.2.4 installed through the mailman3-web package > for ubuntu focal (https://packages.ubuntu.com/focal/mailman3-web) This is very old. Current Postorius is 1.3.10. 1.2.4 is from February 2019. The Debian/Ubuntu packages are out of date. We recommend installing via the doc 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

2 years

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

by Mark Sapiro

On 11/22/24 11:02, Joshua Bushe wrote: > Unsure where these hide inactive or hide private boxes are located. Looked through all settings. They are at the top of the main Hyperkitty overview page. E.g. like https://lists.mailman3.org/archives/ > Nothing strange in Django's logs. > > Only thing I've noticed is that when i look at my listing. It has the list name then it says "inactive". Not sure if or how to change that to something else? `inactive` means no posts in the last 30 days. However, from your original post, I thought your issue was that you couldn't see the lists. What are the urls of the page with the issue and the page that shows your list as `inactive` (you can replace the host name with example.com if you wish). -- 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: Current status and issue deleting Archives in Mailman3

by Mark Sapiro

On 11/2/21 11:50 AM, bob B wrote: > So I am teaching myself to fish, and see that it is actually django-admin, so that is in > mailman-web? (in docker) > > But i get this: > > $ docker exec -it mailman-web /bin/bash > bash-5.0# django-admin shell > Python 3.8.10 (default, May 6 2021, 06:30:44) > [GCC 9.3.0] on linux > Type "help", "copyright", "credits" or "license" for more information. > (InteractiveConsole) >>>> from hyperkitty.models import MailingList > Traceback (most recent call last): ... > raise ImproperlyConfigured( > django.core.exceptions.ImproperlyConfigured: Requested setting INSTALLED_APPS, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings. Do what it says. I.e. run DJANGO_SETTINGS_MODULE=path/to/settings; django-admin shell -- 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: django-allauth failures, but only for some users (independent of browser?)

by Mark Sapiro

On 12/7/23 14:33, Jered Floyd wrote: > > FYI, The django-allauth author has proposed fixing both of these with an even simpler change, which is now upstream and queued for a future release. > > --Jered Thank you again for your work on this. I can confirm that the patch below fixes my issue with https://msapiro.net/accounts/social/connections/ and SITE_ID = 0. > --- a/allauth/socialaccount/adapter.py > +++ b/allauth/socialaccount/adapter.py > @@ -228,7 +228,10 @@ class DefaultSocialAccountAdapter(object): > provider_to_apps = {} > > # First, populate it with the DB backed apps. > - db_apps = SocialApp.objects.on_site(request) > + if request: > + db_apps = SocialApp.objects.on_site(request) > + else: > + db_apps = SocialApp.objects.all() > if provider: > db_apps = db_apps.filter(Q(provider=provider) | Q(provider_id=provider)) > if client_id: -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

[MM3-users] Re: Hyperkitty error - not archiving

by Mark Sapiro

On 7/26/25 10:55 AM, Odhiambo Washington via Mailman-users wrote: > Another thing I have seen, inside /etc/mailman3/ > root@list:/etc/mailman3# ls -al > total 40 > drwxr-xr-x 3 mailman mailman 4096 Jul 26 10:52 . > drwxr-xr-x 110 root root 12288 Jul 26 07:17 .. > -rw-r--r-- 1 mailman mailman 948 Jul 25 02:48 mailman.cfg > -rw-r--r-- 1 mailman mailman 352 Oct 25 2023 mailman-hyperkitty.cfg > drwxr-xr-x 2 mailman mailman 4096 Jul 26 03:11 __pycache__ > <===== Is the presence of this directory expected? > -rw-r--r-- 1 mailman mailman 4971 Jul 26 03:10 settings.py > -rw-r--r-- 1 mailman mailman 863 Jul 25 04:14 uwsgi.ini Yes, in any directory that contains .py files, when those files are imported, a corresponding compiled byte code .pyc file is placed in a __pycache__ directory. This is normal Python 3 behavior. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 2 weeks

[MM3-users] Re: Your Dashboard

by Mark Sapiro

On 2/11/20 1:27 PM, Allan Hansen wrote: > > Our site has over 50 lists and several moderators are responsible for multiple lists. In addition to a dashboard like described here I would like to have a ‘comment’ field next to each request, so tha the moderator can keep track of the status of each. Our approval process involves multiple steps. > > Time to visit gitlab? GitLab is the one place for feature requests for Mailman 3/Htperkitty/Postorius. Things requested in list posts get lost and forgotten. That said, the more specific you can be in a request, the better. I.e., if you want a dashboard, what do you want on it for, e.g., the site admin, a user who may or may not be an owner of a couple of lists, a moderator of a couple more and a member of still others. -- 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: mailman3 does not send to the members of the lists

by Mark Sapiro

On 7/12/20 3:53 PM, maszap(a)tin.it wrote: > Hi, > > I added the line to the main.cf file > > owner_request_special = no > transport_maps = hash:/var/lib/mailman3/data/postfix_lmtp > local_recipient_maps = hash:/var/lib/mailman3/data/postfix_lmtp > relay_domains = hash:/var/lib/mailman3/data/postfix_domains > > In my log MTA mail.warn I get: > Jul 13 00:44:56 gamelia postfix/trivial-rewrite[8317]: warning: do not list domain pratico.work in BOTH virtual_mailbox_domains and relay_domains What's in your mail.log for a message to and from the list? > I check > my /var/log/mailman3/smtp.log > but is empty If Mailman is sending any mail at all, there should be entries in smtp.log unless the log level is higher than info. What does mailman conf -s logging.smtp show? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

[MM3-users] Re: DMARC - was: Disable user registration

by Mark Sapiro

On 3/20/21 4:00 PM, mailman3(a)digicrime.com wrote: > My understanding was that DMARC is merely a superset of DKIM+SPF along with some other policies. I have that set up on some of my domains. The weird part is that DKIM and SPF both passed, but DMARC was failing - I didn't realize it can happen but apparently it can: https://dmarcian.com/how-can-spfdkim-pass-and-yet-dmarc-fail/ Your reference explains it. DMARC requires a valid SPF or DKIM sig with a domain which "aligns" with the domain of the From: address. Your valid SPF and DKIM signature from your domain will not be enough for DMARC to pass because your domain won't "align" with the From: domain. "align" is a technical term defined in RFC 7489. This is what ARC (RFC 8617) is trying to address. -- 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: Migration of archives from Sympa to MM3

by Mark Sapiro

On 2/28/22 10:53, Tom Fillmore wrote: > > Moving existing lists to MM3 looks doable the archives are a different story. Has anyone ever migrated archives from Sympa to MM3? Mailman can import archives where the messages are in a Unix format mbox file. It appears sympa can export archives as a zip file containing monthly files of messages <https://sympa-community.github.io/manual/customize/archives.html>. If these files are in Unix mbox format, HyperKitty's hyperkitty_import function can import them directly, either individually or concatenated. If not, they would need to be processed to add Unix `From ` lines and possibly make other changes. In any case, the mbox to be imported should be checked for unescaped `From ` lines in message bodies with a script such as the one at <https://www.msapiro.net/scripts/cleanarch3>. -- 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: Detectors and Bounces

by Mark Sapiro

On 8/5/22 11:12, summersan(a)nclack.k12.or.us wrote: > > Thank you for refocusing the issue in terms of the "large numbers of bounces", too. > > Here is what I have in `mailman.cfg` for the `[mta]` section: > > `[mta]` > `verp_confirmations: yes` > `verp_personalized_deliveries: yes` > `verp_delivery_interval: 1` > > Does this help narrow down the problem any further? Not really. You need to see why you are getting these bounces. What's in Mailman's bounce.log? Are bouncing users getting their delivery disabled? What are your list(s) `Bounce Processing` settings. In particular, if you set all the `Notify owner ...` settings to `Yes` and `Forward unrecognized bounces` to either `List Admins` or `Site Admin`, what do you see? Also, if there are queued bounces in `/opt/mailman/mm/var/queue/bounces`, you can examine them with `/opt/mailman/mm/bin/mailman qfile` -- 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: Twitter OAuth2

by Mark Sapiro

On 12/26/22 06:14, Odhiambo Washington wrote: > I'd like to integrate Twitter OAuth as part of the Social Accounts in my > setup. > I have gone through > https://django-allauth.readthedocs.io/en/latest/providers.html#twitter, but > cannot find the config options to add to my settings. > Does someone have a config block setting for "SOCIALACCOUNT_PROVIDERS =" ? The last I looked into using Twitter as an OAuth2 provider, which was some time ago, it would not work because Twitter would not provide the user's email address via OAuth2. Possibly this could work if the user's name was her Twitter handle. As far as SOCIALACCOUNT_PROVIDERS is concerned, you don't need anything. You just need to create your OAuth2 app and provide the keys via the Django admin SOCIAL ACCOUNTS interface. See https://django-allauth.readthedocs.io/en/latest/providers.html#twitter-oaut… -- 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: IndexError in archiving queue

by Mark Sapiro

On 3/16/23 04:13, Jacob Sievert via Mailman-users wrote: > Hello, > > it seems I have forgotten where I can kick an email out of the archiving > queue as it produces this error in a loop. > Might one of you know where I can do that? > Thanks in advance. The underlying error is a bogus Message-ID header in the message. We have observed cases of Message-IDs like Message-ID: <[d1e99408882e4aed93b0df4c1c28dfa3-JFBVALKQOJXWILKNK4YVA7COOVDWK5D4IVWWC2LMKB2WE3DJONUGK4T4IV4G6U3NORYA====(a)microsoft.com]> where the `[` and `]` are the problem. See the report at https://gitlab.com/mailman/mailman/-/issues/732 and fix for that at https://gitlab.com/mailman/mailman/-/merge_requests/1099 I would like to see the headers of the message in your case. To answer your question, the offending message is queued in Mailman's var/archives/hyperkitty/spool/ directory and can be examined with Mailman's `mailman qfile` 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, 8 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 12:30, Wikinaut wrote: > Now I wanted to start uwsgi, after having setup everything as documented but I got in the error log this: > > ModuleNotFoundError: No module named 'allauth.account.middleware' As it says at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… "Note either downgrade django-allauth or update MIDDLEWARE, but not both." Now you have added 'allauth.account.middleware.AccountMiddleware' to MIDDLEWARE and downgraded django-allauth<0.56. You can either do ``` pip install --upgrade django-allauth ``` or remove ``` x = list(MIDDLEWARE) x.insert(0, 'allauth.account.middleware.AccountMiddleware') MIDDLEWARE = x ``` from /etc/mailman3/settings.py. Either will do, but DO NOT DO BOTH. -- 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: Removing a moderator via the REST API

by Mark Sapiro

On 11/15/24 06:38, Andy Matthews wrote: > > Given a list address of announce(a)bar.com, and a subscriber of andy(a)bar.com, the API endpoint would be: > ``` > 'lists/announce.bar.com/moderator/andy@bar.com' > ``` > > Is that correct? Yes. > One question, I think I assumed that removing a user from the list would also cascade to remove any roles that user may have had. So we're currently POSTing to `lists/announce.bar.com/roster/member`, and I was expecting that to also remove the moderator role. But it sounds like it would require an extra call to explicitly remove them as moderator? Yes, member, nonmember, owner and moderator roles are all separate. removing a user from one of those roles has no effect on any other role the user might have. -- 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: Cannot Install Web UI

by Mark Sapiro

On 10/23/25 11:57, dap1--- via Mailman-users wrote: > OK, so gnuicorn is easier to install and set up. However, it has its own glitch not in the docs. I'm getting the following error trying to start web: > > gunicorn[42860]: !!! > !!! WARNING: configuration file should have a valid Python extension. This is just a warning and can be ignored. > gunicorn[42860]: !!! > gunicorn[42860]: Error: Error: '/opt/mailman/mm/var/logs/error.log' isn't writable [PermissionErr> > > The docs say to use conf but I think the error implies it should be py. In addition I'm guessing I have to change the log and access file names to something like gunicorn.error.log. The access.log and error.log names are correct. They should be owned by `mailman` and your /etc/systemd/system/mailmanweb.service should include User=mailman -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 2 weeks

[MM3-users] Re: The message is larger than the 40 KB maximum size

by Mark Sapiro

On 9/18/20 12:48 PM, Phil Stracchino wrote: > On 2020-09-18 15:32, Mohsen Masoudfar wrote: >> Hi, >> >> I am trying to find how I may change this. I have an attachment of 800 KB, and when I post it to the list, I do not get any response and nothing is hold. It looks like the message is just dropped. > > > Assuming that this works roughly the same in mm3 as it does in mm2, you > can set max_message_size in your list configuration. It defaults to 40; > units are KB. Yes, and you can set it to zero for "unlimited", but even if that is a satisfactory workaround, the much more interesting question, at least to me, is why does the message "disappear". -- 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: (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 11:48, Wikinaut wrote: > > I was "_forced_" :-) to install that in one of the very first steps of the documentation. https://docs.list.org/en/latest/install/virtualenv.html#installing-mailman-… > > What I suggest is: > > I will (try to help) to fix the documentation, so that it also can work for mysql. > Please, I am willing to help. It seems to me that adding a sentence following "This will install latest release of Mailman Core, and Python bindings for Postgresql database." such as "If you are using a different database manager, do not install psycopg2-binary." would suffice. What do 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, 1 month

[MM3-users] Re: hyperkitty threads by month question

by Mark Sapiro

On 7/25/24 11:20, Bryan Fields wrote: > Sorry for the delay, I was on some travel last week. > > On 7/19/24 7:30 PM, Mark Sapiro wrote: >> That URL gives me as server error. What's in the Django (mailman-web) >> logs for that? > > I did notice hitting a 500 error on occasion, sometimes it works. I just tried it twice more and got the error both times. > When this happens, I get an email error below. This is really wierd. See below. >> Are you running all the Django periodic jobs and is qcluster running? > > Ok, the docs said that qcluster service wasn't needed under uWSGI > https://docs.mailman3.org/en/latest/install/virtualenv.html#automatically-s… > qcluster does appear to be running: Right, you don't need to create a separate service for it with our recommended uWSGI configuration because uWSGI runs it, but it does need to run. ... > line 88, in reverse > return resolver._reverse_with_prefix(view, prefix, *args, **kwargs) > File > "/opt/mailman/venv/lib/python3.10/site-packages/django/urls/resolvers.py", line 828, in _reverse_with_prefix > raise NoReverseMatch(msg) > > Exception Type: NoReverseMatch at > /archives/list/nanog(a)nanog-mm3.keekles.org/ > Exception Value: Reverse for 'hk_archives_with_month' with keyword > arguments '{'year': 999, 'mlist_fqdn': 'nanog(a)nanog-mm3.keekles.org', > 'month': 12}' not found. 2 pattern(s) tried: > ['archives/list/(?P<mlist_fqdn>[^/@]+@[^/@]+)/(?P<year>\\d{4})/(?P<month>\\d\\d?)/$', 'hyperkitty/list/(?P<mlist_fqdn>[^/@]+@[^/@]+)/(?P<year>\\d{4})/(?P<month>\\d\\d?)/$'] > Raised during: hyperkitty.views.mlist.overview It appears to be trying to get the threads for December, 999. What do these queries show? SELECT * FROM hyperkitty_thread WHERE EXTRACT(year FROM date_active) < 1000; SELECT id FROM hyperkitty_email WHERE EXTRACT(year FROM date) < 1000; -- 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: Mailman 3 Keeps Forgettings Imported Lists

by Mark Sapiro

On 07/30/2018 07:37 AM, Ryan McClung wrote: > GNU Mailman 3.2.0 (La Villa Strangiato) > Python 3.6.5 (default, Apr 10 2018, 17:08:37) > [GCC 4.8.5 20150623 (Red Hat 4.8.5-16)] > config file: /opt/mailman/var/etc/mailman.cfg > db url: sqlite:////opt/mailman/var/data/mailman.db > devmode: DISABLED > REST root url: http://localhost:8001/3.1/ > > Shortly after I run an import on a bunch of lists they all disappear. > [root@mailman3(stg) mailman]# mailman lists > No matching mailing lists found > > I have 30+ lists. Does the 'mailman lists' command invoke the identical 'mailman' file as the 'mailman import21' command that did the imports. And how did you create the lists before importing them? We have done several imports of 2.1 lists to <https://mail.python.org/mm3/mailman3/> and have never seen an issue like this. -- 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: Mailman Core 3.3.2 is now out

by Mark Sapiro

On 11/22/20 1:04 AM, Torge Riedel wrote: > Am 07.11.20 um 04:24 schrieb Abhilash Raj: >> I missed it in the original email, but a full list of changes in this >> version is present here: >> >> >> https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… >> > > Hi, > > this link now points to 3.3.3, is there a chance to make this link more > stable? Maybe > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… Those links are created by Sphinx and as you note the fragments are not stable. I don't know if it's possible to tell Sphinx via the .rst source how to name the fragments. Maybe the best idea is to not use fragments at all and just point to the document. -- 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: Moderation emails

by Mark Sapiro

On 3/3/21 7:59 PM, peter(a)chubb.wattle.id.au wrote: > > The third part is another message/rfc822 part that says, > If you reply to this message, keeping the Subject: header intact, > Mailman will discard the held message. The 'this message' in that text refers to the message in the message/rfc822 part. I know it's confusing, but it's been that way since Mailman 2.1.0. That said, it should be fixed. It should at least say "If you reply to this attached message part, not the outer message, keeping ...". It also refers to an Approved: header with the list password, and there is no list password. There is a moderator_password which works in this context, but it is rather obscure. Not only that, but it doesn't work anyway. See <https://gitlab.com/mailman/mailman/-/issues/631> and <https://gitlab.com/mailman/mailman/-/issues/169> -- 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: Using Header filters

by Mark Sapiro

On 8/13/21 10:55 AM, Mohsen Masoudfar wrote: > Hi, > > I wonder if it is possible using the "Header filters" option to filter for a specific word to push the message to Moderation? You can use Header filters to hold for moderation any messages that have a header matching a pattern. The pattern match is unanchored and case insensitive so for example to hold for moderation any message which contains the string `word` or `Word`, etc. anywhere in the Subject: you would create a Header Filter with Header = subject, Pattern = word and Action = Hold for moderation. If you want to match only the word `word` and not things like `foreword` and `wordless`, you'd use a pattern like (^|\W)word(\W|$). See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rules/docs…> and <https://docs.python.org/3/library/re.html>. -- 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: Whitelist in mailman3: How to allow only ~400 e-mail senders in a file whitelist to send to a list?

by Mark Sapiro

On 8/3/25 13:52, Wikinaut wrote: > In mailman2, it was quite handy to place "@whitelist" into the field sender/accept_these_nonmembers, when such a file has been set up. > > How can I (per list or programmatically) define the ~400 e-mail senders to be allowed to send to my about 30 lists? > And, yes, I already searched for a solution of this problem, but could not find any. This feature was added in Mailman core 3.3.10. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… https://gitlab.com/mailman/mailman/-/issues/794 https://gitlab.com/mailman/mailman/-/merge_requests/1154 and documented in postorius 1.3.13. See https://gitlab.com/mailman/postorius/-/issues/589 https://gitlab.com/mailman/postorius/-/merge_requests/938 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 1 week

[MM3-users] Re: localhost[::1] said: 550 Requested action not, taken: mailbox unavailable

by Mark Sapiro

On 10/26/2017 11:30 PM, Bjoern Franke wrote: > > Oct 27 08:24:58 srv20 postfix/lmtp[2981]: 8798E40979: > to=<admin(a)lists.ffnw.de>, relay=localhost[127.0.0.1]:8024, delay=0.51, > delays=0.43/0.02/0.02/0.03, dsn=5.0.0, status=bounced (host > localhost[127.0.0.1] said: 550 Requested action not taken: mailbox > unavailable (in reply to end of DATA command)) This may be a Mailman bug. I'll look further when I have time. The message above says that Postfix tried to deliver the message to Mailman's lmtp runner and the runner said there was no such list. I'm guessing that there may be confusion between the admin@... list address and a listname-admin@... address. If this is the case, it means there is a bug which would affect any lists named 'admin', 'bounces', 'confirm'. 'join', 'leave', etc. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 1 month

[MM3-users] Re: Change settings via mailman shell

by Mark Sapiro

On 3/6/19 1:32 AM, kk(a)eco.cept.org wrote: > I am trying to find a way to set some parameters on the lists from a shell script. One specific parameter - max_message_size is not presented through the REST interface apparantly, and i found a way to set this with mailman shell command. Continuing this path i seem not to be able to set any other parameters like this: > m.archive_policy = 'never' You can't set archive_policy to a string. it has to be set to an attribute of mailman.interfaces.archiver.ArchivePolicy i.e. from mailman.interfaces.archiver import ArchivePolicy m.archive_policy = ArchivePolicy.never See <https://mailman.readthedocs.io/en/latest/src/mailman/handlers/docs/archives…> > m.subject_prefix = '' > m.dmarc_mitigate_action = 'munge_from' Likewise dmarc_mitigate_action is an attribute of mailman.interfaces.mailinglist.DMARCMitigateAction See <https://mailman.readthedocs.io/en/latest/src/mailman/handlers/docs/dmarc-mi…> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 9 months

[MM3-users] Re: Strange URL in error message

by Mark Sapiro

On 7/14/24 9:14 AM, waps(a)tantalus.jena.thur.de wrote: > (Debian 12) > > I have the problem that the hyperkitty archive is empty. The file /var/log/mailman3/mailman.log show sometimes the message > > urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='www.XXXXX-project.demailman3', port=443): Max retries exceeded with url: /hyperkitty/api/mailman/archive (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7fa48b43a910>: Failed to establish a new connection: [Errno -2] Name or service not known')) > > (there is a slash missing between 'project.de' and 'mailman3'). My goal is, of course, to have an running archive. But I think the error message could be a hint about the reason) It appears that your setting for base_url in mailman-hyperkitty.cfg is missing the slash. I.e., it is http://www.XXXXX-project.demailman3/ and should be http://www.XXXXX-project.de/mailman3/ -- 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: Migrating from old V2 server to new V3 server. Questions.

by Mark Sapiro

On 10/2/24 20:33, jkoral(a)luc.edu wrote: > Not sure if this means anything. This is the log from old server after trying to send. I edited the FQDN and IP though. Any thoughts? I think it may be the configuration of postfix on the new server though. > > Oct 2 22:26:59 listservls01 postfix/smtp[139911]: B1FD27ED: to=<test(a)listservnew.example.com>, orig_to=<olivertest(a)lists.luc.edu>, relay=listservnew.example.com[x.x.x.x]:25, delay=0.01, delays=0/0/0.01/0, dsn=4.4.2, status=deferred (lost connection with listservnew.example.com[x.x.x.x] while receiving the initial server greeting) The message is deferred. Postfix will keep trying for maximal_queue_lifetime (default 5 days). Possible causes are a firewall on the new server blocking port 25 connects or some postfix misconfiguration on that server. Can that server receive mail at all? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 2 months

[MM3-users] Re: Confirm and Moderate Unsubscribe Requests

by Mark Sapiro

On 10/21/20 8:53 AM, Brian Carpenter wrote: > If you set the unsubscription policy to confirm then moderate for a list > and someone unsubscribes, they receive a confirmation request. That is > good. They respond to it. That is also working fine. However the list > owner/moderator than gets a request to approve the unsubscribe request > and well, unless I am missing something, I don't see an interface to > handles such requests via Postorius. This is <https://gitlab.com/mailman/postorius/-/issues/332>. > How does one handle an unsubscribe request that requires moderator > approval? I'm not sure at this point, I can look further later, but if the notice to the admin has a token, it might work to send a `confirm <token>` command to the list-request address. Otherwise, don't moderate unsubscription requests. -- 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: High memory usage

by Mark Sapiro

On 2/16/22 00:18, Philip Colmer wrote: > Thank you for the replies from Mark and Stephen. > > One of the reasons why Prasanth & I are concerned with this specific system > is because the first time memory usage crept up, it got to the point where > oomkiller stepped in and, as is usual for that particular mechanism, one of > the processes it killed was sshd, thus removing access to the system :(. I > know that oomkiller can be tuned to stop it killing processes like sshd but > it will, nevertheless, start killing *some* processes if it sees an out of > memory situation. It sounds like there is a memory leak somewhere. This is an issue with some versions of Python. I know both Python 3.10.2 and 3.9.10 were released ahead of schedule to fix this. See https://bugs.python.org/issue46347 -- 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: Cross-List and Domain based sender whitelisting ( accept_these_nonmembers )

by Mark Sapiro

On 1/9/23 05:31, Johannes Rohr wrote: > > Thanks! I assume, there is a reason why this cannot be easily > implemented, else it would have been. Asking because I know a number of > people would make extensive use of this in MM2. The actual implementation is probably not difficult, but it's more than just handling things like `@list_id` in *_these_nonmembers. It also requires developing appropriate unit tests, updating REST and `mailman import21` to accept the syntax and documentation updates at least for Postorius Settings -> Message Acceptance -> * these non-members. That adds up to a significant amount of work. I recognize it's a significant regression for some, but we are a small, all volunteer project and can't do everything. A well crafted merge request would certainly be accepted. -- 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: MM2.1 -> MM3.3 migration. To hold or not hold

by Mark Sapiro

On 11/18/24 23:13, mark(a)suburbia.org.au wrote: > - Modified second test user to "Hold for moderation" in Members list. Noted the Moderation was set to "List default" before changing it to "Hold for moderation" The actual value is None, but Postorius displays/sets that as List default. >> If that is true, I can only think that at the time of that post, >> settings weren't as they are now. > > I think for now I will have to assume that's the case, until the next email can be readied against the proper list. If you hear nothing further, assume that this was all based on some random quirk (by humans or machines). I'll update if it happens again. Thank you for doing the test. -- 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: mailman addmember/syncmember commands print undecoded UTF-8 [ADD] or [DEL] mail addresses in its messages like "[ADD] =?utf-8?q?John_=....."

by Mark Sapiro

On 8/6/25 04:44, Wikinaut wrote: > Dear Mark, > > the problem has not gone. Now, in production during regular list upgrades, I got one member with 2(two) entries, one regularly encoded, the other double-escaped (can we call that so?). I'm interested in exactly what is done to produce these entries. Are you running `mailman syncmembers` or `mailman addmembers`? If so what is the input file that produces this. You can send it to me off list. > If you send me your private address, I can send you a screenshot. You can email me off list at the address in this and all my other posts. -- 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: Cannot Create New List

by Mark Sapiro

On 11/8/25 13:25, dap1--- via Mailman-users wrote: > Same as before. > > <venv> $ mailman info > GNU Mailman 3.3.10 (Tom Sawyer) > Python 3.12.3 (main, Aug 14 2025, 17:47:21) [GCC 13.3.0] > config file: /opt/mailman/var/etc/mailman.cfg And is /opt/mailman/var/etc/mailman.cfg now a symlink to /etc/mailman3/mailman.cfg? If not, make it so. If it is you could try rm /opt/mailman/var/etc/mailman.cfg cp /etc/mailman3/mailman.cfg /opt/mailman/var/etc/mailman.cfg > db url: sqlite:////opt/mailman/var/data/mailman.db > devmode: DISABLED > REST root url: http://localhost:8001/3.1/ > REST credentials: restadmin:restpass > > It is getting late here so I probably won't get back to this until tomorrow. Thanks for your help and sorry for being a PITA. We want to help. The only pain is when you don't provide requested information. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month

[MM3-users] Re: Difficulties setting up MM3 with Postfix MTA in Docker Environment: Invalid EHLO domain name & Authentification as lists.local

by Mark Sapiro

On 10/21/18 4:51 AM, Niklas Frühauf wrote: > > To me it seems like mailman is trying to authenticate as “lists.local” or “mail.local” or “localhost” to postfix (which of course isn’t working), then issues a EHLO/HELO to postfix which is not a FQDN. If the MTA requires authentication, you need to set smtp_user: and smtp_pass in the 'mta' section of mailman.cfg. By default, these are empty which means Mailman will not attempt to authenticate to the MTA for outgoing smtp. The actual connection to the MTA is via Python's smtplib. See <https://mailman.readthedocs.io/en/latest/src/mailman/mta/docs/authenticatio…> and <https://mailman.readthedocs.io/en/latest/src/mailman/mta/docs/connection.ht…>. -- 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: Missing Archived emails - Hyperkitty - CERT Issue

by Mark Sapiro

On 7/28/25 13:07, Willie Castillo wrote: > I tried with a new post and still, not showing the messages from July 25th in the Archive. There must be a way to force the archiving of the messages from July 25th. > > List metrics > > Created at March 25, 2016, 11:15 a.m. > Last post at July 25, 2025, 12:01 p.m. > Digest last sent at July 25, 2025, 12:01 p.m. > Volume 135 Did the new post get archived? If so, why is last post at still July 25, 2025? If no, why not. The post must go to the archiver to cause the queue to be processed. If the post was archived and the July 25 messages are still queued, what's in Mailman's mailman.log. There should be error messages and tracebacks indicating the issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 2 weeks

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

by Mark Sapiro

On 7/31/25 10:38, Odhiambo Washington via Mailman-users wrote: > > In one response, he mentioned that "Other mailinglists on the same host are > doing fine. Even a 1:1 copy of the list works - only the original list does > not work". > Does it mean that "the issue is in the outgoing runner" only for a single > list? So far we have not determined what the issue is. Until we do, we don't know in which module it is. It could be in outgoing runner involving something in the list's configuration or membership that isn't in the "1:1 copy" or it could be something to do with the message itself. It could even be an OS error such as "out of memory" due to the large number of list members. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 1 week

[MM3-users] Re: Memory footprint

by Mark Sapiro

On 04/10/2017 02:25 PM, David Krantz wrote: > Hi. > > Now running mailman 3 I am a bit surprised that the memory footprint > is so large. I count to 13 processes with each a virtual space of > 160-250MB and a reserved space of about 50MB each. Not much, but quite > much to run on smaller cloud instances which generally have limited > memory. This is (a lot) more than the corresponding postgres > installation uses, > > Is this normal? Those numbers seem "normal" but you really have to look deeper to understand if you just have a bunch of processes sitting in memory because the memory is available and nothing else wants it, or if there's real memory contention going on. The article at <https://wiki.list.org/x/4030711>, while written about Mailman 2.1, has some general information which may be of interest. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 8 months

[MM3-users] Re: Template Ignored?

by Mark Sapiro

On 2/17/22 10:10, Stephen Daniel wrote: > Fixed the POSTORIUS_TEMPLATE_BASE_URL. Doesn't fix the issue. > I've been playing with wget, and no matter what I put, I keep getting a 404 > error. > > So: this works: > > wget -O wget.out --user restadmin --password restpass ' > http://localhost:8001/3.1/lists/list.example.com' > > but this does not (404 error): > > wget -O wget.out --user restadmin --password restpass ' > http://localhost:8001/3.1/templates/list/list.example.com/list:user:notice:… You are using Mailman core's REST API which is wrong. You need to get the template from Postorius. Maybe something like http://localhost/postorius/api/templates/list/list.example.com/list:user:no… Where http://localhost/postorius/ is the URL you use to access Postorius, maybe mailman3 instead of postorius. Once you figure that out, POSTORIUS_TEMPLATE_BASE_URL is just the scheme and domain part of that. -- 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: Subscribing users stuck in pending hell

by Mark Sapiro

On 5/24/23 08:11, Quanah Gibson-Mount wrote: > Hi, > > We frequently end up with users who never receive their email to confirm > their account, leaving them in a netherworld where they cannot become > list members. If I try to subscribe them via the mass subscribe option, > it says I can't because their subscription is pending. If I go to > subscription requests, it says there are 0. If I go to "non-members" in > the UI, I can find them, but I don't see an option to convert them to > members. Subscription requests says 0 because it only counts those pending moderator approval, but if you pull down the menu and select Pending Confirmation, it should show the request and enable you to delete it, and then mass subscribe will work. -- 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: General question mailman3: message sender acceptance "always"

by Mark Sapiro

On 10/23/23 05:41, Wikinaut wrote: > > I could not find such an option (in the moderation dialog) in Mailman3 (only "accept" or "reject" and "discard", but "accept and add to white-list = accept always"). In the Postorius held messages view, click on the message's subject to open a dialog showing the messages content and a dropdown to set the moderation for this user and a box to enter a reject reason if you are going to reject the message. If you want to accept further messages from this yser, it is best to set moderation to Default processing rather than Accept immediately as the latter bypasses other checks that could result in the message being held. Note that even though the dropdown says Set member moderation, it works for non-members too. -- 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: repeated headers in mails from mailinglists

by Mark Sapiro

On 7/12/24 11:30 PM, Tobias Diekershoff wrote: > Dear all, > > we have recently migrated from Mailman2 to Mailman3 and now discovered > that all mails going through Mailman3 have the headers Archived-At and > List-Archive repeated identically in the mail header ~100 times each. This should definitely not happen unless mailman/handlers/rfc_2369.py is broken. > We are running Mailman3 on Debian Bookworm from the Debian repositories > (mailman3 3.3.8-2~deb12u2) with postfix (3.7.11-0+deb12u1) and > hyperkitty (1.2.1-1). This may be a Debian issue. See https://wiki.list.org/x/12812344 > Can somebody of you help me to get rid of the repeated header? You could in Postorius set Alter Messages -> Include RFC2369 headers to No, but this will not include any of the List-* or Archived-At headers at all which is not 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

1 year, 5 months

[MM3-users] Re: makemigrations --merge error after Debian upgrade

by Mark Sapiro

On 9/30/24 03:00, Chupin Maxime via Mailman-users wrote: > Hi, > I upgraded my debian version, Issues with the Debian Mailman packages should be reported to Debian. Please see https://wiki.list.org/x/12812344 and https://mail.python.org/archives/list/mailman-users@python.org/message/T6LB… > and since, it seems that I have a problem. I tried `mailman-web migrate` (and `mailman-web collectstatic` etc.) and I get the error message: > ``` > CommandError: Conflicting migrations detected; multiple leaf nodes in the migration graph: (0010_auto_20220618_2315, 0014_schedule_cluster in django_q; 0014_auto_20220618_2315, 0018_alter_emailtemplate_language in postorius). > To fix them run 'python manage.py makemigrations --merge' > ``` > So I tried `mailman-web makemigrations --merge` that ended with > ``` > PermissionError: [Errno 13] Permission denied: '/usr/lib/python3/dist-packages/postorius/migrations/0019_merge_20240930_1159.py' > ``` Did you run this as the Mailman user (`list` in the Debian packages)? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 2 months

[MM3-users] Re: Connection lost during _handle_client()

by Mark Sapiro

On 11/27/24 5:58 PM, Alain D D Williams wrote: > Nov 28 00:59:45 2024 (1268378) ('127.0.0.1', 42128) connection lost > Nov 28 00:59:45 2024 (1268378) ('127.0.0.1', 42128) Connection lost during _handle_client() > > I am concerned about the connection lost message above. It is normal and not a concern. > Mailman sees it, the message ID matches that at the end of the first line > in the exim log (above): > /var/log/mailman3/mailman.log > Nov 28 00:59:45 2024 (1268377) ACCEPT: <Z0fAe9xODd2y33N8(a)phcomp.co.uk> So Mailman got the message and accepted it. > Is there any more logging that I can look-at/switch-on to see what is happening ? Is there anything else in mailman.log? Does the message get archived? Is there anthing in any of Mailman's var/queue/* directories? Is Mailman core running? Does `mailman members --nomail enabled` list any members? -- 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: Issue with Held Messages

by Mark Sapiro

On 08/19/2016 10:39 PM, Jean-Luc Wasmer wrote: > On 2016-08-19 17:58, Mark Sapiro wrote: >> On 08/17/2016 09:17 PM, Jean-Luc Wasmer wrote: >>> >>> No matter what action I set for member posts (Hold for moderator, >>> Reject) they are always delivered. >> >> >> I don't know why this would be. Perhaps the member's moderation is set >> to Accept immediately - you can see this on ther member's options page >> in Postorius when logged in as a list owner. > > Apart from "Mode of Delivery" that is set to "Regular" for the user, > none of the following attributes are set: > > Mail Delivery > Receive own posts to the list > Receive acknowledgement mails > Conceal address from the subscriber list > Avoid duplicate copies of messages If you look at the user's options when logged in as a list owner, you should see an additional "Administration options" section below those with a "Moderation" setting. What is that set to? ... > By the way, I didn't mention before but in Settings | Message > Acceptance, the "Acceptable aliases:" box contains "[]". When I try to > Save changes after modifying something, I gut "An error occured: []" in > the yellow banner (instead of "The settings have been updated."). What happens if you clear the Acceptable aliases box before saving? ... >> This is apparently <https://gitlab.com/mailman/mailmanclient/issues/10> >> fixed by <https://gitlab.com/mailman/mailmanclient/merge_requests/16> > > Any ETA when this will be pushed to "mailman-bundler"? I expect bundler will be updated when 3.1 is released and that should be soon. You may find <https://wiki.list.org/x/17891998> of interest. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 3 months

[MM3-users] Re: ARC issues

by Mark Sapiro

On 3/2/20 7:45 AM, Stephen J. Turnbull wrote: > David Krantz writes: > > > Is there any known issues with ARC that I should be aware of? > > Doesn't Postfix do ARC yet? :-( rspamd seems to be recommended by a > couple of Linux distros, supports the milter interface that Postfix > uses to call out to 3rd party processes, and the website looks good. > See rspamd.com. That said, if you want to use Mailman's support... I've been trying openarc <https://github.com/trusteddomainproject/OpenARC> with Postfix as well as Mailman's ARC. I still haven't got it all worked out - I have a fairly convoluted mail flow with the possibility of messages being altered before they ever get to Mailman. There is an issue with Mailman's ARC signing in a supporting library. See <https://github.com/ValiMail/authentication-headers/issues/5>. -- 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: Where do I find the check_hk_archive script

by Mark Sapiro

On 11/18/23 11:21, Lars Bjørndal wrote: > In https://docs.mailman3.org/en/latest/migration.html I'm adviced to run > the check_hk_archive script found in hyperkitty/contrib. When trying > `git clone https://gitlab.com/mailman/hyperkity`I get: > > Username for 'https://gitlab.com': > > Is it possible to get the script without an account on gitlab? I've updated some project settings. You should now be able to `git clone https://gitlab.com/mailman/hyperkity` without a gitlab account. However, why are you wanting to do this. If you have HyperKitty installed, there should be a hyperkitty/contrib directory in your installation, e.g. /opt/mailman/venv/lib/python3.x/site-packages/hyperkitty/contrib/ containing the check_hk_import and cleanarch3 scripts. Even if you don't have that, you can download the script from https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/contrib/chec… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

[MM3-users] Re: Weird hourly indexing error

by Mark Sapiro

On 6/9/20 9:29 PM, Mark Dadgar wrote: > On Jun 9, 2020, at 1:57 PM, Mark Sapiro <mark(a)msapiro.net> wrote: >>> THANK YOU for all the help. >> >> >> I'm glad we finally got it resolved. > > > I may have spoken too soon: > > [ERROR/MainProcess] Failed indexing 1 - 1000 (retry 5/5): Term too long (> 245): XSUBJECT95251413 (pid 729081): Term too long (> 245): XSUBJECT95251413 > Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/haystack/management/commands/update_index.py", line 97, in do_update > backend.update(index, current_qs, commit=commit) > File "/usr/local/lib/python3.8/dist-packages/xapian_backend.py", line 492, in update > database.replace_document(document_id, document) > xapian.InvalidArgumentError: Term too long (> 245): XSUBJECT95251413 > > "XSUBJECT95251413“ has some serious weirdness embedded in it. > > Not sure how to search for that in the django shell? I suspect the issue here is the 'weirdness' is in the Subject: rather than the message body. The script we were using only looked at the body. The message you sent me had a Subject which visually looked like `[PDC] MEGAMillions- Ticket №7383246 9` but the № and the digits were interspersed with strings of unicode zero width spaces, so the decoded Subject: was actually '[PDC] MEGAMillions- Ticket №7\u200b\u200b\u200b\u200b\u200b\u200b\u200b3\u200b\u200b\u200b\u200b\u200b\u200b\u200b8\u200b\u200b\u200b\u200b\u200b\u200b\u200b3\u200b\u200b\u200b\u200b\u200b\u200b\u200b2\u200b\u200b\u200b\u200b\u200b\u200b\u200b4\u200b\u200b\u200b\u200b\u200b\u200b\u200b6\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b9\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b\u200b' where all the \u200b unicodes are the zero width spaces. I suspect your current issue is with the Subject:. Actually, looking back at the thread, the prior one probably was too, but we also found messages that had this in the body. To alter the specific script to look at the Subject: just change the line if email.content.find('\u200b'*5) >= 0: to if email.subject.find('\u200b'*5) >= 0: There's probably a reply there somewhere that has the Subject: but didn't quote the bad stuff in the body. -- 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/14/22 08:21, Stephen J. Turnbull wrote: > Mark Sapiro writes: > > > That combination at least produces multipart/signed messages with > > multipart/* parts containing a Content-Transfer-Encoding: header. > > > > The Python 3 email library considers this to be a > > InvalidMultipartContentTransferEncodingDefect() message defect. > > Merely containing C-T-E is not an error per RFC 2045, although it > seems to consider it a stupid thing to do. If present, it may be > "binary", "7-bit", or "8-bit" (below summarized as "cleartext"). > > Did Apple Mail apply a non-cleartext C-T-E? Or has an RFC tightening > that restriction been published since? (I don't know why it would, > though.) Yes. The C-T-E on all the multipart parts was quoted-printable, not allowed under RFC 2045. > Even with a non-cleartext C-T-E, it seems reasonable for Mailman to > treat it as application/octet-stream and pass it through, unless the > list is configured to do something like strip application/octet-stream > or that requires decoding like spam-filtering (Postel principle, > although one could argue it shouldn't be sent on on the same principle > -- ah, the joys of being an e-mail Mediator). That would be > especially true it if were quoted-printable, since any relevant MIME > headers would (presumably) be pure ASCII and therefore unencoded. The Python email library says the message is defective. Mailman's lmtp runner in turn rejects the defective message with a 501 status https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/lmtp.p… It could accept a defective message or one with specific defects, but this is problematic for further processing. For example, at least one MUA, Thunderbird, renders such a message with an empty body. -- 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: "mailman start" hangs

by Mark Sapiro

On 02/13/2018 05:40 AM, Peter Münster wrote: > Hi, > > When starting mailman in a terminal, then it works: > > --8<---------------cut here---------------start------------->8--- > $ mailman start > Starting Mailman's master runner > $ > --8<---------------cut here---------------end--------------->8--- > > But from "cron", it seems to hang. Output of pstree: > > --8<---------------cut here---------------start------------->8--- > |-cron(3022)---cron(21962)-+-mailman(21986) > | `-sendmail(22043)---postdrop(22044) > --8<---------------cut here---------------end--------------->8--- > > So it seems, that mailman does not go into the background, and the email > with the output is never sent... I think Abhilash's answer is probably closer to the mark, but there can be issues with running 'mailman' from cron or init scripts which don't set a UTF-8 compatible LANG in the environment as described at <http://mailman.readthedocs.io/en/latest/src/mailman/docs/install.html#runni…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 10 months

[MM3-users] Re: Changing posting address

by Mark Sapiro

On 11/7/18 10:59 PM, Johannes Winter wrote: > Dear list, > > I'd like to change the sending address of a mailinglist, but when I try > to set it via mmclient with > > ./manage.py mmclient > lists=client.lists > l=lists[listnumber] > l.settings['posting_address']='new name' > > > I get `ValueError: value is read-only`. > > Is it possible to change this value, or should I use another setting > for this objective? You can't change the list's posting_address. You have to change the list_name which you can't do via mmclient, but you can do via 'mailman shell'. If you want to change the posting_address without changing the list name, you can alias the desired posting address to the list_name@domain address in the MTA and add the desired posting address to the list's acceptable_aliases. -- 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: Shunt Error Mail?

by Mark Sapiro

On 3/2/21 2:52 PM, Pete Ashdown wrote: > I have a number of list managers with subscribers who are confused as to > why their messages are silently disappearing. I've read the archives on > how to decipher why a message was shunted, but this is not workable at > scale. Is sending an error email back to the sender a consideration? Why are messages being shunted? Each shunted message has thrown some kind of uncaught exception which is logged with a traceback in Mailman's mailman.log. These should be due to bugs that should get fixed or possibly malformed messages which are almost always spam. In short, under normal circumstances messages should not be shunted at all and when they are it is something the site admins need to address. It is normally not something the sender of the message can do anything about. -- 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: Help! List traffic shunted to gmail/yahoo spam folders

by Mark Sapiro

On 7/10/21 2:42 PM, Matt Wilbur EFS via Mailman-users wrote: > Hello, > > I've been through DKIM hell and back. Now I'm to the point where when I > "show original" mail with gmail it says SPF, DKIM and DMARC all pass, > but it's still going to the spam folders. Does your list domain publish a DMARC record? If not publishing a DMARC record with policy of none may help, but it seems you are probably doing that. Beyond that, it is probably filtering based on something in the message content and the recipient ISPs will never tell you what because they consider that kind of information proprietary. Setting up feedback loops with gmail and yahoo also may help, but there's really not much else you can do. -- 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: Template - "You can use these variables in the templates" - The variable for "leave" is missing

by Mark Sapiro

On 11/4/23 06:28, Stephen J. Turnbull wrote: > Wikinaut writes: > > > fxied in merge request > > https://gitlab.com/mailman/postorius/-/merge_requests/852 > > I wish you wouldn't. It's just bloat in the code and in the > docstring. Better to document that the administrative addresses can > be constructed using ${short_listname}. I believe Mailman still > supports both "list-leave" and "list-unsubscribe", as well. Actually, https://gitlab.com/mailman/postorius/-/merge_requests/852 only added documentation of the existing $description replacement which is appropriate, but it duplicates part of https://gitlab.com/mailman/postorius/-/merge_requests/851 which does that and adds a bit more documentation. Also see https://gitlab.com/mailman/mailman/-/issues/1108 and https://gitlab.com/mailman/mailman/-/merge_requests/1153 -- 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: False attachments in Outlook 2019?

by Mark Sapiro

On 1/24/21 3:29 AM, Brian Olesen wrote: > Dear Mailman 3 users, > > I seriously think of upgrading from Mailman 2.1.33 to this new RC2 or the > final one, when it comes out. > > > > But there is an annoying issue that I'd like to ask you about. > > It's the false attachments that Outlook creates for the footer. Is this > still an issue when using Mailman 3, or have you made some sort of work > around? See the FAQ at <https://wiki.list.org/x/4030707> for a discussion of why we don't try to insert headers and footers into HTML message parts. This applies to Mailman 3 as well as Mailman 2.1. I don't know if anyone has tried it, but the MIMEDefang solution mentioned in the FAQ would probably work with Mailman 3. -- 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: Unable to get Postfix to bounce messages to non-existent lists

by Mark Sapiro

On 2/19/24 09:14, skenny(a)scss.tcd.ie wrote: > > The only problem with this is that if someone sends a message to a non-existent mailing list, Postfix nevertheless accepts the mail, and it loiters in the queue for several days before eventually being bounced back to the sender. I want to get Postfix to reject mail to non-existent mailing lists immediately. I've come up short with each variation of main.cf settings I've tried, and would greatly appreciate any advice. What is Postfix's reason for deferring the mail - `mailq` will show the reason. What if you just omit the relay_domains = regexp:/var/mailman-data/postfix_domains setting. This may cause all list mail to be rejected, but it may work (I'm not sure if transport_maps takes priority). -- 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 search on Message-ID?

by Mark Sapiro

On 12/5/24 04:25, Bryan Fields wrote: > I've been working with a rather large import and am finding that I can't seem > to get the search on a Message-ID: to return anything. ... > Any ideas how to get it indexing the ID so a layperson can search on it? Message-ID is not one of the fields indexed. These are defined at https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/search_index… A bit obscure for laypersons, but one can compute the message_id_hash from the Message-ID ``` from base64 import b32encode from hashlib import sha1 def get_message_id_hash(msg_id): return b32encode(sha1(msg_id).digest()).decode() ``` I can't help but wonder though how one has the Message-ID without having the message. I'm wondering in general how often if ever the layperson would be searching the archive for a Message-ID. -- 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: Mm3 - new adventure

by Mark Sapiro

On 03/15/2017 07:35 AM, SP2L wrote: > > Today started reading belows document: > > http://docs.mailman3.org/en/latest/devsetup.html > > There is evidently misleading command > repeated more than once: > > $ git clone git@gitlab.com:mailman/mailman.git > > (at least, above is not working from Debian command line) > > which should read: > > $ git clone https://gitlab.com/mailman/mailman.git In order to use the former command, you must register for a gitlab account and install your ssh public keys there. This is mentioned in two places in the document at https://wiki.list.org/DEV/SetupDevEnvironment which is the first thing referenced in the document at http://docs.mailman3.org/en/latest/devsetup.html It also needs to be mentioned at http://docs.mailman3.org/en/latest/devsetup.html Thanks for pointing that out. This is now reported at https://gitlab.com/mailman/mailman-suite-doc/issues/3 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 8 months

[MM3-users] Re: mailman.cfg (use_https: yes) fails

by Mark Sapiro

On 11/16/19 4:54 AM, Wolfgang Bock via Mailman-users wrote: > I will look at the https issue further when I get time. > In this context I faced a strange behavior: > > In the database mailman3web in table django_site are listed several > domains, either in the django-domain-management site > https://[mydomain]/mailman3/admin/sites/site/ > > id domain name > 1 example.com Example.com > 2 [mydomain-1] [mydomain_name_1] > 3 [mydomain-2] [mydomain_name_2] > 4 [mydomain-3] [mydomain_name_3] > > In case I delete line 1 with the id 1, in the database or in the > django-web-site, postorius fails to work. After re-inserting this line, > postorius works again. In your settings.py, you probably have SITE_ID = 1. Thus, when you delete the site with id = 1, Postorius fails. You need to set SITE_ID to an existing site in settings_local.py. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

[MM3-users] Re: Mailman REST API not available. Please start Mailman core.

by Mark Sapiro

On 7/28/20 1:07 PM, joseverde(a)gmail.com wrote: > [Does your systemd script set the user to the Mailman user, and does the > Mailman user have read/write permission on Mailman's var/locks/?] > > How do I check for that? ls -la /path/to/mailman/var/locks > Also, what's the difference between the mailman command and the systemctl mailman3? Are they the same processes? Presumably your mailman3.service actually uses the `mailman start` command to start Mailman. The `mailman` command is a shell with many subcommands for various purposes including starting and stopping Mailman. > Oh and does the /3.1 matter at the end of the Rest url for Django? Do not put the 3.1 at the end of your MAILMAN_REST_API_URL. Postorius adds it. See <https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/utils.py#L…>. -- 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: web api

by Mark Sapiro

On 8/4/21 10:44 AM, Ethan Furman wrote: > Greetings again! > > Is there a remote API I can use to manage a list? Mailman core's REST API is documented at <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…>. By default it listens only on localhost:8001 and requires authentication with user = restadmin and password = restpass but these are all settings in the webservice section of mailman.cfg. See <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.…> for the settings and their defaults. You could set [webservice] hostname: 0.0.0.0 admin_pass: My_Secret in mailman.cfg to have it listen for connects from anywhere and require a different password. You'd also need to adjust some or all of the settings for MAILMAN_REST_API_URL MAILMAN_REST_API_USER MAILMAN_REST_API_PASS In your Django settings. There is also <https://gitlab.com/mailman/lemme> however, that's only a skeleton and not useful as is. -- 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: OK, so I backed out completely and re-installed. Here's my *original* error. Should I modify virtual mailbox maps?

by Mark Sapiro

On 10/16/24 10:26, Bill Oliver wrote: > > 1) I set up a mailinglist (tradfp(a)forensicpath.us) for "old school" > forensic pathologists to discuss cases. Does the forensicpath.us domain have an alias_domain configured in mailman causing mailman to create /opt/mailman/mm/var/data/postfix_vmap and /opt/mailman/mm/var/data/postfix_vmap.db? You need this. > In my previous attempt, I added > > hash:/opt/mailman/mm/var/data/postfix_lmtp > > to both virtual_mailbox_maps and virtual_alias_maps, but I haven't > done that yet here. I thought I'd ask and make sure I should. > > Should that be my next step? You should add hash:/opt/mailman/mm/var/data/postfix_vmap to virtual_alias_maps only. -- 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: Installation issues

by Mark Sapiro

On 04/20/2016 01:11 AM, Andrew Hodgson wrote: > > My next stab at this was going to be using venvs, but creating the venv as the directory /opt/mailman which gives cleaner paths (to my mind anyway), but haven't got round to doing it yet. You should be aware that mailman-bundler uses two venvs, one for Python 2 and one for Python 3. The idea is you create the Python 2 venv and activate it when running mailman-bundler's buildout, but that process will also create a venv-3.x venv in the bundler directory. I think what may make sense is to clone mailman-bundler directly into /opt/mailman rather than /opt/mailman/mailman-bundler. Then follow the docs from there. This should give you paths like /opt/mailman/venv/, /opt/mailman/venv3.x/, /opt/mailman/deployment/, /opt/mailman/mailman-web/, /opt/mailman/bin/, /opt/mailman/var/ and so on without the extra mailman-bundler/ level. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 7 months

[MM3-users] Re: Installing mailman 3

by Mark Sapiro

On 07/25/2017 12:35 PM, Rafael Mora wrote: > This is from the file /var/log/maillog: > > Jul 24 17:29:21 localhost postfix/postfix-script[2092]: starting the > Postfix mail system > Jul 24 17:29:21 localhost postfix/master[2096]: daemon started -- version > 2.10.1, configuration /etc/postfix > Jul 25 03:30:05 localhost postfix/pickup[2785]: 03F4160D143F: uid=0 > from=<root> > Jul 25 03:30:05 localhost postfix/cleanup[3191]: 03F4160D143F: > message-id=<20170725073005.03F4160D143F(a)localhost.localdomain> > Jul 25 03:30:05 localhost postfix/qmgr[2113]: 03F4160D143F: > from=<root(a)localhost.localdomain>, size=508, nrcpt=1 (queue active) > Jul 25 03:30:05 localhost postfix/local[3195]: 03F4160D143F: > to=<root(a)localhost.localdomain>, orig_to=<root>, relay=local, delay=0.11, > delays=0.07/0.03/0/0.01, dsn=2.0.0, status=sent (delivered to mailbox) > Jul 25 03:30:05 localhost postfix/qmgr[2113]: 03F4160D143F: removed > > > It seems that postfix is working, isn't it? At least for receiving mail queued by the sendmail command and delivered to root. -- 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: Adding user - Error 409 Subscription request already pending

by Mark Sapiro

On 4/20/19 10:13 AM, brian(a)emwd.com wrote: > Hi Mark, > > I followed your instructions to confirm the user. When I ran ">> util.confirm('hex_token')" nothing happened which I take it to mean it worked. I then ran ">> list(util.find(mlist=m,pend_type='subscription'))" and the pending member did not show up which I thought was a good thing. But . . . > > I tried to mass subscribe the user and got back: > > "HTTP Error 409: b'{"title": "409 Conflict", "description": "Subscription request already pending"}'" Did you do commit() or exit shell (which does an implicit commit) before trying the mass subscribe? I'm not going to be able to look at this further for some time as I am traveling today, but I will. -- 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: Subscribing by E-Mail

by Mark Sapiro

On 5/21/20 4:47 PM, Peter Adebahr via Mailman-users wrote: > > on MM2 systems, we used to subscribe people via an external application > by sending an e-mail to the request address with a subject of > "subscribe address=user(a)example.com" > > This returns a "bad argument" in MM3 - any ideas how to solve this? Currently, a subscribe or join command sent to the -request address only supports one argument, `digest=<no|mime|plain>`. To subscribe an arbitrary address, you can send to the -join or -subscribe address with the From: set to the address you want to subscribe, but you say > We cannot set the actual from-address in a foreign application... Modifying mailman/commands/eml_membership.py to accept an address= argument shouldn't be difficult. If you submit an issue at <https://gitlab.com/mailman/mailman/-/issues>, I'll look at it. -- 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: "To:" header field

by Mark Sapiro

On 08/05/2018 06:20 AM, Asaf Ohayon wrote: > > Comparing to Mailman 2.1, which we recently upgrading from, > and didn't got spammed, the "To:" field was set to the actual reciever, > While in Mailman 3.2, the "To:" field is set to the list's address. > > How can this be configured ? This is full personalization. See <http://mailman.readthedocs.io/en/latest/src/mailman/handlers/docs/cook-head…>. This setting is not yet exposed in Postorius, so you have to set it via 'mailman shell'. E.g. $ bin/mailman shell -l test(a)msapiro.net Welcome to the GNU Mailman shell The variable 'm' is the test(a)msapiro.net mailing list >>> m.personalize <Personalization.none: 0> >>> from mailman.interfaces.mailinglist import Personalization >>> m.personalize = Personalization.full >>> m.personalize <Personalization.full: 2> >>> commit() -- 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: API access to Hyperkitty

by Mark Sapiro

On 2/9/21 10:23 AM, Brian Carpenter wrote: > Is it possible to download Hyperkitty's archives to a remote server via > an API? Is there documentation that explains how to accomplish this task? > I don't think there is documentation, but if you look at the target of any `download` button, it should be obvious. I.e. the link to download the entire archive for this list is https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/export/… The `mailman-users(a)mailman3.org-2021-02.mbox.gz` part is the name of the file to download to and the `-2021-02` part can be anything or nothing, but the name must begin with the list posting address and end with `.mbox.gz`. If the archive is large, this can time out in which case adjust `start` and `end` to download it in pieces. -- 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: Problems with web interface after upgrade

by Mark Sapiro

On 2/9/21 3:26 PM, Victoriano Giralt wrote: > > It's CentOS7, but sassc was already installed and has -t as short for --style. You wrote > ModuleNotFoundError: No module named 'sassc -t compressed {infile} {outfile}' It should be looking for just sassc, not 'sassc -t compressed {infile} {outfile}'. Whats in your settings for COMPRESS_PRECOMPILERS. That may not be the issue. You also wrote > compressor.exceptions.FilterError: Error: It's not clear which file to > import for '@import "../libs/bootstrap/stylesheets/bootstrap"'. > Candidates: > ../libs/bootstrap/stylesheets/_bootstrap.scss > ../libs/bootstrap/stylesheets/bootstrap.scss > Please delete or rename all but one of these files. > on line 4 of static/hyperkitty/sass/hyperkitty.scss You need to remove the older of hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/bootstrap.scss and hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_bootstrap.scss That may be the whole issue. -- 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: migrate MM3 list from an old server to a new one

by Mark Sapiro

On 8/6/24 01:43, noc(a)iem.at wrote: > > PS: (again) I'm resending this message, as the one i sent yesterday seems to have vanished (i *did* check the archvies). i have no clue why this happens, as i can post via the webinterface just fine (only when using my trusted MUA they just vanish). Your messages are being discarded for matching a header filter rule. The messages contain content-type: application/pgp-keys; name="OpenPGP_0xB65019C47F7A36F8.asc" and the content-type rule regexp is `^ *application(?!.*signature)` I.e we accept things like application/pgp-signature and application/pkcs7-signature, but not application/pgp-keys I have changed that regexp to `^ *application/(?!(pgp|[^ ;]*signature))` so we will now accept `content-type: application/pgp.*` as well so you now should be able to post/reply from your MUA. -- 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: Must issue a STARTTLS command first when forwarding from old server to new server

by Mark Sapiro

On 11/14/24 15:53, jkoral(a)luc.edu wrote: > I have a fully functioning Mailman3 server now and have setup and alias on the old server to forward mail to the new server. We have TLS enabled on the new server, but not the old server, so the new server is rejecting the mail coming through. Our IT security will not allow me to disable TLS on the new server. > > Is there a way to make an exception in mailman3 to allow a specific host to send mail through without using TLS? This is all the MTA, not Mailman. As you suggest in a follow up, you should enable TLS on the old server. In Postfix main.cf, I think ``` smtp_tls_security_level = may ``` should do it. -- 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: Cannot Create New List

by Mark Sapiro

On 11/5/25 09:59, dap1--- via Mailman-users wrote: > As far as I know I did everything (except the /etc/mailman3 stuff) in the venv environment. Pip is not even available outside of mailman user. When I try to run pip again it says requirement already satisfied. I don't suppose there is a checkparms like in mailman2. I'm not aware of any Mailman 2.1 checkparams. There is check_perms, but I don't know if that's what you want. The fact remains that something is checking for `/usr/bin/django-admin`, finding it and then trying to run `flock -n /var/run/mailman3-web/cron.minutely /usr/share/mailman3-web/manage.py runjobs minutely` If everything is in your venv, why is there a `/usr/bin/django-admin` and perhaps a `/usr/share/mailman3-web/manage.py`. These all look like artifacts from an install of the Ubuntu mailman-web package. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 1 week

[MM3-users] Re: Header Filters

by Mark Sapiro

On 5/31/20 7:23 PM, Peter Adebahr via Mailman-users wrote: > > Hi *, > > we are trying to dispose of automatic replies like "out of office" etc. > > For these ends, we have set > > Header to "subject" (w/o quotes) > Pattern to ".*out.of.office.*" > Action to "Hold for moderation" This should hold any message that contains 'out of office' (case insensitively) anywhere in the Subject: - also the leading and trailing '.*' is superfluous as the pattern is matched with re.search - BUT this test is applied after member moderation so if the message is from a member and the member's moderation action is Accept either explicitly or via list default, the message will be accepted without applying further tests. You want the member's moderation action to be Defer so that additional checks such as header matching are applied. -- 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: Source Installation Assistance

by Mark Sapiro

On 11/29/19 7:37 AM, actionmystique(a)gmail.com wrote: > mark.van.holsteijn＠gmail.com > I stumbled across the same issue as Brian Carpenter within a slightly different environment: > Ubuntu focal 20.04 > PostgreSQL 12.1-1 > > I tried to replace the following line in ```/usr/lib/python3/dist-packages/hyperkitty/migrations/0007_allauth_20160808_1604.py``` from ```python3-django-hyperkitty``` (1.3.0-1ubuntu1): > ``` > cursor.execute("SELECT 1 from social_auth_usersocialauth") > ``` > with > ``` > cursor.execute("SELECT 1 from information_schema.tables where table_name ='social_auth_usersocialauth' and to_regclass('social_auth_usersocialauth') is not null") > ``` > then > ``` > python3 manage.py makemigrations > ``` > leads to a different issue: We are working on a proper fix for this issue. See <https://gitlab.com/mailman/hyperkitty/merge_requests/200>. In the mean time, to work around this issue on a new install, the simplest change is to just delete the second to last line ``` migrations.RunPython(migrate_social_users), ``` from hyperkitty/migrations/0007_allauth_20160808_1604.py -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

[MM3-users] Re: How to create user accounts and mail addresses through CURL instead of Site Administration ?

by Mark Sapiro

On 8/10/20 11:18 AM, Shashikanth Komandoor wrote: > I am currently automating a few things using the CURL commands but only > postorius related as of now. Now I have a requirement. > > I need to create a lot many users and their mapping email ids through > Site Administration almost daily. But it is becoming to do the same through > Graphical Interface. > > So, I just want to know the CURL commands that can be used to create the > user accounts and email ids mapped to user accounts. The accounts you are talking about are Django accounts. You cannot create these via CURL to the Mailman core REST API. You might find <https://www.django-rest-framework.org/tutorial/quickstart/> of interest. -- 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: How To Install Mailman 3 on Debian 10 (Complete Guide)

by Mark Sapiro

On 2/26/21 1:19 PM, Andreas Barth wrote: > > Re the "latest greatest", that's always the same question for all > software. If one is happy what comes from the distribution, I always > recommend to use that (or just use the currently developed stable > version, i.e. testing or unstable, perhaps even only for these > packages). If one needs something newer / else / specific local > patches, it's good to have documentation that helps. We're not talking bleeding edge here (although the server that supports this list and the python.org lists is bleeding edge). We are talking about installing the current releases from PyPI. Mailman 3 is still relatively young and there are many important features and fixes in the current releases that aren't in the Debian/Ubuntu packages. -- 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: Moderation request reminders

by Mark Sapiro

On 1/14/23 09:33, Allan Hansen wrote: > > I and my moderators are getting daily moderation request reminders. Is there a way to set them to be weekly instead? I looked around in the UI for it but did not see it. It started with my latest server upgrade. As list owner I get 50+ of these messages every morning and my modertors each get only one, but don't like it. This is `mailman notify` <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d…> run by cron. > I still don't see a link for my moderators to see the membership lists even though the lists are set to allow it. Is that among the planned bug fixes? This is <https://gitlab.com/mailman/postorius/-/issues/369>. There is an abandoned MR at <https://gitlab.com/mailman/postorius/-/merge_requests/423> but see the recent notes. -- 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: search this list searches more then just this list

by Mark Sapiro

On 1/29/24 03:09, Marco van Tol wrote: > > Right now I’m back at the original issue as I see no other solution than to go back to whoosh. > > Thanks! > > Marco van Tol > > Paste: > ---- > Indexing 194620 emails > [ERROR/MainProcess] Failed indexing 156001 - 157000 (retry 5/5): Term too long (> 245): XSUBJECThttp://www.google.com/url?q=%68%74%74%70%73%3a%2f%2f%68%64%72%65%64… (pid 32): Term too long (> 245): XSUBJECThttp://www.google.com/url?q=%68%74%74%70%73%3a%2f%2f%68%64%72%65%64… I'm not sure why the patch you are using doesn't avoid this, but you could try the other patch at <https://github.com/alexsilva/xapian-haystack/commit/a53523d2d0d13929a0729d4…> instead. If that fails, you could always find the offending message in the database maybe with a query like ``` SELECT * FROM hyperkitty_email Where subject LIKE 'http://www.google.com/url?q=\%68\%74\%74%'; ``` and modify or delete it - it's probably spam anyway. -- 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: The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header.

by Mark Sapiro

On 9/23/25 09:39, Stephen J. Turnbull wrote: > nirmal--- via Mailman-users writes: > > > Eventhough I have downgraded it. Archiving is not working. Kindly > > help me to solve. > > Does the subject have anything to do with this problem, or did you > reply to some other thread? > > If it's related to the problem, that's one problem. Most likely the > api_key setting in mailman-hyperkitty.cfg' doesn't match the > MAILMAN_ARCHIVER_KEY in 'settings.py', or possibly you have the wrong > quoting in one of the files. This could have happened in the > downgrade if you downgraded only some of the Mailman packages. Actually, this is an incompatibility issue. It results from mailman-hyperkitty < 1.2.0 in combination with HyperKitty >= 1.3.5 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 months, 2 weeks

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

by Mark Sapiro

On 5/14/19 12:18 AM, Alan So wrote: > One more finding. If the user select "All" in the "Filter by role" box, nothing can be shown. So, that shouldn't be related to the default limit of 50 with find_lists. Otherwise, at least some lists should be displayed. If you are saying no lists are shown when the user selects "all", is it possible that no lists are advertised? I.e., all lists have Settings -> List Identity -> Show list on index page = No. If that is not the case the advertised list should be shown on the "all" view or when not logged in. I don't see an issue at <https://lists.mailman3.org/mailman3/lists/> or <https://mail.python.org/mailman3/lists/>. -- 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: Language Support In Templates

by Mark Sapiro

On 1/25/21 12:18 PM, Brian Carpenter wrote: > Hello MM3 Users, > > I have a question regarding the use of templates in different languages. > I created a template for the unsubscribe notification in Postorius in > Greek. The template shows up fine in Greek via Postorius. However the > email that is sent out has a bunch of question marks where the Greek > should be: This is a bug in Postorius. I just reported it at <https://gitlab.com/mailman/postorius/-/issues/465>. There are a couple of workarounds. Assuming the list's preferred language is Greek (el), You can put the template in Mailman's var/templates/lists/<list-id>/el/ directory (creating it if necessary and ensuring it's readable by the Mailman user. You can set ``` [language.master] charset: utf-8 ``` in mailman.cfg to change the default character set from ascii to utf-8 -- 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: Dealing with recipients' servers spam filtering

by Mark Sapiro

On 2/13/21 7:31 AM, Gilles Filippini wrote: > > Writing down what I've learned so far, in case it may help others: > > 1- The lists server DNS record (lists.example.com) should be of 'A' type > (no 'ALIAS' or 'CNAME') Not only that, reverse lookup of the IP in the A record must point back to the same (lists.example.com) domain. See, e.g., <https://en.wikipedia.org/wiki/Forward-confirmed_reverse_DNS>. > 2- The SPF record should be set for the very same DNS name; e.g. > lists.example.com (not just example.com) > 3- This record seems to work for my server: > lists.example.com. IN TXT "v=spf1 ip4:123.123.123.123 -all" > Where the IP address is the same as the one registered for the 'A' > record. And you should also DKIM sign outgoing mail. -- 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: How to store additional information about lists?

by Mark Sapiro

On 5/25/21 12:28 AM, Stephen J. Turnbull wrote: > Andreas Barth writes: > > > private: hand-selected people, think about e.g. board or steering > > committees internal discussions. Of course, the archive (if there is > > any) should be restricted to the actual members. Posting to these > > lists is currently not restricted, so no derivation needed from the > > current set in postorius. > > This is already possible by requiring admin approval, or by setting > the ban list to something that matches everything like "^.". The ban list can't be used in this way. A banned address can't be subscribed by any means including admin action. And even if an admin temporarily removes the ban, subscribes the address and then restores the ban, the now banned member can't post. -- 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: How to delete user completely?

by Mark Sapiro

On 1/21/22 4:32 PM, William Oliver wrote: > I have installed mailman3 and it's up and running great. However, I > noticed that, during a mass subscribe, I mis-typed an address, e.g. > name(a)domain.ned rather than name(a)domain.net. I found how to unsubscribe > the bad address, but I haven't found a "delete" option under Users or > anywhere else. How to I purge a user from the users list? You need to do it via REST or `mailman shell`. In mailman shell, ``` >>> um = getUtility(IUserManager) >>> usr = um.get_user('user(a)example.com') >>> um.delete_user(usr) >>> commit() ``` > As a related question, in docs.mailman.org, I can find a list member's > manual, but I can't seem to find an admin manual. Is there one? No, not per se. -- 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: Pb with archive display

by Mark Sapiro

On 5/4/22 05:45, Pierre Malard via Mailman-users wrote: > > On the other hand Mailman3 does not seem to take into account the display of the archives. The contributions are indeed in the directory "/var/lib/mailman3/archives/hyperkitty/spool" but HyperKitty does not take them into account when displayed on the Web interface. > > Is this normal? No. The messages are in /var/lib/mailman3/archives/hyperkitty/spool because delivery to HyperKitty failed. There should be messages in Mailman's var/logs/mailman about the failures. The setting for api_key in mailman-hyperkitty.cfg must match the setting for MAILMAN_ARCHIVER_KEY in your Django settings. Also, the setting for base_url in mailman-hyperkitty.cfg must be good. If you append `/api` to that url, the result should return a page of documentation of HyperKitty's REST API. Also see this thread https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… -- 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: Issues encountered while upgrading to 3.3.7

by Mark Sapiro

On 12/5/22 02:37, Odhiambo Washington wrote: > > Here again, Google-fu came to the rescue. I added the following line to > settings_local.py and the warnings were suppressed. > DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' > I need to understand how this affects everything and how this is likely to > impact the functionality of MM3. What is the proper solution for this? > And should it be django.db.models.BigAutoField or > django.db.models.AutoField? Which is which? Prior to Django 3.2 Django set default primary keys to 32 bit integers. In 3.2 Django introduced the possibility to set default primary keys to 64 bit integers by setting the type to django.db.models.BigAutoField. Thus, putting ``` DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' ``` in your settings will maintain compatibility with pre 3.2 versions and existing tables and this is the correct thing to do. -- 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: upgrading in FreeBSD 13.1-p7: problem with aiosmtpd and lmtp runner

by Mark Sapiro

On 4/3/23 23:12, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > Just to make it clear: It happened upgrading from 3.3.7 to 3.3.8 > > The upgrade procedure I did all the times is > > pip install --upgrade django-mailman3 mailman mailman-hyperkitty > mailmanclient postorius django hyperkitty uwsgi mod-wsgi > > and if I see some trouble I did it with a --force-reinstall parameter > (not that I remember it happened last times that I upgraded) > > (and then the collectstatic, etc.) > > If I missed something, I don't know. Mailman 3.3.5, 3.3.6 and 3.3.7 all required aiosmtpd>=1.4.1 so your prior upgrades should have installed aiosmtpd>=1.4.1. Possibly aiosmtpd>=1.4.1 was installed somewhere, but your jail configuration was such that it wasn't the one actually used by lmtp runner. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 8 months

[MM3-users] Re: Bulk changes to delivery mode and moderation action

by Mark Sapiro

On 1/7/22 6:07 PM, David Newman wrote: > On 1/7/22 4:32 PM, Mark Sapiro wrote: > >> I suspect an issue trying to connect to the MTA to send the messages. >> This can be caused by permission errors. Check permissions on >> Mailman's var/templates/* > > Bingo. This list had regular and digest footer templates with 0644 > permissions owned by root:root, and there was an exception and traceback > for the most recent message in shunt about the permissions issue. That comes from running `mailman import21` as `root`. Always run `mailman` commands as the Mailman user. > I've changed ownership to mailman:mailman and restarted the mailman3 > service. > > As soon as I fixed this, my inbox filled with test messages... Good! >> Is there a 'Cannot connect to SMTP server ... on port ...' anywhere in >> mailman.log? > > Yes, lots. This might or might not be a different issue. It is exactly this issue which is now corrected. > As I mentioned earlier, the most recent message in shunt was from 0000 > hours today. There are many "Cannot connect" messages since then, but > none since fixing the issue above. The Cannot connect messages are from the issue of ownership of the templates and Mailman's out runner continually retrying the send. This is separate from the shunted messages. > Seems OK now. The superuser sees all posts after the unshunt action. So it appears that you ran `mailman unshunt` and the shunted messages were successfully processed, so whatever caused them to be shunted in the first place is fixed. Individual messages don't get shunted because of this template ownership issue, but it may be that digests do get shunted for this reason. -- 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 change the language in mailman3

by Mark Sapiro

On 7/22/20 10:17 AM, blackout69 wrote: > Hi everybody, > > with > $sudo updatedb > $sudo locate,I don't find these path Mailman core in mailman/messages/ > Hyperkitty in hyperkitty/local/ > django-mailman3 in django-mailman3/local/ > postorius in postorius/local/from here > https://www.pratico.work/file.tar.xz you can download the following > files: my file /usr/share/mailman3-web/settings_local.py $sudo locate > it/LC_MESSAGES > mypath.txt I can't (re)generate the .mo files because > there are no path above. Thank You for help Max I'm having trouble deciphering what you are saying, however, the actual paths you are looking for are: For Mailman core: mailman/messages/it/LC_MESSAGES/mailman.po For HyperKitty: hyperkitty/locale/it/LC_MESSAGES/django.po For djangomailman3: django_mailman3/locale/it/LC_MESSAGES/django.po For Postorius: postorius/locale/it/LC_MESSAGES/django.po Note 'locale', not 'local' -- 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: Posterious membership listing for non-owner/moderators?

by Mark Sapiro

On 3/11/21 4:58 AM, Duane Raymond wrote: > Hi, > > I'm configuring my new mailman3 lists and one option I wish to use is a membership listing (which list members can opt-in/out of via their preferences). The only problem is, via the web interface (Posterious / Hyperkitty) I can't find that listing when logged in as an ordinary member. Am I missing something or is this not built in yet? > > I have my test list setting under List Identity -> Members List Visibility set to "Only mailinglist members", but all I can find in terms of members is the side-listing of posters to the list/thread. > > (as usual before asking the question I explored a lot and searched the archives/documentation). Maybe you should also check issues. This is <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

4 years, 9 months

[MM3-users] Re: Apple Mail encoding again

by Mark Sapiro

On 4/14/22 21:33, Stephen J. Turnbull wrote: > > Whether we *want* to do that depends on how much trouble that causes > for our main constituency (list and site admins), and whether we can > provide discoverable documentation of the problem. My take is that > this seems to be an extremely rare problem, and at least some MUAs are > able to read the message, so we should let it through. First, we are not silently dropping this message. We are rejecting it at LMTP time so the sender should be notified. Then the broader question is should we accept all messages with defects, almost all of which are spam, or only certain defects and which ones. I note that Apple has now released Mail 16 so maybe they've fixed this. My macs are still on Big Sur, so I can't test this. -- 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: Aborted connection message in log in every 5 minutes

by Mark Sapiro

On 1/31/24 04:00, andrea.janna.unipd(a)gmail.com wrote: > > Yes it's mailman gatenews that triggers mariadbd "[Warning] Aborted connection" log entries. > I don't use this feature so as a workaround I set a large gatenews_every interval in mailman.cfg. > > [nntp] > gatenews_every: 1000000m Or you can do as Danil does <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> and put ``` [runner.nntp] start: no ``` in mailman.cfg. However, it is unclear what in gatenews would do this. Assuming you have no lists for which gateway_to_mail is true, all gatenews will do is ``` def process_lists(glock): list_manager = getUtility(IListManager) for mlist in list_manager.mailing_lists: glock.refresh() listname = mlist.fqdn_listname if not mlist.gateway_to_mail: continue ``` The database operations involved in this are things Mailman core is doing all the time, presumably without issues. -- 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: Installing mailman 3

by Mark Sapiro

On 08/02/2017 07:55 AM, Rafael Mora wrote: > HyperKitty is looking for some files in /static/CACHE/... but it doesn't > find them: > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/b3547a2ab51b.css HTTP/1.1" > 404 107 > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/4c17bb8058aa.css HTTP/1.1" > 404 107 > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/2fa1cba00450.css HTTP/1.1" > 404 107 > [02/Aug/2017 14:53:38] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" 404 > 105 > [02/Aug/2017 14:53:39] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" 404 > 105 > > > Should I run any command to activate the CACHE dir? You need to ensure you have a working sass compiler. As I said at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>, See the third bullet under <http://docs.list.org/en/latest/prodsetup.html#dependencies>. Then you need to run commands like django-admin collectstatic --clear django-admin compress -- 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: Subscription notification sent from the site admins work-mail.

by Mark Sapiro

On 09/13/2018 05:01 AM, Henrik Rasmussen wrote: > One of my list administrators told me that all seven list administrators on a list received a "None <foo(a)example.com> has been successfully subscribed to [LIST NAME].", when someone subscribed to their list, however the sender of the mail (From:) was my own work mail address. I am not associated with the list other that I am site admin. This is expected behavior. In Mailman 2.1 notices like this were sent From: the site list (normally 'mailman'). In Mailman 3, there is no site list so the notices are from the site admin. If you'd rather not expose your work mail address in this way, set the site admin to something generic like mailman-admin(a)example.com and alias that to where you want the mail to go. -- 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: Cannot see the cron jobs for Mailman 3 Installed

by Mark Sapiro

On 1/23/20 4:49 AM, Shashikanth Komandoor wrote: > Hi, > > I have setup the Mailman 3 on my RHEL 7.5 box and found it was working > fine. But I found that I am not getting daily summary notifications for > which I learnt after browsing through different websites, there should be > an entry of *checkdb* in the cron job list. checkdbs is a Mailman 2.1 job The equivalent Mailman 3 job is `mailman notify` > But I did not find any such nor I don't find any cron job updated after > the installation of mailman 3. See <https://docs.mailman3.org/en/latest/config-core.html#configuring-cron-jobs> and <https://docs.mailman3.org/en/latest/config-web.html#scheduled-tasks-required> If you installed Mailman from a package and the cron's weren't installed, report this to the packager. -- 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: Subscription issue with ghost confirmations

by Mark Sapiro

On 10/31/20 7:28 AM, Brian Carpenter wrote: > > This has occurred again. A person sends an email to listname-subscribe@listdomain and the subscription policy of said list is set to moderate only. Instead of honoring this, a confirmation email is sent out. The issue is that when a request is received to subscribe an address to a list and that address is not verified and the pre_verified flag is not set in the request, the user is sent a confirmation request. This is not a request to confirm the subscription request, but rather a request to confirm the address, however they use the same template so they are indistinguishable. We probably should check the subscription policy and not send this request if the policy is moderate. We should also ignore a pending request if the policy is moderate per <https://gitlab.com/mailman/mailman/-/issues/789>. -- 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: Can't deliver mails in queue

by Mark Sapiro

On 5/19/21 2:45 PM, Nathanael Schneider wrote: > > They were in fact not identical, as I changed some stuff in hopes to get > it up and running again quickly. I now changed the completely new List > to be identical with the cleanly created one (as far as postorius shows > me) and it still works just fine. Do I understand correctly that you deleted the MM 2.1 imported list and created a new list in Postorius with just two members and it doesn't work. If that understanding is not correct, please outline all the steps you took to arrive at the current list that doesn't work. Also, please capture one of the .pck or .bak files from the out queue and send it to me off list. I will treat it confidentially, but there might be clues in 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: list footer web customization procedure

by Mark Sapiro

On 11/30/21 1:11 AM, Stephen J. Turnbull wrote: > > Does Django empty out the "spacetebasket" if it's all white space, or > does spurious whitespace in that box lead to an (apparently) empty > footer being added? Postorius used to remove leading and trailing whitespace from the template, but not since https://gitlab.com/mailman/postorius/-/issues/301 was fixed. > Anway, I recommend to the OP that they make sure there's no whitespace > in the Data box. A good recommendation. While a header or footer template with some whitespace might not be noticeable when added to a text/plain message, it will cause extra mime parts to be added to more complex messages. Also, if the goal in setting an empty footer is to avoid breaking a DKIM signature, even adding a bit of whitespace to a text/plain message is an issue. -- 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: Python 3.9 support

by Mark Sapiro

On 2/24/22 14:01, dancab(a)caltech.edu wrote: > > Only mail delivery was hung overnight. I had to restart the Gunicorn process followed by a Mailman core restart for mail to flow again. Because Mailman's "out" runner (/opt/mailmanve/lib/python3.9/site-packages/mailman/runners/outgoing.py from the above traceback) is what hit the exception and died. The master watcher should restart it, but see https://gitlab.com/mailman/mailman/-/issues/898 > Any insight into how we could monitor this in the future? For example which specific "runner" reported the error above? Something like ``` ps --ppid=`cat /opt/mailman/mm/var/master.pid|tr -d '\n'`|wc -l ``` will report the number of child processes of the master. You could test that against the expected number and do something. Note that `mailman restart` probably won't start a runner that died - you need to do `mailman stop;mailman start` to be sure. -- 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: Strange messages after upgrading Mailman3

by Mark Sapiro

On 12/4/22 20:09, Allan Hansen wrote: > Hi all, > > I have been getting a few of these messages after my Mailman 3 was upgraded: > > "The content of this message was lost. It was probably cross-posted to > multiple lists and previously handled on another list." > > The messages appear to come from list members and are distributed to the relevant lists, but with nothing of the original contents. > They have appeared on different lists with, apparently different senders (unless spoofed). > Other messages are going through the system unchanged. > > Anyone has any ideas? To what version did you upgrade? This is most likely https://gitlab.com/mailman/mailman/-/issues/955 which was fixed in Mailman core 3.3.6, but it could be https://gitlab.com/mailman/mailman/-/issues/1027 if the posts are to umbrella lists (lists with other lists as members). -- 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: Messages hold for moderation - compared to mailman2 it appears that there are fewer options: missing option(?)

by Mark Sapiro

On 3/7/24 9:35 AM, Wikinaut wrote: > Hello, I miss sadly the option of > > both: > > i) discarding the current message of a sender (not member of a closed list) ; and in the same action > ii) adding this person to the whitelist, i.e. accept further mails from this sender. When you go to the held messages view in the web UI and click the Subject: of the held message, there is a dropdown to set the sender's moderation action. you can select `default processing` to accept subject to additional checks or `accept` to accept unconditionally, subsequent posts from that sender before clicking the `discard` or other button. This works for non-members as well as for members. -- 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: [Bug] Someone not a member of list is treated as member - strange

by Mark Sapiro

On 8/23/25 11:51, Wikinaut wrote: > > Because it may be a breaking change in mailman3 - no one wants this I do not think is is a breaking change and I strongly disagree that no one wants it. If you want prior Mailman behavior, just don't link multiple addresses to one user. You can have a separate user for each address and then each address will be considered as belonging to a different person which is apparently what you want. Going back to your original issue, why do you have a problem? The fact that a post from one of your addresses was accepted even though it wasn't from the address that was subscribed in no way says that a post from an arbitrary nonmember would be accepted. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 2 weeks

[MM3-users] Re: Block members from sending cc's and bcc's

by Mark Sapiro

On 10/26/25 10:38, Cathryn McGuire wrote: > > Since setting to Default Processing, ALL members posts are being held for moderation. That's what happened last time. Obviously there's some setting somewhere that's telling the list to do that with that setting. We'll try to find it by doing testing like you said. Meanwhile, we're quite busy in our other endeavours and having to unblock every post (some days more than others, and not that many relatively speaking) is what we're doing. What is the reason given for the post being held? I don't know about affinity, but Postorius gives the reason in the list of held messages. Also the message itself has a X-Mailman-Rule-Hits: header that says which rule caused the message to be held -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 2 weeks

[MM3-users] Re: Installing mailman 3

by Mark Sapiro

On 07/21/2017 06:46 PM, Rafael Mora wrote: > Can I use it for mailing lists? like MailChimp? Yes, if all you want is a simple one way announcement type list, Mailman can do that quite well, with appropriate list configuration[1], but as I tried to say, MailChimp has many more features that are oriented towards that kind of mailing. [1]There are many horror stories of people setting up a mailing list and subscribing a bunch of people to it without ensuring that members can't post back to the list. Then with the first post, people start posting back to be removed and then others reply that they didn't send that mail and it snowballs and within an hower, the poor list server is so backlogged that the clueful replies take hours to be delivered. I personally have been added to more that one list to which this happened. -- 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: Uncaught runner exception with out runner process

by Mark Sapiro

On 5/18/19 7:35 AM, Alan So wrote: > The out runner process shutdown with the following error. Any clue? > > May 16 17:32:12 2019 (31602) Uncaught runner exception: (pymysql.err.InternalError) (1053, 'Server shutdown in progress') ... Mailman is running and the MySQL server is being shutdown. If this occurred during shutdown of the entire server, it is a race condition due to the out runner continuing to process a message while the MySQL server is being shut down. Upon restart, the out runner may recover the message from the .bak file in its queue. To avoid this, you could stop Mailman and wait for all Mailman processes to terminate before shutting down/rebooting the server. Note that if the message in process was shunted, the .bak file was probably removed during the shunting process, so you should unshunt it to finish delivery. -- 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: No styling for web apps?

by Mark Sapiro

On 11/26/20 8:44 PM, Morris Jones wrote: > I have most of a new mailman suite server built and working ... > > collectstatic gathered a good array of static files (uncompressed so far) > > nginx appears to be serving them successfully > > The Firefox developer tools show css and js files all being delivered > > But none of the postorius or hyperkitty pages exhibit any styling at > all, only bare HTML elements. > > The Firefox inspector will show the available styles being requested and > delivered (style.css, bootstrap, jquery, all the things). > > But if I use the inspector to look at the page, nothing has any CSS > properties. > > I know I'm missing something simple. Try running collectstatic and, if you use it, compress again. These have to be run following various kinds of changes. -- 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: Reduction of spam - FROM_LOCAL_HEX

by Mark Sapiro

On 10/31/23 01:55, Kyriakos Terzopoulos wrote: > > My guess is that the From address is very large, for example: > > mylist-confirm+3eafa5bd24e52738c900e2e3fd05e366b7ea7580(a)myproject.eu > > Is there any way to mitigate this problem? The string 'mylist-confirm+3eafa5bd24e52738c900e2e3fd05e366b7ea7580' is created according to the setting ``` verp_confirm_format: $address+$cookie ``` in the [mta] section of mailman.cfg. You could override that by setting ``` [mta] verp_confirm_format: $address ``` or maybe even something like `` [mta] verp_confirm_format: $address+no_reply ``` in mailman.cfg, but then you would also need to provide edited versions of the templates list:user:action:unsubscribe, list:user:action:invite and list:user:action:subscribe to remove the bits about 'simply replying to this message'. Note that your spamassassin report is only assigning a score of 0.3 to FROM_LOCAL_HEX which isn't very much. Plus, there's no evidence that Gmail's proprietory spam checks even care about this. -- 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: A little stuck with installation of MM3 - ModuleNotFoundError: No module named 'flufl.lock'

by Mark Sapiro

On 7/27/20 4:29 AM, Odhiambo Washington wrote: > On Mon, 27 Jul 2020 at 02:49, Mark Sapiro <mark(a)msapiro.net> wrote: >> >> Is there an empty /opt/mailman/mm/__init__.py file? >> > > No. There has to be one. Create it and then Django will be able to import your settings. See the first line after Create directories: ... and files: at <https://wiki.list.org/DOC/Mailman%203%20installation%20experience#line-69> > Yes. However, that also means the /opt/mailman should be owned by mailman3, > right? So I wasn't quite mistaken. It doesn't matter what user actually `owns` this directory and its subordinates as long as the Mailman user, mailman3 in your case, can read and write there. Of course, making everything owned by the Mailman user is the easiest way to ensure this. Note also that any commands in /opt/mailman/mm/bin need to be run as the Mailman user and not root. Running them as root can create things owned by root the can't be read by the Mailman user. > PS: There is the issue with qcluster, which doesn't seem to have been > documented in details from your "experience". > I see the configuration file and the init script, but not how to install > it, or whether the procedure already installed it. qcluster is part of Django. If you have this # # Asynchronous tasks # Q_CLUSTER = { 'timeout': 300, 'save_limit': 100, 'orm': 'default', } or similar uncommented in your Django settings, and also 'django_q' in your INSTALLED_APPS, it's there and all you need to do is run /opt/mailman/mm/bin/django-admin qcluster to run it, but it should be run as a service via init or ?? -- 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 on Debian 10

by Mark Sapiro

> On Wed, Jan 29, 2020, at 9:22 AM, Bala Mutyam wrote: > >> but the mailman service is not able to start it’s giving below error. Could you help me how to resolve it please? And also instructions for to install Mailman3 using Debian packages mailman3-full. I would like to use MySQl as backend and Exim4 as mail server. I couldn’t find new mailing list using the command line utility (/usr/sbin/newlist? Questions about the installation of Debian packages should be directed to Debian. >> Please see the attached Traceback. Which said in part: > urllib.error.HTTPError: HTTP Error 401: b'{\n "title": "401 Unauthorized",\n "description": "REST API authorization failed"\n}' The most likely cause of this is your Django settings in settings(_local).py for MAILMAN_REST_API_USER and MAILMAN_REST_API_PASS do not match the mailman.cfg [webservice] settings for admin_user and admin_pass (defaults restadmin and restpass). -- 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: Null sender?

by Mark Sapiro

On 6/28/20 10:18 AM, tom(a)gather.coop wrote: > Oh I get it! Hmm, I wonder why SendGrid is bouncing my mail then. I have the domain validated... Time to contact support... If SendGrid is your outgoing MTA, you probably don't have log info. You need to see the DSN for the reason. Unfortunately, MM 3 doesn't provide a way for you to see that directly (I just filed https://gitlab.com/mailman/mailman/-/issues/737 for this). This patch --- a/src/mailman/runners/bounce.py +++ b/src/mailman/runners/bounce.py @@ -90,7 +90,7 @@ class BounceRunner(Runner): else: log.info('Bounce message w/no discernable addresses: %s', msg.get('message-id', 'n/a')) - maybe_forward(mlist, msg) + maybe_forward(mlist, msg) # Dequeue this message. return False will forward non-verped received bounces to the list admins, not just unrecognized ones. The notice will say it was unrecognized, which it wasn't, but you'll be able to see it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

[MM3-users] Re: MAILMAN_ARCHIVER_KEY - 401 error

by Mark Sapiro

On 4/14/22 06:32, Torsten R. wrote: > Aah, one last question that came just up. > Due to the removal of the list and the recreation there are now some message files with the extension psv in the bad queue. > Is it safe to just delete them manually or how should they be treated? These are messages that were queued in some queue, but now can't be dequeued after a few retries. In your case, this is probably due to permissions because of incorrect ownership. Examine the files with `mailman qfile`. If you don't want to continue processing the message, just remove the file. If you do, rename it, changing the extension from .psv to .pck and change the ownership as needed - probably from root to mailman, and move the file to the original queue indicated in the metadata - the second object shown by `mailman qfile`. -- 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: Importing mailman 2 shows member's "Moderation Action" = "Default processing". But new members show = "None". Why

by Mark Sapiro

On 5/25/23 10:59 AM, mrl(a)psfc.mit.edu wrote: > I imported my mailing lists from mailman 2. If I view the Members, it say "Moderation Action" = "Default processing". > > But when I now subscribe myself or other people to the list, and view the new Members, it say "Moderation Action" = "None" for them. > > Should that be happening? The mailing list 's "Default action to take when a member posts to the list" setting is set to "Default processing". All of that is expected. import21 sets a members Moderation Action based on the Mailman 2.1 list settings and members moderation. New members get Moderation Action = None which means use the list default. -- 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: mailman-web Cleaning Up a Few Issues

by Mark Sapiro

On 11/5/25 10:22, dap1--- via Mailman-users wrote: > Mark: I hope to do that but I am getting killed with emails in the mean time. I'm guessing all these issues stem from the incorrect location of django. How do I fix that? See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… and https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… I find it very difficult to help you when you don't report the results of things I suggest > Stephen: I can't find anything. Here is /opt/mailman/venv/lib/python3.12/site-packages/hyperkitty/jobs: > > empty_threads.py __pycache__ thread_starting_email.py > __init__.py recent_threads_cache.py update_and_clean_index.py > new_lists_from_mailman.py sync_mailman.py update_index.py > orphan_emails.py thread_order_depth.py The problem isn't with your virtualenv install. It is with some left over crontab from a prior attempt to install Ubuntu packages. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 1 week

[MM3-users] Re: Getting rid of held messages from the command line

by Mark Sapiro

On 03/19/2018 02:22 PM, Aymeric Mansoux wrote: > > Ah, so if I understand you correctly, as long as I'm on 3.1.1, I could > run into this issue again, but then: Yes, this issue will recur with Mailman 3.1.1 and a MySQL database. > - Would patching 3.1.1 with 5477a201 be enough to prevent further issues > until the next stable is released? I think so. The only potential issue is if mailman/database/alembic/versions/4bd95c99b2e7_fix_template_password.py is not in 3.1.1. I think it is, so I think it's OK, but if not, you'd need to modify mailman/database/alembic/versions/3f31035ed0d7_further_increase_pendedkeyvalue_value_.py to point to the 3.1.1 head of the alembic versions. > - How can I clean the current pendedkeyvalue table? With phpMyAdmin or the mysql command. I think you can just delete those entries from 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

7 years, 8 months

[MM3-users] Re: HyperKitty Question

by Mark Sapiro

On 5/4/20 6:11 PM, Samir Faci wrote: > > I have nginx running with multiple website being serviced from the same > server. > > I updated the config where port 80 gets redirected to SSL. > > I tried setting mailman3-hyperkitty.conf to both: > > base_url: http://localhost/hyperkitty> base_url: https://lists.domain.com/hyperkitty/ > Either should be OK, possibly dependent of your nginx config. > But neither seem to be working. Does hyperkitty require traffic to be > going over port 80? No. https should work. Can you go to https://lists.domain.com/hyperkitty/ in a browser? Do you have api_key: set in mailman3-hyperkitty.conf and is it set to the same value modulo quotes as MAILMAN_ARCHIVER_KEY in your Django settings. Note the value needs to be quoted in MAILMAN_ARCHIVER_KEY = 'the_value' and not in api_key: the_value because the former is a Python string and the latter is a config value. -- 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: Footer from templates not working - DB issue?

by Mark Sapiro

On 9/25/22 05:26, mailman--- via Mailman-users wrote: > Dear All, > I have a similar issue. Also on Debian 11. Also installed as Debian PKG. It's version GNU Mailman 3.3.3 (Tom Sawyer) > I am using sqlite3. When I do the SQL-query I get an URI which is in multiple reasons wrong > http://localhost/mailman3/postorius/api/templates/list/....../list:member:r… The initial part of that URL is set from the Django setting `POSTORIUS_TEMPLATE_BASE_URL`. If that is set to `http://localhost/mailman3/`, it should probably be just `http://localhost/`. > OK - the hostname could be changed but the path is not existing at all. > There is no file "list:member:regular:footer" on the complete filesystem. It's not a file. It refers to an entry in the postorius_emailtemplate table in the database which is retrieved via the Postorius API. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

[MM3-users] Re: Postorius claims 2 messages held when there are none - out of sync

by Mark Sapiro

On 6/26/23 12:01 AM, Ken Alker wrote: > When I view a list via Postorius the "Held Messages" menu item has an inverse-red-"2" next to it, as if there are two held messages. There are, in fact, no messages in "/opt/mailman/mm/var/queue/*" (assuming the held messages should be in "pipeline" subdirectory). When I click on "Held Messages" I get "Something went wrong" followed by "HTTP Error 500: {"title": "500 Internal Server Error"}". How do I fix this? The held messages are not in any queue. They are stored in Mailman's var/messages/ hierarchy. They can be examined with `mailman qfile` Also, there is a long thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… and maybe others that might be relevant. -- 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: Topics - Tags

by Mark Sapiro

On 3/21/24 21:10, Mark wrote: > Hi, > > I'm reading the docs on "Message tagging" > (https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/handlers/d…) as saying shell access is needed to: (a) enable topics, and (b) write the keywords. > > In Mailman 2 there is an Admin web UI for "Topics". Is there such a web > UI that can be enabled in Mailman 3 so that the list owners can create > topics (tags) in their lists? At this point, topics are not exposed in REST. Managing them via Postorius first requires updating the REST API to read and set the topic attributes and then updating Postorius to display/set them. Further, there is currently no implementation for list member topics of interest either in Mailman core or the REST API. I.e., there is no way for a list member to indicate topics of interest. -- 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: Moving existing lists to a new domain

by Mark Sapiro

On 11/21/24 07:43, Jeremy Stanley wrote: > > Preparing to test this, I poked around the schema a bit and noticed > that the domain names are also embedded as strings in the following > fields: > > django_mailman3_maildomain.mail_domain > django_site.domain > django_site.name These are all Django things. You can modify those values in the db. Note that django_site.name is just a name and doesn't need to be the exact domain name. > domain.mail_host This is Mailman core's domain table. Again, you can modify the value in the db. > Can anyone think of any additional tables/columns which would need > updating for this? I'll see if scanning a dump of the full DB > content turns up anything I might be missing too. Thanks again! I don't think there's anything else. -- 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: changing the main template for subscriptions and more

by Mark Sapiro

On 6/22/21 2:41 AM, Andreas Barth wrote: > > I'm using this patch (however, german-only) > > > Andi > > > diff --git a/src/mailman/templates/de/list:admin:action:post.txt b/src/mailman/templates/de/list:admin:action:post.txt ... > diff --git a/src/mailman/templates/de/list:admin:action:subscribe.txt b/src/mailman/templates/de/list:admin:action:subscribe.txt ... > diff --git a/src/mailman/templates/de/list:admin:action:unsubscribe.txt b/src/mailman/templates/de/list:admin:action:unsubscribe.txt ... > diff --git a/src/mailman/templates/de/list:user:notice:welcome.txt b/src/mailman/templates/de/list:user:notice:welcome.txt ... It isn't necessary to patch the source in this way. If you put the modified templates in Mailman's var/templates/site/de/ directory, ensuring that the Mailman user can read them, they will be used and you won't have to patch the source every time you upgrade. -- 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: New messages not being archived

by Mark Sapiro

On 7/15/21 2:11 PM, Sarah H wrote: > I get a 301 when I go to http and the full html page not found text that is above if I go to https. if I curl loopback on html I get the same html response, https I get: > > curl: (35) error:1408F10B:SSL routines:ssl3_get_record:wrong version number A 301 from http will be an issue always. I'm not sure where the `wrong version number` comes from. This could be the issue. If I do for example, curl -X POST https://lists.mailman3.org/archives/api/mailman/archive I get the response <html><title>Auth required</title><body> <h1>Authorization Required</h1><p>Please check whether the MAILMAN_ARCHIVER_KEY is provided by you and it is correct. </p></body></html> This is the expected response. You need to figure out what base_url will give you a similar response. -- 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: hyperkitty url not found

by Mark Sapiro

On 3/9/22 07:13, Eggert Ehmke wrote: > I installed mailman3 in a virtualenv following this guide: > > https://docs.mailman3.org/en/latest/install/virtualenv.html[1] > The mailinglists work very good. However, I did not manage to set up hyperkitty archiving. > Archiving is enabled in mailman.cfg. I can call the Archive site from my configuration page, > but it is empty. > > In my /opt/mailman/mm/var/logs/mailman.log > file I find error messages like: > > HyperKitty failure on http://localhost/mailman/hyperkitty/api/mailman/archive: > The requested URL was not found on this server. Your setting in mailman-hyperkitty.cfg for base_url is base_url: http://localhost/mailman/hyperkitty/ It needs to be the base URL for accessing hyperkitty, possibly base_url: http://localhost/mailman3/hyperkitty/ or whatever you use to access hyperkitty from a web browser. Whatever it is, `<base_url>/api` should return a page of API documentation. -- 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: hyperkitty_import performance boosting potential

by Mark Sapiro

On 7/8/24 11:59 AM, dlb-ml--- via Mailman-users wrote: > > I can throw all of the resources I need at it in order to make it faster, but I'm not sure if the import application is single-threaded only. Is there a way to enable a multi-threaded option? Can I safely run multiple commands at the same time using something like /usr/bin/parallel? If you're concerned about down time while doing the switch over, you could just do the hyperkitty_import processes while the MM 2.1 lists are still up, and then just import only the latest messages while the MM 2.1 lists are down. That said, in order to provide parallelism, you could split the mbox into pieces and run multiple hyperkitty_import processes concurrently. If you do this, be sure to specify --since on the commands to be sure you get all the older 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, 5 months

[MM3-users] Re: Funny responds to subscriptions emails

by Mark Sapiro

On 09/02/2017 01:36 PM, Claus-Justus Heine via Mailman-users wrote: > > But I also get a second rather confusing email: > >> The results of your email command are provided below. >> >> - Original message details: >> From: Claus-Justus Heine <Claus-Justus.Heine(a)IANS.Uni-Stuttgart.DE> >> Subject: Test >> Date: Sat, 2 Sep 2017 22:24:08 +0200 >> Message-ID: <44151460-05a8-4c35-e0d4-646efe3cf234(a)IANS.Uni-Stuttgart.DE> >> >> - Results: >> Confirmation email sent to Claus-Justus Heine <Claus-Justus.Heine(a)IANS.Uni-Stuttgart.DE> >> No such command: Test >> No such command: --=20 >> No such command: Claus-Justus >> No such command: f=C3=BCr >> No such command: Numerische >> No such command: Stuttgart >> No such command: +49 >> No such command: +49 >> >> - Done. See <https://gitlab.com/mailman/mailman/issues/212>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 3 months

[MM3-users] Re: Postorius endless loading on Sign in / Register then "Internal Server Error"

by Mark Sapiro

On 6/10/20 10:55 AM, Jacob Bargery wrote: > So I couldn't find a schema.cfg file but but when checking mailman-web.py and mailman.cfg they both have the same password. Albeit not the restpass but a much longer random password. I was able to connect using both telnet options. > > For reference the instructions I followed for installing this (up to the SSL cert) were here: https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan… See <https://wiki.list.org/x/12812344 The next step is to try this in `django-admin shell` from mailmanclient.restbase.connection import Connection from django.conf import settings url = settings.MAILMAN_REST_API_URL user = settings.MAILMAN_REST_API_USER pwd = settings.MAILMAN_REST_API_PASS conn = Connection(url, user, pwd) conn.call('3.1/lists') That should return `<Response [200]>` and a bunch of json. What happens 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

5 years, 6 months

[MM3-users] Re: mailman3 does not send to the members of the lists

by Mark Sapiro

On 7/12/20 6:30 PM, maszap(a)tin.it wrote: > Hi, > > you say I have to delete these lines? > > virtual_alias_maps = mysql:/etc/postfix/mysql_virtual_alias_emails.cf, mysql:/etc/postfix/mysql_virtual_alias_maps.cf > virtual_gid_maps = static:5000 > virtual_mailbox_base = /var/vmail > virtual_mailbox_domains = mysql:/etc/postfix/mysql_virtual_mailbox_domains.cf > virtual_mailbox_maps = mysql:/etc/postfix/mysql_virtual_mailbox_maps.cf > virtual_transport = lmtp:unix:private/dovecot-lmtp > virtual_uid_maps = static:5000 I say you have to understand what you want Postfix to do and configure it appropriately. I am not a primary resource for Postfix support in general. I will help you to the extent that I can, but you might be better off posting to a Postfix list. I would need much more information in order to know how your Postfix should be configured, and in any case, I don't have time to do any more today. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

[MM3-users] Re: Problem with redirection when entering alias without a / at the end

by Mark Sapiro

On 3/19/21 4:53 PM, Jens Günther wrote: > Sure. It's not much, when I get it right, file was created by > debian-package automatically (I only post the lines without #): > > ->/etc/mailman3/uwsgi.ini > > [uwsgi] > uwsgi-socket = /run/mailman3-web/uwsgi.sock > enable-threads = true > chdir = /usr/share/mailman3-web > wsgi-file = wsgi.py > master = true > process = 2 > threads = 2 > uid = www-data > gid = www-data > plugins = python3 > attach-daemon = python3 manage.py qcluster > logto = /var/log/mailman3/web/mailman-web.log > > > Am 20.03.21 um 00:28 schrieb Abhilash Raj: >> >> Can you also share your uwsgi configuration? How about the actual uwsgi config. Maybe something like /etc/uwsgi.ini See https://uwsgi-docs.readthedocs.io/en/latest/Configuration.html -- 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: mailman-web compress - Invalid template socialaccount/login_cancelled.html

by Mark Sapiro

On 1/24/24 02:38, amg hsn wrote: working packages with exact version. > for me each time i build venv i have different warning or erro. I understand your frustration and I'm sorry. The problem is that the current release of django-mailman3, 1.3.11, just requires django-allauth>=0.56, so a new install will get the latest django-allauth==0.60.1, but django-mailman3==1.3.11 is not compatible with django_allauth>=0.59. This will be fixed in the next release, but in the mean time, you can apply https://gitlab.com/mailman/django-mailman3/-/merge_requests/237/diffs and https://gitlab.com/mailman/django-mailman3/-/merge_requests/243/diffs to update django-mailman3 for compatibility with the latest django-allauth. This can be an issue when any of our third party dependencies is upgraded in an incompatible way. Short of pinning all the dependencies to a specific version, there's not much we can do about it. -- 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: Welcome message template errors

by Mark Sapiro

On 4/23/24 18:12, Mark wrote: > > >>>> import requests >>>> r = >>>> requests.get('https://MYDOMAIN.COM/mailman3/api/templates/list/MYTESTLIST.MYDOMAIN.COM/li…', timeout=5) >>>> r.text > 'Another test Welcome message for new members.' >>>> Did you delete and recreate the template after changing POSTORIUS_TEMPLATE_BASE_URL? If not, the template table still has the old URI. > > ... so all well there. And mailman is running mailman core ... > > # cd /opt/mailman/venv/bin/ > # ls -la > ... > -rwxr-xr-x 1 mailman mailman 230 Jan 26 04:00 gunicorn > -rwxr-xr-x 1 mailman mailman 231 Jan 26 04:00 mailman > -rwxr-xr-x 1 mailman mailman 230 Mar 25 22:18 mailman-web > ... That only shows the user and group that owns the files, not whose running them. What does `ps -fwwu mailman|grep runner` show? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

[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

1 year, 3 months

[MM3-users] Re: clean_users.py

by Mark Sapiro

On 12/8/25 07:37, Christian Stalberg via Mailman-users wrote: > I just ran the clean_users.py script and it removed user email addresses > from Django. I can still find these addresses however using Postorius which > show > > Subscriptions > User has no subscriptions. > Ownerships > User has no ownerships. > > Why are they still listed then? How can I purge my system of all instances > of unsubscribed registrants please? Postorius is showing you Mailman users. If you ran the clean_users.py script with default settings, it only removed Django users. To delete Mailman users with no subscriptions or ownerships, you have to set DELETE_MAILMAN_USER = True As it says, # Set True to delete Mailman users that have no memberships with any role. # Set False to not delete Mailman users. You can change the setting for DELETE_MAILMAN_USER to True and run it again and it will delete those Mailman users. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 days, 5 hours

[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, 10 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

4 years, 1 month

[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, 9 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, 8 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, 5 months

[MM3-users] Re: Removing the footer from mailing list messages

by Mark Sapiro

On 12/7/25 14:00, MegaBrutal via Mailman-users wrote: > > What I already tried: define a custom template for > list:member:regular:footer. The result was that the mailing list stopped > operating altogether, no messages passed through until I deleted this > template. After I deleted it, all delayed e-mails were forwarded at once. How did you create the footer? If you created a file at Mailman's var/templates/whatever/list:member:regular:footer.txt, it probably was not readable by the Mailman user. If you created it via Postorius there is probably and issue with your setting for POSTORIUS_TEMPLATE_BASE_URL. > What would be the right way to remove the footer? For all lists sudo -u mailman cp /dev/null var/templates/site/en/list:member:regular:footer.txt For a single list sudo -u mailman cp /dev/null var/templates/lists/LIST-ID/en/list:member:regular:footer.txt -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 days, 22 hours

[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

4 months, 1 week

[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

6 years, 1 month

[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, 9 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

3 years, 2 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, 6 months

[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

7 months, 1 week

[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

6 years, 1 month

[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

6 years

[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, 11 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, 9 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

4 years, 3 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, 7 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, 5 months

[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, 7 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, 5 months

[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, 4 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, 9 months

[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, 11 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, 10 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, 10 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

3 years, 4 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, 8 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

1 year, 1 month

[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

4 years, 2 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, 9 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

3 years, 2 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

2 years, 2 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

7 months, 2 weeks

[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, 6 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, 10 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, 7 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, 11 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, 5 months

[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, 9 months

[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, 8 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, 11 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, 8 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, 5 months

[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

1 year

[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

8 months, 1 week

[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

4 months, 3 weeks

[MM3-users] Re: Problems with SPOOFED_UNAUTH

by Mark Sapiro

On 9/9/25 08:42, M.Ede via Mailman-users wrote: > Hello everyone, > > I use mailman together with mailcow and have configured my mailing list as follows: > - Anonymous list: Yes > - DMARC mitigation action: Replace From: with list address > - DMARC Mitigate unconditionally: Yes > > My problem is that my emails are not being accepted by mailcow (rspamd) with the error > SPOOFED_UNAUTH (50.00) > ... > What am I still doing wrong? Can you help me, which setting is still missing? > What informations are you still missing? I doubt that this has anything to do with the ARC-*, Authentication-Results or DKIM-Signature headers you quote. There are some threads on SPOOFED_UNAUTH in the mailcow community forum, e.g. https://community.mailcow.email/d/403-spoofed-unauth-rspamd and https://community.mailcow.email/d/637-problems-with-emails-keep-getting-rej… Also see https://www.reddit.com/r/mailcow/comments/12lhw8e/whitelist_ip/ These came up in a google search for SPOOFED_UNAUTH. -- 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: 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

1 year, 1 month

[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, 8 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, 10 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, 8 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, 5 months

[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, 6 months

[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

6 years, 1 month

[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, 11 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, 10 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, 8 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

8 years, 4 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, 7 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, 6 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

5 years, 2 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

5 years

[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, 10 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

1 year, 3 months

[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

5 years, 3 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, 8 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, 8 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, 6 months

Search results for query "sapiro"