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

[MM3-users] Re: Unable to update templates

by Mark Sapiro

On 5/28/25 01:14, Mark wrote: > > Then I created a template using Postorius and updated the uri in > mailman.templates to: > > file:///opt/mailman/mm/var/templates/lists/testlist.example.com/en/list:use… - and that works. Which says get the template from the file system at that location and don't ask for it from Postorius at all. This would be the default action if there were no entry for this template in the mailman.template table at all. I.e. you now have a template in Postorius, but it is not used. > It's looking promising. Now I just need to modify my script that > periodically copies the data from the > "mailmanweb.postorius_emailtemplate" table to a file and updates the uri. > > Why it won't handle the templates in the database I don't know. But at > least I can get a work-around solution in place now. If you want to continue to use the template at /opt/mailman/mm/var/templates/lists/testlist.example.com/en/list:user:notice:welcome.txt just delete the template from Postorius and update that file directly. If Postorius template updates don't work because of web server caching or whatever, just don't use them and use templates in the /opt/mailman/mm/var/templates/ hierarchy instead. You can create sitewide templates at /opt/mailman/mm/var/templates/site/en/*, domain specific templates in /opt/mailman/mm/var/templates/domains/en/* and list specific templates in /opt/mailman/mm/var/templates/lists/<list-id>/en/ without any entries in the mailman.template table. Note that sitewide templates can be the most useful and can't be created in Postorius 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

[MM3-users] Re: Auth question

by Mark Sapiro

On 03/30/2017 02:27 PM, David Krantz wrote: > > I tried to upgrade today. The result is a broken install which fails > when trying to upgrade the database. > > > $> ./bin/mailman-post-update > [...] > File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/db/backends/base/base.py", > line 236, in _commit > return self.connection.commit() > File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/db/utils.py", > line 94, in __exit__ > six.reraise(dj_exc_type, dj_exc_value, traceback) > File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/db/backends/base/base.py", > line 236, in _commit > return self.connection.commit() > django.db.utils.IntegrityError: update or delete on table "auth_user" > violates foreign key constraint > "social_auth_usersocial_user_id_193b2d80880502b2_fk_auth_user_id" on > table "social_auth_usersocialauth" > DETAIL: Key (id)=(3) is still referenced from table > "social_auth_usersocialauth". This is <https://gitlab.com/mailman/hyperkitty/issues/106>. > I have tried to drop and recreate the databases but I get the above > result anyway. I'm not sure what you mean by drop and recreate the databases. You should just drop the `social_auth*` tables, or if there's nothing in the database you want, just starting with an empty database should work. > The description in > https://wiki.list.org/DOC/Mailman%203%20installation%20experience is > very hazy. The process of symlinking in libraries is fiddly to say the > least. I get mailman to start but not any web interface. I have not > tested mailman so if it works rather than just start I do not know. Sorry about that. The symlinking was due to my starting with bundler and then "undoing that" without trying to find everywhere the old paths might be referenced. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 2 months

[MM3-users] Re: Invalid confirm text

by Mark Sapiro

On 8/14/20 3:28 AM, w.schoener(a)alp.dillingen.de wrote: > > Now, when I try to subscribe to the list, I get my first message in german language, with the confirm request: > return the message unchange. > > When I return the message, I get an answer: > Invalid confirm text. With current releases of Mailman, the confirm request you receive should be: From: <listname>-confirm+<hex-token>@<list.domain> Subject: confirm <hex-token> with actual values for <listname>, <hex-token> and <list.domain>. This will change in Mailman 3.3.2, see <https://gitlab.com/mailman/mailman/-/merge_requests/678> > My request is pending. And there is no way to solve this pending request, in the webinterface, no subscription request is shown, no member is shown and no no-member is shown. Your reply should go to <listname>-confirm+<hex-token>@<list.domain>. Some MTA/MDA in the delivery chain may drop the ++<hex-token> suffix. If this is the issue, you can send a message with the one line confirm <hex-token> as either the Subject or body of the message to <listname>-request@<list.domain>. That should work. Note in the web UI (Postorius), at least in recent versions, even though it shows "Subscription requests 0" that should be a pull-down with the two choices Pending Approval and Pending Confirmation and selecting Pending Confirmation should show yours. The count badge only counts Pending Approval. > Have you any hint, what is going wrong. What do I have to respect to create a message, where the confirmation is working. See the current English confirmation template at <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/templates/en/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, 10 months

[MM3-users] Re: Bad Signature with Gmail

by Mark Sapiro

