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

[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, 1 month

[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

4 years, 11 months

[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, 1 month

[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, 1 month

[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, 1 month

[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

4 years, 4 months

[MM3-users] Re: MM3 shunting mails

by Mark Sapiro

On 03/17/2017 03:59 AM, Anders Nilsson wrote: > > I do have problems with some lists occasionally going into some kind of > shunt mode, where alla mails sent to them gets shunted. In the Mailman > log I get entries for each shunted email: > > Mar 17 11:54:11 2017 (6217) Uncaught runner exception: Multiple rows > were found for one_or_none() ... > File "/usr/lib/python3.4/site-packages/mailman/handlers/rfc_2369.py", > line 70, in process > archiver_set = IListArchiverSet(mlist) mailman/handlers/rfc_2369.py is adding the List-* headers. Here it is looking up all the archivers that are enabled for this list. ... > File "/usr/lib/python3.4/site-packages/mailman/model/mailinglist.py", > line 607, in __init__ > ListArchiver.name == archiver_name).one_or_none() and here we are in code that is trying to see if there are any system enabled archivers that are not already associated with this mailing list and if so, add them to the archivers enabled for this list. The above is the last line of exists = store.query(ListArchiver).filter( ListArchiver.mailing_list == mailing_list, ListArchiver.name == archiver_name).one_or_none() which is querying the archivers enabled for this list for the name of a system enabled archiver and expects to find at most one entry > File "/usr/lib64/python3.4/site-packages/sqlalchemy/orm/query.py", > line 2733, in one_or_none > "Multiple rows were found for one_or_none()") but finds more than one. > sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for > one_or_none() > Mar 17 11:54:11 2017 (6217) SHUNTING: > 1489748051.1949184+7a59df19c81493cb419306d620376efc0e381819 So the cause is there appear to be multiple database entries for this list and some archiver name, but I don't know how that can happen. I have not seen this error. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 5 months

[MM3-users] Re: Change digest frequency and default threshold

by Mark Sapiro

On 10/04/2018 12:19 AM, Henrik Rasmussen wrote: > > Currently I am running Mailman version 3.2.0a1 which doesn't seem to have a --periodic option. 3.2.0a1 was never an 'official' release. It could be any HEAD version between June 4, 2017 and Jul 10, 2018. The --periodic option was added April 28, 2018. > When running "docker exec mailman-core mailman digests --send --verbose -l listname(a)lists.example.com", output is "listname.lists.example.com sent volume 11, number 4" and this increases each time, but even I do approve held mails, none are sent (according to the smtp.log and docker logs posrfix). Are there accumulated messages for the digest when you run the command?. I.e., is there a var/lists/listname.lists.example.com/digest.mmdf file with messages in it? Are there list members receiving digests? If so, there should be something in Mailman's smtp.log. > As I understand, using --sent should send a digest immediately (except when used with --dry-run). Correct,if there is one to send. > As the default Digest size threshold was 30KB, making very small digests being sent, I increased this (for test) to 5000 KB (or is it Kilo bits, as the text says "How big in Kb should a digest be before it gets sent out?"? It is Kilobytes. > Could Digest size threshold have any impact on why no digests are sent even I run "docker exec mailman-core mailman digests --send --verbose -l listname(a)lists.example.com" or is this an issue in the version I am using? The digest size threshold has no effect on whether or not a digest is sent by 'mailman digests'. -- 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: Add domain to Mailman, can't create list with that new domain

by Mark Sapiro

On 10/17/24 13:41, Andy Matthews wrote: > > and then rebuilt kubernetes, I found that when I hit the API to get all lists, the list mailman(a)foobar.com existed, and was the default. I could create lists against foobar.com but could no longer create them against mydomain.com. > > So it looks like when you're initially configuring mailman you have to create your first mailing list, and whatever domain you use becomes your "primary domain". I don't know where this is documented, but could someone confirm this behavior for me so that I know that I'm on the right path? And previously you wrote: > 1. Shell into the mailman server > 2. Shell into the mailman Python environment: mailman shell > 3. Add a new mailing list. > from mailman.interfaces.domain import IDomainManager > from zope.component import getUtility > manager = getUtility(IDomainManager) > manager.add('testing.com') > show_domains() # with method from the above documentation URL > <Domain testing.com> > <Domain mydomain.com> Did you commit() after doing the above? I'm not sure how kubernetes fits in to this, but `mailman create` for a list in an unknown domain will create the domain unless -D or --no-domain is specified. See `mailman create --help`. Mailman core has no concept of `primary domain` which is why it's not documented. Are you creating lists via REST as you posted previously. If so, the domain must exist, but if you created domains as above, they should exist as long as you committed your changes. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 4 weeks

[MM3-users] Re: Disabling mail/news gateway was: Moderation action "None" is misleading

by Mark Sapiro

On 2/5/25 13:03, Ron / BCLUG wrote: > > I've been digging into MM3 resource usage vs MM2 and have been > wondering: are there any other runners that can be disabled, or invoked > via cron job to run every $interval then exit again? The task runner is a candidate. It only actually does anything at intervals defined by the run_tasks_every setting in the [mailman] section of mailman.cfg, default 1 hour https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.…, but it still wakes up and comes into memory every sleep_time which defaults to 1 second. If just having the runners sleep longer works for you, you can set, e.g. ``` [runner.task] sleep_time: 10m ``` to only wake up the task runner every 10 minutes. If you really want it gone, you could put ``` [runner.task] start: no ``` in mailman.cfg to prevent starting it as a persistent runner, and make a python script like: ``` #!/opt/mailman/mm/venv/bin/python from mailman.core import initialize from mailman.runners.task import TaskRunner initialize.initialize() TaskRunner('task')._do_periodic() ``` and run that periodically via cron. I'm not certain, but I think task runner is the only runner for which it's that simple. > Second question, similar topic but MM2: how to disable NNTP? (if that's > what this is doing): > > /usr/bin/python2 /var/lib/mailman/bin/qrunner --runner=NewsRunner:0:1 -s Put this in mm_cfg.py del QRUNNERS[QRUNNERS.index(('NewsRunner', 1))] or if you already have some modifications to the QRUNNERS list in mm_cfg.py, make the appropriate adjustment to remove the NewsRunner entry. -- 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

Search results for query "sapiro"