On 9/19/20 10:11 AM, Massimo Zappalà wrote: > Hi everyone, > if I write a my lists from other email address I get the correct message: > opendkim[23516]: 8EEE440FFD: DKIM-Signature field added (s=mailselector, d=catania.linux.it). > > While if I write to a my lists from email address Gmail, on opendkim I get the following messages: > opendkim[23516]: BA95241952: no signing table match for 'maszap69(a)gmail.com' > opendkim[23516]: BA95241952: s=20161025 d=gmail.com SSL error:04091068:rsa routines:int_rsa_verify:bad signature > opendkim[23516]: BA95241952: bad signature data OpenDKIM on your server is not signing the message because it is not configured to sign messages From: 'maszap69(a)gmail.com' What's in your opendkim SigningTable and what's in your opendkim.conf for SenderHeaders. The recommend config is SenderHeaders List-Post,Sender,From to use the domain of the list for signing list mail and then to include that domain in SigningTable. > I also receive an email at superuser: > > [Django] ERROR (EXTERNAL IP): Internal Server Error: /hyperkitty/api/mailman/archive > > Internal Server Error: /hyperkitty/api/mailman/archive > OperationalError at /hyperkitty/api/mailman/archive > (1366, "Incorrect string value: '\\xF0\\x9F\\x98\\xB1\\xF0\\x9F...' for column `mailman3web`.`hyperkitty_email`.`content` at row 1") > ... This appears to be unrelated. HyperKitty is trying to store the message in the database hyperkitty_email table and gets this error. To say more, I'd need to see the complete raw message which you may be able to find in Mailman's var/archives/prototype/<list_address/new/ and if available, a full traceback and possibly more from the email you receive from Django or from the log file configured in your Django settings. -- 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: Confirmation emails aren't sent to users.

by Mark Sapiro

On 2/12/26 13:58, Ibiam Chihurumnaya via Mailman-users wrote: > > I created an admin user and when I try to sign in with that user, I get a page that tells me that a confirmation > email has been sent and I should confirm the user. > > I created another user with a different email, and I got the same thing, didn't receive the confirmation emails in my inbox. Do you mean you are creating these users by adding them as list owner or moderator or are you creating them via the https://example.com/accounts/signup/ page. > I looked at mailman smtp logs, and didn't see any event related to the confirmation emails. > The uwsgi logs show the events though. If this is the latter, it has nothing to do with Mailman core or the smtp log. It is via django-allauth and the mail comes from Django. > The only place I see something about it is in uwsgi; > 3050415 [pid: 1985548|app: 0|req: 518823/979759] 127.0.0.1 () {54 vars in 1197 bytes} [Thu Feb 12 21:52:32 2026] GET /accounts/confirm-email/ => generated 1556 bytes in 48 msecs (HTTP/1.0 200) 9 headers in 359 bytes (1 switches on core 0) OK, this is Django. The default EMAIL_BACKEND from mailman_web/settings/base.py is django.core.mail.backends.smtp.EmailBackend and unless you've changed that or added overrides various other defaults are EMAIL_HOST = "localhost" EMAIL_PORT = 25 EMAIL_HOST_USER = "" EMAIL_HOST_PASSWORD = "" EMAIL_USE_TLS = False EMAIL_USE_SSL = False EMAIL_SSL_CERTFILE = None EMAIL_SSL_KEYFILE = None Are those appropriate? Do you have an outgoing MTA listening on `localhost:25`? What's in it's logs? -- 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: Mailman 3 Keeps Forgettings Imported Lists

by Mark Sapiro

On 07/31/2018 01:52 PM, Ryan McClung wrote: > That explains a lot. Is there any documentation you can provide to show me > where I can set a static config/db? See <http://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.html> That may not specifically address your question, but it will explain the issue in detail. An example of what I do on several servers I support is this. First, I install Mailman in a virtualenv which is /opt/mailman/mm/venv. Then the commands I run are all put in /opt/mailman/mm/bin. the actual installed 'mailman' command is /opt/mailman/mm/venv/bin/mailman but I never run that directly or as 'mailman' with the venv active. My var/ directory is /opt/mailman/mm/var. My mailman.cfg is actually outside of the var/ directory in /opt/mailman/mm/mailman.cfg. (In some cases for historical reasons it's in /opt/mailman/mm/deployment/mailman.cfg, but ignore that.) In /opt/mailman/mm/bin/mailman, I have #!/bin/bash unset PYTHONSTARTUP exec /opt/mailman/mm/venv/bin/mailman \ -C "/opt/mailman/mm/mailman.cfg" \ $@ The details such as installing in a venv or where things are are not the important things. The important thing is the only 'mailman' command I ever run invokes Mailman with a -C option that points to the only config I want to use and that in turn has a var_dir setting pointing to, in my case, /opt/mailman/mm/var. Also, the 'unset PYTHONSTARTUP' is there to address an issue with 'mailman shell' that would double the size of the shell history file each time it was run. I'm not certain that's still needed. -- 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: How to change the language in mailman3

by Mark Sapiro

On 7/20/20 5:19 PM, Massimo Zappalà wrote: > Hi everyone, > Debian buster run on my server. > I installed the apt install mailman3-full package and configured it. Everything works fine. > I'm trying to change the language (mailman3, postorius and hyperkitty) from English to Italian, but it's not clear what I'm missing. > These are the files that I modified to try to set the Italian language: > > /etc/mailman3/mailman.cfg > default_language: it > --------------------------------------------------------------- > /etc/mailman3/mailman-web.py > LANGUAGE_CODE = 'it-IT' > TIME_ZONE = 'Europe/Rome' > USE_I18N = True > USE_L10N = True > USE_TZ = True > --------------------------------------------------------------- Assuming this is the Debian packages Django settings file for mailman, it probably contains something like try: from settings_local import * except ImportError: pass at the end. You should put your local changes in the /etc/mailman3/settings_local.py file. > /usr/lib/python3/dist-packages/django/conf/global_settings.py > TIME_ZONE = 'Europe/Rome' > USE_TZ = True > LANGUAGE_CODE = 'it-IT' > --------------------------------------------------------------- This probably isn't needed as it should be overridden by the above. > With this command, I set the Italian language to the list. It takes the setting, but it doesn't work > sudo mailman shell -l test(a)pratico.work >>>> m.preferred_language='it' >>>> commit() >>>> CTRL-D > > Can anyone tell me what I'm missing? The source distribution for Mailman core does not contain the compiled message catalogs, and Debian's package probably doesn't either. Find the mailman/messages/it/LC_MESSAGES directory, cd to that directory and give the command msgfmt mailman.po -o mailman.mo -- 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: Cannot Create New List

by Mark Sapiro

On 11/8/25 10:35, dap1--- via Mailman-users wrote: > ~$ 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 What is /opt/mailman/var/etc/mailman.cfg? Is it a symlink to /etc/mailman3/mailman.cfg or is it a separate file. In any case `mailman info` should report /etc/mailman3/mailman.cfg as the config file. Are you running these commands as the mailman user with the venv active. That MUST always be the way you run them. > db url: sqlite:////opt/mailman/var/data/mailman.db Is this the sqlite db you are looking at? > I haven't replied to your link because the list apparently hasn't been created properly yet. If you are referring to https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… the questions there were to help diagnose why the list was apparently not created, at least where you think it should be. They ask for more detail about how you ran the commands that didn't do what you expect. What they ask doesn't in any way require the list to be created where you think it should me. What is going on here is if I had root access to your server, I could probably figure this out in minutes, but I don't have that access and I would refuse it if offered for multiple reasons, so I need to ask you to do what I would do and report the results so I can move on to the next thing. So if you want to solve this, please do and report the things I ask. -- 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: [MM3-users]Exim, Mailman3 and missing Message-ID:

by Mark Sapiro

On 7/26/19 11:05 AM, Stephen J. Turnbull wrote: > The problem is that Mailman's LMTP server rejects malformed mail. I > seem to recall that in Mailman 2, Mailman itself would add a > Message-ID field if one was not present. I don't know how easy it > would be to provide this feature, since we would have to patch the > LMTP server code so the message could make it to Mailman proper > (Mailman 3 imports the LMTP server from the stdlib). It's a simple patch to the lmtp runner (Mailman's LMTP server). There's a closed issue on this at <https://gitlab.com/mailman/mailman/issues/490> - closed because I convinced the submitter it wasn't the right thing to do. > > My solution for now (apart from telling people not to use old > > broken Outlook!) is to modify the exim mailman3_transport so that > > any message with a missing Message-ID: will have one generated by > > exim before it's passed to LMTP. This reproduces the same behaviour > > exim uses for locally submitted messages. > > I'm not sure it's a good idea to do this (and certainly not by > default). The only times I've seen messages without a Message-ID are > spam messages. I suppose we can add this to the documentation. I added Robert's solution at <https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html#troubles…> The requirement for a Message-ID: is documented, albeit not very prominently, at <https://mailman.readthedocs.io/en/latest/build/lib/mailman/runners/docs/lmt…>. -- 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: Hyperkitty download mbox

by Mark Sapiro

On 4/25/21 2:20 PM, Andrew Hodgson wrote: > Hi, > > Hyperkitty 1.3.4. > > I am trying to download a complete list mbox by going to all threads view and using the download option. I have tried a couple of tools (Gunzip and Winrar) and both are giving me an unexpected end of file when trying to decompress the gz file. > > Here is the list URL I am using: https://lists.hodgsonfamily.org/hyperkitty/list/plextalk@lists.hodgsonfamil… Depending in the web server configuration, timeouts can occur when downloading large archive mboxes. instead of downloading the entire mbox with <https://lists.hodgsonfamily.org/hyperkitty/list/plextalk@lists.hodgsonfamil…>, do it in pieces by adjusting start and end. e.g. <https://lists.hodgsonfamily.org/hyperkitty/list/plextalk@lists.hodgsonfamil…> <https://lists.hodgsonfamily.org/hyperkitty/list/plextalk@lists.hodgsonfamil…> <https://lists.hodgsonfamily.org/hyperkitty/list/plextalk@lists.hodgsonfamil…> Although, I don't think timing out is the issue, and I'm not sure what is, but I think it has something to do with messages in the archive. If I try to get the 3 pieces as above, the first piece with start=2008-02-19&end=2012-12-31 works but the others don't and even the smaller <https://lists.hodgsonfamily.org/hyperkitty/list/plextalk@lists.hodgsonfamil…> fails the same way. If I try to get 2013 month by month, all work except December which gives me an internal server error. What's the traceback from that error. -- 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

Search results for query "sapiro"