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

[MM3-users]Re: mailman 2 vs. mailman 3: what happened to multipart/digest?

by Simon Hanna

On 05/12/2016 09:26 PM, Barry Warsaw wrote: > On May 12, 2016, at 12:18 PM, Mark Sapiro wrote: > >> It is the intent that Postorius will eventually expose all these >> settings. We're not there yet. At present you could possibly do this by >> interacting with mailmanclient, although I'm not certain the settings are >> exposed there. > > I'm not sure if they're exposed in mailmanclient, but they are exposed in the > core's REST API, on the member resource. It's the `delivery_mode` attribute > and it takes as legal values one of 'regular', 'plaintext_digests', > 'mime_digests', and 'summary_digests' (IOW, the enum item names for the > DeliveryMode enum). They are exposed in mailmanclient and are used in postorius. They can be found in the users personal subscription settings https://lists.mailman3.org/mailman3/accounts/mailmansettings/ > > Cheers, > -Barry > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

9 years, 7 months

[MM3-users] Re: Timeout in Postorius when trying to approve or reject moderated messages

by Sebastian Hagedorn

Am 27.08.20 um 18:05 schrieb Mark Sapiro: > On 8/27/20 8:07 AM, Sebastian Hagedorn wrote: >> >> Right now everything is running as root (except for Apache). I realized >> too late that I should've used a mailman user. Could that be the reason >> for the issue? > > Since you have determined it was a browser issue, that probably isn't > the reason, but running Mailman as root is a bad idea in general for > security reasons. Thanks, I'm aware, and I'm not going to on a production system. This installation is just a trial run. > I don't know if it's relevant or not, but I have just recently had > issues with Firefox not working properly on two different (not mailman) > web sites, and these issues were fixed by clearing cookies and cached > data from the affected sites and restarting Firefox. I can confirm that that worked in my case as well.

5 years, 3 months

[MM3-users] Re: Another interesting error...

by Darren Smith

"It's in Mailman's database in the 'message' table." I can see the message table - is there a way to see where it is marked as "held"? All I'm seeing in that table is id, message_id, message_id_hash, and path. I'm wanting to be able to query for held messages for a given mailing list, as there are currently over 98,000 entries in the message table. -Darren On Mon, Apr 23, 2018 at 3:17 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 04/23/2018 01:31 PM, Darren Smith wrote: > > So it appears that there was a message sent to one of our mailing lists > > that was put into the held message queue. However, when attempting to go > to > > the message to do the moderation, the web page returns and Error 500. > > > > Looking in the mailman log, I found this: > > > > Apr 23 14:21:02 2018 (17878) REST request handler error: > > Traceback (most recent call last): > > File "/opt/mailman3/conda/lib/python3.6/wsgiref/handlers.py", line > 137, > > in run > > self.result = application(self.environ, self.start_response) > > File > > "/opt/mailman3/conda/lib/python3.6/site-packages/ > mailman/database/transac > > tion.py", line 50, in wrapper > > rtn = function(*args, **kws) > > File > > "/opt/mailman3/conda/lib/python3.6/site-packages/ > mailman/rest/wsgiapp.py" > > , line 214, in __call__ > > return super().__call__(environ, start_response) > > File "/opt/mailman3/conda/lib/python3.6/site-packages/falcon/api.py", > > line 227 , in __call__ > > responder(req, resp, **params) > > File > > "/opt/mailman3/conda/lib/python3.6/site-packages/ > mailman/rest/post_modera > > tion.py", line 167, in on_get > > resource = self._make_collection(request) > > File > > "/opt/mailman3/conda/lib/python3.6/site-packages/ > mailman/rest/helpers.py" > > , line 159, in _make_collection > > for resource in collection] > > File > > "/opt/mailman3/conda/lib/python3.6/site-packages/ > mailman/rest/helpers.py" > > , line 159, in <listcomp> > > for resource in collection] > > File > > "/opt/mailman3/conda/lib/python3.6/site-packages/ > mailman/rest/post_modera > > tion.py", line 157, in _resource_as_dict > > resource = self._make_resource(request.id) > > File > > "/opt/mailman3/conda/lib/python3.6/site-packages/ > mailman/rest/post_modera > > tion.py", line 100, in _make_resource > > make_header(decode_header(resource['subject']))) > > File "/opt/mailman3/conda/lib/python3.6/email/header.py", line 174, in > > make_he ader > > h.append(s, charset) > > File "/opt/mailman3/conda/lib/python3.6/email/header.py", line 295, in > > append > > s = s.decode(input_charset, errors) > > UnicodeDecodeError: 'gb2312' codec can't decode byte 0x87 in position 2: > > illegal multibyte sequence > > > > It LOOKS as if there might be a character in the email somewhere - > possibly > > in the subject or sender fields? - that is somehow unexpected. > > > It appears that the Subject: header is RFC 2047 encoded and there is an > encoded word with charset gb2312 that contains an invalid encoding. > > The message is apparently defective, but this kind of defect shouldn't > cause a 500 error. > > I can't tell for sure from the traceback if this is Postorius or some > other application accessing the REST api. Is it Postorius or something > else? > > > > I am attempting to find the held message - can someone point me where I > can > > go to see the message so that I can see what might be causing the > problem? > > > It's in Mailman's database in the 'message' table. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

7 years, 7 months

[MM3-users] Re: cache files?

by Dave McGuire

On 7/12/21 10:45 PM, Mark Sapiro wrote: >> Hi folks. I'm seeing quite a few .css files, thousands of them >> totaling 600+MB, building up in /var/lib/mailman3/web/static/CACHE/css. >> Some of them date back to when I set up the mm3 instance a few years ago. >> >> Is this expected, or am I missing a cron job or something to clean >> them up? > > This is not expected. I don't see it on the instances I manage. > > In the `static` directory, I see > ``` > $ du -h -d 1 > 1.7M ./admin > 12K ./facebook > 68K ./django_extensions > 4.0K ./browserid > 68K ./django-mailman3 > 2.6M ./postorius > 12K ./paintstore > 1.6M ./rest_framework > 5.2M ./hyperkitty > 404K ./CACHE > 12M . > $ find -type f|wc > 401 401 18253 > ``` > > I think when you run the Django admin `collectstatic` command, you need > to specify the `--clear` option. Interesting, I know nothing of that command. Is that something that should be run periodically? Thanks, -Dave -- Dave McGuire, AK4HZ New Kensington, PA

4 years, 5 months

[MM3-users] Re: remove non members from a list

by Guillermo Hernandez (Oldno7)

On 6/8/21 19:33, Mark Sapiro wrote: > On 8/6/21 10:28 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > >> Thanks. Now it's no showing errors (and nothing at all) but >> apparently it does nothing. The non mebers of the list (the few that >> remains: I've been deleting one at a time from the web) aparently >> still are there.. >> >> Knowing the correct procedure will ease me to try tomorrow with a >> clean head. > > It doesn't report anything, and if you don't commit() or exit with > control-D, any changes will be rolled back. I think I did a typpo. (forgot to add "()" after the "commit" sentence). And exit with quit() maybe not helps. I've done it exactly as you wrote it and it worked like a charm. Thank you very very much > > What does > > list(m.nonmembers.members) > > show before doing the unsubscribe() and commit() and then what after? >

4 years, 4 months

[MM3-users] Re: Is logging.subscribe working in /etc/mailman.cfg?

by Alan So

Mark Sapiro wrote: > On 12/11/18 2:11 AM, ktso(a)cuhk.edu.hk wrote: > > I have put the following in /etc/mailman.cfg and restart mailman. An > > empty file can be created but nothing can be logged when admin or non-member > > subscribe/unsubscribe. Anything I have missed? So far I can only see log appear in > > mailman.log and smtp.log. Thanks. > > > > [logging.subscribe] > > path: subscribe.log > > level: debug > > The above is correct. As far as not seeing things in the log, very > little is logged in the subscribe log. Only (un)subscription requests > held for moderator approval and moderator approval of held unsubscribes > but not subscribes. > > In other words, unless your list's subscription police includes > 'moderate' nothing will be logged in subscribe.log. It looks like there is only a subscription policy but no unsubscription policy. I can't find anything even by exporting the settings using Python mailman client. Is it correct?

7 years

[MM3-users] Re: Mailman web interface / uwsgi

by Jan Eden

On 2022-11-26 22:59, Mark Sapiro wrote: > > Another (unrelated) question: Why is mailman_hyperkitty.cfg placed in > > /opt/mailman/mm and not in /etc/mailman3 with the other configuration > > files when using the virtualenv installation instructions > > (https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… > > > mailman_hyperkitty and its mailman-hyperkitty.cfg are part of mailman core, > not mailman-web. If you want, you could put mailman-hyperkitty.cfg in > /etc/mailman3/ by putting > ``` > configuration: /etc/mailman3/mailman-hyperkitty.cfg > ``` > in the `[archiver.hyperkitty]` section of mailman.cfg, but as it really > belongs to core and not mailman-web we choose to put it in /opt/mailman/mm/. I see. But the mailman.cfg is placed in /etc/mailman3, and this file also belongs to the core, doesn't it? In any case, I changed the configuration parameter for [archiver.hyperkitty] as you suggested and all settings are in one place now. I will post two more questions to this list today, and promise to stop spamming you afterwards. :) Thanks again, Jan

3 years

[MM3-users] Re: Sending to mangled 'From' addresses.

by Jeremy Stanley

On 2024-06-01 09:49:54 -0700 (-0700), Mark Sapiro wrote: [...] > If this is the result of a `reply` and not `reply-all` the client > is not behaving reasonably. [...] I haven't seen it with replies, but rather mail clients recording every address they see into their address book, and then when the user of such a client wants to send new mail to someone they start typing that person's name and their mail client happily auto-completes it with the mailing list's address instead of the intended personal address. This is one of the reasons we don't use DMARC mitigations for most of our lists, and instead we just try to make Mailman avoid altering anything in the message headers or body that might invalidate DKIM signatures (so no changing From or Reply-To, no adding list-specific subject prefixes, no appending list unsubscribe info to the end of messages...). It's an unfortunate trade-off, but some of our users do tend to get confused by address book pollution. -- Jeremy Stanley

1 year, 6 months

[MM3-users] Re: Can't subscribe on new site/domain

by Flo

On 10/11/25 00:18, Mark Sapiro wrote: > On 10/10/25 1:47 PM, Flo via Mailman-users wrote: >> >> :/var/lib/mailman3/data# sqlite3 mailman.db >> SQLite version 3.46.1 2024-08-13 09:16:08 >> Enter ".help" for usage hints. >> sqlite> SELECT * from django_mailman3_maildomain JOIN django_site ON >> site_id = django_site.id; >> Parse error: no such table: django_mailman3_maildomain >> sqlite> > > Is there a second database? Something like mailmanweb.db. If so, use > that one. > I found it, it's in a different directory: /var/lib/mailman3/web# sqlite3 mailman3web.db SQLite version 3.46.1 2024-08-13 09:16:08 Enter ".help" for usage hints. sqlite> SELECT * from django_mailman3_maildomain JOIN django_site ON site_id = django_site.id; ... ... 8|lists.example.com|7|7|Lists of Example|lists.example.com sqlite> The two working domains are first (...) . The problematic domain (renamed to lists.example.com) appears when I create it in Postorius. For me the only conspicuous is that the numbers are 8|.|7|7 while at the other two entries they are the same for the whole line: 2|.|2|2 and 4|.|4|4 . Flo

2 months

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

by Brian Carpenter

On 12/25/20 10:07 PM, Mark Sapiro wrote: > On 12/25/20 6:36 PM, Brian Carpenter wrote: >> Dear List, >> >> First of all Merry Christmas to those of you that are observing it. >> >> I have an issue on one of my Mailman 3 servers. The bounce runner is not >> running, even after restarting mailman core. All the other runners are >> working fine. Here is the problem, after restarting it, a number of >> messages show up in queue/bounces from a single list. > > What happens if instead of restating core, you stop and then start it? Same behavior. > I don't really understand what's going on. The only messages which get > queued in queue/bounces/ are messages to the LIST-bounces address > delivered from the MTA, unless possibly they are somehow in queue/retry/ > and being retried. What do you see in the MTA logs? > The mail logs shows bounce notifications being sent out as per the list settings. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 11 months

[MM3-users] Unnecessary coded-words? [was: Shorted Subjects in Mailman]

by Stephen J. Turnbull

Mark Sapiro writes: > However, I did a test injecting directly to Mailman a message with > ``` > Subject: [SAV-LINUX] Notice from Sophos_Anti-Virus on server.example.com > [DEMO1] > ``` > on a German language test list with subject prefix [Janinsliste] and I > get the same result, I.e. the RFC 2047 encoded > ``` > Subject: > =?utf-8?q?=5BJaninsliste=5D=5BSAV-LINUX=5D_Notice_from_Sophos=5FAnti-Virus_on_server=2Eexample=2Ecom?= > ``` > so this is definitely a Mailman bug (or a bug in the underlying Python > email package. There seem to be other bugs here. First, I can't see any content-based reason for encoding this 100% ASCII content. I guess the list is set to always encode the subject prefix, and we just encode the whole field body if any part is encoded? Perhaps this is a quick workaround for the OP: set MIME-encoding for the subject prefix to "as needed". Second (and this is important because of RFC conformance!), the encoded word is over 75 characters. I've filed https://gitlab.com/mailman/mailman/-/issues/1021 for this.

3 years, 4 months

[MM3-users] Re: Uncaught runner exception: 'str' object has no attribute 'decode'

by Mark Sapiro

On 09/28/2017 06:11 AM, Henrik Rasmussen wrote: > Sep 25 07:20:57 2017 (35) Uncaught runner exception: 'str' object has no attribute 'decode' > Sep 25 07:20:57 2017 (35) Traceback (most recent call last): > File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 171, in _one_iteration > self._process_one_file(msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 264, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/runners/pipeline.py", line 37, in _dispose > process(mlist, msg, msgdata, pipeline) > File "/usr/local/lib/python3.6/site-packages/mailman/core/pipelines.py", line 53, in process > handler.process(mlist, msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/handlers/subject_prefix.py", line 174, in process > mlist, msgdata, subject, prefix, prefix_pattern, ws) > File "/usr/local/lib/python3.6/site-packages/mailman/handlers/subject_prefix.py", line 72, in all_same_charset > chunks.append(chunk.decode(charset)) > AttributeError: 'str' object has no attribute 'decode' > Sep 25 07:20:57 2017 (35) SHUNTING: 1506324057.584686+a13cc47dc1027a0cfb00c892396b3ba7efabb3dc This is <https://gitlab.com/mailman/mailman/issues/359> It is fixed in the current source by <https://gitlab.com/mailman/mailman/commit/e92359323cda1fb118415c2ccb6967979…>. > In addition, the log contains other trace backs that might or might not associate to this problem: > > Sep 24 21:11:27 2017 (34) Uncaught runner exception: 'ascii' codec can't encode character '\udcea' in position 3093: ordinal not in range(128) > Sep 24 21:11:28 2017 (34) Traceback (most recent call last): > File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 171, in _one_iteration > self._process_one_file(msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 264, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/runners/outgoing.py", line 93, in _dispose > self._func(mlist, msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/mta/deliver.py", line 86, in deliver > refused = agent.deliver(mlist, msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/mta/bulk.py", line 101, in deliver > mlist, msg, msgdata, recipients) > File "/usr/local/lib/python3.6/site-packages/mailman/mta/base.py", line 70, in _deliver_to_recipients > sender, sorted(recipients), msg.as_string()) > File "/usr/local/lib/python3.6/site-packages/mailman/mta/connection.py", line 84, in sendmail > results = self._connection.sendmail(envsender, recipients, msgtext) > File "/usr/local/lib/python3.6/smtplib.py", line 855, in sendmail > msg = _fix_eols(msg).encode('ascii') > UnicodeEncodeError: 'ascii' codec can't encode character '\udcea' in position 3093: ordinal not in range(128) > Sep 24 21:11:28 2017 (34) SHUNTING: 1506287488.0529234+cbf8a31cad265a40a18e8955be0c9ad8b48a1b66 This may be a bug. The msgtext argument in 'self._connection.sendmail(envsender, recipients, msgtext)' is supposed to be a string containing only ascii characters. I'm interested in what's in Mailman's var/queue/shunt/1506287488.0529234+cbf8a31cad265a40a18e8955be0c9ad8b48a1b66.pck. You may be able to print the contents with Mailman's bin/mailman queue var/queue/shunt/1506287488.0529234+cbf8a31cad265a40a18e8955be0c9ad8b48a1b66.pck There shouldn't be raw unicodes like \udcea in the text of the message, but we should defend against that anyway. > Sep 25 07:20:57 2017 (35) Uncaught runner exception: 'str' object has no attribute 'decode' Same as above. > Sep 25 09:19:58 2017 (30) deque: do_confirm_verify > Traceback (most recent call last): > File "/usr/local/lib/python3.6/site-packages/mailman/app/workflow.py", line 69, in __next__ > return step() > File "/usr/local/lib/python3.6/site-packages/mailman/app/subscriptions.py", line 420, in _step_send_confirmation > raise StopIteration > StopIteration This is normal. It is not an issue. > Sep 26 09:21:07 2017 (36) deque: > Traceback (most recent call last): > File "/usr/local/lib/python3.6/site-packages/mailman/app/workflow.py", line 69, in __next__ > return step() > File "/usr/local/lib/python3.6/site-packages/mailman/app/subscriptions.py", line 217, in _step_sanity_checks > MemberRole.member) > mailman.interfaces.member.AlreadySubscribedError: sender(a)foo.bar is already a MemberRole.member of mailing list listname(a)listserver.foo.bar This appears to be an attempt to subscribe someone who's already a member. This should have resulted in an appropriate message to the attempted subscriber. > Sep 26 13:32:29 2017 (30) Uncaught runner exception: > Sep 26 13:32:29 2017 (30) Traceback (most recent call last): > File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 171, in _one_iteration > self._process_one_file(msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 264, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/runners/command.py", line 196, in _dispose > mlist, msg, msgdata, parts, results) > File "/usr/local/lib/python3.6/site-packages/mailman/commands/eml_confirm.py", line 53, in process > mlist).confirm(token) > File "/usr/local/lib/python3.6/site-packages/mailman/app/subscriptions.py", line 540, in confirm > PendableUnsubscription.PEND_TYPE) > AssertionError I'm not sure about this one. a message has been sent to the LISTNAME-confirm address to confirm a subscription or unsubscription. The confirmation token exists but is neither a pending subscription or unsubscription token. > Sep 27 13:23:02 2017 (32) Uncaught runner exception: 'content-transfer-encoding' > Sep 27 13:23:02 2017 (32) Traceback (most recent call last): > File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 171, in _one_iteration > self._process_one_file(msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/core/runner.py", line 264, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/runners/outgoing.py", line 93, in _dispose > self._func(mlist, msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/mta/deliver.py", line 86, in deliver > refused = agent.deliver(mlist, msg, msgdata) > File "/usr/local/lib/python3.6/site-packages/mailman/mta/bulk.py", line 101, in deliver > mlist, msg, msgdata, recipients) > File "/usr/local/lib/python3.6/site-packages/mailman/mta/base.py", line 70, in _deliver_to_recipients > sender, sorted(recipients), msg.as_string()) > File "/usr/local/lib/python3.6/email/message.py", line 158, in as_string > g.flatten(self, unixfrom=unixfrom) > File "/usr/local/lib/python3.6/email/generator.py", line 116, in flatten > self._write(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 181, in _write > self._dispatch(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 214, in _dispatch > meth(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 272, in _handle_multipart > g.flatten(part, unixfrom=False, linesep=self._NL) > File "/usr/local/lib/python3.6/email/generator.py", line 116, in flatten > self._write(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 181, in _write > self._dispatch(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 214, in _dispatch > meth(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 358, in _handle_message > g.flatten(msg.get_payload(0), unixfrom=False, linesep=self._NL) > File "/usr/local/lib/python3.6/email/generator.py", line 116, in flatten > self._write(msg) > File "/usr/local/lib/python3.6/email/generator.py", line 189, in _write > msg.replace_header('content-transfer-encoding', munge_cte[0]) > File "/usr/local/lib/python3.6/email/message.py", line 558, in replace_header > raise KeyError(_name) > KeyError: 'content-transfer-encoding' > Sep 27 13:23:02 2017 (32) SHUNTING: 1506518582.300981+aa68949ca566c7170a81a0bd643cee803f29c312 As I said in a prior reply, this is <https://gitlab.com/mailman/mailman/issues/256>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 2 months

[MM3-users] Re: Uncaught runner exception: 'str' object has no attribute 'decode'

by Henrik Rasmussen

Thanks, Mark. @Abhilash, any chance for an update to Docker-mailman to fix these known issues soon? https://gitlab.com/mailman/mailman/issues/256 https://gitlab.com/mailman/mailman/issues/359 @Mark, Mark Sapiro wrote: >>> In addition, the log contains other trace backs that might or might not associate to this problem: >>> >>> Sep 24 21:11:27 2017 (34) Uncaught runner exception: 'ascii' codec can't encode character '\udcea' in position 3093: ordinal not in range(128) >> >> This may be a bug. The msgtext argument in >> 'self._connection.sendmail(envsender, recipients, msgtext)' is supposed >> to be a string containing only ascii characters. I'm interested in >> what's in Mailman's >> var/queue/shunt/1506287488.0529234+cbf8a31cad265a40a18e8955be0c9ad8b48a1b66.pck. >> You may be able to print the contents with Mailman's >> >> bin/mailman queue >> var/queue/shunt/1506287488.0529234+cbf8a31cad265a40a18e8955be0c9ad8b48a1b66.pck Isn't this a Mailman 2 command? What is the Mailman 3 equivalent? -- Henrik Rasmussen <her(a)adm.ku.dk> University of Copenhagen, Danmark

8 years, 2 months

[MM3-users] Re: How to fix: [Django] ERROR (EXTERNAL IP)

by Jigme Datse

On Fri, 1 Nov 2024 20:56:42 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 11/1/24 20:14, Jigme Datse wrote: > > > > python venv/lib/python3.12/site-packages/mailman_web/manage.py > > migrate > > > > which *might* be the wrong manage.py but other than the change with > > the migrate command, without it looks to throw the same output. > > > > The Django log was at that time empty it's now attached (larger than > > I'd like). > > It is not necessary to post the entire log which repeats the same > ERROR and traceback over 300 times. The errors all seem to be > disallowed hosts. 321 from IP 45.79.102.219, 5 from > mail01.datsemultimedia.com and a few others. The PTR from IP > 45.79.102.219 is mail01.datsemultimedia.com and its A is > 45.79.102.219. Is this your server, if so add both 45.79.102.219 and > mail01.datsemultimedia.com to ALLOWED_HOSTS. > Thank you... I while helpful, I think I'll abandon this project... Appreciate the help.

1 year, 1 month

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

by Stefan Tatschner

On Sun, 2018-11-18 at 14:38 -0800, Mark Sapiro wrote: > No. This is not normal. This is apparently coming from Django qcluster. > At least it is qcluster that uses the django_q_ormq table, but these > repeated queries are not normal, at least I don't see them in the sites > I administer. Thank you for the pointer to qcluster. I don't know so much about these web components and their relationships. According to the documentation [1] it seems that qcluster is not needed as long as cronjobs are configured. Since debian ships the entries in /etc/cron.d [2, 3] I disabled the qcluster components. Also there is a debian package issue; qcluster is started twice when using the provided service files: * the uwsgi script ini starts qcluster * the mailman3-qcluster service starts it as well I know the debian thing is out of scope here, I just want it documented somewhere. Stefan [1]: https://hyperkitty.readthedocs.io/en/latest/install.html#asynchronous-tasks [2]: https://gitlab.com/mailman/hyperkitty/blob/master/example_project/crontab [3]: https://salsa.debian.org/mailman-team/mailman-suite/blob/master/debian/mail…

7 years

[MM3-users] Re: import21: ModuleNotFoundError: No module named 'Mailman'

by Christian Schwarz

On Sun, 2019-07-28 at 17:07 -0700, Mark Sapiro wrote: > As to how to proceed, there are a couple of ways. One is to fix import21 > so it ignores this issue. I just reported > <https://gitlab.com/mailman/mailman/issues/618> on this, but I'm not > sure how to fix it. I don't think it will work to try the pickle.load > and pass the ModuleNotFoundError exception because I think the rest of > the pickled data won't be returned. > > It looks like you still have the MM 2.1 installation, so you could use > either MM 2.1's bin/withlist or bin/config_list to set the list's > bounce_info to an empty dictionary. and then use the updated config.pck > for the import. > > This assumes that bounce_info is the issue. You can verify that there is > a non-empty bounce_info dictionary with either bin/withlist or bin/dumpdb. Indeed, bounce_info is not empty! I think I need more precise instructions on how to empty bounce_info using config_list, though.

6 years, 4 months

[MM3-users] Re: An archive/read-only list on a full setup?

by Andreas Schamanek

Thanks a lot, Mark! After some tests with a test setup I came to the conclusion that what you suggested was better than what I had so far (i.e. the empty Mailman list). So, I deleted the empty list, leaving only the Hyperkitty list. On Tue, 11 Apr 2023, at 11:22, Mark Sapiro wrote: > Since there is no Mailman list, attempts to post or reply directly from > HyperKitty will fail, ... Yep, I get a 404. Doesn't look nice but should be OK. Not many people will try, and the description of the list makes clear that it is only an archive. I have also added a Redirect on the webserver so that people who click [Manage subscription/this list] are redirected to the actual remote list. That helps, too. So, no fake list, and the link to subscribing still works. The particular list is low volume. So, it will take some time until I can report how well it worked out. But after my tests I am confident. Thanks again, -- -- Andreas :-)

2 years, 8 months

[MM3-users] Re: Mailman not able to process "big" requests

by Darren Smith

Our installation at https://lists.rootsweb.ancestry.com has around 33,000 lists and somewhere around 1.5 million members. We have lists with 5,000+ members. Note that I haven't tried any mass subscriptions. When we upgraded from mailman 2 to mailman 3, we used the old .pck files and ran the import on each of the lists. It did take about 6 weeks to do the full import all 33,000 lists. I'm not joking. As for sending messages - there isn't any problem sending that many messages out, but then we are also not trying to subscribe list members at the time. We are, though, in the process of importing the old archives from our old mailman 2 system. This doesn't seem to affect the rest of the system. We have seen some inefficiencies in the new system, such as the front page of postorius - loading all of the information for 200 lists (if the user set the "lists per page" to 200) was bringing down the system. We have our own metadata system to be able to search for lists by state/region/surname (ours is a genealogy mailing list system), so we had to replace the front page with our own "find a list" functionality. The other main problem was the page where a user can see what lists they subscribe to. That page was also a denial of service if the user had several hundred lists they are subscribed to. And for a genealogy mailing list system, this is common. We have actually ended up creating our own API layer (only accessible on the local machine) and make certain calls to it for the most painful of the issues. One of these days (when we get a moment to breathe) we are going to post some of our changes to the project so that we can ditch our own API and just use the internal REST API. To be fair, the inefficiencies are not necessarily with mailman or the rest API itself - but with Postorius making hundreds of calls to load a single page. Though if the API supported loading multiple lists at once instead of having to load them serially, that might help as well. So while we have not seen any timeout issues on the call to mass subscribe users, we HAVE found several other calls that are effectively a denial of service and have gotten around them ourselves, with plans to contribute to the project in the near future. -Darren On Tue, Apr 24, 2018 at 8:47 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 04/24/2018 12:36 AM, Abhilash Raj wrote: > > On Mon, Apr 23, 2018, at 10:41 PM, Jonas Felber wrote: > > >> We also have a problem with sending out emails to "large" (>50) groups, > >> as they seem to not getting sent out at all. Do you have any idea what > >> the problem here could be? > > > > Which MTA are you using? What do you see in mailman's logs and MTA's > logs? > > > > I haven't seen this kind of problem before with Mailman 3. This very > list is hosted using Mailman 3 and I believe has more than 50 subscribers. > > > Nor have I seen this issue. This list currently has 158 non-digest > members. There are several @python.org Mailman 3 lists with over 100 > non-digest members including the active yt-users(a)python.org list with > 301 members, and I have gotten no reports of an issue like this. > > Also, there are over 600 lists at <https://lists.fedoraproject.org/>, > and I don't think this is an issue there either. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

7 years, 7 months

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

by Wolfgang Bock

Hi again, in this case I'll check out either and report. Regards Wolfgang Am 18.11.2019 um 05:06 schrieb 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. >

6 years

[MM3-users] Re: ValueError: ...:EVP_DigestInit_ex:disabled for fips

by Ralf Wiegand

Hello Mark, Can I substitute Django with something that will be FIPS complaint? Can I do without it? Thank You, Ralf On 5/19/20 1:02 PM, Mark Sapiro wrote: > On 5/19/20 5:57 AM, Ralf Wiegand wrote: >> (venv-3.6) [root@maildev mailman-suite_project]# python manage.py migrate >> Operations to perform: >> Apply all migrations: account, admin, auth, contenttypes, >> django_mailman3, django_q, hyperkitty, openid, postorius, sessions, >> sites, socialaccount >> Running migrations: >> Applying contenttypes.0001_initial...Traceback (most recent call last): > ... >> File >> "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/db/backends/utils.py", >> line 221, in names_digest >> h = hashlib.md5() >> *ValueError: error:060800A3:digital envelope >> routines:EVP_DigestInit_ex:disabled for fips* >> >> >> >> Hello group, I am running into this error. any idea what is going >> wrong here? > This is a Django issue, not Mailman per se. The migration that's failing > is django/contrib/contenttypes/migrations/0001_initial.py. A brief > search seems to indicate that this won't work with NSS FIPS. >

5 years, 6 months

[MM3-users] Re: certain msgs not archived

by Sandor Dibuz

On 2/17/22 19:16, Mark Sapiro wrote: > > If you rerun hyperkitty_import with the since= option set to a date > earlier that the oldest message to import, it should just work. Messages > which are already in the archive (by Message-ID:) will be ignored by the > import process. Great! So valuable info. Thank you, Mark. "earlier that the oldest message" you sure mean earlier then the oldest of already archived. Or since= any date of the mbox messages to be imported. Will check the hyperkitty_import for since= option format. Yet another question. Is it supposed to stop minutely/hourly/etc. mailman3-web cron jobs during import to avoid any collisions? Or even mailman3-web completely but probably it needs to be running. I only ask because my last import attempt on a test maillist failed with [ERROR/MainProcess] Failed indexing 1 - 2 (retry 5/5): (1712, 'Index hyperkitty_attachment is corrupted') (pid 5841): (1712, 'Index hyperkitty_attachment is corrupted') Optimizing cured the hyperkitty_attachment InnoDB index corruption problem but scared the sh.. out of me for a moment... Thank you for your help, Mark. Sanyi

3 years, 9 months

[MM3-users] Re: bulk deletion of messages from Hyperkitty

by Timour Bakeev

Hi Mark! Mark Sapiro wrote: > On 7/10/24 12:27 PM, Danil Smirnov via Mailman-users wrote: > > I'm aware of the tools you mentioned and they were properly used. > > Your issue is almost certainly caused by unescaped From lines in > message bodies and preprocessing the mbox with the > hyperkitty/contrib/cleanarch3 script should fix those. Could you take a look at my MR for this script? Right now I have to use a locally modified version of it, as the one in contrib/ doesn't work out of the box. > > Please let us focus on the question I asked - how do we delete messages of > > a particular date if there are too many of them so using Hyperkitty UI > > isn't an option? > > You can do > DELETE FROM hyperkitty_email WHERE archived_date = <your datetime>; Thanks a lot for this detailed walk-through, it is very helpful and I'm going to use it to clean up my migrated archives. With best regards, Timur Bakeev.

1 year, 5 months

[MM3-users] Re: Any good ideas on how to troubleshoot django allauth

by Stephen J. Turnbull

Mark Sapiro writes: > I only discovered this because I saw the ERROR entries in the log while > looking for something else. In any case, it turned out that > python-openssl was installed on mail.python.org and not on > lists.mailman3.org. Removing it from mail.python.org allowed OAuth2 > logins to work. I think that part of the problem here may be that distros have not caught up to current Python upstream distribution practices. MacPorts is particularly bad (ie, heinous), in that they don't even follow their own Python distributions. In MacPorts, OpenSSL and GNU readline have both bitten me; basically, the add-on packages should be labeled "unless you know you need this, and know why, and accept that NO WARRANTEE means what it says (we don't support it at all), don't install this!" I've opened Mailman/Mailman issue#323 for this. Probably it should be moved to Installation and Troubleshooting documentation, but maybe leaving an open issue in the tracker would help discoverability?

8 years, 7 months

[MM3-users] Re: mailman3-web and the django middleware problem

by Thomas Stein

Using the virtenv installation method seems to be reasonable, yes. Adding the suggested line i did not try yet. Thanks! Am 26. April 2024 10:29:18 MESZ schrieb Odhiambo Washington <odhiambo(a)gmail.com>: >On Fri, Apr 26, 2024 at 8:30 AM Thomas Stein <himbeere(a)meine-oma.de> wrote: > >> Am 2024-04-26 00:52, schrieb Mark Sapiro: >> > On 4/25/24 14:01, Thomas Stein wrote: >> >> Am 2024-04-25 22:03, schrieb Mark Sapiro: >> >>> >> >>> I don't know how things are arranged in the Debian/Ubuntu package, >> >>> but you may have a settings.py which at the end does something like >> >>> ``` >> >>> try: >> >>> from settings_local import * >> >>> except ImportError: >> >>> pass >> >>> ``` >> >>> If that is the case, adding the above snippet to the end of >> >>> settings_local.py should work. >> >> >> >> Yes, that's the case. I added the snippet in question to >> >> settings_local.py but this leads to another error: >> >> >> >> File "/usr/share/mailman3-web/settings.py", line 503, in <module> >> >> from settings_local import * >> >> File "/usr/share/mailman3-web/settings_local.py", line 194, in >> >> <module> >> >> x = list(MIDDLEWARE) >> >> ^^^^^^^^^^ >> >> NameError: name 'MIDDLEWARE' is not defined >> >> dpkg: error processing package mailman3-web (--configure): >> > >> > Yes. I understand. In your case, MIDDLEWARE is only defined in >> > settings.py and not in settings_local.py. As I understand it originally >> > you added >> > ``` >> > x = list(MIDDLEWARE) >> > x.insert(0, 'allauth.account.middleware.AccountMiddleware') >> > MIDDLEWARE = x >> > ``` >> > to settings.py and you say it didn't help. I don't know why that >> > wouldn't work as long as there is no setting for MIDDLEWARE in >> > settings_local.py and you added that after the MIDDLEWARE setting in >> > settings.py. >> > When you say it didn't help, do you mean you still get the >> > >> > django.core.exceptions.ImproperlyConfigured: >> > allauth.account.middleware.AccountMiddleware must be added to >> > settings.MIDDLEWARE >> > >> > message or something else? I note that the original post in this thread >> > refers to /etc/mailman3/mailman-web.py which is presumably where the >> > package ultimately puts the Django settings, and I don't know what >> > `dpkg --configure` is doing. >> > >> > One thing you could try is in settings_local.py, put >> > ``` >> > from settings import MIDDLEWARE >> > x = list(MIDDLEWARE) >> > x.insert(0, 'allauth.account.middleware.AccountMiddleware') >> > MIDDLEWARE = x >> > ``` >> > to work around the NameError. >> >> After that I get: >> >> File "/usr/share/mailman3-web/urls.py", line 20, in <module> >> from django.conf.urls import include, url >> ImportError: cannot import name 'url' from 'django.conf.urls' >> (/usr/lib/python3/dist-packages/django/conf/urls/__init__.py) >> dpkg: error processing package mailman3-web (--configure): >> installed mailman3-web package post-installation script subprocess >> returned error exit status 1 >> Errors were encountered while processing: >> >> I guess I'll wait for the new package for now. >> > > >How about adding: > >MIDDLEWARE += ('allauth.account.middleware.AccountMiddleware',) > >in settings_local.py > >And how about you use the virtualenv method ><https://docs.mailman3.org/en/latest/install/virtualenv.html> for more >peace of mind in the future? > >

1 year, 7 months

[MM3-users] Re: Templates and docker-mailman

by Abhilash Raj

On Tue, Mar 20, 2018, at 2:47 PM, Mark Sapiro wrote: > On 03/20/2018 02:13 PM, jwhathaway(a)locklaw.com wrote: > > > > /opt/mailman/core/var/templates/site/en/list:member:generic:footer > > > > But this is not being honored by the mailman container. I have restarted all of the containers. Is there something else I need to do? > > > That's only one place the template is looked for. The search is first > list, then domain then site. > > So the search will be first in > /opt/mailman/core/var/templates/list/<list-id>/en/ followed by > /opt/mailman/core/var/templates/domains/<domain>/en/ followed by > /opt/mailman/core/var/templates/site/en/ > > and the first list:member:regular:footer or list:member:generic:footer > found is what will be used for regular deliveries and the first > list:member:digest:footer or list:member:generic:footer found is what > will be used for digest deliveries. I'd probably have to look at the code, but aren't they supposed to have either .txt or .html extensions? -- Abhilash Raj maxking(a)asynchronous.in

7 years, 8 months

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

by Élodie BOSSIER

Le 18/02/2022 à 18:23, Mark Sapiro a écrit : > If you go to https://example.com/mailman3/domains/ (the Domains view > in Postorius) you will see at least two entries, one with Mail Host > ml.franceserv.fr and one with Mail Host ml.viticreation.fr. > > What are the Web Host entries for these? > You should have two separate site entries in the django_site table > (https://example.com/admin/sites/site/) for these domains. Ah alright, now I understand how to proceed and it's working perfectly. I need to add domains through https://ml.franceserv.fr/admin/sites/site/ and define a new site_id for each domain name. Thank you very much for your help. This is my result : https://images.franceserv.fr/images/2022/02/18/06d4eb84a0ded88d55c0296ff0c3… Now, I need to find how to set it automatic when I will add a new list. Perhaps I could do it with an an SQL command if there are no bash command ? I will check with "mailman create" and the --domain argument. Thank you again for your help.

3 years, 9 months

[MM3-users] Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /archives/search

by Odhiambo Washington

On Sat, Jan 28, 2023 at 11:25 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/28/23 11:48, Stephen J. Turnbull wrote: > > Odhiambo Washington writes: > > > > > from mailman_web.settings.base import * > > > from mailman_web.settings.mailman import * > > > > I think just putting these as close to the top as possible, and > > including a comment (or two) saying that this is importing defaults > > that can be overridden by any assignment made later in the file is > > about as far as we can go for explaining. > > > I've Just updated this. It now says: > ``` > # Get the default settings. > from mailman_web.settings.base import * > from mailman_web.settings.mailman import * > > # Settings below supplement or override the defaults. ``` > Yes, this now is awesome - for reading between the lines :) Thank you. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 10 months

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

by Shashikanth Komandoor

Thank you Mark for your response. I am not sure. How can I check that if it is from unshunting ? <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Wed, Sep 23, 2020 at 10:33 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 9/23/20 6:32 AM, Shashikanth Komandoor wrote: > > Dear Mark, > > > > As I already said, your suggestion worked well on one list. > > > > But when I tried to implement the same trick on another list, I > > found the below error messages in the mailman.log. > > > > > >> * Sep 23 18:31:31 2020 (22951) Uncaught runner exception: > [Errno > >> 2] No such file or directory: > >> '/var/lib/mailman/mailman/var/lists/ > press.dpr-pb.lsmgr.nic.in/digest.mmdf > >> <http://press.dpr-pb.lsmgr.nic.in/digest.mmdf>'* > >> > >> > >> *Sep 23 18:31:31 2020 (22951) Traceback (most recent call last):* > >> * File "/usr/lib64/python3.6/mailbox.py", line 581, in __init__* > >> * f = open(self._path, 'rb+')* > >> *FileNotFoundError: [Errno 2] No such file or directory: > >> '/var/lib/mailman/mailman/var/lists/ > press.dpr-pb.lsmgr.nic.in/digest.mmdf > >> <http://press.dpr-pb.lsmgr.nic.in/digest.mmdf>'* > >> *During handling of the above exception, another exception occurred:* > >> *Traceback (most recent call last):* > >> * File "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 173, > >> in _one_iteration* > >> * self._process_one_file(msg, msgdata)* > >> * File "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 266, > >> in _process_one_file* > >> * keepqueued = self._dispose(mlist, msg, msgdata)* > >> * File "/var/lib/mailman/mailman/src/mailman/runners/pipeline.py", line > >> 37, in _dispose* > >> * process(mlist, msg, msgdata, pipeline)* > >> * File "/var/lib/mailman/mailman/src/mailman/core/pipelines.py", line > 50, > >> in process* > >> * handler.process(mlist, msg, msgdata)* > >> * File "/var/lib/mailman/mailman/src/mailman/handlers/to_digest.py", > line > >> 47, in process* > >> * with Mailbox(mailbox_path, create=True) as mbox:* > >> * File "/usr/lib64/python3.6/mailbox.py", line 893, in __init__* > >> * _mboxMMDF.__init__(self, path, factory, create)* > >> * File "/usr/lib64/python3.6/mailbox.py", line 585, in __init__* > >> * f = open(self._path, 'wb+')**FileNotFoundError: [Errno 2] No such > >> file or directory: > >> '/var/lib/mailman/mailman/var/lists/ > press.dpr-pb.lsmgr.nic.in/digest.mmdf > >> <http://press.dpr-pb.lsmgr.nic.in/digest.mmdf>'* > >> > >> I ran in both the ways you suggested i.e. through "mailman > shell" > > and "mailman remove". But no luck. > > > > Could you please suggest me at this point ? > > > Mailman is trying to add a message to the digest of the > press.dpr-pb.lsmgr.nic.in list, but the > /var/lib/mailman/mailman/var/lists/press.dpr-pb.lsmgr.nic.in/ directory > doesn't exist, presumably because the list has been removed. > > The question is why is Mailman trying to write to this list's > digest.mmdf? Did the above result from unshunting something from before > the list was removed? > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Thanks & Regards, Shashi Kanth.K 9052671936 <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

5 years, 2 months

[MM3-users] Re: Archive date/time vs elapsed time

by Mark

On 2023-06-27 13:34, Mark Sapiro wrote: > On 6/26/23 7:46 PM, Mark wrote: >> Hi >> >> In the archive's "Recent", "Most active" etc displays, the date and >> time of each post is shown. >> >> However, when viewing by "Thread" listing, each post shows the elapsed >> time since it was posted ie. the number of days, hours since it was >> posted (eg. 1 day, 2 hours). > > I don't see this. It may have been recently changed. Please visit the > archive of this list at > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/ > and if you see the issue there, post a URL of a page on which you see > it. No, I don't see it on the MM users' archive. The archive where I'm seeing it is HyperKitty version 1.3.4 on a Debian packaged MM 3.3.3 The problem lay therein? In the Hyperkitty docs there doesn't appear to be any mention of options or changes for the display of datetime/elapsed-time

2 years, 5 months

[MM3-users] Re: postorius configuration of the from-part

by Wolfgang Bock

Hello, thanks for your information. After creating the dmarc-entries in the DNS-databases everthing works as wanted! Regards Wolfgang Am 13.11.2019 um 06:02 schrieb Mark Sapiro: > On 11/12/19 2:27 PM, Wolfgang Bock via Mailman-users wrote: >> Hello, >> >> can someone give me an advice how I can configure in the >> postorius-menues the view of the from-part of my list-member like in >> this mailinglist: >> >> Wolfgang Bock_via Mailman-users_ <mailman-users(a)mailman3.org> > > The above is the result of Settings -> DMARC Mitigatations -> DMARC > mitigation action = "Replace From: with list address" > > You can apply that to only messages From: a domain the publishes a DMARC > policy of reject or quarantine or to all messages depending on DMARC > Mitigate unconditionally. > > >> case 1 reply goes to the list or to the member >> case 2 reply goes only to the list > > The DMARC Mitigatations settings are independent of the various reply > settings on the Alter Messages tab. >

6 years

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

by worik

On 27/02/19 11:54 AM, Mark Sapiro wrote: > On 2/26/19 2:11 PM, worik wrote: >> When I subscribe some body to to a list I on I get a notification that >> says it comes from changeme(a)example.com >> >> As far as I can tell no subscribers are getting mail with that, so this >> is not a crises. But it is untidy and I cannot find where to change it. >> >> SERVE_FROM_DOMAIN is set in the mailman-web/environment section of >> docker-compose.yaml (I am using the docker distribution...) > You set it in your mailman.cfg. As it says in mailman/config/schema.cfg > > There is no `mailman/config/schema.cfg` on my system. Should I raise a issue over at the docker-mailman github? I have: /opt/mailman/core/mailman-extra.cfg /opt/mailman/core/var/etc/mailman.cfg Should I change it in the second one? -- If not me then who? If not now then when? If not here then where? So, here I stand, I can do no other root(a)worik.org 021-1680650, (03) 4821804 Aotearoa (New Zealand)

6 years, 9 months

[MM3-users] Re: Subscribing users stuck in pending hell

by Quanah Gibson-Mount

--On Wednesday, May 24, 2023 3:34 PM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On May 24, 2023 9:45:45 AM PDT, Quanah Gibson-Mount > <quanah(a)fast-mail.org> wrote: > > >> That shell script seems to have errors: >> >>>>> pendings = getUtility(IPendings) >>>>> for token, data in pendings.find( >> ... token_owner=TokenOwner.subscriber, >> ... pend_type='subscription'): >> ... print("hello") >> ... >> Traceback (most recent call last): >> File "<console>", line 3, in <module> >> File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", >> line 85, in wrapper return function(args[0], config.db.store, *args[1:], >> **kws) >> TypeError: find() got an unexpected keyword argument 'token_owner' > > > Your Mailman core is too old for that script. Tell me your core version > and I will try to make one that works for you. Thanks Mark! We're hoping to upgrade to something more current next month. Right now apt shows: apt show mailman Package: mailman Version: 1:2.1.29-1+deb10u5 Regards, Quanah

2 years, 6 months

[MM3-users] Re: howto reallow a banned email ?

by Nicolas Pettiaux

much thanks. I use mailman 2 interface (and will switch soon to 3) i'll look asap. --- Nicolas Pettiaux - PhD - nicolas(a){educode,pettiaux}.be - Président de Educode asbl Informer, former et susciter la réflexion des acteurs du monde de l'enseignement face aux évolutions d'un monde numérique - http://2019.educode.be & http://2018.educode.be Le 2019-06-19 6:33, Mark Sapiro a écrit : > On 6/18/19 9:12 PM, Nicolas Pettiaux wrote: >> >> By mistake a user has been banned to post to mailman list. How can I >> allow him not only to post but also to become a member of a list ? >> >> I have not found any info on the web, or I have been unable to search >> correctly. > > > Do you have the Postorius web UI in your installation? If so go to the > list's Ban List and remove the unwanted entry. > > Or is this perhaps a Mailman 2 question? If so you'll find the ban_list > in the web admin UI at Privacy options... -> Subscription rules.

6 years, 5 months

[MM3-users] spam filtering (was: Re: list of subscribers)

by Peter Münster

On Sun, Feb 04 2018, Mark Sapiro wrote: > This would seem to be specific to your use case. I think in general what > we would want to display is the display_name from the list's member record. Ok, I see. Now I know, how to generate such list (email + full name) as site administrator, so it's ok for me. > We tried to send your copy of your post to you, but your MTA called it spam. > > Feb 4 19:38:09 mailman postfix/smtp[29085]: 89D4C8031E: > to=<pmlists(a)free.fr>, relay=mx1.free.fr[212.27.48.7]:25, delay=1.3, > delays=0.04/0/0.81/0.41, dsn=5.0.0, status=bounced (host > mx1.free.fr[212.27.48.7] said: 550 spam detected (in reply to end of > DATA command)) IMO, spam filtering should be done at user level, every user should be free to filter what he likes, not the MTA. Perhaps I should do it like you, and manage my own email relay host? I've tried to subscribe with an address at orange.fr but it does not seem to work, probably the same problem as with free.fr... -- Peter

7 years, 10 months

[MM3-users] Re: Postorius confirmation mails shown in uwsgi-error.log but not sent

by Abhilash Raj

Do you have something like this[1] in your settings.py file? [1]: https://gitlab.com/mailman/mailman-suite/-/blob/master/mailman-suite_projec… `EMAIL_BACKEND = 'django.core.mail.backends.console.EmailBackend'` `This is a dummy email backend which will basically only print the email to stdout, which seems to happen in your uwsgi-error.log. If you do, please comment it out and see if that solves your issue.` `Abhilash` On Sat, Mar 28, 2020, at 5:38 PM, Ralph Seichter wrote: > * Mark Sapiro: > > > What is the complete log message from uwsgi-error.log? > > I'll attach a typical log file to this message. It shows startup > messages followed by a recorded confirmation email. User name and > domain are obfuscated, but other than that the log is unchanged. > > -Ralph > > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > *Attachments:* > * uwsgi-error.log -- thanks, Abhilash Raj (maxking)

5 years, 8 months

[MM3-users] Re: How to delete user completely?

by William Oliver

On Fri, 2022-01-21 at 16:50 -0800, Mark Sapiro wrote: > 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. > Thanks! billo

3 years, 10 months

[MM3-users] Re: AttributeError: 'MailingList' object has no attribute 'get_requests_count'

by Shashikanth Komandoor

Hi Mark, Thank you very much for your response. I understood myself as quite ignorant even to find out the versions of each of the component. But my "mailman info" output looks like the below: *(venv3) [root@dlist-lsmgr mailman]# mailman info* *GNU Mailman 3.3.2rc2 (Tom Sawyer)* *Python 3.6.8 (default, Aug 10 2019, 06:54:07)* *[GCC 4.8.5 20150623 (Red Hat 4.8.5-36)]* *config file: /var/lib/mailman/mailman/var/etc/mailman.cfg* *db url: postgres://<username>:<password>@127.0.0.1/mailman* *devmode: DISABLED* *REST root url: http://localhost:8001/3.1/ <http://localhost:8001/3.1/>* *REST credentials: restadmin:restpass* *(venv3) [root@dlist-lsmgr mailman]# pwd* */var/lib/mailman/mailman* How to find out the versions of the each and every component of the mailman 3 like mailman core, mailmancilent, postorius, hyperikitty, mailman-hyperkitty, django-mailman3, mailman-suite and so, after installation? If I am running an old mailmanclient or older version of any other mailman component, please suggest how to upgrade either one or multiple components based on the requirement. Is there any link that would help me to upgrade ? I have used the link https://docs.mailman3.org/en/latest/devsetup.html to install the mailman 3 components. I expected that the procedure followed in this link would install the latest versions of the mailman 3 components. Please correct me if I am wrong. Is there any latest version compatibility table ? Also please suggest me an URL that would install the latest versions of mailman 3 components and allow me to do customizations related to our domain. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Mon, Oct 26, 2020 at 4:16 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/25/20 8:22 AM, Shashikanth Komandoor wrote: > > Hi Team, > > > > I am currently running Mailman 3 with version 3.3.2rc2 and > in > > built postfix version 2.10.1-6 on RHEL 7.5 with PostgreSQL 11.9 version > > with default values. As of now, we don't have any lists and just > installed > > software components only. > > > > After the installation and configuration, I have tried > > creating the domains and lists. I was successful in creating them but > when > > I tried to login and browse the lists using LDAP authentication, I am > > getting the "Mailman REST API not available. Restart Mailman core". > > > > I see the below trace in the mailmansuite.log. > > > > > *Traceback (most recent call last): File > > > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/mailmanclient/restbase/base.py", > > line 119, in __getattr__ return self._get(name) File > > > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/mailmanclient/restbase/base.py", > > line 86, in _get raise KeyError(key)KeyError: 'get_requests_count > ... > > > > I don't see any error messages in the mailman.log. And I > > also executed a few curl commands in getting the details of the lists > > created and list info which I got their results successfully. > > > > Could you please guide where exactly I am missing or do I > > need to make any changes in my customizations ? > > > I think the issue is your mailmanclient is too old. The version of > Postorius you are running requires mailmanclient >3.3.1 which is only > available from GitLab <https://gitlab.com/mailman/mailmanclient>. > > What version of Postorius is this? It appears to be >1.3.3. If you > install Postorius from unreleased code on GitLab, you have to install > all of mailman, mailmanclient and django-mailman3 as well. > > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

5 years, 1 month

[MM3-users] Re: very few moderation capabilities for moderators

by Guillermo Hernandez (Oldno7)

On 17/9/21 19:58, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > On 17/9/21 17:24, Mark Sapiro wrote: >> On 9/17/21 6:18 AM, Guillermo Hernandez (Oldno7) via Mailman-users >> wrote: >>> On 16/9/21 16:40, Mark Sapiro wrote: >>>> >>>> Are you asking what the equivalent MM 3 scripts would be? >>>> >>> More or less: I'm asking for a general direction here. I think I >>> cannot use tthe "withlist" method as before, inside a python script, >>> and I'm not sure how to do it. >> >> >> You can run scripts via withlist in Mailman 3 similarly to Mailman 2. >> See >> https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d… >> >> > First, thanks for the prompt response, Mark. > > Maybe I'm a little bit ofuscated, but I readed this doc many times > when I was searching how to do it... but I cannot imagine how to do a > shell or a python script, using the needed parameters, that sets hold > on a member of a list. > > I'll try to do some tests tomorrow. I've followed the indications of a mailman -C /usr/local/mailman3/var/etc/mailman.cfg shell --details I've been trying to "translate" the python script that I made for mailman2 to new mailman3, but obviously, I'm missing something. It seems that mailman cannot locate the "module" needed. The script is named "moderar.py": *-*-*-*-*-*-*-*-*-* (begin of /usr/local/mailman3/moderar.py) /usr/local/mailman3 # cat moderar.py #! /usr/local/bin/python3 # # script via withlist para moderar a pelo en mailman3 # import os import sys sys.path.insert(0, '/usr/local/mailman3') os.environ['PYTHONPATH'] = '/usr/local/mailman3' os.environ['DJANGO_SETTINGS_MODULE'] = 'settings' os.environ['MAILMAN_CONFIG_FILE'] = '/usr/local/mailman3/var/etc/mailman.cfg' import mm_cfg def moderar(mlist, member): if not mlist.Locked(): mlist.Lock() mlist.setMemberOption(member, mm_cfg.Moderate, True) mlist.Save() mlist.Unlock() *-*-*-*-*-*-*-*-*-* (end of /usr/local/mailman3/moderar.py) When I execute a mailman withlist -r moderar -l list_to_use(a)mydomain.com address(a)moderate.com The system returns: Traceback (most recent call last): File "/usr/local/bin/mailman", line 11, in <module> load_entry_point('mailman==3.3.4', 'console_scripts', 'mailman')() File "/usr/local/lib/python3.7/site-packages/click/core.py", line 829, in __call__ return self.main(*args, **kwargs) File "/usr/local/lib/python3.7/site-packages/click/core.py", line 782, in main rv = self.invoke(ctx) File "/usr/local/lib/python3.7/site-packages/mailman/bin/mailman.py", line 68, in invoke return super().invoke(ctx) File "/usr/local/lib/python3.7/site-packages/click/core.py", line 1259, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) File "/usr/local/lib/python3.7/site-packages/click/core.py", line 1066, in invoke return ctx.invoke(self.callback, **ctx.params) File "/usr/local/lib/python3.7/site-packages/click/core.py", line 610, in invoke return callback(*args, **kwargs) File "/usr/local/lib/python3.7/site-packages/click/decorators.py", line 21, in new_func return f(get_current_context(), *args, **kwargs) File "/usr/local/lib/python3.7/site-packages/mailman/commands/cli_withlist.py", line 293, in shell r = call_name(dotted_name, m, *run_args) File "/usr/local/lib/python3.7/site-packages/mailman/utilities/modules.py", line 69, in call_name named_callable = find_name(dotted_name) File "/usr/local/lib/python3.7/site-packages/mailman/utilities/modules.py", line 52, in find_name module = import_module(module_path) File "/usr/local/lib/python3.7/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1006, in _gcd_import File "<frozen importlib._bootstrap>", line 983, in _find_and_load File "<frozen importlib._bootstrap>", line 965, in _find_and_load_unlocked ModuleNotFoundError: No module named 'moderar' I've done a ln -s /usr/local/mailman3/moderar.py /usr/local/lib/python3.7/site-packages/mailman/bin/moderar.py But with the same result. And I'm not sure if I'm doing well importing "mm_cfg" in the script. My enviroment is open wide installation of mailman, python, etc. in a FreeBSD 12.2-RELEASE-p10 Mailman Core Version GNU Mailman 3.3.4 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.7.9 (default, Nov 6 2020, 21:14:59) [Clang 8.0.1 (tags/RELEASE_801/final 366581)] Postorius version: 1.3.5 If someone can give a hint it will be much appreciated.

4 years, 2 months

[MM3-users] Re: Weird hourly indexing error

by Mark Dadgar

On Jun 9, 2020, at 11:04 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > The `django-admin` command that is being run doesn't itself point to > your settings. In my case, I run django-admin via a wrapper that contains > ``` > #!/bin/bash > . /opt/mailman/mm/venv/bin/activate > cd /opt/mailman/mm > export PYTHONPATH=/opt/mailman/mm > export DJANGO_SETTINGS_MODULE=settings > django-admin $@ > ``` > The critical things are the exports of PYTHONPATH and > DJANGO_SETTINGS_MODULE. The former is the path to where your settings > module lives and the latter is its name without the .py extension. OK, making progress: mark@mail:/usr/local/bin$ !! ./mm3-admin shell Python 3.8.2 (default, Apr 27 2020, 15:53:34) [GCC 9.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. (InteractiveConsole) >>> from hyperkitty.models import Email >>> emails = Email.objects.all() >>> for email in emails: ... if email.content.find('\u200b'*5) >= 0: ... print('Found in ml {}, hash {}'.format( ... email.mailinglist.name, ... email.message_id_hash)) ... ./mm3-admin: line 6: 702058 Killed django-admin $@ Now what? - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 6 months

[MM3-users] Re: Problems with SPOOFED_UNAUTH

by M. Ede

Am 11.09.25 um 20:38 schrieb Mark Sapiro: > On 9/11/25 10:03, Stephen J. Turnbull wrote: >> >> I don't think Mark was suggesting that would help with the >> SPOOFED_UNAUTH problem. I read his mail as saying that it needs to be >> fixed because it breaks anonymous_list. > > Exactly. Issue is now reported at https://gitlab.com/mailman/mailman/-/ > issues/1241 > In my tests, I sent an email via an anonymized list from an external list member who signed his emails with DKIM. The email sent via the anonymized list still contained the DKIM header with the following information: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmx.de; s=s31663417; t=1757947718; x=1758552518; i=medebb(a)gmx.de; bh=vcgwKHYW2uGBjO0+fBhuE4cVWQCtMNWYPsAtoVGcSpU=; h=X-UI-Sender-Class:Message-ID:Date:MIME-Version:To:From:Subject: Content-Type:Content-Transfer-Encoding:cc: content-transfer-encoding:content-type:date:from:message-id: mime-version:reply-to:subject:to; b=efMRr8yABy1/lYtU+rDbUup/kNJlirY6jaBCCMRbu1mHZG+6aa5jwk2+p7xSs2An WI4aVD5Dm5LsUjEz6VIFn7mYF6yy2h7DFoFFKaysbE4SEx8z1Vz23Ob0K9KnOlUgK fX7C+WS1Cr4rg0arSWN/OhRMHZUYwUv6q9Kk7FQcM+92UepNNsgnYNtI9NmGryL36 Ui536gOGLLqg7tpS/RkRYSvSYonHgvnsS2kM5VFdC8Ikyb6RC1Xzy5Nj3pO8xFy// 2xABTzbMuA3jnSTQ5PxlLUT7gg4c8c9WvW18+IAUIJKvedyfWgZnGRUxtDbiFKrDF sbX47CSb1jW6b3UPOg== This means that both the domain and the email address of the original sender are included. Don't all DKIM headers also have to be removed from anonymized lists?

2 months, 4 weeks

[MM3-users] Re: Shunt Error Mail?

by Pete Ashdown

On 3/2/21 4:09 PM, Mark Sapiro wrote: > 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. This is good to know. I was concerned that shunting could happen due to HTML or message content (ie: not size).

4 years, 9 months

[MM3-users] Re: MAILMAN_ARCHIVER_KEY - 401 error

by Torsten R.

Mark Sapiro wrote: > The issue is not related to message content. > One possibility is that there is an incompatibility between > mailman-hyperkitty >= 1.2.0 and HyperKitty <= 1.3.4. that could cause > this. What are your versions? Understood, just wanted to mention that as I read it in another thread about the 401. Hyperkitty is 1.3.4 and mailman-hyperkitty is 1.2.0 > What is your setting in mailman-hyperkitty.cfg for base_url: base_url is set to https://www.fqdn.tld/mailman/hyperkitty > if you append api/ to that and do something like > curl base_url/api/ > it should return a page of documentation of the API. If that is the > case, the issue is almost certainly communicating the api key between > mailman-hyperkitty and HyperKitty I get some information back when appending /api/ to that URL mentioned above about REST API and some formats and endpoints. So, from your words it looks like there is some issue in the communication between mailman-hyperkitty and HyperKitty. Is there some place I could/should start looking or some log I should be examining (maybe some loglevel to be increased as well)?

3 years, 8 months

[MM3-users] Re: A few more MM3 questions

by Marc SCHAEFER

Re, On Wed, May 29, 2024 at 09:23:07AM -0400, Mark Sapiro wrote: > > 2) I imported a list and all messages get a footer of: > > %(web_page_url)slistinfo/%(_internal_name)s > > which I guess changed between MM2 and MM3; however when I > > look at that list configuration in the web interface of MM3, > > I see no templates defined, nor any clue where this is > > configured: where may I change this? > > import21 creates these templates in (I think in your case) > /var/lib/mailman3/templates. Yes, I used import21, and there are files there, and they contain the "web_page_url" that is the cause of the problem. May I just modify those files, and is there any way to see, in the web GUI, where those files are referenced? In the database itself, the template table is empty (as seen in the GUI) and I did not see the text "web_page_url" in a dump of the database, so I have some issues to understand how this is used by Mailman (except direct file access to /var/lib/mailman3/templates?)

1 year, 6 months

[MM3-users] Re: FYI: Django security releases issued: 4.0.6 and 3.2.14

by David Newman

On 7/7/22 1:20 PM, Mark Sapiro wrote: > On 7/7/22 12:44 PM, David Newman wrote: >> >> However, pip now throws a warning when looking at package info: >> >> (venv) mailman@somehost:/home/dnewman$ pip show mailman-web >> WARNING: Ignoring invalid distribution -jango >> (/opt/mailman/venv/lib/python3.9/site-packages) >> ... > > What does > ``` > ls -la /opt/mailman/venv/lib/python3.9/site-packages/-jango* > ``` > show? I suspect you have some spurious stuff there. The timestamps might > give a clue as to how it got there. > > If it shows anything, > ``` > rm -rf /opt/mailman/venv/lib/python3.9/site-packages/-jango* > ``` > will probably fix it. That was my first thought too. But there's nothing in that directory beginning with a hyphen, not even with the -a switch. The Django directories are as follows: django Django-3.2.14.dist-info django_allauth-0.47.0.dist-info django_appconf-1.0.5.dist-info django_compressor-3.0.dist-info django_extensions django_extensions-3.1.5.dist-info django_gravatar django_gravatar2-1.4.4.dist-info django_haystack-3.1.1.dist-info django_mailman3 django_mailman3-1.3.7.dist-info django_picklefield-3.0.1.dist-info django_q django_q-1.3.9.dist-info djangorestframework-3.13.1.dist-info dn

3 years, 5 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 Gilles Filippini

Gilles Filippini a écrit le 12/03/2021 à 01:41 : > Mark Sapiro a écrit le 12/03/2021 à 00:59 : >> On 3/11/21 3:10 PM, Gilles Filippini wrote: >>> >>> Looking at the offending message with 'mailman qfile', it appears it is >>> a legitimate one actually, sent from an Android phone. >>> >>> Couldn't hyperkitty be a bit less strict? >> >> >> Possibly. It looks like this may be >> <https://gitlab.com/mailman/hyperkitty/-/issues/271>, fixed? by >> <https://gitlab.com/mailman/hyperkitty/-/merge_requests/215>. What >> HyperKitty version is this? >> <https://gitlab.com/mailman/hyperkitty/-/merge_requests/215> is in 1.3.2. >> >> If your HyperKitty is >= 1.3.2, please file a new issue at >> <https://gitlab.com/mailman/hyperkitty/-/issues> > > This is Hyperkitty 1.3.4. > I'll file an issue tomorrow. Here it is: https://gitlab.com/mailman/hyperkitty/-/issues/346 Thanks, _g.

4 years, 9 months

[MM3-users] Re: Problem with debian uipgrade

by Lars Schimmer

Am 08.03.2022 um 21:08 schrieb Mark Sapiro: > Possibly one way to fix this is to run > ``` > django-abmin migrate socialaccount > ``` > where django-admin is the name of your django management command. > > Then running `django-abmin migrate` should succeed. The issue appears to > be due to the face that `django-admin migrate` runs the migrations in > alphabetical order by app. This is fine if migrations were run during > the period after socialaccount.0003_extra_data_default_dict was created > and before hyperkitty.0007_allauth_20160808_1604 was created, but it's > an issue in an installation that wants to migrate > hyperkitty.0007_allauth_20160808_1604 without having previously migrated > socialaccount.0003_extra_data_default_dict. Thx for your always competent answers. In this case I just needed to uncomment the not needed socialaccount lines in mailman3.cfg. As we do not use them. And now I hope for a debian package upgradem or I need to replace them with virtuelenv install as soon as I need to upgrade. MfG, Lars Schimmer -- ------------------------------------------------------------- TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723

3 years, 9 months

[MM3-users] Re: Caching problem with templates

by Mark

> On 6/26/25 04:25, Mark wrote: >> >> A footer template is created and initially it works as expected. >> >> Editing the footer template sees the new content written to the >> database, >> >> In addition to viewing the edited content in the database, the new >> template can also be viewed in Lynx on localhost at: >> >> http://localhost:8000/mailman3/api/templates/list/<IDENTIFIER>/list:member:regular:footer >> >> The problem is that the original template is being cached somewhere >> and the old footer persists in new emails. ================================= On 2025-06-26 16:10, Mark Sapiro wrote: > What does the database query > ``` > SELECT uri FROM template WHERE name = 'list:member:regular:footer' AND > context = '<IDENTIFIER>'; > ``` > return? ================================= The result of the query is: +--- uri +---- http://localhost:8000/mailman3/api/templates/list/<IDENTIFIER>/list:member:regular:footer +---- I should have also said, if I delete the template, emails still use the old footer -- not the Mailman default as I would have expected. And I had a look in /opt/mailman/mm/var/templates/lists/ -- nothing there.

5 months, 2 weeks

[MM3-users] Re: Missing Base64 encoding from control message reply

by Stephen J. Turnbull

Mark Sapiro writes: > The issue is the message declares > > Content-Transfer-Encoding: base64 > > but the body is not base64 encoded so the MUA tries to base64 decode it > and even though that's invalid, produces the garbled output. :-( > I tried to duplicate this in a test installation with the charset > for English set to utf-8, but I get a similar response but with > > Subject: =?utf-8?q?The_results_of_your_email_commands?= I think that's unfortunate. Not really a bug, but the RFCs recommend using the defaults (ie, US-ASCII) where that's possible. I wonder if it's possible to use email.policy to change that.[1] With respect to the actual problem, I don't have anything to say until we have more information about the relevant settings. Oh, I guess I also wonder if maybe the language doesn't have a translation for that message yet? Steve Footnotes: [1] Speaking of bugs, my MUA decoded that MIME word when it quoted the message even though it's not in the header! Aaargh.

2 years, 2 months

[MM3-users] Re: Migrating Mailman 3 lists

by Stephen J. Turnbull

Andrew Hodgson writes: > Mark Sapiro wrote: > >On 5/19/20 7:25 PM, Mark Dadgar wrote: > >> For reference my pgloader script looks like: > >> > >> load database > >> from sqlite:///var/lib/dbconfig-common/sqlite3/mailman3-web/mailman3web.db > >> into postgresql://mailman3:XXREDACTEDXX@localhost/mailman > >> > >> with include drop, create tables, create indexes, reset sequences, no truncate > Have you tried this without indexes and then run the migrate > script? It may re-create them as part of the schema upgrade > check. That was my immediate guess. I'm not an SQL expert, but I believe that sequences and indexes are different entities, they're both optimizations that you don't need (ie, ignoring performance), and implementations differ on how they're implemented. Eg, if sqlite implements them as tables, while PostgreSQL has a special data structure, you could run into this kind of behavior. I'm pretty sure that these will be recreated appropriate to the new database when the schema validator is done. But don't trust me, and *do* keep a backup. ;-) Steve

5 years, 6 months

[MM3-users] Re: List archives Recent Posts problem

by Mark Dadgar

On Jun 23, 2020, at 3:19 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/18/20 9:01 AM, Mark Dadgar wrote: >> In the last day or so, hitting the Recent page in my list archives results in a spinner and an error message: >> >> Internal Server Error: /mailman3/hyperkitty/list/trackjunkies(a)pdc-racing.net <mailto:mailman3/hyperkitty/list/trackjunkies@pdc-racing.net>/recent-threads >> >> AttributeError at /hyperkitty/list/trackjunkies(a)pdc-racing.net <mailto:hyperkitty/list/trackjunkies@pdc-racing.net>/recent-threads >> 'NoneType' object has no attribute 'subject' > > > Is this still an issue? > > If so, see the entire thread at > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> > for a possible solution. It’s still a problem. I restarted the whole machine and that did not fix it. I also tried to delete any row in the hyperkitty_thread table where starting_email_id was null and that did not return any deleted rows. mailman=> delete from hyperkitty_thread mailman-> where starting_email_id = null; DELETE 0 All of my member functions are still broken as well. :( - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 5 months

[MM3-users] Re: Templates

by Odhiambo Washington

On Tue, 17 Nov 2020 at 06:09, Mark Sapiro <mark(a)msapiro.net> wrote: > On 11/16/20 4:02 AM, Odhiambo Washington wrote: > > Hello good people, > > > > So today I decided that I should be looking at MM3 to see how far it can > > take me. > > I started from the templates and created one for a footer for non-digest > > messages. > > > How did you create this footer?. If you created it by creating a file in > Mailman's var/templates directiory, can Mailman read it? > > I went into Postorius and selected the list. It's the only one. Selected Templates -> New Template. root@gw:/opt/mailman/mm/var/templates/site/en # ls -al /opt/mailman/mm/var/templates/site total 24 drwxr-xr-x 3 mailman3 wheel 512 Jul 25 14:44 . drwxr-xr-x 3 mailman3 wheel 512 Jul 25 14:44 .. drwxr-xr-x 2 mailman3 wheel 512 Jul 25 14:51 en I cannot find anything specific to the particular list in the path. Mailman runs as mailman3, who owns all the files. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

5 years

[MM3-users] Re: spanish localization

by Victoriano Giralt

El sáb, 13-02-2021 a las 14:53 -0800, Mark Sapiro escribió: > What translations are those? Please give specific examples. What I am > saying is Mailman core 3.3.3 is currently up to date with weblate. There > are no Spanish translations for core done after 7 November in weblate > and weblate shows 100% completion for Spanish for Mailman core. Mark, please, how do you check when translations happened? Nov 7th is a very significant date for me (it is my wedding anniversary) and I'm 90% sure that I dedicated time to Weblate after that date... All strings related to Mailman (core, django_mailman3, postorius and hyperkitty) are translated into Spanish 100%, but the interfaces, after updating to the latest releases, are still in Englanish (more English than Spanish). This is not a fight, we want to help, but do not know how. Thanks! -- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN ================================================================== Note: signature.asc is the electronic signature of present message A: Yes. > Q: Are you sure ? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email ?

4 years, 10 months

[MM3-users] Re: Domain admin

by Johannes Winter

Am Wed, 25 Apr 2018 08:39:58 -0700 schrieb Mark Sapiro <mark(a)msapiro.net>: > On 04/24/2018 11:57 PM, Johannes Winter wrote: > > > > We would like to give our users the priviledge to create lists per > > domain. I Haven't found any options for that in the web interface. > > > > Is this possible somehow with mailman3? > > > It is not currently possible. From the point of view of Mailman Core, > anyone who can run the 'mailman' command or access the REST API can > create domains and lists. > > Postorius could support this in some way and could maintain it's own > 'authorized users' data, but it would be better to also add some > concept of domain admin to core. > > These would be significant changes. > A possible workaround could be to create several webhosts to control access rights to the mailing lists. At least I understand the option to create new "web-hosts" in "add domain" in this way. But I haven't found any further information for setting up multiple web-hosts. Is there any yet?

7 years, 7 months

[MM3-users] Re: Caching problem with templates

by Mark

> On 6/28/25 21:50, Mark wrote: > > > > Yes, I thought so too. I also tried 0d -- which wrote the expiry > > date > > the same as the created date (to the second). > > > > # /etc/mailman3/mailman.cfg > > [mailman] > > cache_life: 0d > > > > But, just as with writing in a past date, it didn't solve the > > problem. > > I also spun up a brand new server to thrash it out there, but no > > joy > > there either. > > On Sat, 2025-06-28 at 22:55 -0700, Mark Sapiro wrote: > This is a different issue. See > https://gitlab.com/mailman/mailman/-/issues/1231 > > The template is not removed from the cache until the next run of the > task runner which defaults to running every hour. > Dang! If you know, you know. Thank you for that, and the patch information. I'll leave my hack in place for now (it works) until the next release. My brain is fried from the last couple of days getting to grips with this. Best, Mark

5 months, 2 weeks

[MM3-users] Re: Problems with New MM3 Installation

by Jeff

Thanks Mark and Abhilash (who responded separately). I have worked out all the issues I was having and now the list is running smoothly. The trick for POSTORIUS_TEMPLATE_BASE_URL with uwsgi was "http://[hostname]/mailman3/ <http://[hostname]/mailman3/>“. I appreciate all the help I’ve received from this mailing list. > On May 11, 2021, at 11:43 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 5/11/21 7:46 PM, Jeff wrote: >> >> I really appreciate your assistance. New messages are now being archived as expected, but I still have a few small remaining issues to work out with my MM3 installation: >> >> 1) some emails that arrived before I got the archive working are still sitting in: >> >> /usr/local/mailman3/mm/var/archives/prototype/[listname]@[domain]/new >> >> Strangely this includes at least one email that was archived. Should this directly be cleared as messages are archived? Is there a way to force it to be cleared? > > /usr/local/mailman3/mm/var/archives/prototype/[listname]@[domain] is a > collection of messages in maildir format. This is how the prototype > archiver stores messages. This has nothing to do with HyperKitty. It is > a separate archiver. If you don't want messages to be stored there, you > can disable the prototype archiver for the list by unchecking prototype > in Postorius -> Settings -> Archiving -> Active archivers or disable it > entirely for the installation by setting > ``` > [archiver.prototype] > enable: no > ``` > in mailman.cfg > >> 2) Some messages that arrived while I was having other problems with the setup have been stored in: >> >> /usr/local/mailman3/mm/var/queue/shunt >> >> What should I do to get these messages processed? > > > Assuming the issues that caused them to be shunted have been fixed, just > run the command > ``` > mailman unshunt > ``` > >> 3) Similar to above, some messages are in: >> >> /usr/local/mailman3/mm/var/queue/bad >> >> How can I get these messages processed? > > > First examine the messages with > ``` > mailman qfile /usr/local/mailman3/mm/var/queue/bad/<file> > ``` > To be sure you want them. Also examine mailman.log for the times they > were stored in the `bad` queue. You are looking for 'Skipping and > preserving unparseable message: <file>' and/or 'SHUNTING FAILED, > preserving original entry: <file> messages and you want to determine > which runner preserved the message. There may be a 'whichq' entry in the > message's metadata in which case, that's the answer. > > Once you have determined the queue, you can just move the .psv file from > the bad queue to the appropriate queue, renaming it from .psv to .pck in > the process. > > >> 4 Modified the template for “list:admin:action:post” through Postorious and emails that arrived after that were put in the “shunt” queue. I traced this problem to POSTORIUS_TEMPLATE_BASE_URL. By default, it is set to "http://localhost:8000 <http://localhost:8000/>” which is where uwsgi is listening. However, uwsigi is listening for uwsgi:/ not http://. Should I change POSTORIUS_TEMPLATE_BASE_URL to “uwsgi://localhost:8000 <uwsgi://localhost:8000>” or keep http but make it something else? > > > I know little about uwsgi. setting it to `uwsgi://localhost:8000` might > work. You could also set it to the base URL that a user would use to > access the web UI, e.g. `https://example.com` and that would presumably > be proxied to uwsgi. For example, on the server for this list we have > ``` > POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.mailman3.org' > ``` > which gets proxied to gunicorn, but the idea is the same. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 7 months

[MM3-users] Re: How to strip DKIM headers on a domain level or a list level

by Joel Lord

On 11/23/20 11:15 PM, Mark Sapiro wrote: >> # If the following is set to a non-empty string, that string is the name of a >> # header that will be added to personalized and VERPed deliveries with value >> # equal to the base64 encoding of the recipient's email address. This is >> # intended to enable identification of the recipient otherwise redacted from >> # "spam report" feedback loop messages. For example, if >> # RCPT_BASE64_HEADER_NAME = 'X-Mailman-R-Data' >> # a header like >> # X-Mailman-R-Data: dXNlckBleGFtcGxlLmNvbQo= >> # will be added to messages sent to user@@example.com. >> RCPT_BASE64_HEADER_NAME = '' >> >> >> This hasn't been implemented for Mailman 3 but could be if there's demand. I hadn't spotted that in Mailman 2.1, I will go looking for it there. My 2.1 server has not moved to 3 yet for several reasons, but it's getting close. This feature would get me just a bit closer. -- Joel Lord

5 years

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

by Odhiambo Washington

On Sat, Oct 2, 2021 at 8:58 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/2/21 4:26 AM, Odhiambo Washington wrote: > > On Thu, Sep 30, 2021 at 4:09 PM Abhilash Raj <maxking(a)asynchronous.in> > > wrote: > >> > >> Yes, please update it to have SITE_ID = 2 to correspond to the site you > >> want and restart. > > > > > > I did this, but there is still a problem: The hyperkitty URL still shows > > example.com. > > Maybe I need to re-import the database to clear this? > > > The SITE_ID setting affects the domain displayed at the top left of > HyperKitty pages. Is this the correct domain? > No. Mine is showing example.com > > What hyperkitty URL are you talking about? > My url (nothing to hide anyway) is https://lists.fem-international.org/mailman3/hyperkitty/list/members@lists.… . Screenshotted below [image: msapiro.PNG] -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' :-)

4 years, 2 months

[MM3-users] Re: MM3 Postfix FROM header issue

by Stephen J. Turnbull

Mark Sapiro writes: > Presumably that's the 'Recipient address rejected: User unknown in > virtual alias table' message, but I see no virtual_alias_domains in > your posted main.cf. I'm pretty sure that what's going on here is that the message is coming in from outside, Postfix runs down the various relays (including local delivery) available, none matches, the last in line is virtual aliases, and that table is empty so the user is unknown. That's the only way I can see the sender_canonical_maps variable affecting *recipient*-based decisions, by making it look like the sender is local, and so enabling delivery to non-local addresses. Why a Mailman list appears to be non-local is a question I am not sure. My guess is myhostname = localhost because Postfix doc says mydomain "is derived from $myhostname by stripping off the first part (unless the result would be a top-level domain)," so literally "localhost" is the only deliverable domain left, and some-list(a)the.actual.dom doesn't work. Except that the.actual.dom should be in postfix_domains.db, so ... ???? Steve

1 year, 11 months

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

by Ruth Ivimey-Cook

On 24/06/2020 00:20, Mark Sapiro wrote: > Go to your Django admin web UI and look at your Django Mailman 3 Mail > domains. This will be at a URL like > https://greyarea-web1.cam.ivimey.org/admin/django_mailman3/maildomain/ > > Do you see this domain there? If so, delete it. I hadn't logged in as admin before, so having done so I can now confirm that having done so this screen shows "0 mail domains" Because I could, I then visited "VIEW SITE" and see a mailing lists page, which is I think the same one I have been trying to visit, except of course now I am logged in. I do now see the correct, and only, mailing list configured on the core server. Returning to the previous "maildomain" page, that now shows the expected mailing list as well. Other admin pages seem to be working fine as well. I think, possibly, that it is now installed and working. ... But I don't know why. Ruth -- Software Manager & Engineer Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

5 years, 5 months

[MM3-users] Re: timezone in hyperkitty

by matthew_saunders＠harvard.edu

Mark Sapiro wrote: > On 6/29/20 12:18 PM, Marco Marinello wrote: > > I'm expirencing the same behaviour in Postorius. Is > > it possible to set a default timezone for new users? Already set it in settings_local.py > > but not having any effect, still seeing "Africa/Abidajin" in new users. > > Do you mean the users time zone as displayed in the user's profile? This > is a Django setting and the default should come from the TIME_ZONE > setting in settings_local.py, at least if USE_TZ is set True I'm seeing the same behavior on my development site, and I was even able to reproduce this when I created my account on this very site moments ago using OAuth. If you check the django_mailman3_profile table in the DB, I expect you'll see that my timezone record is blank (since I haven't touched it from the Accounts page). FWIW, it's empty... not NULL, since there's a not-null constraint on this field. Is it possible to have this set to a default (non-empty) value somehow? TIME_ZONE & USE_TZ isn't doing it.

5 years, 4 months

[MM3-users] Re: What to backup?

by Alain Kohli

I have noticed that especially the var/messages directory has a rather considerable size compared to the rest. What exactly is this for and what would be the consequences if that was lost? And more generally, would not backing up var/ at all only result in the loss of some short term data (e.g. messages that are held or currently processed) or would long term data also be lost? Or in other words, what exactly would be non-recoverable if that isn't backed up? On 5/22/19 5:21 PM, Mark Sapiro wrote: > On 5/22/19 6:31 AM, Alain Kohli wrote: >> Hi >> >> What exactly are we supposed to include in our mailman backups? >> Obviously the database, but are there any other files that should be >> included to make sure we can properly restore? > > I would backup all of Mailman's var/ directory. Additionally, I would > backup the directory where Haystack's backend search engine stores its > indices. For the default Whoosh backend with default settings this is > the fulltext_index/ directory in the same directory as your Django > settings.py file. >

6 years, 6 months

[MM3-users] Re: Manual setup - permissions

by Tobias Hachmer

Hi Mark, thanks for your response. On 9/23/19 1:29 AM, Mark Sapiro wrote: > On 9/22/19 2:11 AM, Tobias Hachmer via Mailman-users wrote: >> >> Now, running the scheduled tasks (which run from user+group "nginx") for >> django I ran into permission problems, because the nginx user can't >> access/write to the needed files in /opt/mailman3/core/... >> >> I would appreciate any hints how to run the different peaces of mailman3 >> with the correct user/groups/permissions. > > > Set up everything as user:group mailman3:mailman3. I.e., > > chown -R mailman3:mailman3 /opt/mailman3/web > > and set the uwsgi service to drop privileges to user+group "mailman3". So simple, now the scheduled tasks are working, but the whole web service did not work because the web server user nginx can't access and write to the uwsgi socket anymore /opt/mailman3/web/project/run/uwsgi.sock. # chown -R nginx:mailman3 /opt/mailman3/web This works for all. But isn't it a security risk that e.g. manage.py and settings.py is read- and writeable by the webserver? Regards, Tobias

6 years, 2 months

[MM3-users] Re: xapian db corruption - xapian.DatabaseCorruptError: Couldn't read enough (EOF) ??

by Odhiambo Washington

On Mon, Jul 29, 2024 at 9:35 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/29/24 03:27, Odhiambo Washington via Mailman-users wrote: > > Today, my hourly cron job has generated an error and continues to do so > > every hour: > > > > ``` > > Subject: Cron <mailman@gw> /opt/mailman/mm/bin/django-admin runjobs > hourly > > ``` > > > > Not sure what caused this. Perhaps a reboot when the cronjob hadn't > > completed? And a possible manual remedy would be to wipe the indexed db > and > > let the cron run again? > > > Or maybe just run `/opt/mailman/mm/bin/django-admin rebuild_index Nice to know. I just deleted the contents of the xapian_index folder and then ran the cronjob. Solved. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 4 months

[MM3-users] Re: User cannot reset password

by Greg Newby

On Sun, Aug 11, 2024 at 11:10 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 8/11/24 10:56, Greg Newby wrote: > > I imported MM2.1 lists to Mailman3 (using import21 - details are in my > > previous messages to mailman-users), and have had a couple of reports of > > people for whom the password reset function via "Forgot password" on the > > list login screen doesn't work as expected. > > > Django (web) accounts (Postorius and HyperKitty) are separate from > Mailman core. Users inported from MM 2.1 do not have web accounts. They > have to sign up, not request a password reset. > 1. Will the new (Django) and imported (Postorius) usernames automatically be matched to the same email address? The goal is for someone to use the web-based front end to manage their migrated subscriptions. 2. How can I customize the email that went to users who selected "Forgot password?" ( You are receiving this email because you, or someone else, tried to access an account with email I didn't find that string in the source code. Thanks as always! ~ Greg

1 year, 4 months

[MM3-users] Re: Search problem in 3.2.1?

by Mark Dadgar

On Oct 22, 2019, at 6:44 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 10/22/19 7:51 AM, Mark Dadgar wrote: >> Anyone seen this before? This is the result of any search query I run. I installed ElasticSearch as the search engine yesterday and this is the result. It is still indexing (large archives). > > > How did you install ElasticSearch. What ElasticSearch version? From .deb, version 5.6.16. > This is a bug in HyperKitty. We've never encountered it, but the code at > <https://gitlab.com/mailman/hyperkitty/blob/master/hyperkitty/views/search.p…> > only considers the whoosh and xapian backends and needs to be updated > for elasticsearch. I've reported that at > <https://gitlab.com/mailman/hyperkitty/issues/263>. Hmm, maybe I’ll take another shot at getting Xapian running then. Whoosh ran for 5+ days trying to index my archive of 556,000+ messages before I gave up. Thanks for your help, Mark. Much appreciated. If we ever bump into each other here in the Valley, I owe you a beer or 9 for all the value I’ve gotten from mailman over the years. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

6 years, 1 month

[MM3-users] Re: Moderation Action Changed After Import

by Brian Carpenter

On 2/12/21 4:21 PM, Mark Sapiro wrote: > Yes, You did the right thing. I was mislead by "He said the previous > moderation was the list's default which was hold for moderation." which > is Mailman 3 terminology. > > The list does need to be created first, but it should be a new list with > no members, owners, etc., not an operational Mailman 3 list. > > So, it seems that most of the members of the MM 2.1 list were moderated > and the list's member_moderation_action was Reject. Is this not the case? Sorry for the wrong terminology I can't confirm what was set on the old MM2 list as it is no longer accessible. I am just going on the word of the List Owner. My opinion is that the moderation for those list members were set to Reject on the previous MM2 list. I am mainly interested to see if you know of this happening to anyone else and/or perhaps there is an existing bug that could impact the moderation settings of imported MM2 lists. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 10 months

[MM3-users] Re: mailman3-web and the django middleware problem

by Thomas Stein

Am 2024-04-25 22:03, schrieb Mark Sapiro: > On 4/25/24 12:34, Thomas Stein wrote: >> >> I'm not sure how to add that to my django settings. Adding: >> >> x = list(MIDDLEWARE) >> x.insert(0, 'allauth.account.middleware.AccountMiddleware') >> MIDDLEWARE = x >> >> did not help. Any hints? > > I don't know how things are arranged in the Debian/Ubuntu package, but > you may have a settings.py which at the end does something like > ``` > try: > from settings_local import * > except ImportError: > pass > ``` > If that is the case, adding the above snippet to the end of > settings_local.py should work. Yes, that's the case. I added the snippet in question to settings_local.py but this leads to another error: File "/usr/share/mailman3-web/settings.py", line 503, in <module> from settings_local import * File "/usr/share/mailman3-web/settings_local.py", line 194, in <module> x = list(MIDDLEWARE) ^^^^^^^^^^ NameError: name 'MIDDLEWARE' is not defined dpkg: error processing package mailman3-web (--configure): I hope you can helo again. cheers, t.

1 year, 7 months

[MM3-users] Re: MM2.1 -> MM3.3 migration. To hold or not hold

by mark＠suburbia.org.au

Once again, thanks for taking time to reply. Mark Sapiro wrote: > On 11/18/24 04:12, mark(a)suburbia.org.au wrote: > This should not happen. In the message as delivered to the list what do > you see in the X-Mailman-Rule-Misses: header and the > X-Mailman-Rule-Hits: header if any? ``` X-Mailman-Version: 3.3.8 X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address X-Mailman-Rule-Hits: member-moderation ``` > What if anything is in the lists Accept these non-members setting? Default action to take when a member posts to the list: Hold for moderation Default action to take when a non-member posts to the list: Hold for moderation Emergency Moderation: No Accept these non-members: (none listed) Hold these non-members: (none listed) If you would like me to enable debugging and do another test, I'm happy to. I will admit given the odd behaviour that there's a (small, unexpected) chance that there were settings changed or made during the process by another moderator, but that is not the belief at the moment. cheers, Mark

1 year

[MM3-users] Re: All addresses in a bounced list posting seem to be considered as bouncing

by Andy Smith

Hi Mark, On Fri, Sep 30, 2022 at 01:16:10PM -0700, Mark Sapiro wrote: > What is your version of flufl.bounce? I'm using Debian stable, and this is what is packaged: $ dpkg -l | grep flufl ii python3-flufl.bounce 3.0.1-1 all email bounce detectors (Python 3) > I suspect this is https://gitlab.com/warsaw/flufl.bounce/-/issues/12 which > was fixed in flufl.bounce 4.0 and upgrading to 4.0 will fix this. So that probably answers that then. Hmm, I wonder about the best way to proceed. The next stable release of Debian will have something that calls itself 4.0-2 and looks like it is fixed there: https://salsa.debian.org/python-team/packages/flufl.bounce/-/blob/master/fl… so maybe I can ask for that package to be put in stable-backports. I think the other option might be to remove system package python3-flufl.bounce, add it back with "equivbs" so that its system dependencies think it is present and then install the latest one from pip. I'll report the bug in Debian anyway. Thanks! Cheers, Andy

3 years, 2 months

[MM3-users] Re: High memory usage

by Philip Colmer

One small correction: > The largest is 15K messages, then 2K then 1K. That should be *discussions*, not messages. The message count is way higher than the discussion count. Philip On Wed, 16 Feb 2022 at 08:18, Philip Colmer <philip.colmer(a)linaro.org> 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. > > So, as Prasanth said, we doubled the memory available and stuck an alarm > on it to trigger when usage exceeded 85% for 5 minutes. I've saved a > screenshot of the monitored memory usage over the last couple of weeks: > > https://1drv.ms/u/s!Aq7dn8GDGLdCodsU-pybJBdckxWU1A?e=BJY1UA > > (It is stored on OneDrive in case you don't recognise the URL format) > > We changed the server on 4th February to the larger memory size. On 11th > Feb, it triggered the alarm and we rebooted the server. Memory usage is > starting to climb again, albeit not at the pace that it was previously. > > What is particularly curious for us is that we have four Mailman 3 > servers. Two of them are single domain and two are hosting two domains. > This server is one of the servers hosting two domains, but it is also the > ONLY one of the four servers exhibiting this memory pattern. By comparison, > the memory usage for the other server hosting two domains looks like this: > > https://1drv.ms/u/s!Aq7dn8GDGLdCodsVyEufkeQqit_cGA?e=ifrJHs > > The biggest difference we are aware of with the "problematic" server is > that some of the list archives are quite large by comparison with our other > servers. The largest is 15K messages, then 2K then 1K. The other three > servers have lists with relatively small archives by comparison (double or > triple digits at worst). > > Finally, and just FYI, we're using PostgreSQL for the database and Xapian > for the indexing engine. > > Regards > > Philip > > On Tue, 15 Feb 2022 at 16:36, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 2/15/22 08:11, Stephen Daniel wrote: >> > TL;DR: quite likely your system has plenty of memory and is operating >> > normally. >> ... >> > On Tue, Feb 15, 2022 at 5:28 AM Prasanth Nair <prasanth.nair(a)linaro.org >> > >> > wrote: >> > >> >> Hi, >> >> >> >> We are having an issue with high memory usage on our Mailman3 server. >> >> Initially, our server had 16GB RAM and the memory usage went up from >> 5% to >> >> 92% within a week. So, we increased the memory capacity to 32GB RAM >> and we >> >> can see that the memory usage is going up in the same pattern. >> >> >> >> Any idea why it is happening? or any suggestions? >> >> >> Just for reference, mail.python.org supports 231 MM 2 lists and 182 MM 3 >> lists with 16 GB of ram and no swap. >> >> The server that supports this list and also the www.list.org web site >> has 4 GB of ram and no swap. >> >> -- >> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, >> San Francisco Bay Area, California better use your sense - B. Dylan >> _______________________________________________ >> Mailman-users mailing list -- mailman-users(a)mailman3.org >> To unsubscribe send an email to mailman-users-leave(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> >

3 years, 9 months

[MM3-users] Re: Disable archives per list

by Bernd Wurst

Hello. Thank you for your answers. Am 25.02.21 um 22:01 schrieb Mark Sapiro: > 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. This will take effect for all lists at once, I suppose. :( > I'm not sure what you mean by "custom archiver settings", but other than > enable/disable and public/private, probably not. Hyperkitty has a rather cool frontend but stores all messages from all lists together in one database table. Additionally, neither Mailman nor Hyperkitty seems to know or tell anything about archive sizes of a list. This is horribly for accounting. So I thought if I can have a separate hyperkitty installation per user without having to duplicate the whole mailman. Alternatively, I'd like to enable archiving only for some customers that buy a suitable plan. I did not really get into mailman plugins. Is is possible for plugins to hook into such settings? I could not really find examples for plugins. regards, Bernd

4 years, 9 months

[MM3-users] Re: mailman 3.x upgrade and downgrade

by C. Souza

On Tue, Jul 12, 2022 at 12:21 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/12/22 6:12 AM, skooperit(a)gmail.com wrote: > > Hi all, > > > > I have a few contradictory questions. > > > > 1. How to upgrade the 3.x version? > > > > 2. Is it possible to migrate (downgrade) the lists from mailman 3.x to > 2.1? > > > > 3. If so, what would be the best way to do that? > > > > > > My mailing list server is running on a CenOS-7x with postgreSQL and the > following mailman packages: > > > > django-mailman3 1.3.5 > > mailman 3.3.2 > > mailman-hyperkitty 1.1.0 > > mailman-web 0.0.3 > > mailmanclient 3.3.2 > > postorius 1.3.3 > > > > We have ~200 lists with more than a decade of history. > > > So you have installed Mailman 3, apparently following > https://docs.mailman3.org/en/latest/install/virtualenv.html. There is a > caveat. Current released versions of HyperKitty (I don't see your > version above) don't work with mistune >= 2.0.0. > > This is https://gitlab.com/mailman/hyperkitty/-/issues/431, fixed by > https://gitlab.com/mailman/hyperkitty/-/merge_requests/379 but not yet > released. > > If your installed mistune is not 2.0.0rc1, you can work around this with > this patch > ``` > --- a/hyperkitty/lib/renderer.py > +++ b/hyperkitty/lib/renderer.py > @@ -4,7 +4,7 @@ from django.conf import settings > > import mistune > from mistune.plugins.extra import plugin_url > -from mistune.scanner import escape_html, escape_url > +from mistune.util import escape_html, escape_url > > > class MyRenderer(mistune.HTMLRenderer): > ``` > Or you can downgrade mistune with > ``` > pip install mistune==2.0.0rc1 > ``` > in your virtualenv. > > To answer your questions, to migrate your lists, you use `mailman > import21` and to migrate archives, `mailman-web hyperkitty_import`. Give > these commands with the `--help` option for more info. > > Downgrading lists from Mailman 3 to Mailman 2.1 is not currently > possible. There is no inverse to `mailman import21`. You can export a > HyperKitty archive as a mbox to use as input to Mailman 2.1s bin/arch. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Thanks Mark. You're right it was installed in a virtualenv using pip. I can't see the mistune package, maybe it wasn't a requirement for that version of mm3. 1 Package Version 2 ------------------- ---------- 3 aiosmtpd 1.2.4 4 alembic 1.5.3 5 arrow 0.17.0 6 asgiref 3.3.1 7 atpublic 2.1.2 8 authheaders 0.13.0 9 authres 1.2.0 10 bleach 3.3.0 11 blessed 1.17.12 12 certifi 2020.12.5 13 cffi 1.14.4 14 chardet 4.0.0 15 click 7.1.2 16 cmarkgfm 0.5.2 17 cryptography 3.3.1 18 decorator 4.4.2 19 defusedxml 0.6.0 20 Django 3.0.12 21 django-allauth 0.44.0 22 django-appconf 1.0.4 23 django-compressor 2.4 24 django-extensions 3.1.0 25 django-gravatar2 1.4.4 26 django-haystack 3.0 27 django-mailman3 1.3.5 28 django-picklefield 3.0.1 29 django-q 1.3.4 30 djangorestframework 3.12.2 31 dkimpy 1.0.5 32 dnspython 2.1.0 33 docutils 0.16 34 falcon 2.0.0 35 flufl.bounce 3.0.1 36 flufl.i18n 2.0.2 37 flufl.lock 3.2 38 gunicorn 20.0.4 39 HyperKitty 1.3.3 40 idna 2.10 41 importlib-resources 5.1.0 42 lazr.config 2.2.3 43 lazr.delegates 2.0.4 44 mailman 3.3.2 45 mailman-hyperkitty 1.1.0 46 mailman-web 0.0.3 47 mailmanclient 3.3.2 48 Mako 1.1.4 49 MarkupSafe 1.1.1 50 networkx 2.5 51 nose 1.3.7 52 oauthlib 3.1.0 53 packaging 20.9 54 passlib 1.7.4 55 pip 21.0.1 56 postorius 1.3.3 57 psycopg2-binary 2.8.6 58 publicsuffix2 2.20191221 59 pycparser 2.20 60 Pygments 2.7.4 61 PyJWT 2.0.1 62 pyparsing 2.4.7 63 python-dateutil 2.8.1 64 python-editor 1.0.4 65 python3-openid 3.2.0 66 pytz 2021.1 67 rcssmin 1.0.6 68 readme-renderer 28.0 69 requests 2.25.1 70 requests-oauthlib 1.3.0 71 rjsmin 1.1.0 72 robot-detection 0.4 73 setuptools 39.2.0 74 six 1.15.0 75 SQLAlchemy 1.3.23 76 sqlparse 0.4.1 77 typing-extensions 3.7.4.3 78 urllib3 1.26.3 79 uWSGI 2.0.19.1 80 wcwidth 0.2.5 81 webencodings 0.5.1 82 wheel 0.36.2 83 Whoosh 2.7.4 84 zipp 3.4.0 85 zope.component 4.6.2 86 zope.configuration 4.4.0 87 zope.deferredimport 4.3.1 88 zope.deprecation 4.4.0 89 zope.event 4.5.0 90 zope.hookable 5.0.1 91 zope.i18nmessageid 5.0.1 92 zope.interface 5.2.0 93 zope.proxy 4.3.5 94 zope.schema 6.0.1

3 years, 5 months

[MM3-users] Re: ARC

by Marvin Gülker

Am 13. August 2019 um 05:42 Uhr -0700 schrieb Mark Sapiro: > The question is not whether they support ARC, but whether they will > trust you. Well. That's nothing new, given that GMail and Microsoft liberally reject e-mail from small providers for no reason anyway (I have experienced it myself). If this situation doesn't change with ARC, I can live with this (by paying for an SMTP relay provider that proxies my e-mail). However, I thought the entire point in ARC was fixing automatic rejections caused by DMARC invalidation by mailing lists, which are vital for so many open-source projects (including Mailman iself). If ARC falls short of solving that problem, because the large providers do not automatically trust ARC, then supporting ARC on my mailing list server is kind of void. Why should almighty Microsoft trust my small personal mailing list server? ARC can only achieve its goal with black-listing untrusted relays rather than white-listing known good ones, because it is simply unfeasable to manually maintain a list of all open-source project mailing lists in the entire world. I could set a new one up tomorrow, how should you know? -- Blog: https://mg.guelker.eu

6 years, 4 months

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

by Brian Carpenter

On 4/3/21 5:04 PM, Mark Sapiro wrote: > On 4/3/21 1:45 PM, Brian Carpenter wrote: >> I have run several tests. It looks like on the 'Maximum number of >> recipients' setting, a 2 means 1. If I set it to 2, I can have the >> listname(a)listdomain.com only. If I have a CC, it comes to me for >> moderation. If I set it to a 3, I can send out to >> listname(a)listdomain.com plus a CC. If I set it to 3 and add 2 CC's plus >> the listname(a)listdomain.com address, it comes to me for moderation. > > I understand it's confusing, but it's been that way since the beginning > of Mailman 2.1. The docs at > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rules/docs…> > say "For backward compatibility, the message must have fewer than the > maximum number of explicit recipients." > > I agree the description in Postorius could be clarified see > <https://gitlab.com/mailman/postorius/-/issues/515>. > That explains it. Thanks for solving this mystery. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 8 months

[MM3-users] Re: Twitter OAuth2

by Stephen J. Turnbull

Mark Sapiro writes: > 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. Yeah, but then I (@yasegumi@twitter) could log in as yasegumi(a)example.com and every other yasegumi in the world. There probably aren't any of those that aren't me, but of the 30 kids in my 6th grade class 5 were named something with the diminuative "Steve", and we also had one Stephanie. So I could log in as steve(a)turnbull.sk.tsukuba.ac.jp (that's me) or steve(a)xemacs.org (that's not me, I'm stephen(a)xemacs.org) or steve(a)any.old.com. Not good. Also, I wouldn't trust Musk's Twitter with no security staff left to give out only confirmed email addresses. If they give out any address you gave them, then anybody can spoof anybody. So I would advise not using Twitter as an idP under any conditions, unless it's to prove you own a Twitter handle. Steve

2 years, 11 months

[MM3-users] Re: mailman admin (django) interface does not work anymore after deleting website example.com

by Torge Riedel

Am 10.03.19 um 16:44 schrieb Mark Sapiro: > On 3/10/19 8:18 AM, Torge Riedel wrote: >> I deleted the existing "example.com" and added a new one >> "lists.mydomain.de". >> >> Now the admin (django) interface always gives "An error occurred while >> processing your request". After one of the first navigation clicks I saw >> a message that "site with id 1 is missing". > > In your Django settings your have > > SITE_ID = 1 > > which pointed to the example.com domain you deleted. > > You need to override this in settings_local.py. Probably > > SITE_ID = 2 > > but if that doesn't work, try '0' > Ah, thank you Mark. That makes a kind of sense. I changed the database directly to fix it. And renamed example.com to lists.mydomain.de. Now the error is gone. I'm wondering why the initial database set up of postorius (?) adds "example.com". Is there a way to directly add my domain instead? Somewhere in settings_local.py?

6 years, 9 months

[MM3-users] Re: duplicate SITE_IDs and broken /postorius/lists/ display; Mailman Client

by Stanisław Findeisen

On Thu, Mar 24, 2022 at 09:27:06PM -0700, Mark Sapiro wrote: > The issue is client.create_domain doesn't support setting a Web Host. Web Hosts are the sites in the django_site table and SITE_ID is the id of > the table entry. See `sites` in the Django admin UI. > > So when you create a domain with client.create_domain it gets arbitrarily assigned to a `site` Ok thanks, this is good to know. How about mailing list creation using Mailman Client, like this? domains = client.domains domains = list(filter(lambda x: (domain_name == x.mail_host), domains)) # .. check if domains is a singleton list .. domain1 = domains[0] domain1.create_list(list_name, style_name=style_name) Do you know of any quirks/deficiencies related to this kind of code? This code is taken from mailman3-utils: https://github.com/sfindeisen/mailman3-utils , a set of scripts I stitched together to facilitate common Mailman3 operations on the command-line. Most importantly this can apply the (currently hardcoded) set of list settings uniformly across the different lists (and different domains). (I realize part of this overlaps with the mailman command, especially in the local setting.) Thanks Stanisław

3 years, 8 months

[MM3-users] Re: Apache+mod_wsgi issue

by Odhiambo Washington

On Fri, Dec 23, 2022 at 2:02 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/22/22 13:57, Odhiambo Washington wrote: > > > > WSGIDaemonProcess mailman-web display-name=mailman-web > > maximum-requests=1000 umask=0002 user=mailman group=mailman > > > python-path=/opt/mailman/mm/venv/lib/python3.9/site-packages:/opt/mailman/mm/venv/lib/python3.9 > > python-home=/opt/mailman/mm/venv home=/opt/mailman/mm/var > > WSGIRestrictSignal Off > > > Add /opt/mailman/mm to python_path. I.e. > > > > python-path=/opt/mailman/mm:/opt/mailman/mm/venv/lib/python3.9/site-packages:/opt/mailman/mm/venv/lib/python3.9 > Now working as expected. With this, my questions about running MM3 with either gunicorn or mod_wsgi are bound to get reduced to an acceptable level. There is just one more thing - I have this in settings.py: LOGGING['handlers']['file']['filename'] = '/opt/mailman/mm/var/logs/mailmanweb.log' However, the referenced file is ever empty. At what point is it supposed to record anything? Thank you very much and may you enjoy your festive season - the one we call Christmas. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 11 months

[MM3-users] User stories about topics, dynamic sublists, or sibling lists

by Stephen J. Turnbull

Mark Sapiro writes: > On 3/27/24 08:05, Markus Grandpre wrote: > > > > after I migrated a list from Mailman21 to Mailman3 I missed the > > Mailman21 setting "regular_include_lists" (or something similar) > > in Mailman3. How are sibling lists treated in Mailman3? > > The sibling list features do not exist in Mailman 3. Topics, dynamic lists, now sibling lists. All of these address a set of related problems, characterized by a large number of users who are divided into subgroups by interest, where the interests are pretty concrete and don't overlap much, each user may have several of those interests, and each subgroup considers the threads on other topics to be an interruption of their preferred workflow. I would be interested in hearing user stories about their sites' use cases for these features (and any similar features whether or not they were implemented in Mailman 2). Also horror stories, if any. (I can imagine that mixing rosters could leak personal information or result in annoying crosstalk.) Please keep it in this thread, or write me personally if you prefer. Steve

1 year, 8 months

[MM3-users] Re: SpamAssassin header confusion

by skenny＠scss.tcd.ie

Mark Sapiro wrote: > On 4/8/21 3:18 PM, skenny(a)scss.tcd.ie wrote: > > On the face of it, it looks like Mailman has removed the X-Spam-* headers. > > This should not be the case. Mailman removes some headers from posts to > anonymous lists, but not X-Spam- headers even there. Are you sure you > are looking at the raw message headers and not some MUAs rendition of them? > I can think of no reason why Mailman would remove those headers. I think I may have been misreading what's going on. The spam email is first received by Postfix and rinsed by SpamAssassin. In the copy that gets retained as a gzipped file under /var/lib/amavis/virusmails, there's a header present near the top that says "Delivered-To: spam-quarantine" - as well as all the X-Spam-* headers. So Postfix must consider the message "delivered" in that sense. My guess is that it then hands off the original email - minus all the X-Spam-* and other headers, but with the amended Subject: line (***SPAM*****) - to Mailman. Thus Mailman never sees those spam-related headers in the first place (?) Stephen

4 years, 8 months

[MM3-users] Re: Held messages: Long time waiating for response of the Mailman API

by Stephan Krinetzki

Stephen J. Turnbull wrote: > Mark Sapiro writes: > > mailmancore/API ->database > > that seems to have an issue and only with this one > > DELETE FROM pendedkeyvalue WHERE pendedkeyvalue.id = XXX > > query. However, like you, I have no idea as to what you could do further > > to debug this. > > I have an idea, but it seems so obvious that presumably it's already > been tried: log in to the database as mailman with pgsql and try > deleting something. If that works immediately, try with mailmanclient > and the mailman command line utility. > Steve Well, we didn't try this. Since we don't know what the query for deleting a held message in the database needs to look like, we left that out for now. If someone can help me there, it would be great. Over the mailman shell it hangs as long as on the web ui (using mailman shell -l list@host and iterating over the held messages). So it is the communication Mailman API <-> Database.

3 years, 10 months

[MM3-users] Re: Mailman web interface / uwsgi

by Stephen J. Turnbull

Mark Sapiro writes: > On 11/27/22 00:19, Jan Eden via Mailman-users wrote: > > > > I see. But the mailman.cfg is placed in /etc/mailman3, and this file > > also belongs to the core, doesn't it? In any case, I changed the > > configuration parameter for [archiver.hyperkitty] as you suggested and > > all settings are in one place now. > > In that case, it's probably just an oversight. Yes, I think that's what's going on. There's been quite a bit of simplification and unification of the Django configuration over time, which is ongoing and not 100% reflected in all documentation. Because of the way most Linux distros work (and I think it's probably true for *BSD and other POSIX systems), it makes sense to put users' site configurations in /etc. I don't see a particular reason why with the current relatively small set of config files we'd want to put HyperKitty or Postorius files elsewhere than /etc/mailman3 (although it might make sense to have more separation given the existence of EMWD's Affinity etc). Steve

3 years

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

by Bryan Fields

On 7/26/24 11:19 PM, Mark Sapiro wrote: > On 7/26/24 18:53, Bryan Fields wrote: >> On 7/26/24 4:01 PM, Mark Sapiro wrote: >> >>> If this returns just the one message_id, I would then >>> >>> DELETE FROM hyperkitty_thread WHERE id = 35670; >>> DELETE FROM hyperkitty_email WHERE id = 150555; >> >> It's giving an error due to a fk constraint on another table. I'm not >> familiar with the db structure enough to be certain how to clean/fix it. > > Yes, you need to do these first. > > DELETE FROM hyperkitty_favorite WHERE thread_id = 35670; > DELETE FROM hyperkitty_tagging WHERE thread_id = 35670; > DELETE FROM hyperkitty_lastview WHERE thread_id = 35670; > DELETE FROM hyperkitty_vote WHERE email_id = 150555; > > Not all those will exist, but then you should be able to > > DELETE FROM hyperkitty_thread WHERE id = 35670; > DELETE FROM hyperkitty_email WHERE id = 150555; Sill no go on it. mailmanweb=> DELETE FROM hyperkitty_favorite WHERE thread_id = 35670; DELETE 0 mailmanweb=> DELETE FROM hyperkitty_tagging WHERE thread_id = 35670; DELETE 0 mailmanweb=> DELETE FROM hyperkitty_lastview WHERE thread_id = 35670; DELETE 0 mailmanweb=> DELETE FROM hyperkitty_vote WHERE email_id = 150555; DELETE 0 mailmanweb=> DELETE FROM hyperkitty_thread WHERE id = 35670; ERROR: update or delete on table "hyperkitty_thread" violates foreign key constraint "hyperkitty_email_thread_id_038c9aee_fk_hyperkitty_thread_id" on table "hyperkitty_email" DETAIL: Key (id)=(35670) is still referenced from table "hyperkitty_email". mailmanweb=> DELETE FROM hyperkitty_email WHERE id = 150555; ERROR: update or delete on table "hyperkitty_email" violates foreign key constraint "hyperkitty_thread_starting_email_id_fa7c55f5_fk_hyperkitt" on table "hyperkitty_thread" DETAIL: Key (id)=(150555) is still referenced from table "hyperkitty_thread". >> I'm actually thinking I need to fix the archive mbox, then delete them and >> re-import them once they are cleaned. > > > Actually, that would be safest. Fix the mbox, delete the entire archive > and re-run the import. I'll attempt to clean this up tomorrow an clean it up/re-import. Is there a quick/easy way to drop the entire archive from the db or must I delete the entire list? >>> Also, FYI, assuming those messages with very old Date: headers had >>> reasonable unix from dates, the hyperkitty/contrib/cleanarch3 script >>> would fix them, except you have to get the script from >>> https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/contrib/clea… >>> or https://www.msapiro.net/scripts/cleanarch3 because the script in the >>> latest release has a bug. >> >> I tried the dry run option on your script and it gave a bunch of output >> for bad >> dates. This was absent on the one shipping with the source. What's >> interesting >> is that pipermail seems to have no issue with this, detecting the date >> correctly. > > If I recall correctly, pipermail checks date skew and 'fixes' the dates > in the archive, but they remain off in the mbox. I'll have to check that, but I've got at least some good leads now and tools to find suspected issues. It does seem like a bad design that importing a mailman2 mbox can cause the server to error 500. >> Is the archive tool in pipermail's import more robust in this manner? >> I'd argue >> it's common to have missing In-Reply-To: headers where the subject and time >> would need to be used to infer the likely thread. I'll agree this is a >> major >> violation of the relevant RFC's to be missing this, but many MUA's (M$) are >> famous for doing just this. > > > Yes, it's arguably a defect in HyperKitty to not implement Jamie > Zawinski's threading algorithm <https://www.jwz.org/doc/threading.html>, > but it doesn't. Well that kinda blows :-( I'm not going to take down the old archives, but I'd like at least one to be searchable, which is why we wanted to use mailman3/hyperkitty. Thank you, -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net

1 year, 4 months

[MM3-users] Re: Moving from forum to Mailman 3

by Stephen J. Turnbull

Mark Sapiro writes: > On 10/9/20 4:39 PM, jonathan.mailing.lists(a)gmail.com wrote: > > > > Thanks for this. I’m sure I could turn that basic information > > (from, date, subject) into an mbox file somehow. What else does > > Mailman need, eg to work out which messages are in reply to > > which? > > To properly thread messages, each message should have a unique > Message-ID: header and all replies should have an In-Reply-To: header > with the Massage-ID: of the message to which it's a reply. [example thread omitted] > The angle brackets around the strings are required and every Message-ID: > in the entire archive for a list must be unique. This is harder to do well (or even "well enough") than you might think. I recommend using some software targeting RFC 4122: https://tools.ietf.org/html/rfc4122. RFC 4122 is implemented in the Python standard library (the uuid module), so if you have Mailman, you have it. The command line utility uuidgen is also good, and you probably have that too if you prefer CLI scripting to Python. Steve

5 years, 2 months

[MM3-users] Re: installation

by Brian Carpenter

On 11/22/20 6:54 PM, Henry S wrote: > > Now I am trying to figure out how to configure mailman+postfix to pass > the unnecessarily convoluted world of spam-free certification and ip > blockings by those 'security lawmakers'. > > Any suggestions on how to not be blocked by gmail, hotmail, etc? I > have used DKIM (no signing yet), SPF, DMARC to no avail. Maybe not an > appropriate question to this mailman list. Mark Sapiro provided some very good suggestions. Is this a new IP address or one that has been used for mail traffic for a white? The only way Gmail and Hotmail will block an IP address is if you have some major outgoing spamming problems or in the case of a new IP address, the IP address has a sordid history which will be reveal if you do a RBL check on it. Gmail likes SPF records and MTA's that utilizes SSL for outbound mail. For Hotmail deliveries, you will want to signed up for Microsoft's Smart Network Data Service (SNDS) program which I find very good. Also sign up for their JMRP program for your IP address. -- Brian Carpenter Harmonylists.com Emwd.com

5 years

[MM3-users] Re: Hyperkitty

by Onyeibo

Hi Mark, On Mon, 30 Jan 2023 12:24:24 -0800 Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/30/23 11:58, Onyeibo wrote: > >> 2. Your MM3 log files - do they say anything? > >> > > Nothing! No new errors. It is very strange and frustrating > > > Are there files in /opt/mailman/mm/var/archives/hyperkitty/spool/? > YES! A lot of them > Do messages received from the list have an Archived-At: header:? > No > Do messages received from the list have a List-Archive: header:? > No > If the first answer is yes, the mailman_hyperkitty archive_message > method is failing. > > If the second answer is no, the mailman_hyperkitty permalink method > is failing. > > If the second answer is no, the mailman_hyperkitty list_url method is > failing. > That means they are all failing. Wow > All of these failures log errors to the mailman.archiver log which by > default is written to mailman.log. The log doesn't have entries pointing to failures above > > If by chance there is an Archived-At: header, what is it? > The mails don't have that header. I suspect I may have to investigate SELinux.

2 years, 10 months

[MM3-users] Re: lists.mailman3.org web site.

by Barry Warsaw

On Aug 30, 2016, at 12:01 AM, Mark Sapiro wrote: >Django Allauth is now properly configured and working on >lists.mailman3.org. You can log in by email/password as noted above or via >OAuth2 with a GitHub, GitLab, Google or Facebook identity. > >If you are an existing user, in order to use one of the OAuth2 providers, you >must first log in with email and password and go to the Account Connections >tab in your account settings and add the 3rd party account(s) you wish. This works pretty great. I tried it with my GitHub and GitLab accounts and was easily able to associate those with my Postorius and HK accounts. I didn't try FB or Google, but I guess those would work the same way. I'll miss Persona but I think this is an entirely acceptable alternative, with plenty of choice for folks wanting to control which authority they delegate to. I'd mildly like to see Launchpad support, but I understand 1) it's a minority platform; 2) it only supports OAuth 1. Thanks to the developers for adding this support and to Mark for enabling it. Cheers, -Barry

9 years, 3 months

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

by Thomas Stein

Thanks for the clarification Mark. cheers t. On Friday, 4 January 2019 19:25:20 CET Mark Sapiro wrote: > 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…>. > >

6 years, 11 months

[MM3-users] Re: Module Not Found Error after update

by Abhilash Raj

On Thu, Feb 4, 2021, at 8:52 AM, Brian Carpenter wrote: > > On 2/4/21 11:46 AM, Mark Sapiro wrote: > > You need django-mailman3 1.3.5 > > > > > > While all are not required in this case, when you upgrade like this with > > pip, you should upgrade all of django-mailman3, hyperkitty, mailman, > > mailmanclient, mailman-hyperkitty and postorius. > > Thanks Mark. Perhaps Abhilash can include that in the instructions on > the following page for future releases: > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… I was hoping pip would actually upgrade django-mailman3 given that P requires ‘django-mailman3>=1.3.5’ [1] but looks like it didn’t :( [1]: https://gitlab.com/mailman/postorius/-/blob/master/setup.py#L56 > I will make a note of this in my own personal documentation and the > Debian 10 How-to guide that I am currently working on. > > -- > Brian Carpenter > Harmonylists.com > Emwd.com > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

4 years, 10 months

[MM3-users] Re: Moderate mails from owner

by Henrik Rasmussen

Mark Sapiro wrote: > This can happen in a few ways., If this list was originally imported > from Mailman 2.1 by the 'mailman import21' command, there may be a > legacy accept_these_nonmembers attribute for the list. If so, and if a This makes sense. The list was in fact imported from Mailman 2.1. > You need to check the list's accept_these_nonmembers attribute and the > non-member address's moderation action. > > If you have recent Postorius, you can see nonmembers and their options > from the 'users' -> Non-members view. I currently have Postorius 1.2.2 so I don't have it yet. > mailman shell -l list.example.com The sender is in the list of accept_these_nonmembers, however the command memb.moderation_action = m.default_nonmember_action doesn't seem to remove it from accept_these_nonmembers. bash-4.3# mailman shell -l [LISTNAME].lists.example.com Welcome to the GNU Mailman shell The variable 'm' is the [LISTNAME].lists.example.com mailing list >>> m.accept_these_nonmembers ['listadmin(a)senderdep.example.com'] >>> memb = m.nonmembers.get_member('listadmin(a)senderdep.example.com') >>> memb.moderation_action <Action.accept: 3> >>> memb.moderation_action = m.default_nonmember_action >>> m.accept_these_nonmembers ['listadmin(a)senderdep.example.com'] -- Henrik

6 years, 7 months

[MM3-users] Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /archives/search

by Johannes Rohr

Am 23.01.23 um 21:08 schrieb Mark Sapiro: > On 1/23/23 02:41, Johannes Rohr wrote: >> >> I don't understand what the cause for the "permission denied" could >> be. The directory "fulltext_index" is owned by mailman:mailman >> >> Does anyone have a hint? I did some googling for the error, but to no >> avail, unfortunately. > > > It's actually trying to create fulltext_index, so clearly it's not > looking at the fulltext_index that you are. If you are following > https://docs.mailman3.org/en/latest/install/virtualenv.html you > probably need to specify the path in /etc/mailman3/settings.py as in, > e.g. > ``` > HAYSTACK_CONNECTIONS['default']['PATH'] = > '/opt/mailman/mm/var/fulltext_index' Thanks! Indeed. Including this line helps. It makes the error go away. So I guess the instructions should be amended. After that, for some reason, I have to re-index all lists, because initially, empty results were returned for any query, only after re-indexing to I get results. Again, thanks so much for your support! Johannes > ``` >

2 years, 10 months

[MM3-users] Re: Adding / manipulating users

by Seth Seeger

> On Nov 18, 2019, at 2:28 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 11/18/19 6:15 AM, Seth Seeger wrote: >> >> My next question - I have two lists from Yahoo to import. I’ve migrated them through groups.io and have a convenient export. I now have all the data in formats I can handle. (json file for members, mbox for archives.) What’s the best way to import hundreds of users, setting their mail delivery status and moderation status at the same time? (There doesn’t seem to be a command line option for adding members anymore where you can also set their delivery status.) I’ve looked at the documentation, but couldn’t figure out what to do. > > > ... > > Alternatively, you could create a script that would post the appropriate > transactions to add a member and set moderation and delivery status to > Mailman's REST API and use that to process your members. Great! I can definitely do the REST API route. If I create a script to take a CSV and push it through the API, is there a place I can post it to make it useful for others? Seth

6 years

[MM3-users] Re: I did something stupid. Can i back out of it?

by William Oliver

On Sat, 2022-02-19 at 13:11 -0800, Mark Sapiro wrote: > On 2/19/22 12:41 PM, William Oliver wrote: > > > > So, I can just kill the listname user altogether? > > > As far as Mailman is concerned, Yes. > > No joy. I deleted the list as well, and recreated it with the same name -- and the error repeated. I created a list with a different name, and there's no error. I must have really screwed something up in dovecot. Happily, this is a small list, so I'll just migrate everybody to the newly named "listname2". So.. as an aside, it was a bit of a hassle to copy and paste all the usernames from the "Users" list in Postorius to the "Mass subscribe." The only way I could see to do it was copy and paste them one at a time. That worked OK for me, since it's a small list, but that made me wonder if there was a way to select, say, 100 users out of Users and subscribe them all to a list. billo

3 years, 9 months

[MM3-users] Re: Subscribing users stuck in pending hell

by Quanah Gibson-Mount

--On Wednesday, May 24, 2023 9:21 AM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > 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. The only elements that have a drop down menu are: Users Mass operations There is no "Pending Confirmation" with either of these. Note: Postorius Version 1.2.4 --Quanah

2 years, 6 months

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

by Jered Floyd

I believe this is correct, and will need to be fixed on the Mailman side. The practical effects seem to be -- for me at least -- that any of the pages for social logins fail to receive any template styling. --Jered ----- On Nov 8, 2023, at 10:01 AM, Jeremy Stanley fungi(a)yuggoth.org wrote: > On 2023-11-07 19:46:01 -0800 (-0800), Mark Sapiro wrote: > [...] >> I don't think this is fatal, but I have reported it at >> https://github.com/pennersr/django-allauth/issues/3513 > > We've been seeing the same thing in our deployment, I just hadn't > found the time to look into it yet. Looks like upstream won't-fixed > it, so I guess it was an intentionally backward-incompatible change > and the template files will need some minor reworking? > -- > Jeremy Stanley > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to jered(a)convivian.com

2 years

[MM3-users] Re: CPU usage when idle

by roughnecks

Il 28/05/2025 23:42, Mark Sapiro ha scritto: > On 5/28/25 08:27, roughnecks via Mailman-users wrote: >> >> It's the manage.py qcluster whatever is called. I have shut down MM >> for the time being, because I'm not fully motivated to have it >> running, so I can't be more accurate right now. > > I don't know how qcluster is configured in the Debian packages (which > are out of date and possibly buggy anyway). You may be using django-q > <https://django-q.readthedocs.io/en/latest/> and if so, you should > migrate to django-q2 <https://django-q2.readthedocs.io/en/master/>. Both > typically use memcached as a backend. I wouldn't know how to migrate and if that means doing anything not in the debian-way (haven't opened any link so far). About qcluster configs, yes, all correct but there is no configuration for caches, so probably it's the default one you specified. I can look into this. > You can get info about what qcluster is doing with `manage.py qinfo` and > monitor things with `manage.py qmemory` and `manage.py qmonitor`. Thanks, helpful.

6 months, 2 weeks

[MM3-users] Re: Multiple domain problem

by Lars Bjørndal

On Thu, Feb 09, 2023 at 02:05:09PM -0800, Mark Sapiro wrote: > On 2/9/23 13:21, Lars Bjørndal wrote: > > > > I have lists on two domains, example1.com and example2.com. The mail > > interface works perfectly. However, connecting a browser to > > example1.com, I get the title List index - example1.com, and the web > > interface seems to work fine. > > > > If I connect to example2.com, the title is example2.com, without the > > preceding List index. And the body says Page not found. > > > What's in the browser's address bar for that page? It's https://example2.com/mailman3/lists/ For the domain that works, it is https://example1.com/mailman3/lists/ Please note that I've changed mailman to mailman3 for the complete installation. > What's in Postorius domains view? I realized that I have to change SIT_ID to 1 to be able to connect to http://localhost:8000/. Then, when checking Domains, I have both domains with different SIT_ID value (1 and 2). > What's in the Django admin sites view. Going to http://localhost:8000/admin and choosing Sites, I have both domains listed. Thanks Lars

2 years, 10 months

[MM3-users] Re: search this list searches more then just this list

by Marco van Tol

Op 23 jan 2024, om 19:09 heeft Mark Sapiro <mark(a)msapiro.net> het volgende geschreven: > > On 1/23/24 05:49, Marco van Tol wrote: >> Small unfortunate twist, this leads to: >> --- >> [ERROR/MainProcess] Failed indexing 204001 - 205000 (retry 5/5): Term too long (> 245): ... >> --- >> I have seen comments on that from back in 2020, but what’s the latest advise on how to deal with this? > > This issue is discussed at <https://github.com/notanumber/xapian-haystack/pull/181>. > There are two patches for this issue. They are somewhat different approaches, but either one is OK. One patch is the one in the above PR <https://github.com/notanumber/xapian-haystack/pull/181/files>. The other is at <https://github.com/alexsilva/xapian-haystack/commit/a53523d2d0d13929a0729d4…>. > > I use the one from the PR, but it requires a substitution `s/force_text/str/`. Hi, thanks! Just to double check, do you mean `str` or `force_str` in the substitution? I found a comment on this topic regarding django-4 where they advice to use force_str. https://stackoverflow.com/questions/70382084/import-error-force-text-from-d… Thanks! Marco van Tol

1 year, 10 months

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

by Odhiambo Washington

On Sat, Jul 26, 2025 at 8:28 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/26/25 1:23 AM, Odhiambo Washington via Mailman-users wrote: > > I am seeing the error below and wondering what's the cause: > > The message has some issue which is causing HyperKitty to not be able to > archive the message. The message will be queued in Mailman's > var/archives/hyperkitty/spool/ directory and can be examined with > `mailman qfile`. If you do that and the cause is not clear, you can post > the message, and we will investigate. If the message is unwanted, you > can just remove the file from Mailman's var/archives/hyperkitty/spool/ > directory. > I had examined the message using 'mailman qfile', but did not see anything obvious. There were 3 files inside the spool/ directory. I have just checked again and they are no longer there. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

4 months, 2 weeks

[MM3-users] Re: Mailman3 reinstall fail, need some help

by Yvan ♞

Finally succeed to reinstall with a very precious help !!! /etc/mailman3 folder was removed before the mailman3 package was supressed, apt noticed it and he believed that it was a modification of the configuration of mailman that was wanted, so each time the debian mailman3 package was reinstalled, he did not put the conf in /etc/mailman3, which caused the package installation to crash, and therefore the app install on ynh Le 03/04/2022 à 12:53, Odhiambo Washington a écrit : > On Sun, Apr 3, 2022 at 12:06 PM Yvan ♞<elemac(a)free.fr> wrote: > >> Hello every body >> I have progress to try to reinstall mailman3 on yunohost server but I >> still have an error, if somebody can help me as I don't understand the log >> https://paste.yunohost.org/raw/ugijepuyuv >> Sincerely. >> Yvan >> > Hi Yvan, > > As previously advised by Mark Sapiro, you are better off taking to the > YunoHost support people for help. > They will most likely help you with the failing dependencies issue. > > But I also wonder - why don't you follow the virtualenv method to install? >

3 years, 8 months

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

by Matthew Blissett

On 11/07/2024 04:11, Mark Sapiro wrote: > 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. Thanks. I have implemented it by adapting the Mailman 2 script to use the REST API of Mailman 3: https://gist.github.com/MattBlissett/c1f58dcc182423f48e2305b3d91ea44d -- Matt

1 year, 5 months

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

by Mark Dadgar

On Nov 10, 2020, at 1:40 PM, Mark Sapiro <mark(a)msapiro.net> wrote: >> Brian specified: >> >> verp_personalized_deliveries: no >> >> Doesn’t that default back to regular mass delivery, as opposed to individualized VERPed envelopes, which mandates individual deliveries? > > > That depends on the setting of verp_delivery_interval. If > verp_delivery_interval = 1, every message will be VERPed regardless of > verp_personalized_deliveries. If verp_delivery_interval = 0 and > verp_personalized_deliveries = no, deliveries won't be VERPed as you > note. If verp_delivery_interval = 0 and verp_personalized_deliveries = > yes, only personalized deliveries (i.e. individual messages, not > digests, from lists with Personalization enabled) will be VERPed. > > The theory is VERPing has a cost because it requires a separate message > sent to each recipient rather than a single message with multiple > recipients, but personalization also requires a separate message sent to > each recipient, so those can be VERPed at no extra cost. > > But to be clear, automated bounce processing does not require VERP. It > just works a tiny bit more reliably with VERP. Great explanation - thank you. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 1 month

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

by Hans Mayer

Hi Mark, many thanks for this hint. I updated table "template" and replaced "localhost" with the real name and it worked. // Hans -- On 25.09.22 19:28, Mark Sapiro wrote: > 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. >

3 years, 2 months

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

by Bryan Fields

On 7/9/24 3:39 PM, Mark Sapiro wrote: > See this post and maybe more of that thread which may help. > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… Thanks Mike, I've been looking into this, and I don't think it's that. What I did find is that our mbox from the mailman2 list is actually a amalgamation of mailman2, and majordomo archives. The mbox is not in order, but the start of the mbox starts in 2007 (coinciding with the last displayed month). Later on in the mbox file, the archives going back to 1992 from majordomo are present. There is no errors in the check_hk_import for this, and the messages are present in the index when I search for them and there are no errors during import. mailman 2.1 archives works just fine with this mbox file. Here's a link to the server in question, it's just a text box as we work through this. There's about 14k people on this list, so we want to get it right before cut over. https://nanog-mm3.keekles.org/archives/list/mm2-mm3@nanog-mm3.keekles.org/ Any ideas? -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net

1 year, 4 months

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

by Andreas Barth

* Mark Sapiro (mark(a)msapiro.net) [210922 20:46]: > On 9/22/21 11:22 AM, cfarley(a)iastate.edu wrote: > >I have a new mailman3 install setup with Okta as a social application. This is working well for logins and data comes through as expected, but for some reason the username is being set at to a lowercase version of the given_name. The Extra data on the social users in the admin interface looks good, so I don’t think it’s a problem with the attributes coming from Okta. > > > >We have tried a number of variations on the below setting, but that all of them other than the default of “username” end up with the username being empty. > >ACCOUNT_USER_MODEL_USERNAME_FIELD = “email” > > > >Any direction would be welcome. > > This is an issue for Django allauth > <https://django-allauth.readthedocs.io/en/latest/index.html>. > Mailman has no control over this. The username is part of Django's > login and is not used by Mailman at all. Does that mean, not having an user name would work for mailman? I always thought having an user name was required Regards, Andi

4 years, 2 months

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

by Barry Warsaw

On Dec 09, 2016, at 09:37 AM, Mark Sapiro wrote: >I understand you need to feel comfortable about everything going into >the core and this takes time and energy to review all the MRs, but I >think it is pretty important to get the DMARC mitigations into the core. >If there's anything I can do to help with this, let me know. > >I will rebase my branch again and possibly make one minor tweak, but I >think it should be OK. Thanks for pushing back on this Mark. Obviously, I have a high degree of trust in your work, but yeah, my compulsive behavior is showing through. ;) Please do rebase and if you can, remilestone the MR to 3.1. We'll get it in. >I can also work on Postorius. Also in this vein I have a question. >Should the DMARC settings be added to the Alter Messages tab in the List >Settings view or would it be better to have a separate DMARC Mitigations >tab. My gut reaction is to add a separate DMARC Mitigations tab, but Florian and Terri have final say I think. Cheers, -Barry

9 years

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

by Stephen J. Turnbull

Henrik Rasmussen writes: > > Fra: Mark Sapiro <mark(a)msapiro.net> > > It should be TIME_ZONE = 'UTC' > > > > Times passed from Mailman core are naive times, I.e. they don't have > > time zone info, but they are in UTC. Mark is saying that Mailman core converts to UTC. All times that come out of Mailman core in the relevant API are UTC. > As stackoverflow.com/questions/29311354/how-to-set-the-timezone-in-django > seems to say otherwise ("You can use TIME_ZONE = 'Europe/Istanbul'"), > to make sure, am I right to understand it as for Mailman, Danish time > should be stated as "TIME_ZONE = 'UTC+1' " with use of "USE_TZ = True"? No, USE_TZ=True means "hey Django, you need to add a time zone to this datetime." And you use TIME_ZONE=UTC (exactly), because this variable is *not* the local time zone, it's the time zone that Postorius tells Django to add to datetime objects that don't carry their timezone with them. There is a setting somewhere else that tells Django what time zone should be used for I/O. Steve

3 years, 10 months

[MM3-users] Custom Archiver

by Stephen J. Turnbull

Mark Sapiro writes: > On 4/1/23 16:33, Peter Knowles wrote: > > That all being said, on a slight segway... Aside from using the > > REST API, is it practical or possible to manipulate the database > > directly? That is, in doing so would it just work or are there > > extra moving parts when an API request is issued? > > It probably is possible, but I would definitely discourage it. The > REST API should provide everything you need without your having to > reimplement everything it does. I think it would probably be a really heavy lift, because Mailman internally uses an object-relational manager, SQAlchemy. We occasionally change the schema, and SQAalchemy will automatically upgrade the database schema. You would have to handle that by hand in your code. I would recommend you get the sources for mailmanclient (https://gitlab.com/mailman/mailmanclient, iirc). They're quite repetitive, you wouldn't want to literally port them, but once you're familiar with the scaffolding and a couple of the commands you should be able to write a lot of PHP really fast to cover the REST endpioints you most need in a library with an API to your taste. Steve

2 years, 8 months

[MM3-users] Re: AttributeError: 'MailingList' object has no attribute 'get_requests_count'

by Shashikanth Komandoor

Can I go back to any previous version which is felt as working fine ? <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Wed, Oct 28, 2020 at 11:43 AM Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > Mark Sapiro writes: > > > I think the issue is your mailmanclient is too old. The version of > > Postorius you are running requires mailmanclient >3.3.1 which is only > > available from GitLab <https://gitlab.com/mailman/mailmanclient>. > > > > What version of Postorius is this? It appears to be >1.3.3. If you > > install Postorius from unreleased code on GitLab, you have to install > > all of mailman, mailmanclient and django-mailman3 as well. > > Shouldn't Postorius's setup.py be checking for this? > > Steve > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

5 years, 1 month

[MM3-users] Re: Mailman 3 Installation

by Mark Dadgar

On Jan 16, 2021, at 7:31 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/16/21 6:06 PM, bruce.dubbs(a)gmail.com wrote: >> I do have sqlite installed, but the documentation discusses mysql/mariadb and postresql. What are the considerations as to why I would need one of these other DBs? > > You can use sqlite, but if you don't already have a mysql/mariadb > database on the server, we recommend postgresql for performance and > robustness. I personally have had issues with mysql and use postgresql > on one production server that uses mysql for other applications. I’ll word this a little more strongly: do not use sqlite for a production server. Do not "just start with sqlite to get it running and then I’ll migrate it to something else down the road.” There is currently no validated way to migrate a mailman3 instance from sqlite to something else, and by “no validated way” what I actually mean is “no one has managed to get this to work, me included.” Put in the extra effort to start with posgresql or mysql/mariadb up front. You’ll regret it if you don’t. Ask me how I know. 😁 - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 10 months

[MM3-users] Re: How to promote non-members to members?

by Quanah Gibson-Mount

--On Tuesday, March 15, 2022 10:29 PM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/15/22 11:16, Quanah Gibson-Mount wrote: >> Hello, >> >> We have a constant issue with confirmation emails for subscribers >> getting lost and then the subscriber contacting us because their posts >> to the list never show up. Is there a way I can, as an administrator, >> do the confirmation on their behalf or in some other way promote them to >> being a member from non-member? > > See this thread > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/threa > d/MJOOH23W6EKZO7GI5HRDKB4S733JEEVG/ > > If they don't have an outstanding subscription waiting user confirmation, > you can just mass subscribe them. > > If they do and your Postorius and Mailman core is reasonably up to date, > you can find the pending request at Subscription requests -> Pending > Confirmation, delete it and then mass subscribe them. Hi Mark, Thanks for the response. Unfortunately I'm currently stuck with the junk shipped by Debian. Yet another reason to move to a standalone install and avoid their broken packages. Regards, Quanah

3 years, 8 months

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

by Franklin Weng

Hi Mark, Mark Sapiro 於 2019/10/26 上午2:08 寫道: > The issue is the list welcome message is sent in the character set of > the new member's preferred language and if that is not set in the > subscription request, and it's not possible to do that in Postorius, it > defaults to the installation's preferred language. > > It should probably default to the list's preferred language. See > <https://gitlab.com/mailman/mailman/issues/608> > > You have two choices: > > You can set the installation's default language by putting > > [mailman] > default_language: zh_TW > > in your mailman.cfg, or you can leave the default language English and > set the character set for English to utf-8 by putting > > [language.en] > charset: utf-8 > > in your mailman.cfg. Thanks for your help. After trying I found that it only worked when I set the [language.en] charset to utf-8. If I didn't set this but only set default_language in [mailman] section to zh_TW it still sent ? in the welcome messages. I commented in the issue. Thanks, Franklin

6 years, 1 month

[MM3-users] Re: Mailman archive issues (Hyperkitty)

by Ruth Ivimey-Cook

On 03/06/2021 15:09, Mark Sapiro wrote: > On 6/3/21 1:06 AM, Kimmo L wrote: >> Thanks for the quick replay! >> If its not a big trouble, could you kindly give me some advice/guide >> how upgrade my Hyperkitty/Postorius/Django from python2 to python3. >> I would be very grateful. > > > It depends heavily on how Mailman was installed to begin with, but > essentially you just upgrade the various components to the latest > versions using pip. Some things you need to be aware of are at > https://docs.mailman3.org/en/latest/upgrade-3.2.html If you start with python libs installed using a package manager (apt, yum, etc) and later upgrade them using pip, make sure you lock the packages at their current version so they cannot be changed by package updates, or you'll eventually have the package manager do an unintended downgrade. It is usually best to start with a distinct installation from pip, into a python venv to avoid changing system libs. You can of course seed that install with the current setup first! Ruth -- Software Manager & Engineer Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

4 years, 6 months

[MM3-users] Re: nginx configuration on a multitasking server

by David Newman

On 12/23/21 9:18 AM, Mark Sapiro wrote: > However, that's not the issue. You originally reported and I didn't look > closely enough: > >> Update: The above worked fine until MM3 informed a list owner of >> pending subscription requests, with a URL like this: >> >> https://lists.example.com/mailman/admindb/listname >> >> and that URL returned a 404 error. > > > That URL is from a Mailman 2.1 installation. Are you still running > Mailman 2.1? I'm not, but that, and me not looking closely, was the problem. The system doesn't run MM2.1 any more, and no longer has it installed. But I failed to notice the dates on those 'admindb' messages: They were from the day of the upgrade, about 30 minutes before decommissioning MM2.1. And the docs do say explicitly to deal with any pending tasks before doing a cutover. The task-pending message that MM3 sends to list owners and moderators just says generically to check the dashboard, without providing a URL. Can that be modified to provide an explicit URL, something like this? https://lists.example.com/mailman3/lists/listname Thanks again for spotting this. dn

3 years, 11 months

[MM3-users] Re: [NON-INTERNAL] Re: Missing Archived emails - Hyperkitty - CERT Issue

by Odhiambo Washington

PS: I beg you to put your responses below the last one. Makes the hierarchy look better. Now, have you edited your /etc/mailman3/mailman-hyperkitty.cfg and restarted MM3? On Tue, Jul 29, 2025 at 3:18 PM Willie Castillo < Willie.Castillo(a)caemilusa.com> wrote: > Odhiambo, long time no hear from you. Hope you are doing well. > > The last archived post for that specific list is July 3rd. 2025. We do not > see the one for July 25th. Also, I just noticed something else in the logs, > apparently the server is still having "SSLCertVerificationError" issues > even after updating the DigiCert, CA-Certificate,etc. I must be missing > something else. > > Based on that, looks like the archiving is failing still due to the > "SSLCertVerificationError". > > The spool directory now has 8 *.pck files in it. However, I do not see the > original ones from 7/25 > > ~# ll -t /opt/mailman/mm/var/archives/hyperkitty/spool/ > -rw-rw---- 1 mailman mailman 14725 Jul 29 08:07 > 1753790859.2498085+320096cb9852779b55a4cbb1e4f9603736ebd78d.pck > -rw-rw---- 1 mailman mailman 15122 Jul 29 08:07 > 1753790859.2437658+7fddf881d592f27be60e32aa5b3c34c7077b9988.pck > -rw-rw---- 1 mailman mailman 6399 Jul 29 08:07 > 1753790859.2370558+ee410eb31691bf2854cca46c64e80e3bf61c3523.pck > -rw-rw---- 1 mailman mailman 26619 Jul 29 08:07 > 1753790859.230345+b2e70f5b65900731895bbee5a3d83401f1500567.pck > -rw-rw---- 1 mailman mailman 15676 Jul 29 08:07 > 1753790859.2225533+82371c8a0202d62eaa046dd3633a23d6837d7a80.pck > -rw-rw---- 1 mailman mailman 98273 Jul 29 08:07 > 1753790859.2136636+8ee9273fbbaf4352d482e69d177e2eb2824078a5.pck > -rw-rw---- 1 mailman mailman 98109 Jul 29 08:07 > 1753790859.2026713+49d82ecd57eda7eaa582ba925449e2343bea5c56.pck > -rw-rw---- 1 mailman mailman 88479 Jul 29 08:07 > 1753790859.191489+162aa89dcac50ca6f5463ce1098c828728af12d1.pck > > > > > ------------------------------ > *From:* Odhiambo Washington <odhiambo(a)gmail.com> > *Sent:* Tuesday, July 29, 2025 7:59 AM > *To:* mailman-users(a)mailman3.org <mailman-users(a)mailman3.org>; Mark > Sapiro <mark(a)msapiro.net> > *Cc:* Willie Castillo <Willie.Castillo(a)caemilusa.com> > *Subject:* Re: [MM3-users] Re: [NON-INTERNAL] Re: Missing Archived emails > - Hyperkitty - CERT Issue > > > CAUTION: This email originated from outside of the organization. Do not > click links or open attachments unless you recognize the sender and know > the content is safe. > > > > On Tue, Jul 29, 2025 at 2:25 PM Willie Castillo < > Willie.Castillo(a)caemilusa.com> wrote: > > The issue started right after the site's CERT expired. The CERT expired on > 7/8/25. This is what's in the log... > > Jul 16 15:19:45 2025 (3777209) Connection to HyperKitty failed: > HTTPSConnectionPool(host='XXX.com', port=443): Max retries exceeded with > url: /hyperkitty/api/mailman/urls?mlist=jmats-versions%40XXX.com (Caused by > SSLError(SSLCertVerificatio > nError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: > certificate has expired (_ssl.c:1000)'))) > > The CERT has been updated but the 7/25 message is not archived still. > > > While at it, also edit your /etc/mailman3/mailman-hyperkitty.cfg to what > is documented so that the issue doesn't recur: > ``` > [general] > base_url: http://127.0.0.1:8000/archives/ > <https://urldefense.us/v3/__http://127.0.0.1:8000/archives/__;!!E8b8mVbrrfWV…> > api_key: Secret_Hyperkitty_API_Key > ``` > > PS: I haven't seen your responses to @Mark Sapiro <mark(a)msapiro.net>'s > questions quoted below: > ``` > 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. > ``` > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > In an Internet failure case, the #1 suspect is a constant: DNS. > "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) > [How to ask smart questions: > http://www.catb.org/~esr/faqs/smart-questions.html > <https://urldefense.us/v3/__http://www.catb.org/*esr/faqs/smart-questions.ht…> > ] > -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

4 months, 2 weeks

[MM3-users] Re: Cannot Install Web UI

by Andreas Vetter

On Montag, 20. Oktober 2025 19:56:39 CEST Mark Sapiro wrote: > On 10/20/25 10:32, Dennis Putnam via Mailman-users wrote: > > > I'm trying to install the web UI for mailman3. I am getting the > > following failure. Can someone help? TIA. > > > > (venv) mailman :~$ pip install mailman-web mailman-hyperkitty > > ... > > > FileNotFoundError: [Errno 2] No such file or directory: > > > > '/tmp/pip-install-y364_cvm/cmarkgfm_9fcba25730114ac4a08d1e > > 7733112a45/src/cmarkgfm/cmark.cffi.h' > > > > [end of output] > > > > > > > > note: This error originates from a subprocess, and is likely not a > > > > problem with pip. > > error: subprocess-exited-with-error > > > > × Getting requirements to build wheel did not run successfully. > > │ exit code: 1 > > ╰─> See above for output. > > > > note: This error originates from a subprocess, and is likely not a > > problem with pip. > > > I think I've seen a similar error, but I don't recall what I did to work > around it. In this case cmarkgfm is a dependency of readme_renderer > which in turn is a dependency of postorius. > In your venv try > > pip install cmarkgfm > > first and then > > pip install mailman-web mailman-hyperkitty > > That may avoid this. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan It seems to me cmarkgfm is broken today. I tried to update it in my working environment and get the same error: (venv) mailman@lists:~> pip install -U cmarkgfm Requirement already satisfied: cmarkgfm in ./venv/lib64/python3.11/site- packages (2024.11.20) Collecting cmarkgfm Using cached cmarkgfm-2025.10.20.tar.gz (145 kB) Installing build dependencies ... done Getting requirements to build wheel ... error error: subprocess-exited-with-error × Getting requirements to build wheel did not run successfully. │ exit code: 1 ╰─> [41 lines of output] Traceback (most recent call last): File "/opt/mailman/venv/lib64/python3.11/site-packages/pip/_vendor/ pyproject_hooks/_in_process/_in_process.py", line 389, in <module> main() File "/opt/mailman/venv/lib64/python3.11/site-packages/pip/_vendor/ pyproject_hooks/_in_process/_in_process.py", line 373, in main json_out["return_val"] = hook(**hook_input["kwargs"]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib64/python3.11/site-packages/pip/_vendor/ pyproject_hooks/_in_process/_in_process.py", line 143, in get_requires_for_build_wheel return hook(config_settings) ^^^^^^^^^^^^^^^^^^^^^ File "/tmp/pip-build-env-mdd_0nfr/overlay/lib/python3.11/site- packages/setuptools/build_meta.py", line 331, in get_requires_for_build_wheel return self._get_build_requires(config_settings, requirements=[]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/tmp/pip-build-env-mdd_0nfr/overlay/lib/python3.11/site- packages/setuptools/build_meta.py", line 301, in _get_build_requires self.run_setup() File "/tmp/pip-build-env-mdd_0nfr/overlay/lib/python3.11/site- packages/setuptools/build_meta.py", line 317, in run_setup exec(code, locals()) File "<string>", line 5, in <module> File "/tmp/pip-build-env-mdd_0nfr/overlay/lib/python3.11/site- packages/setuptools/__init__.py", line 115, in setup return distutils.core.setup(**attrs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/tmp/pip-build-env-mdd_0nfr/overlay/lib/python3.11/site- packages/setuptools/_distutils/core.py", line 148, in setup _setup_distribution = dist = klass(attrs) ^^^^^^^^^^^^ File "/tmp/pip-build-env-mdd_0nfr/overlay/lib/python3.11/site- packages/setuptools/dist.py", line 321, in __init__ _Distribution.__init__(self, dist_attrs) File "/tmp/pip-build-env-mdd_0nfr/overlay/lib/python3.11/site- packages/setuptools/_distutils/dist.py", line 309, in __init__ self.finalize_options() File "/tmp/pip-build-env-mdd_0nfr/overlay/lib/python3.11/site- packages/setuptools/dist.py", line 784, in finalize_options ep(self) File "/tmp/pip-build-env-mdd_0nfr/overlay/lib/python3.11/site- packages/setuptools/dist.py", line 804, in _finalize_setup_keywords ep.load()(self, ep.name, value) File "/tmp/pip-build-env-mdd_0nfr/overlay/lib64/python3.11/site- packages/cffi/setuptools_ext.py", line 229, in cffi_modules add_cffi_module(dist, cffi_module) File "/tmp/pip-build-env-mdd_0nfr/overlay/lib64/python3.11/site- packages/cffi/setuptools_ext.py", line 50, in add_cffi_module execfile(build_file_name, mod_vars) File "/tmp/pip-build-env-mdd_0nfr/overlay/lib64/python3.11/site- packages/cffi/setuptools_ext.py", line 26, in execfile exec(code, glob, glob) File "src/cmarkgfm/build_cmark.py", line 21, in <module> with open(CMARK_DEF_H_PATH, encoding='utf-8') as fh: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ FileNotFoundError: [Errno 2] No such file or directory: '/tmp/pip- install-8e12fhsc/cmarkgfm_dbeb0911a2014cbe9bb4b5b09ee7602f/src/cmarkgfm/ cmark.cffi.h' [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. error: subprocess-exited-with-error × Getting requirements to build wheel did not run successfully. │ exit code: 1 ╰─> See above for output. note: This error originates from a subprocess, and is likely not a problem with pip. -- Mit freundlichen Gruessen, Andreas Vetter

1 month, 3 weeks

[MM3-users] Re: MM3 not starting afte an upgrade

by Gelpi Andrea

Il 23/07/20 23:05, Mark Sapiro ha scritto: > On 7/23/20 4:35 AM, Gelpi Andrea wrote: >> Hi, >> to day in a Debian system I upgraded some packages. >> >> After the MM3 doesn't start anymore. . . . >> Jul 23 13:29:39 posta mailman3[2608]: os.kill(pid, 0) >> Jul 23 13:29:39 posta mailman3[2608]: PermissionError: [Errno 1] >> Operation not permitted > > > I think you have a stale lock issue and the master is trying to > determine if the process that set it still exists. > > Remove Mailman's var/locks/master.lck* > Thanks Mark, now MM3 star but postorius is not working. The web pagge return: An error occurred while processing your request. I receive an email with: ... Exception Type: KeyError at /postorius/lists/ Exception Value: 'file' Request information: USER: AnonymousUser GET: No GET data POST: No POST data FILES: No FILES data COOKIES: No cookie data Is that related to Django id setting or there is a passphrase mismach some where? How can I check? -- Gelpi ing. Andrea ************************************************** I documenti vitali dimostreranno la loro vitalitˆ spostandosi spontaneamente da dove li avevate lasciati a dove non riuscirete a trovarli. **************************************************

5 years, 4 months

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

by Alex Schuilenburg

On Fri, 2020-10-02 at 12:00 -0700, Mark Sapiro wrote: > [...]There's much more detail in my reply at< > https://gitlab.com/mailman/hyperkitty/-/issues/320#note_422894486>;, > butyou can fix the ResponseNotReady() issue from the sync_mailman job > byfinding the entries in the hyperkitty_sender table with > invalidaddresses in the address column and deleting them. As per comment https://gitlab.com/mailman/hyperkitty/-/issues/320#note_422958260 , it was not a simple delete, but an insert/update/delete > We can try to address this specific issue in hyperkitty_import, > butthere are in general various mbox defects that we can't detect. > mboxesneed to be checked for unescaped `From ` lines in message > bodies andother defects before importing them. The Mailman 2.1 > bin/cleanarchscript and the new hyperkitty/contrib/check_hk_import > script can helpwith some of this. I ran both on the original archive, cleanarch made no changes and check_hk_import just retported the number of messages. As it turns out, the message was imported, but with the dodgy email as sender which was fixed by the insert/update as per my comment. Hope you have some success with the redacted mbox example. Cheers -- Alex

5 years, 2 months

[MM3-users] Re: problems installing mailman3 under gentoo and upgrading mailman2 to mailman3

by John Covici

On Sat, 13 Mar 2021 14:46:55 -0500, Mark Sapiro wrote: > > On 3/13/21 11:14 AM, John Covici wrote: > > > > Now one thing came up while trying to create the database, I got a > > traceback complaining about a revision error because gentoo had a > > slightly different version (3.3.2) instead of 3.3.3 using pip. When I > > upgrade mailman, am I going to have to do something to the database as > > well and why should the database have some kind of reference to the > > mailman version? > > > I don't know why this is an issue. You shouldn't need to do anything > with the database when you upgrade. Please post the full traceback and > error message. Sorry I can't reproduce it, after dropping and recreating the database the error went away, but it was in alembic and it was talking about an invalid revision and gave a long hex string. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una covici(a)ccs.covici.com

4 years, 9 months

[MM3-users] Re: mailman-cli tools

by Abhilash Raj

On Wed, Sep 27, 2017, at 08:44 AM, Mark Sapiro wrote: > On 09/27/2017 08:26 AM, Dmitry Makovey wrote: > > On 09/27/2017 08:25 AM, Dmitry Makovey wrote: > >> I've come across mailman-cli docs: > >> > >> http://mailman-cli.readthedocs.io/en/latest/src/mailmanclient/cli/docs/usin… > >> This is basically one of our GSoC projects which hasn't yet been merged with MailmanClient. It uses the REST API to to provide a command line client for Mailman, while there hasn't been any in-compatible changes in API since this project was finished, I am not sure about the current status of it. > >> yet I cannot figure out what's the official source for the installation. Official source for MailmanClient is at gitlab.com/mailman/mailmanclient and it doesn't have a CLI, the Github project you linked to says right on the top that it is not official project (Thanks for that Rajeev!). Also, I would say not to use this client to remotely access Mailman, the REST API is not meant to be exposed over internet (unless you have a VPN or other sort of setup to securely access the box remotely). -- Abhilash Raj maxking(a)asynchronous.in

8 years, 2 months

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

by Gilles Filippini

Mark Sapiro a écrit le 15/06/2020 à 20:21 : > On 6/15/20 9:43 AM, Gilles Filippini wrote: >> Hi, >> >> I'm seeing the above error in mailman-core logs each time an email is >> processed. Is there something I missed in the configuration? I'm using >> dockerized mailman 0.3 from maxking. > > > I'm guessing you have one message in var/archives/hyperkitty/spool/ that > is causing this issue. The message itself will probably have invalid > utf-8 encodings in a message part declared as charset=utf-8. > > Every time a new message is archived, HyperKitty reprocesses this > message and hits the error again. > > You can examine the message with `bin/mailman qfile`. It is a Python > pickle of a message object. There are 4 emails stored into this folder. 3 of them are spam, and the last one is a legitimate email. This is annoying that such emails could accumulate and stay into var/archives/hyperkitty/spool/ forever, causing more and more hyperkitty errors. Any idea how to make their processing more error proof? Thanks, _g.

5 years, 5 months

[MM3-users] Re: Phantom Email Address in Nonmember List

by Steve Brown

Mark Sapiro wrote: > The senders are defined as addresses in the headers listed in > the configuration setting sender_headers, default = from, from_ > meaning envelope sender, reply-to and sender. See > <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.…> This was very useful in explaining why MM3 (3.3.9) accepted the problem post and attributed it to my address, even when seeing the bounce+ address as a different sender. Thank you for taking the time to reply. > Are you saying that the bounce+... address ends up as a nonmember of > the list you are sending to. I don't think that should happen. Yes, that is what is happening, but only for messages from the steve@stevebrown address. I can send a screenshot and a .txt of the headers (of the message after sent back to me from MM3 and long!) but didn't see a way to do that on the archive page. Do I need to post from my gmail address? One clue I hadn't spotted before was a bodyhash_mismatch warning in the headers. No idea where that came from. Doesn't appear in emails from me to other addresses. Steve

1 year, 2 months

[MM3-users] Re: Deleting moderation requests in database

by Joachim Schrod

Mark Sapiro writes: > On 12/2/24 6:40 PM, Joachim Schrod wrote: > > > > First: I assume that all information about moderation is in the > > database mailman3. If that's not the case, please tell me. > > > It is the case, but it's easier to use mailman shell. Something like > ``` > $ mailman shell -l test.example.com > Welcome to the GNU Mailman shell > Use commit() to commit changes. > Use abort() to discard changes since the last commit. > Exit with ctrl+D does an implicit commit() but exit() does not. > The variable 'm' is the test.example.com mailing list > >>> pendingsdb = getUtility(IPendings) > >>> for token, data in pendingsdb.find(m): > ... if data.get('token_owner') == 'moderator': > ... if data['type'] == 'unsubscription': > ... pendingsdb.confirm(token, expunge=True) > ... > >>> commit() > ``` Thanks a lot, worked like a charm! Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Joachim Schrod Email: joachim(a)schrod.org Roedermark, Germany ``How do we persuade new users that spreading fonts across the page like peanut butter across hot toast is not necessarily the route to typographic excellence?'' -- Peter Flynn

1 year

[MM3-users] Re: Member Issue Discovered

by Brian Carpenter

On 10/23/20 1:04 PM, Mark Sapiro wrote: > On 10/23/20 9:37 AM, Brian Carpenter wrote: >> How would a person already be a core user outside of a registration with >> Affinity? Via a list subscription or the import21 script? > > Yes, or even just by sending a post to a list as a nonmember. > > Everyone who is or has been a member, non-member, owner or moderator of > a list has a user and one or more address records in Mailman core. And those records are kept in the database? Is that correct? >> I do want to apologize for my tone Mark. I was wrong in the way I communicated. > > Apology accepted. I understand that it can be frustrating to be > dependent on something you don't control and that this can sometimes > lead to "anomalous" behavior. > > Here's a take on this that is intended to be humorous, but is actually > quite frightening. https://xkcd.com/2347/ I actually came across that cartoon months ago and that one person reminded me of you. So the fact that you are sharing that cartoon is ironic and very funny! -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 1 month

[MM3-users] Re: Extracting mailing list users

by Eggert Ehmke

Am Montag, 2. Januar 2023, 02:40:58 CET schrieb Mark Sapiro: > Understood, but there are a couple of things at work here. One is that > this particular task is a one-off the correct the result of a bug, but > perhaps more significantly, mailman developers (at least me) are > comfortable with `withlist` (it's been around since MM 2.1) and if I can > do it that way, it reduces the motivation to make something more > friendly for the normal admin. Unfortunately doing things easily that > way requires a lot of specialized knowledge of Mailman internals, so > most admins need help with it. Mark, I completely understand your situation as a core developer with limited time and lots of requests from all directions. Being a Python programmer myself, I would be happy with a consistent documentation of the relevant Python classes to be able to develop own applications. The isolated code snippets in the mm3 documentation are not too helpful. Such a documentation would possibly remove some of the workload you feel by constantly answering admin questions.´ When you look at the documentation of the Qt library you know what I mean. Thank you again for this great project! Cheers, Eggert

2 years, 11 months

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

by Brian Carpenter

On 10/21/20 1:14 PM, Mark Sapiro wrote: > 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. Well I can't dictate that to my list owners and there is no confirm token sent with the moderation notice. Why include this option in Postorius when it can't be properly handled? -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 1 month

[MM3-users] Re: Apache+mod_wsgi issue

by Odhiambo Washington

On Sun, Dec 25, 2022 at 3:47 PM Stephen J. Turnbull < stephenjturnbull(a)gmail.com> wrote: > Mark Sapiro writes: > > > You don't need all of those. ^postorius/ and ^mailman3/ are two > > different ways to access Postorius, and ^hyperkitty/ and ^archives/ are > > two different ways to access HypereKitty. You only need one of each, > > That's true from "outside", but there are internal links as well. For > example, in Postorius top page, the link to HyperKitty is .../archives. > I guess it's a good idea to grep the templates to see which URLS are > used. > > > > Now my question is about what could be adding the /mailman3. Is it > possible > > > that I installed something out of the ordinary? > > Besides mod_wsgi as Mark suggests and the uwsgi configuration, the > only thing I can think of is an Apache rewrite rule. It's not in the > Postorius and HyperKitty templates. > And I do not have any rewrite rules in my VHOST config: https://pastebin.ubuntu.com/p/9MRMJST9zZ/ -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 11 months

[MM3-users] Re: Remove ALL Members button - was: Re: Setting base_url for the domain to use it in the templates.

by Odhiambo Washington

On Thu, Jul 11, 2024 at 6:28 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/10/24 10:46 PM, Odhiambo Washington via Mailman-users wrote: > > > > I find the unsubscribe_all button quite scary! I have never used it > though, > > so I am not quite sure about its behavior. What scares me > > is the possibility of clicking it and then in one fell swoop you've > removed > > ALL the members without a "confirmation". > > See the thread at > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > and the issue at https://gitlab.com/mailman/postorius/-/issues/545. > > Bottom line - there is a confirmation. Try it, perhaps on a test list if > you're really scared. > Will do that test :) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 5 months

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

by Gerald Vogt

Hi, On 04.11.24 02:06, Mark Sapiro wrote: > On 11/3/24 11:31, Arte Chambers via Mailman-users wrote: > 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). is it really necessary that the mailman user can write that directory? For most services, directories and files in /etc/ may be readable for the service but usually not writable as you don't want the service itself change it's core configuration. On your server it looks like this: # ls -la /etc/mailman3 total 28 drwxr-xr-x. 2 root mailman 95 Oct 25 08:12 . drwxr-xr-x. 99 root root 8192 Oct 29 07:42 .. -rw-r--r--. 1 root mailman 266 Oct 25 07:37 gunicorn.conf -rw-r-----. 1 root mailman 92 Nov 21 2023 mailman-hyperkitty.cfg -rw-r-----. 1 root mailman 797 Sep 9 11:20 mailman.cfg -rw-r-----. 1 root mailman 3015 Oct 25 08:12 settings.py and it works just fine. Regards, Gerald

1 year, 1 month

[MM3-users] Re: Can't subscribe on new site/domain

by Flo

On 10/10/25 03:59, Mark Sapiro wrote: >> >> Is there a possibility to export all members including real names. It >> doesn't work with Postorius, yet, is there another possibility? If I >> have my user data exported, I could delete everything and start from >> scratch. Maybe this is the most reasonable ... > > You can install mailman following https://docs.mailman3.org/en/latest/ > install/virtualenv.html and keep your existing database(s) which will > include all lists and memberships. > I think I am still using a sqlite database. This is the database when I installed the packages. There is a hint that it should be replaced by mysql or postgres. I only have very few lists, yet. The only thing I really don't want to loose is the addresses and names. > The current released versions of Postorius include only emails in the > csv export. This is fixed for the next release by https://gitlab.com/ > mailman/postorius/-/merge_requests/993 > > You can currently get a list of members with display names with the > `mailman members` command. See `mailman members --help`. > This is working! That's great. Thank you! Flo

2 months

[MM3-users] Re: Hyperkitty CPU usage

by Alain Kohli

I have run "python manage.py rebuild_index" before, doesn't that do clear_index as well? Apart from that, I run hyperkitty in a docker container and didn't know fulltext_index should be persistent, so that got deleted after every version update for sure. On 4/26/19 10:18 PM, Mark Sapiro wrote: > On 4/26/19 11:14 AM, Alain Kohli wrote: >> I see loads of "A string literal cannot contain NUL (0x00) characters." >> messages, but I haven't found missing messages in the archives yet. Not >> sure how that could be related, though. Apart from that I don't see >> anything unusual. The other jobs (quarter_hourly, hourly, etc.) seem to >> run and finish normally. > > Did you upgrade from a Python 2.7 version of HyperKitty to a Python 3 > version? The Haystack/Whoosh search engine databases are not compatible > between the two and "A string literal cannot contain NUL (0x00) > characters." is the symptom. > > You need to run 'python manage.py clear_index' or just remove all the > files from the directory defined as 'PATH' under HAYSTACK_CONNECTIONS in > your settings file (normally 'fulltext_index' in the same directory that > contains your settings.py. >

6 years, 7 months

[MM3-users] Re: Hipperkitty failing to archive messages in a list

by Guillermo Hernandez (Oldno7)

On 6/1/22 19:19, Mark Sapiro wrote: > On 1/6/22 4:25 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> >> In the last part of your suggestions you wrote: >> >> "I suggest you do >> >> pip install --upgrade hyperkitty mailman-hyperkitty >> >> and ensure it installs hyperkitty 1.3.5 and mailman-hyperkitty 1.2.0" >> >> But this is exactly what made me fall in this mess: > > > Sorry, I was confused. I thought the error message you were seeing was > changed before HyperKitty 1.3.5 was released, but that isn't correct. > > The problem is probably in Apache. See the last 2 posts in the thread > at > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > I'll try tomorrow, now I'm a bit slow-head after a hard day (and the collateral effects of the third vaccine). It looks the right way (I have apache running in that server) to solve it. What intrigues me is the fact that I didn't change anything in the apache config or update apache itself. Well, tomorrow will be antoher day. Thanks for the point.

3 years, 11 months

[MM3-users] Re: Held for notification - runner exception: 'ascii' codec can't encode character

by Seth Seeger

> On Jan 2, 2022, at 3:47 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > Thanks for sending me the shunted .pck. It turns out I didn't need it. Had I looked more closely at the Traceback, I would have realized that the issue is that the list's list:admin:action:post template contains non-ascii. In particular, the character in position 5 is ’ which is a unicode right_single_quote, not an ascii apostrophe. > > There may be other unicode fancy quotes ad well. > > You can fix the template to contain only ascii or you can set the character set for English to utf-8 by adding > ``` > [language.en] > charset: utf-8 > ``` > to mailman.cfg. The downside of the latter is that outgoing message bodies will always be base64 encoded which generally precludes grepping mailboxes to find things. Ah hah! Right you are. I removed the offending fancy apostrophe. What about that traceback pointed to the template? (Is it something I could have figured out?) Is it possible to filter out UTF-8 chars from the templates when they are saved in Postorius? Thanks again, Seth

3 years, 11 months

[MM3-users] Re: Python backtrace from `mailman -h`

by Peter Chubb

>>>>> "Mark" == Mark Sapiro <mark(a)msapiro.net> writes: Mark> On 8/24/25 17:03, Peter Chubb via Mailman-users wrote: >> Hi Folks, I'm running the Debian-packaged mailman3 (yes I know ...) >> and running: sudo -u list mailman -h gives a python backtrace >> (which I've appended the tail end of). Can someone who has the >> upstream installed version (using venv) please check that `mailman >> -h` works there before I waste too much time investigating in the >> wrong places? Mark> Yes, `mailman -h` works and produces the same help output and Mark> list of subcommands as `mailman` with no arguments or Mark> options. Does it work with no options? Does it work if you do Mark> `mailman -C path/to/mailman.cfg -h`? Thanks. Without options it works; and it works with an explicit config path. So I know where to look to fix it (and will report it on the Debian bug tracker) Interestingly: sudo -u list mailman -C /etc/mailman3/mailman.cfg -h works, but sudo -u list env MAILMAN_CONFIG_FILE=/etc/mailman3/mailman.cfg mailman -h does not. And sudo -u list mailman info reports /etc/mailman3/mailman.cfg as the current configuration file. Peter C

3 months, 2 weeks

[MM3-users] Re: Avoiding non-members to be saved.

by Guillermo Hernandez (Oldno7)

On 7/8/21 20:03, Mark Sapiro wrote: > This is the way MM 3 works. The only reason *_these_nonmembers exists > in MM 3 is to support the legacy regexps from MM 2.1. For non-regexp > addresses the address is a nonmember with the appropriate moderation > action. > > I actually find this convenient. When a nonmember posts spam to a list > and that spam is held, I discard the spam in Postorius and at the same > time set the nonmember's moderation action to discard so I never see > any more from that address. Also, when someone who I recognize as a > list member posts from an alternate nonmember address, I can accept > that post and set the nonmember address moderation action to default > processing. > I find it very convenient too, but it concerns me that spammers, really "profesional" spammers and senders of phising mail change the forged address and sender domain too rapidly to track them. As of it, the non-member database is growing more and more. It could be a "monster" in two or three years... Not a problem now. And I know now how to delete them in one go :) --

4 years, 4 months

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

by Stephen J. Turnbull

Mark Sapiro writes: > But postorius and hyperkitty are dependencies of mailmanweb so only Are they? I'm pretty sure that in my current project which has a pre-existing archiver they wish to keep using I only installed postorius, not hyperkitty. ... oops, HyperKitty *is* there. OK, need to uninstall that. That's actually a bit annoying, since mailmanweb is a friendlier interface for control of either of HyperKitty and Postorius than the underlying Django utilities even if you don't want the other and its unique dependencies (such as Whoosh). (Issue #32 created) OK, so your two-venv approach should actually work. I still don't think it's much of a win since to finish setup you still have to do a lot of work as root and a lot of work outside of pipx's control. Basically it saves one "python3 -m venv", at the cost of "pipx run" to run each program in its own venv. Note, it doesn't save me any venv activationss because I put that in the mailman user's shell .rc. Wikinaut asks: > Has anyone tried that already? Why not you? Steve

1 year, 10 months

[MM3-users] Re: Hiding an ML from a site

by Odhiambo Washington

On Wed, Feb 7, 2024 at 9:45 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On February 6, 2024 7:45:14 AM PST, Odhiambo Washington > <odhiambo(a)gmail.com> wrote: > > > >I had this set to True in settings_local.py, but False in settings.py. > >So it seems to not make a difference in my setup. > > In a standard setup, anything set in settings_local.py overrides any > corresponding setting in settings.py. > > That said, FILTER_VHOSTS is not perfect. It only works for Postorius if > the separate web hosts also have different mail hosts. See lines 1051 et > seq at > < > https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/views/list… > > > What should I do then? Edit some file? Apply some patch? It's pretty easy for me to create a DNS record for the same server (IP) for use with the web host that I'd like to hide. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 10 months

[MM3-users] Re: MM3 Docker

by Odhiambo Washington

On Tue, Jan 8, 2019, 20:34 Abhilash Raj <maxking(a)asynchronous.in wrote: > On Tue, Jan 8, 2019, at 5:52 AM, Odhiambo Washington wrote: > > On Tue, 8 Jan 2019 at 03:29, Mark Sapiro <mark(a)msapiro.net> wrote: > > > > > On 1/7/19 1:18 AM, Odhiambo Washington wrote: > > > > On Sun, 6 Jan 2019 at 23:39, Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> > > > >> Please help me understand what steps are missing and I will try to > > > >> provide the information. > > > > > > > > > > > > Okay. > > > > > > > > At the installation stage, you say the following: > > > > "I already had some things set up in /opt/mailman including a git > > > > subdirectory containing clones of the GitLab mailman, mailmanclient, > > > > mailman-hyperkitty, hyperkitty, django-mailman3 and > > > > postorius projects. On the third server I have added mailman-suite > > > > because I use the settings.py from that project as the basis for > mine." > > > > > > > > Please assume that the reader is a newbie to python3 virtualenv and > give > > > the > > > > details of the commands they need to execute to (a) clone all the > > > projects > > > > needed > > > > and (b) create the virtualenv. > > > > > > > > The next steps are: > > > > mkdir /opt/mailman/mm > > > > > > > > Then you say "I then created a /opt/mailman/mm directory and within > that > > > a > > > > Python 3.6 virtualenv" > > > > What happens here is something that needs clarification, because you > are > > > > specific about "python3.6". > > > > I have googled and realized that one has to be specific about the > python > > > > version they want to use in their virtualenv > > > > as shown here -> > > > > > > > > https://stackoverflow.com/questions/45293436/how-to-specify-python-version-… > > > > > > > > exact command to execute to create the /opt/mailman/mm/venv > > > > exact command to execute to activate virtualenv > > > > > > > > > I have added a comment to the page which I hope gives you what you > want. > > > > > > I also added a section on templates instead of referring to a prior > > > version of the page. > > > > > > > That makes it better. > > However, as a newbie, something is not yet clear: > > > > "When active in a particular shell, it can be deactivated with the > command > > > > deactivate > > or by exiting that shell." > > > > HI am trying to understand the effect of detaching from a venv. I am > > assuming that a virtualenv is a container that is supposed to be always > > active for the services within to be accessible. Is that right? So, how > do > > I ensure it's always running/up, or that does not matter as the scripts > > which run the services will always refer to the files? > > virtualenv is not actually a container that is supposed to be active. It > is merely a set of settings that are applied to your SHELL when you are > in the virtual environment. > > It is not supposed to be always active, only when you actually want to > run commands in that virtual environment. The services will keep on > running after you deactivate your shell and would function like other > normal services on your machine. > > -- > thanks, > Abhilash Raj (maxking) > Thank you for clarifying. So once I have a venv created, the services will just run as long as the startup scripts are running even when I'm logged out of the system? >

6 years, 11 months

[MM3-users] Re: Handling of SPAM mails in mailman3 - Check for X-Spam Header

by Torge Riedel

Am 16.01.20 um 21:43 schrieb Mark Sapiro: > On 1/16/20 10:51 AM, Torge Riedel wrote: >> Such SPAM mails are currently hold for moderation with reason "not from >> a list member". Is there no check for the "X-Spam: Yes" header or is >> this check done later? > > If you set a Header Filter (in Postorius the Header filters tab) those > checks are done before non-member moderation. > > This won't work for posts from members because the header checks are > done between member moderation checks and non-member moderation checks, > but if you create a Header Filter for header 'x-spam' and pattern 'yes' > with action hold, a message from a non-member which has an X-Spam: Yes > header should be held for that reason. > > Hi Mark, thank you for your answer. Just to understand that right: In case a posting with an "X-Spam: Yes" header comes from a member, it will not be held? It will be directly forwarded to the list? If yes, is there any chance to change or extend this? Best regards Torge

5 years, 10 months

[MM3-users] Re: postfix malformed address with confirm replies

by Stephen J. Turnbull

Mark Sapiro writes: > On 2/27/21 4:36 AM, Stephen J. Turnbull wrote: > > is legal, and I think that most servers will accept it, but RFC > > 5321 sets a limit of 64 octets on mailboxes[1], and your > > confirmation mailbox is 67 octets. > > Since the -confirm+<token> part is fixed at 49 octets, this would imply > a limit in list names of 15 octets. Ouch! I'm pretty sure we would have run into this before, if there were a lot of servers out there imposing this limit. 15 octets is pretty darn short, there are probably quite a few list names out there longer than that. Not to mention that the RFC itself says "you SHOULD NOT be a jerk about this". :-) So I don't think this is a big problem in practice, and I hope Steve can reconfigure the obstructive server to not be so picky. For Mailman, I doubt we need a full SHA1 (?) for the purpose. We can truncate the thing, probably opportunistically (ie, so the whole confirmation mailbox fits in 64 octets, or we could even parse the bounce message and resend only if we run into a problem). Steve

4 years, 9 months

[MM3-users] Re: External MTA incoming mail: configuration

by Odhiambo Washington

On Fri, Aug 2, 2024 at 6:44 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 8/2/24 08:12, Roland Giesler via Mailman-users wrote: > > > > It seems though that since I'm not running a local MTA, when then mail > > arrives at the mailman3 server, there's nothing that can process it. So > > should I run postfix in it's most basic setup to allow mail to be > > received or what is the best way to deal with it? Mailman3 has to > > receive mail like signup confirmations, etc after all, not? > > If you use transport_maps on the remote MTA to relay the list mail to > port 8024 on the Mailman server, Mailman's LMTP runner will receive the > mail and you don't need a local MTA. > Nice one! I'd love to know how this config is done in Postfix. Heading to ask Uncle G. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 4 months

[MM3-users] Re: Auth question

by Simon Hanna

On March 31, 2017 6:34:18 PM GMT+02:00, Mark Sapiro <mark(a)msapiro.net> wrote: >On 03/31/2017 01:06 AM, David Krantz wrote: >> On Fri, Mar 31, 2017 at 9:29 AM, Simon Hanna ><simon.hanna(a)serve-me.info> wrote: >>> On 03/31/2017 08:10 AM, David Krantz wrote: >>>> I think that would correspond to this line in urls.py >>>> >>>> url(r'^$', >RedirectView.as_view(url=reverse_lazy('hyperkitty.views.index.index'))), >>> Yes, that's the culprit. Replace it with the following: >>> >>> url(r'^$', RedirectView.as_view(url=reverse_lazy('hk_root'))), >>> You can also update whatever guide you were using... >> >> Great, will try that! I don't know whether I can update the guide. >> It's the one referenced earlier in this thread named something like >> setup experience of mailman 3 in production. > > >Yes, that comes from >"https://wiki.list.org/DOC/Mailman%203%20installation%20experience", >specifically the attachment urls.py. > >The interesting thing is that works for me both at ><https://lists.mailman3.org/> and <https://mail.python.org/mm3/>. Are you using the latest version of django? -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

8 years, 8 months

[MM3-users] Re: lmtp runner not starting

by Guillermo Hernandez (Oldno7)

El 1/4/23 a las 20:44, Mark Sapiro escribió: > ... > lmtp runner did not start because at some point it had died and > restarting Mailman won't restart a runner that died and was marked to > not restart. > > You need to stop Mailman and make sure when mailman is stopped that > there are no files in mailman's var/locks/ directory (remove any that > are there) and then start Mailman and lmtp runner should start. > I stopped mailman and removed all that was in there (there were many locked registers). Restarted mailman, and it shows the same error that in my previous mail. Now there is two new locked files, one (master.lck) which its content is the name of the other file. And the second one has the same content: master.lck|www.proteccion-civil.eu|9389|7022761192045613065 will try deleting the content of var/locks and restarting the server > As to why it died in the first place, there should be something in > mailman.log from the time it died. > -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

2 years, 8 months

[MM3-users] Re: Welcome message template errors

by Mark

On 2024-04-23 11:33, Mark Sapiro wrote: > On 4/22/24 17:06, Mark wrote: >> >> There was no line POSTORIUS_TEMPLATE_BASE_URL in >> /etc/mailman3/settings.py > So presumably you were getting the default > > POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000' > > from mailman-web/settings/mailman.py because of > from mailman_web.settings.mailman import * > in your settings.py. Yes. # Mailman Web configuration file. # /etc/mailman3/settings.py # Get the default settings. from mailman_web.settings.base import * from mailman_web.settings.mailman import * ... > >> Then, as site-owner, creating a new custom Welcome template (again via >> the WebUI) I can see it correctly added to the database in >> mailman.template.uri >> >> - >> https://lists.mydomain.com/mailman3/api/templates/list/lists.mydomain.com/l… That URI should have been; https://lists.mydomain.com/mailman3/api/templates/list/mytestlist.lists.myd… If I go to the above URL, the text of the list's Custom welcome message displays on an otherwise empty webpage. > > > And what happens if you go to that URL in a web browser? Also what do > you get when going to https://lists.mydomain.com/mailman3? I get the Postorius page "Mailing Lists" that displays the table of lists.

1 year, 7 months

[MM3-users] Re: MM3 Docker

by Odhiambo Washington

On Wed, 9 Jan 2019 at 00:16, Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/8/19 10:03 AM, Odhiambo Washington wrote: > > > > Thank you for clarifying. > > So once I have a venv created, the services will just run as long as the > > startup scripts are running even when I'm logged out of the system? > > > As long as the startup scripts actually reference things in the venv. > > If you look at the samples in the Recommended Configuration section at > <https://wiki.list.org/x/17891998> for > > /opt/mailman/mm/bin/django-admin (sample) Script to run Django > management commands. > > /opt/mailman/mm/bin/mailman (sample) Script to run mailman commands. > > and > > /opt/mailman/mm/bin/gunicorn (sample) Script to start Gunicorn. > > You will see they all do things like activate the venv or run a command > from venv/bin. > > > Now that has clarified the matter for me. That even when I am logged out, the scripts do the neccessary to activate the venv to run things. I hadn't looked at the scripts at all. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

6 years, 11 months

[MM3-users] Re: LTMP to Postfix problem

by Brian Carpenter

On 6/18/20 4:09 PM, Mark Sapiro wrote: > Do you have > > lmtp_host: 127.0.0.1 > lmtp_port: 8024 > > in the [mta] section of mailman.cfg? (these are the defaults) > > $ /opt/mailman/mm/bin/mailman conf|grep lmtp > [mta] lmtp_host: 127.0.0.1 > [mta] lmtp_port: 8024 I do > Is Mailman's lmtp runner listening on port 8024? > > $ sudo netstat -lntp|grep python > tcp 0 0 127.0.0.1:8024 0.0.0.0:* > LISTEN 1867/python > tcp 0 0 127.0.0.1:8000 0.0.0.0:* > LISTEN 1199/python > tcp 0 0 127.0.0.1:8001 0.0.0.0:* > LISTEN 1871/python It is. > > Is there some firewall issue blocking access to the port even from > localhost? Let me describe the problem a little better. Mail delivery from postfix to mailman works most of the time. However in the past week or so, lmtp starts refusing connections via postfix about once a day. I have port 8024 open in the firewall (UFW). There are no errors in the smtp.log file. I think restarting Mailman core seems to get things running again. -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

5 years, 5 months

[MM3-users] Re: Django-allauth compatibility (ACCOUNT_AUTHENTICATION_METHOD and ACCOUNT_EMAIL_REQUIRED)

by Jan Eden

On 2025-06-16 17:29, Mark Sapiro wrote: > On 6/16/25 15:26, Eggert Ehmke via Mailman-users wrote: > > I have django-allauth 65.9.0 and still the same problem. mailman-web runjobs minutely throws it each minute, which is annoying. > > Do you have > ``` > ACCOUNT_LOGIN_METHODS = {'email', 'username'} > ACCOUNT_SIGNUP_FIELDS = ['email*', 'username*', 'password1*', 'password2*'] > ``` > in your django settings? > > What releases of HyperKitty, Postorius and Django-Mailman3 are you running? > Current releases do not have any minutely jobs. I did have the same issue about a month ago[1] with the current versions of the above components, and these are the cronjobs I installed according to the docs[2]: @daily /opt/mailman/venv/bin/mailman digests --periodic @daily /opt/mailman/venv/bin/mailman notify * * * * * /opt/mailman/venv/bin/mailman-web runjobs minutely 0,15,30,45 * * * * /opt/mailman/venv/bin/mailman-web runjobs quarter_hourly @hourly /opt/mailman/venv/bin/mailman-web runjobs hourly @daily /opt/mailman/venv/bin/mailman-web runjobs daily @weekly /opt/mailman/venv/bin/mailman-web runjobs weekly @monthly /opt/mailman/venv/bin/mailman-web runjobs monthly @yearly /opt/mailman/venv/bin/mailman-web runjobs yearly - Jan [1] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… [2] https://docs.mailman3.org/en/latest/install/virtualenv.html#cron-jobs-for-m…

5 months, 3 weeks

[MM3-users] Re: Hyperkitty messages stuck in spool

by Stephen J. Turnbull

Mark Sapiro writes: > On 11/18/21 6:38 AM, Andrew Hodgson wrote: > > > > Ok thanks for this. Its happening because the Gunicorn process > > running the Django server is being killed due to OOM > > conditions. Is there any settings I can change to > > troubleshoot/throttle this in Gunicorn or Django? > > I don't think there's anything that can be done in gunicorn or django > about this. This is an OS issue. You need to give the server more memory > or allocate a (bigger) swap file. If those things are difficult, depending on OS and the hardware, it may also be possible to tell the OS that gunicorn is an import process that should not be killed. But in the long run, the server needs more memory. In theory there could be a memory leak in Python or one of the Mailman apps, but I haven't heard of it. And at least the Linux kernel seems to be perfectly happy to kill random processes that are well-behaved. So the fact gunicorn is getting killed is not strong evidence that it's causing the memory pressure, we'd really need to see the stats. Steve

4 years

[MM3-users]Re: mailman 2 vs. mailman 3: what happened to multipart/digest?

by John Hein

Mark Sapiro wrote at 19:18 -0700 on May 12, 2016: > On 5/12/16 3:46 PM, John wrote: > > But mm 2 had: > > > > multipart/mixed > > text/plain (the digest heading) > > text/plain (the TOC) > > multipart/digest <--- this is the part that's gone in mm3 > > message/rfc822 > > message-1 > > message/rfc822 > > message-2 > > ... > > text/plain (footer) > > > > So was that removal intentional, a bug or ?? > > > I'm sorry. I missed the point of your OP. I think it's a bug. > > The doctest at > <http://mailman.readthedocs.io/en/release-3.0/src/mailman/runners/docs/diges…>, > the part just after "The MIME digest has lots of good stuff, all > contained in the multipart." is clearly missing the multipart/digest part. > > It appears that this got lost in the refactoring of the MM2 code for > MM3. Please file an issue at > <https://gitlab.com/mailman/mailman/issues/new>. You can assign it to me > (msapiro), but it any case, I'll work on fixing it. https://gitlab.com/mailman/mailman/issues/234 Thanks.

9 years, 7 months

[MM3-users] Docker, Mailman 3, templates and list user accounts

by Henrik Rasmussen

I used Docker to installed Mailman 3. The top header of the web interface says "Example.Com" while linking to the correct site URL (I believe coming from SERVE_FROM_DOMAIN). In a post[1], Mark Sapiro referred to the template system in Mailman 3 by pointing out that "a custom template can be put in var/templates/site/en/welcome.txt or var/templates/domains/example.com/en/welcome.txt<http://var/templates/domains/example.com/en/welcome.txt> or var/templates/lists/listname.example.com/en/welcome.txt<http://var/templates/lists/listname.example.com/en/welcome.txt> where var is Mailman's configured var_dir". I believe this refers to the mail templates. 1) Where do I change the similar template system, for the web interface, without breaking a laver upgrade? 2) How do I change the site name in the top of the web interface on Mailman 3 to my subside and ? [1] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… The Mailman command in Mailman Core doesn't seem to have a command for listing the accounts users have created by using Sign up in the web interface, so I believe that accounts may be created in the webinterface. Is there similar commands for the web interface like the mailman commands for the Mailman core? Regards, Henrik Rasmussen

8 years, 4 months

[MM3-users] Re: bounces with empty message-id

by Peter Münster

On Tue, Jan 30 2018, Mark Sapiro wrote: > The underlying issue is the orange.fr domain is sending DSNs without a > Message-ID: header. Yes. Is a Message-ID header required in a DSN by any RFC? > If you used VERP (i.e. set verp_delivery_interval = 1 in the [mta] > section of your config), this log message I have verp_delivery_interval = 10 ... > would contain to=<test-bounces+user=example.com(a)my-domain.org> and you > could identify the bouncing address (user(a)example.com in this case) that > way. Yes, that's my intention, but first of all, mailman must receive the DSN. > Beyond that, there are still other issues, the biggest of which is > currently, Mailman is not processing bounces other than storing them in > the database. See <https://gitlab.com/mailman/mailman/issues/343>. Shouldn't the DSNs be forwarded to the owner of the list? > if a recipient MTA can't create a DSN that has a Message-ID:, would > you trust what else it does? I don't know. The question for me is: does the remote MTA needs a fix (i.e. the Message-ID is required by some RFC), or mailman (i.e. a DSN without Message-ID should be acceptable)? -- Peter

7 years, 10 months

[MM3-users] Re: Log rotation

by Abhilash Raj

On Tue, Apr 10, 2018, at 4:12 PM, Mark Sapiro wrote: > On 04/10/2018 03:04 PM, Darren Smith wrote: > > > > 1) Has anyone come up with a good log rotation strategy that doesn't > > necessitate a restart of the service? > > I think Abhilash has answered this, but for completeness, here's what I > use on lists.mailman3.org which uses nginx and gunicorn > > Mailman's logs > > /opt/mailman/mailman-bundler/var/logs/*.log { > missingok > sharedscripts > su mailman mailman > postrotate > /opt/mailman/mailman-bundler/bin/mailman reopen &>/dev/null || true > if [ -r /opt/mailman/mailman-bundler/var/gunicorn.pid ]; then > PID=`cat /opt/mailman/mailman-bundler/var/gunicorn.pid` > kill -s USR1 $PID > fi > endscript > } > > mailman-web log > > /var/log/mailman-web/*.log { > missingok > notifempty > delaycompress > su mailman mailman > } > > > And here's mail.python.org with apache and mod_wsgi > > Mailman's logs > > /opt/mailman/mailman-bundler/var/logs/*.log { > missingok > sharedscripts > su mailman mailman > postrotate > /opt/mailman/mailman-bundler/bin/mailman reopen &>/dev/null || true Oh, I didn't know about the "mailman reopen" command, thanks Mark! -- Abhilash Raj maxking(a)asynchronous.in

7 years, 8 months

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

by Elias Rudberg

Hello again, Mark Sapiro wrote: > I'm not certain, but I think it's a Django issue > rather than a Mailman issue. I got a reply about this in the Django forum at https://forum.djangoproject.com/t/getting-error-need-2-values-to-unpack-in-… Quoting from that forum post: "This is not a bug in Django. This would be functioning in the manner that Django is designed and documented at [link]" "The error here is trying to use a reference in a template without having the view ensure that the context being passed is correct." "Both the template and the view should be corrected here. The view should ensure the right data is put into the context, probably under a different name, and the template should render that data from that name." (end of quote from Django forum) So they think it is not a bug in Django. Does it make sense, that "the template and the view should be corrected" as suggested there? (The template in question would be pagination.html but I'm not sure exactly how it should be corrected.) / Elias

1 year, 4 months

[MM3-users] Re: How to remove global ban using API?

by Nathan Dixon

For those who are interested. To be able to use global_bans = IBanManager(None) and not get the following error: Traceback (most recent call last): File "<stdin>", line 1, in <module>TypeError: ('Could not adapt', None, <InterfaceClass mailman.interfaces.bans.IBanManager>) You need to use: mailman shell Not a standard python3 session. To actually update the global bans not via the API, which has some limitations at the moment (see the issue on Gitlab), I have done the following workaround (later I will put in checks for an existing ban to do an update instead, or a delete then create of the new ban): 1) I create a python script within the docker container within the existing PYTHONPATH that will be the module that runs when I want to create or update my ban (in this case under /usr/bin/) #!/bin/env python def create_valid_domains_ban(valid_domains_regex): from mailman.interfaces.bans import IBanManager global_bans = IBanManager(None) global_bans.ban(valid_domains_regex) print(list(global_bans.bans)[0].email) 2) I can then invoke this as a mailman module from the server using docker exec mailman-core mailman shell -r create_valid_domains_ban $valid_domains_regex On Wed, 15 May 2019 at 21:21, Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/15/19 9:46 AM, Nathan Dixon wrote: > > > > I can create the ban fine by the following: > > > > from mailmanclient import Client > > client = Client(URI,apiuser,apipass) > > > client.bans.add("^(?!.*[(a)\.](validdomain1\.com|validdomain2\.org|validdomain3\.co\.uk)") > > > This is apparently a typo - missing ')' - in the re as you have it > correct below. > > > > However, I cannot seem to be able to remove it using the api: > >>>> client.bans[0].delete() > ... > >>>> client.bans.remove(str(client.bans[0])) > ... > >>>> > > > client.bans.remove("^(?!.*[(a)\.](validdomain1\.com|validdomain2\.org|validdomain3\.co\.uk))") > > > All of the above work for me with both API 3.0 and 3.1 in a non-docker > install of the current GitLab HEADs > > > > And also, when I now try and go into the mailman-core docker image to use > > the mailman.interfaces.bans, it will not let me see the global bans: > > > >>>> from mailman.interfaces.bans import IBanManager > >>>> global_bans = IBanManager(None) > > Traceback (most recent call last): > > File "<stdin>", line 1, in <module> > > TypeError: ('Could not adapt', None, <InterfaceClass > > mailman.interfaces.bans.IBanManager>) > > > I don't see this either. > > > > I have opened an issue in Gitlab for this as I feel it may be a bug > related > > to regex and global bans (there was a similar one for list banned > > addresses): https://gitlab.com/mailman/mailman/issues/598 > > > I also commented on the GitLab issue. I think this must be an issue with > the docker images. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- *Nathan Dixon* MEng Senior Software Architect m: +44 (0)7402 690311 t: +44 (0)20 81231252 e: nathan.dixon(a)evadon.com w: www.evadon.com This e-mail and any attachments are confidential and may be protected by legal, professional or other privilege. If you are not the intended recipient you should not store it, copy it, re-transmit it, use it or disclose its contents, but should return it to the sender immediately and delete your copy from your system. The views expressed are those of the sender and not necessarily those of Evadon. Please note that whilst we scan all e-mails for viruses we cannot guarantee that any e-mail is virus-free. Please be advised that we expressly reserve the right to monitor email content for the purposes of ensuring compliance with legal requirements and company policies and your sending to, or receiving from, us of any email constitutes your agreement to these terms. Evadon Dynamics Limited, registered in England No. 09494097. Registered Office: Electric Works, Sheffield Digital Campus, 3 Concourse Way, Sheffield, S1 2BJ

6 years, 6 months

[MM3-users] Re: hyperkitty won't list more than 5 posts and shows empty grey Activity Summary box

by Barry Warsaw

On Aug 9, 2017, at 15:45, Mark Sapiro <mark(a)msapiro.net> wrote: > However, the sending of periodic digests depends on cron running > something periodically to actually trigger the sending. Right. There will eventually be additional recurring tasks for Core too though, such as processing the bounce database for disables and unsubs, pulling messages from NNTP, and possibly others as time goes on. I’ve always thought about handling these as commands that cron would run, much as in Mailman 2, but it would also be possible to implement a runner, or runners, to do those jobs. I can see advantages and disadvantages with either approach. > Note: I've just looked at the code and there seems to be an issue with > using 'mailman digests --send' to send the periodic digests. It appears > that if a list's digest mbox has any messages, 'mailman digests --send' > will send a digest even if digest_send_periodic is false. I've just > reported <https://gitlab.com/mailman/mailman/issues/384> for this issue. Yep, thanks for the bug report. `mailman digests —periodic` seems like the right approach. Cheers, -Barry

8 years, 4 months

[MM3-users] Re: Hyperkitty Error Curiosity

by Brian Carpenter

On 11/11/20 7:40 PM, Mark Sapiro wrote: > On 11/11/20 4:18 PM, Brian Carpenter wrote: >> Some sort of auto-discard procedure after a number of retries? Is it >> possible to detect a message with a null characters and automatically >> discard them? Do such messages make it into the thread table? > > The message has been delivered to the list, but it is not archived. The > list post has an Archived-At: header with a URL, but the message isn't > there at all. The only way to get it archived is to correct the message > defect. Does the problematic message (null character) make it to the hyperkitty_thread table? > Thus, I don't think it's good to just discard the message at that point. > I'm fine with moving out of or not queueing it in the first place in > var/archives/hyperkitty/spool, but I think it should be preserved > somewhere, say in var/archives/hyperkitty/bad, and along with that, some > kind of notice sent to the site admin so bad messages don't just > accumulate without being seen. > Can a message with a null character be repaired with an automatic process? -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 1 month

[MM3-users] Re: Issues encountered while upgrading to 3.3.7

by Odhiambo Washington

On Mon, Dec 5, 2022 at 8:54 PM Mark Sapiro <mark(a)msapiro.net> wrote: > 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. > Thank you very much for the clarification. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years

[MM3-users] Re: Hyperkitty fulltext search performances

by Mark Dadgar

On Oct 4, 2020, at 8:13 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/4/20 8:07 AM, Brian Carpenter wrote: >> >> On 10/4/20 8:59 AM, Loïc Dachary wrote: >>> After a little digging it turns out the mailman3-web Debian GNU/Linux >>> package I'm using is configured to use Woosh as a haystack backend. >>> And it is not fit for volumes greater than a few hundred mega bytes. I >>> should switch to something else from the list of supported >>> backendshttps://django-haystack.readthedocs.io/en/master/backend_support.html >>> >> For our servers running Postorius/Hyperkitty, we use Xapian. I believe >> the mailman-users (MM3) list also uses Xapian. It is a lot quicker. For >> our Affinity/Empathy servers, we use Elasticsearch which we are very >> happy with. Elasticsearch does have a higher memory requirement I >> believe than Xapian. > > > Brian is correct about this list. We started with Whoosh, then went to > Elasticsearch and ultimately to Xapian. Each step gave better > performance and a smaller footprint than the one before. +1 I have ~700K posts in my archive and Xapian is FAST. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 2 months

[MM3-users] Re: If you delete a list but not the HyperKitty archive

by Philip Colmer

On Tue, 4 Jan 2022 at 18:34, Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/4/22 6:45 AM, Philip Colmer wrote: > > > > So ... should the archive be deleted when the list is deleted and it is a > > bug that it isn't? Or is it expected that access to the archive is > "frozen" > > once a list is deleted? > > > It is often desired to have a public archive available after the > corresponding list has been deleted. Even for a private archive, it may > be desirable for site admins to have access. Furthermore, a list might > not even have a HyperKitty archive in the first place. Thus, what to do > about a HyperKitty archive (or prototype archive or ...) when a list is > deleted is an administrative decision and is best left up to the site > admins to do it or not. > > As you note with a private archive, former members no longer have access > when the list is gone, but unless an attempt throws some uncaught > exception, that is not a bug. > Thanks, Mark, for the clarification. Regards Philip

3 years, 11 months

[MM3-users] Re: API timeout for one list

by Seth Seeger

> On Sep 22, 2020, at 4:30 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 9/22/20 12:45 PM, Seth Seeger wrote: >> I apologize, because I think this was talked about before, but I could not find it in the archives. >> >> For one list, the REST API times out. Doesn’t seem to matter which page I try to go to. The uwsgi-error.log entry: >> > ... >> The other lists work fine. > > This can happen on lists with lots of members. > > Try increasing the timeout. See <https://wiki.list.org/x/17892072> Thank you - that did solve my timeout problem. However, each page for this list takes between 40 and 80 seconds to load. The list has 465 members, and it’s running (via Docker) on a 2 core, 4 GB RAM Linode VM. I’ve watch htop during the load - one CPU is around 20%, and the other hovers around 80%, mostly with the process “runner”. Is there a way to optimize this list? There are no held messages, no subscription requests, no templates. The next biggest list has 438 members, and all those pages load very quickly (0-2 seconds). I can’t figure out what the difference between the two lists. Thanks, Seth

5 years, 2 months

[MM3-users] Re: Mailman3 not able to deliver emails sent through list, but moderation notifications

by Ruth Ivimey-Cook

See after: On 26/11/2022 18:18, Mark Sapiro wrote: > I found this article stating the the SMTP error message >> might be misleading: >> https://blog.tfiu.de/mailman3-cannot-connect-to-smtp-server-localhost-on-po… >> >> >> How to further debug this? >> What could be wrong with my Mailman3 instance and how to fix it? > > The article is relevant and mentions the most likely issue which is > lack of permission on one or more message templates. > > Everything in Mailman's var/ directory should be owned by Mailman's > user:group - normally `list:list` in Debian packages. While this is always true for mailman-core, in some configurations the mailman-web files are also inside the ./var/ tree, and they need to be readable (and, for some, writable) by the process acting as webserver, which may or may not be list:list. In my case (a bit off-piste) I have set mailman-web it up to run as owner=www-data, for example (I forget quite why this was needed now!!). Regards Ruth -- Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

3 years

[MM3-users] Re: Where are the subject templates hidden?

by Simon Hanna

On 11/29/2017 09:25 AM, Thor Atle Rustad wrote: > 2017-11-29 7:40 GMT+01:00 Mark Sapiro <mark(a)msapiro.net>: > >> On 11/28/2017 02:56 AM, Thor Atle Rustad wrote: >>> Using Docker. Suppose I've overcome >>> https://gitlab.com/mailman/mailman/issues/359 and I can make Mailman use >>> the templates/site/no directory for my customized templates. Yes, it >> seems >>> to be working, no hickups when national characters are used in the >>> templates. >>> >>> but... >>> >>> the welcome message still says "Welcome to the "listname" mailing list" >> in >>> English. Is it possible to change that? >> >> Have you put the desired template in >> templates/site/no/list:user:notice:welcome.txt ? >> >> -- >> > Yes, I put it there, and the text in that file is what is shown in the > welcome mail. However, the subject does not change (still English) > Thor > The subjects are currently not part of the templates. The translation of these is done in the Python code, so you would need to export a list of strings Mailman Core uses and translate these...

8 years

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

by Franklin Weng

Hi Mark, Mark Sapiro <mark(a)msapiro.net> 於 2019年10月24日週四上午8:42寫道： > > 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() > Thanks for your help. I did what you said above, but then I still got the same result even after restarting mailman3 services. ~# 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 [zh_TW] Chinese (Taiwan)> >>> quit() I created a new list with Chinese display name, set the preferred_language and then subscribed to it. Also got question marks. Is there anything else to try? Thanks, Franklin

6 years, 1 month

[MM3-users] Re: django-allauth failures, but only for some users (independent of browser?)

by Mark Sapiro

On 12/6/23 14:49, Jered Floyd wrote: > > The difference in behavior was using social login buttons for an existing account vs. creating a new account. > > This is another damn django-allauth regression, starting in 0.57.0. It seem to be this commit that is to blame: > https://github.com/pennersr/django-allauth/commit/be779dfee5a328a3a42edc2c9… > > In allauth/socialaccount/models.py:lookup(self):285 there is an attempt to look up the social account as one that already exists. If that fails, this commit calls self.account.get_provider() without passing the request object, which leads to the eventual error. > > I believe this is a django-allauth bug, and have submitted a pull request to fix it here: > https://github.com/pennersr/django-allauth/pull/3548 Thanks for all your work on this. It is much appreciated. However, your patch doesn't fix my issue with the URL https://example.com/accounts/social/connections/ which still produces the following: ``` ERROR 2023-12-07 00:05:55,032 169452 django.request Internal Server Error: /accounts/social/connections/ Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/handlers/exception.py", line 55, in inner response = get_response(request) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/core/handlers/base.py", line 220, in _get_response response = response.render() File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/response.py", line 114, in render self.content = self.rendered_content File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/response.py", line 92, in rendered_content return template.render(context, self._request) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/backends/django.py", line 61, in render return self.template.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 175, in render return self._render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 167, in _render return self.nodelist.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in <listcomp> return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/loader_tags.py", line 157, in render return compiled_parent._render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 167, in _render return self.nodelist.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in <listcomp> return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/loader_tags.py", line 157, in render return compiled_parent._render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 167, in _render return self.nodelist.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in <listcomp> return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/loader_tags.py", line 157, in render return compiled_parent._render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 167, in _render return self.nodelist.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in <listcomp> return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/loader_tags.py", line 63, in render result = block.nodelist.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in <listcomp> return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/loader_tags.py", line 63, in render result = block.nodelist.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in <listcomp> return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/defaulttags.py", line 321, in render return nodelist.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in render return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 1005, in <listcomp> return SafeString("".join([node.render_annotated(context) for node in self])) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/defaulttags.py", line 238, in render nodelist.append(node.render_annotated(context)) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 966, in render_annotated return self.render(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/defaulttags.py", line 539, in render values = {key: val.resolve(context) for key, val in self.extra_context.items()} File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/defaulttags.py", line 539, in <dictcomp> values = {key: val.resolve(context) for key, val in self.extra_context.items()} File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 715, in resolve obj = self.var.resolve(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 847, in resolve value = self._resolve_lookup(context) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/template/base.py", line 914, in _resolve_lookup current = current() File "/opt/mailman/mm/venv/lib/python3.9/site-packages/allauth/socialaccount/models.py", line 147, in get_provider_account return self.get_provider().wrap_account(self) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/allauth/socialaccount/models.py", line 141, in get_provider provider = self._provider = adapter.get_provider( File "/opt/mailman/mm/venv/lib/python3.9/site-packages/allauth/socialaccount/adapter.py", line 204, in get_provider app = self.get_app(request, provider=provider) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/allauth/socialaccount/adapter.py", line 284, in get_app apps = self.list_apps(request, provider=provider, client_id=client_id) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/allauth/socialaccount/adapter.py", line 231, in list_apps db_apps = SocialApp.objects.on_site(request) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/allauth/socialaccount/models.py", line 27, in on_site site = get_current_site(request) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/contrib/sites/shortcuts.py", line 16, in get_current_site return Site.objects.get_current(request) File "/opt/mailman/mm/venv/lib/python3.9/site-packages/django/contrib/sites/models.py", line 63, in get_current raise ImproperlyConfigured( django.core.exceptions.ImproperlyConfigured: You're using the Django "sites framework" without having set the SITE_ID setting. Create a site in your database and set the SITE_ID setting or pass a request to Site.objects.get_current() to fix this error. ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

[MM3-users] Re: Help request, almost got it going, but ....

by Claus-Justus Heine

Oh well. Am 01.09.2017 um 23:44 schrieb Mark Sapiro: > On 09/01/2017 02:33 PM, Claus-Justus Heine via Mailman-users wrote: >> >> Seemingly, at some point in the deep dungeons of the source code the >> "Acceptable aliases" Text-Box is not interpreted correctly. >> >> Specifically, at the start it contains the string >> >> [] > > > See <https://gitlab.com/mailman/postorius/issues/58>. there they talk about fancy "uni-code thinks" (email addresses?) where the task is to convert a new-line separated text-field into an array. Oops. Kind thanks anyway. > > In order to set things on this page, you need to clear the Acceptable > aliases box before submitting changes. You can't actually set Acceptable > aliases via Postorius until this is fixed. The issue seems not to be overly active. I thought -- coming from Mailman v2 -- that the configuration of acceptable submitters to an email list (e.g. keep everyone moderated?) would be a central and prominent and important configuration issue. Seems not to be a central point. Mmmh. Thanks Claus -- Claus-Justus Heine himself(a)claus-justus-heine.de http://www.claus-justus-heine.de/ Schatzmeister der Camerata Academica Freiburg e.V. --- www.cafev.de

8 years, 3 months

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

by Odhiambo Washington

On Mon, Jan 30, 2023 at 12:39 PM Onyeibo Oku <onyeibo(a)schemefusion.com> wrote: > > On Tue, 3 Jan 2023 09:46:00 -0800 > > Mark Sapiro <mark(a)msapiro.net> wrote: > > > This is all configured in your web server. It needs to proxy requests > > for lists.website.tld to gunicorn and depending on the web server, > > may need more. E.g. see > > > https://docs.mailman3.org/en/latest/install/virtualenv.html#nginx-configura… > > for nginx. > > I have fixed this. > > > > > > Set SITE_ID = 0 in your Django settings. Also see > > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > > Actually "SITE_ID = 1" solved that instead. I also had to go into the > database and update the values (django provided 'example.com' by > default and that was problematic). > The common practice I have see is that one creates their domain on the web interface, which then displays the SITE_ID = N. You then take the value into settings.py to replace the one that's there. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 10 months

[MM3-users] Re: Exception with processing subscription confirmation email

by Eric Broens

Thanks Mark, We are indeed running mailman core 3.3.2 and using mysql. The data appears indeed to be truncated judging from the missing closing curly bracket (see below). Would it be OK to already extend the data column to VARCHAR(510) before upgrading to mailman core 3.3.3, or will this cause problems with upgrading to a newer version? +--------------------------------------------------------------------------- ---------------------------------------------------------------------------- ---------------------------------------------------------------------------- ------------------------------+ | data | +--------------------------------------------------------------------------- ---------------------------------------------------------------------------- ---------------------------------------------------------------------------- ------------------------------+ | {"pre_approved": false, "pre_confirmed": false, "pre_verified": false, "invitation": false, "address_key": "******************@************", "subscriber_key": 1, "user_key": "a44e8b9a34c64775b712f383d438ce1d", "token_owner_key": 1, "send_welcome_message" | +--------------------------------------------------------------------------- ---------------------------------------------------------------------------- ---------------------------------------------------------------------------- ------------------------------+ Best Regards, Eric -----Original Message----- From: Mark Sapiro [mailto:mark@msapiro.net] Sent: donderdag 29 april 2021 18:43 To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Exception with processing subscription confirmation email On 4/29/21 7:56 AM, Eric Broens wrote: > Hi, > > A new user tried to subscribe to a mailinglist, received the confirmation > mail, and replied to it. > > The subscriber is however not subscribed and remains listed in the "pending > confirmation" list. > > The following exception appears in the error.log. > > Does anyone knows how to resolve this? In the past we didn't experience any > issues and no changes but security updates have been installed. > > Apr 29 16:15:55 2021 (1581) deque: do_confirm_verify > > Traceback (most recent call last): > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/workflow.py", > line 69, in __next__ > > return step() > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/subscriptions.p > y", line 356, in _step_send_confirmation > > raise StopIteration > > StopIteration Tracebacks like the above are normal and probably shouldn't be logged at all. > Apr 29 16:16:28 2021 (1490) Uncaught runner exception: Expecting ':' > delimiter: line 1 column 256 (char 255) > > Apr 29 16:16:28 2021 (1490) Traceback (most recent call last): > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", > line 173, in _one_iteration > > self._process_one_file(msg, msgdata) > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", > line 266, in _process_one_file > > keepqueued = self._dispose(mlist, msg, msgdata) > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/runners/command.py" > , line 208, in _dispose > > mlist, msg, msgdata, parts, results) > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/commands/eml_confir > m.py", line 54, in process > > mlist).confirm(token) > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/subscriptions.p > y", line 578, in confirm > > workflow.restore() > > File > "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/workflow.py", > line 146, in restore > > data = json.loads(state.data) > > File "/usr/lib64/python3.6/json/__init__.py", line 354, in loads > > return _default_decoder.decode(s) > > File "/usr/lib64/python3.6/json/decoder.py", line 339, in decode > > obj, end = self.raw_decode(s, idx=_w(s, 0).end()) > > File "/usr/lib64/python3.6/json/decoder.py", line 355, in raw_decode > > obj, end = self.scan_once(s, idx) > > json.decoder.JSONDecodeError: Expecting ':' delimiter: line 1 column 256 > (char 255) > > Apr 29 16:16:28 2021 (1490) SHUNTING: > 1619705788.5856323+57a1a759275c59b732cfa8e2985f76cfcc27dda5 This one is the issue. There was some problem with the user's confirmation reply. View the shunted message with the command ``` mailman qfile path/to/var/queue/shunt/1619705788.5856323+57a1a759275c59b732cfa8e2985f76cfc c27dda5.pck ``` although that probably won't show anything wrong as it appears that the issue is with the saved workflow. You can get the token from the shunted message and then look at the database with something like ``` SELECT data FROM workflowstate WHERE token = '<the token>' ``` but I suspect the issue is because the database is MySQL or MariaDB, your Mailman core is older than 3.3.3 and your database server mode is such that data too long for column results in truncation, and the data in this case is truncated to 255 bytes. In Mailman 3.3.3, this column was changed from VARCHAR(255) to VARCHAR(510) for MySQL. As far as subscribing the user is concerned, you can in Postorius view the subscriptions waiting user confirmation and delete this one and then `mass subscribe` the user. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 7 months

[MM3-users] Re: Mailman messages are getting a TAG in some email clients.....how????

by Guillermo Hernandez (Oldno7)

El 12/9/23 a las 19:43, Mark Sapiro escribió: > On 9/12/23 8:51 AM, bob B via Mailman-users wrote: >> So I know about the setting "Anonymous list" but regardless of that >> setting some email clients put the list name in [] when it displays >> messages in your inbox. Does anyone know how email clients are doing >> this? I have users who email clients do not do this, and was >> wondering if it is a setting in their client or just not possible. > > > This looks like Mailman adding 'Subject prefix', so all list mail will > have this prefix added to the Subject:. So the question isn't how mail > clients are adding it, but rather why do some mail clients suppress it. I think the simple answer is that some mobile mail clients don't show the subject line by default, you have to click to show it explicitely. That users just don't see that. -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

2 years, 3 months

[MM3-users] Re: Migrating from SQLite to PostgreSQL

by Sebastian Hagedorn

--On 17. Juli 2018 um 22:04:12 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 07/17/2018 07:27 PM, Joe Steeve wrote: >> >> I have an installation on SQLite. I want to migrate it to PostgreSQL. Is >> that feasible? Any gotchas I need to watch for? > > > It is feasible. > > You would need to stop Mailman core and all Django processes including > cron jobs and WSGI processes to ensure nothing is accessing the SQLite > database, update the database section in mailman.cfg and the DATABASES > settings in your Django settings, use SQLite tools to dump the relevant > database(s) and PostgreSQL tools to create and load them, and finally > restart Mailman core and all Django processes. I have only now started playing around with Mailman 3.2, because I never managed to get the earlier releases to work, and reading through the documentation I thought that such situations could be handled with Alembic, as described here under "Database Migrations": <http://mailman.readthedocs.io/en/latest/src/mailman/docs/database.html> Is that not the case, and if not, in what cases can or should it be used? -- .:.Sebastian Hagedorn - Weyertal 121 (Gebäude 133), Zimmer 2.02.:. .:.Regionales Rechenzentrum (RRZK).:. .:.Universität zu Köln / Cologne University - ✆ +49-221-470-89578.:.

7 years, 4 months

[MM3-users] Re: remove non members from a list

by Guillermo Hernandez (Oldno7)

On 6/8/21 18:37, Mark Sapiro wrote: > On 8/6/21 9:18 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> Hi all: >> >> I need to remove all non members from a list. I know I can do it via >> Postorius, but it has to be done one at a time. (you can delete ALL >> suscribers but not all non members...) >> >> Anyone has a python recipe to do this? > > $ /opt/mailman/mm/bin/mailman shell -l list.example.com > Welcome to the GNU Mailman shell > Use commit() to commit changes. > Use abort() to discard changes since the last commit. > Exit with ctrl+D does an implicit commit() but exit() does not. > The variable 'm' is the list.example.com mailing list > >>> for nonmember in m.members.nonmembers: > ... nonmember.unsubscribe() > ... > >>> commit() > Thanks a lot for the promt response, Mark. It's not functioning. It says: "AttributeError: 'MemberRoster' object has no attribute 'nonmembers'" My system info is: Mailman Core Version GNU Mailman 3.3.3 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.7.9 (default, Nov 6 2020, 21:14:59) [Clang 8.0.1 (tags/RELEASE_801/final 366581)] Postorius 1.3.4

4 years, 4 months

[MM3-users] converting bulk accept_these_nonmembers in migration from mailman 2 to 3

by Lucio Chiappetti

I have been instructed by Mark Sapiro to subscribe to this list to post questions related to mailman3. On Mon, 31 Jan 2022, Mark Sapiro wrote: > On 1/31/22 06:20, Lucio Chiappetti wrote: >> One of the lists of which I am a co-moderator has been moved from >> mailman 2 to 3. Actually the migration has been made operative yesterday (and so we got the first problems ...). Basic background. There are a number of lists within my institution (a nationwide research institution with many seats across our country), some are institutional (all staff subscribed ex officio) and managed by staff in one seat, some other are non-institutional (subscription is optional) and are managed by a few volunteers in other cities different from the seat where the mailman server runs. > In particular, the list settings for *_these_nonmembers are at Settings > -> Message Acceptance, but these settings in particular are deprecated > in Mailman 3 except for regexps. In Mailman 3 the preferred way to say > accept a nonmember is to create a nonmember for that user and set it's > Moderation action to Default Processing. If, a nonmember posts, the > nonmember record is automatically created, Let me explain our case, and how it was managed in mailman2. - originally our staff (of the order of 1000) had addresses like user(a)place.inaf.it or user(a)place.astro.it. Some had even two (say place1.inaf.it and place2.inaf.it), so they subscribed with ONE of their work addresses - later we got addresses like name.surname(a)inaf.it. New users subscribe with this address but MANY of the old ones continue to use the PREVIOUS address. - we implemented a spam filtering policy as follows: - staff (and former staff) can SUBSCRIBE with any address or CHANGE their address. Any subscribed address will be recognised. Mail is NOT held in moderation unless too bulky, or has undisclosed recipients - mail from non members with any address in the .it TLD or in the tng.iac.es domain (where some of our staff work) goes into moderation (this is achieved via regexp in hold_these_nonmembers) - anything else is silently discarded as spam (generic_nonmember_action = discard) - when some staff posts from a non-subscribed address (be it the home address, or one of the alternate addresses described above) it therefore goes into moderation because of hold_these_nonmembers - in mailman2 we could let them pass "manually" (if we recognised the person) or (in case they used an alternate address) tick to add them permanently to accept_these_nonmembers (in one tick) - at the end we got somehow fed up of this but we did NOT want to accept any address of the form ^.+@.+\.inaf.it (which could be forged) but found that we could simply put in accept_these_nonmembers two entries like @list1 @list2 where list1 and list2 are two institutional lists on the same server which contain all permanent and temporary staff or assimilated with their official address (these lists are automagically generated each week) (so at least any VALID EXISTING official address is accepted) What I found now (after the migration done by the administrators of the central seat) is that in mailman3: - accept_these_nonmembers is empty - there are 189 entries listed in Non-members (which look those formerly in accept_these_nonmembers) - hold_these_nonmembers was copied identical with the same regexp's as in mailman2 - I have inspected a few of them and found that they have Administration options Moderation set to List default - the effect of this apparently was that a post from some.guy(a)inaf.it (whose subscription address is guy(a)somewhere.inaf.it) was hold for moderation is this due to a loop with the regexp in hold_these_nonmembers ? the default action would be to let it pass Or should we set Administration options Moderation to Accept immediately ? - if so, how can we do it automatically for all 189 entries ? - or move back the 189 addresses to accept_these_nonmembers ? - or for the future have persons posting with alternate addrresses accepted for the future WITH ONE CLICk ? - AND LAST BUT NOT LEAST would the syntax @list1 in accept_these_nonmembers work in mailman3 ? already putting it back will save a lot of work. Many thanks -- Lucio Chiappetti - INAF/IASF - via Corti 12 - I-20133 Milano (Italy) For more info : http://www.iasf-milano.inaf.it/~lucio/personal.html ------------------------------------------------------------------------ "All that is google does not glitter Nor all who use alpine/procmail are lost"

3 years, 10 months

[MM3-users] Re: where do I find the text of a bounce email ?

by Per Jessen

Mark Sapiro wrote: >> diff --git a/src/mailman/runners/lmtp.py >> b/src/mailman/runners/lmtp.py index 6a0bdcf5e..eca474089 100644 >> --- a/src/mailman/runners/lmtp.py >> +++ b/src/mailman/runners/lmtp.py >> @@ -217,6 +217,8 @@ class LMTPHandler: >> slog.debug('%s subaddress: %s, queue: %s', >> message_id, canonical_subaddress, >> queue) >> status.append('250 Ok') >> + if queue == 'bounces': >> + config.switchboards['bad'].enqueue(msg, >> msgdata) >> except Exception: >> slog.exception('Queue detection: %s', >> msg['message-id']) config.db.abort() > ``` > will add all received bounces as queue files to var/queue/bad/ where > they can be examined with `mailman qfile`. Thanks. Yep, I'm getting NDRs kept now. "mailman qfile" seems to be a bit slow, 2-3 seconds per go. To look for a specific address that bounced, is there any mailman tool for grepping through a collection of bounces? (I have +1200 after a few days). I'm trying with this: find /var/spool/mailman/bad -type f -name \*pck |\ while read m do (mailman qfile $m | grep -q ad.dr@ess) && echo $m done Is there a better way? -- Per Jessen, Zürich (4.6°C) Member, openSUSE Heroes

4 years, 8 months

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

by Onyeibo Oku

On Tue, 25 Oct 2022 14:46:06 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/25/22 12:56, Onyeibo Oku wrote: > > > > I must be missing necessary policy modules for mailman or I am > > missing relevant parts of the tutorial that deals with SELinux. > > Where do I go from here? > > > Create the necessary SELinux rules to allow `mailman` to access what > it needs to. Roger that. There is progress beyond the previous report (after setting mailman_lock_t on '/opt/mailman/mm/var/locks'. Systemd fails again on '/opt/mailman/mm/var/logs/mailman.log' I applied mailman_log_t SELinux policy to that folder. Unlike the previous AVC, that didn't fix it. PermissionError: [Errno 13] Permission denied: '/opt/mailman/mm/var/logs/mailman.log' AVC avc: denied { append } for pid=774 comm="mailman" name="mailman.log" dev="sda" ino=2070696 scontext=system_u:system_r:init_t:s0 tcontext=unconfined_u:object_r:mailman_log_t:s0 tclass=file permissive=0 > > I don't know if anyone on this list can help you with that. > > Note that if `mailman` is currently a `normal user` as opposed to a > `system user` making it a system user might help. See `man usermod` > Mailman user is a System User here. Regards Onyeibo

3 years, 1 month

[MM3-users] Re: list of subscribers

by Simon Hanna

On 02/04/2018 01:45 PM, Peter Münster wrote: > On Fri, Feb 02 2018, Mark Sapiro wrote: > >>> Yes, the question is rather: where can *normal* members (or moderators) >>> can see the subscriber list? >> Currently, they can't. If you think they should be able to, you can file >> an issue at <https://gitlab.com/mailman/postorius/issues/new>. > Thanks. Done. > > It seems, that even the owner of the list cannot get the full names of > the subscribers, only the email addresses. Is there any other > possibility for the owner (or the site admin) to get the subscriber list > with full names (perhaps with some Python scripting)? You should be able to use mailmanclient to get a list of subscribers with names. Names are optional though, if people signup without them you won't be able to get them. Currently there is no option to require names. I'll open an issue in postorius about showing the name in the member list if there is one associated. IIRC one person(postorius account) can also signup at different lists using different names (regardless of address). There was some discussion about names and potentially using the from header to populate the database but I don't remember the result...

7 years, 10 months

[MM3-users] Re: mailman import21

by Brian Carpenter

On 10/11/20 11:06 AM, Mark Sapiro wrote: > On 10/11/20 7:41 AM, Brian Carpenter wrote: >> Does the import21 script also import custom templates? > No. > > >> Are these custom >> templates contained in the config.pck file? > No. They are in the same MM 2.1 directory as the config.pck, but in a > sub-directory for the language code, i.e. lists/LISTNAME/LC/ > > >> Are there any known issues >> with the importing of mm2 templates into a mm3 environment? > > The replacements are different. i.e., things like %(email)s and > %(listname)s become $user_email and $short_listname. > > Also, there are some MM 2.1 templates that have no MM 3 equivalent. > Also, things like message and digest headers and footers that are MM 2.1 > list attributes that are templates in MM 3, although import21 tries to > handle those. So are how these templates showing up on my Mailman 3 servers? They show up in /opt/mailman/mm/var/templates/lists/listname/en/. I have a client whose old footer template from Mailman 2 still showing up in list messages. He then created a custom footer template via Affinity (same thing happen in Postorius) and both custom footers were being included in list messages. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 2 months

[MM3-users] Weblate spanish translation of templates (was: Re: spanish localization)

by Guillermo Hernandez (Oldno7)

On 14/2/21 2:42, Abhilash Raj wrote: > You can actually translate the templates in Weblate too. That is > actually the whole > reason to go with monolingual template format in Mailman Core. > > Mailman uses the template file's name as the msgid for translations > and all in-tree > templates are copied into English's .po file when we re-generate them. > > For example in here: > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/messages/es/LC… > > > The english .po file is considered as reference in Weblate and used > for source string. I want to contribute making it via Weblate, since it is already done via gitlab repository (thanks to Mark Sapiro for approving the merge requests), making a revision and editing them if needed, but I cannot see how to make it in a consistent way, as I cannot determine how to edit each template in the Weblate UI. I've tried to access via the file name (accessing via msgid as for your example) of the template... but I cannot access them by this way, or I'm missing something. Can you, please, point me in the right direction on how to do it?

4 years, 9 months

[MM3-users] Re: Setting up From: field as list address

by Steven Maddox

Hey, Thanks Mark... found that about 2 minutes after I sent this in :) If you ever get a 'moderator waiting approval' reply when sending into a mailman list... don't suppose there is some magic command you can send into the list to cancel off a pending e-mail? :D Steven Maddox Lantizia On 25/11/2019 15:30, Mark Sapiro wrote: > On 11/24/19 11:54 PM, Steven Maddox wrote: >> Hi folks, >> >> I'm trying to configure our mailman3 lists (via postorious) in a way >> that'll mean they'll behave in the way way that I've witnessed on >> another 3rd party list (one running mailman2). >> >> This is where (when receiving a message from the list) the From: is the >> list itself, and the person who actually sent it bizarrely appears as a >> CC:, for example... >> >> From: Steven Madox via Shropshire LUG <shropshire(a)mailman.lug.org.uk> >> Subject: [Shropshire LUG] Whatever >> To: shropshire(a)mailman.lug.org.uk >> CC: s.maddox(a)lantizia.me.uk > > > Go to Settings -> DMARC Mitigations and set DMARC mitigation action to > "Replace From: with list address" and DMARC Mitigate unconditionally to Yes. >

6 years

[MM3-users] [Django] ERROR (EXTERNAL IP): Internal Server Error: /hyperkitty/list/direttivo@catania.linux.it/top-threads

by blackout69

Il 01/03/21 00:21, Mark Sapiro ha scritto: > On 2/28/21 10:17 AM, blackout69 wrote: > It looks to me like a race condition of some kind or possibly an > incompletely deleted thread. Have you deleted any threads? I have not deleted threads > I'm curious as to how you happen to be going to > <https://lists.catania.linux.it/hyperkitty/list/direttivo@catania.linux.it/t…> > as opposed to > <https://lists.catania.linux.it/hyperkitty/list/direttivo@catania.linux.it/#…>. > I know that ULS and similar ones are in HyperKitty's urls.py, but I > don't see them exposed on any pages. > > Anyway, when you say "from that moment the maiilan3 has stopped > working." (sic) exactly what stopped working. Did core stop delivering > messages? Did Postorius stop working. If so, this all may be related to > some underlying database issue or something like that that was fixed by > the restarts. I don't see how this HyperKitty error could affect > Postorius or Mailman core. When I say that it stops working, I mean that all members of the lists no longer receive messages. Postorius and Hyperkitty continue to work blackout69

4 years, 9 months

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

by tlhackque

On 03-Aug-17 17:14, Rafael Mora wrote: > > > El jue., 3 ago. 2017 a las 16:07, tlhackque via Mailman-users > (<mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org>>) > escribió: > > You've said you're working with labbrands.com <http://labbrands.com>. > > labbrands.com <http://labbrands.com> has address 192.185.51.89 > mail.labbrands.com <http://mail.labbrands.com> has address > 192.185.51.89 > www.labbrands.com <http://www.labbrands.com> is an alias for > labbrands.com <http://labbrands.com>. > > telnet proves that Exim is running on that IP address. Either you're > running it, or hostgator is redirecting the SMTP ports. > > You added: > lists.labbrands.com <http://lists.labbrands.com> has address > 190.145.27.66 > > Presumably that's a different machine. > > So that now needs an MX record, and a firewall routing. > > > I added the MX record on our hostgator hosting like this: > image.png > > Is it correct??? > No. And sending images to the mailing list doesn't get you help. You set up lists.labbrands.com as a secondary server, not an independent mail domain. This will cause you serious grief. You need to get some help from a more suitable list. Setting this up is not mailman-specific, and getting it right is more than a quick note. Try the Postfix documentation & mailing lists. > > > And the SPF > records ... and spam and virus filters, and all the other stuff > you need > to setup an independent, public-facing smtp server. > > But at least you won't have to relay. > > Good luck. > > On 03-Aug-17 16:55, Rafael Mora wrote: > > El jue., 3 ago. 2017 a las 15:49, tlhackque via Mailman-users (< > > mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org>>) > escribió: > > > >> I think you're confused. > >> > >> You already have mail.labbrands.com <http://mail.labbrands.com> > set up as the MX record for > >> labbrands.com <http://labbrands.com>. And it has an A record > with the same address as your > >> webserver. > >> > > I'm working with the hostgator mailserver, we are not running a > local > > mailserver. > > > > As suggested I added an A record like this: > > [image: image.png] > > > > Is it correct? is it redirecting to my Ip so I can redirect it to my > > postfix/mm3 server? > > > > > >> So if you're getting e-mail on that domain, there's another e-mail > >> server running on that IP address. You can't have 2 servers > on port > >> 25. In that case, as has been noted before, you'll need to setup a > >> relay in that server, not a firewall redirect. Depending on > your MTA, > >> you would need to relay to your internal server. And make sure > your > >> firewall setup allows your MTA to do this. > >> > >> We can see it's EXIM: > >> > >> telnet mail.labbrands.com <http://mail.labbrands.com> 25 > >> Trying 192.185.51.89... > >> Connected to mail.labbrands.com <http://mail.labbrands.com> > (192.185.51.89). > >> Escape character is '^]'. > >> help > >> 220-gator4137.hostgator.com > <http://220-gator4137.hostgator.com> ESMTP Exim 4.87 #1 Thu, 03 > Aug 2017 15:47:48 > >> -0500 > >> 220-We do not authorize the use of this system to transport > unsolicited, > >> 220 and/or bulk e-mail. > >> 214-Commands supported: > >> 214 AUTH STARTTLS HELO EHLO MAIL RCPT DATA NOOP QUIT RSET HELP > >> quit > >> 221 gator4137.hostgator.com <http://gator4137.hostgator.com> > closing connection > >> Connection closed by foreign host. > >> > >> Or, consolidate all your e-mail to one server - which is a lot > easier to > >> manage unless you have a really big operation. Postfix is > probably the > >> right choice, but requires more setup. > >> > >> Although Mailman3 configuration is not well documented (as you've > >> discovered), you may want to get help from someone with more > general > >> network and mail experience. You're now into territory that is, as > >> Simon indicated, not Mailman-specific. > >> > >> On 03-Aug-17 16:28, Rafael Mora wrote: > >>> El jue., 3 ago. 2017 a las 15:26, Mark Sapiro > (<mark(a)msapiro.net <mailto:mark@msapiro.net>>) > >> escribió: > >>>> On 08/03/2017 01:22 PM, Rafael Mora wrote: > >>>>> El jue., 3 ago. 2017 a las 15:18, Mark Sapiro > (<mark(a)msapiro.net <mailto:mark@msapiro.net>>) > >>>> escribió: > >>>>>> You need to forward port 25 for SMTP mail delivery and if > you want the > >>>>>> web UI (Postorius and HyperKitty) accessible from the > outside, port 80 > >>>>>> for http and/or port 443 for https > >>>>>> < > >>>>>> > >> > https://www.iana.org/assignments/service-names-port-numbers/service-names-p… > >>>>>>> . > >>>>> I mean for incoming mail redirected from my hostgator > hosting, because > >>>> when > >>>>> I suscribe an email address MM3 sends a confirmation email, > so I have > >> to > >>>>> reply to be suscribed to the list. > >>>> As I said, for mail delivery you need to forward port 25 to > the Mailman > >>>> server. > >>>> > >>> Ok so I'll redirect in my zentyal firewall the port 25 to my local > >> centos7 > >>> with postfix and MM3 with IP 192.168.1.42. Thanks Mark. > >>> > >>> > >>>> -- > >>>> Mark Sapiro <mark(a)msapiro.net <mailto:mark@msapiro.net>> > The highway is for gamblers, > >>>> San Francisco Bay Area, California better use your sense - > B. Dylan > >>>> _______________________________________________ > >>>> Mailman-users mailing list > >>>> mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org> > >>>> > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > >>>> > >> -- > >> This communication may not represent my employer's views, > >> if any, on the matters discussed. > >> > >> _______________________________________________ > >> Mailman-users mailing list > >> mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org> > >> > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > >> > > -- > This communication may not represent my employer's views, > if any, on the matters discussed. > > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org> > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > -- > > Atentamente / Best Regards > > Ing. Rafael Mora > -- This communication may not represent my employer's views, if any, on the matters discussed.

8 years, 4 months

[MM3-users] Re: Rebuilding a list index fails

by Mark Dadgar

On Feb 17, 2021, at 11:06 AM, Mark Dadgar <mark(a)pdc-racing.net> wrote: > On Feb 17, 2021, at 9:58 AM, Mark Sapiro <mark(a)msapiro.net> wrote: >> On 2/16/21 9:59 PM, Mark Dadgar wrote: >>> Now that I’ve got my instance back up and running on the latest released code, I am trying to rebuild a list index. I am using Xapian via haystack, which worked beautifully before my recent list meltdown. >>> >>> Error messages below. >>> >>> rebuild_index fails with the same error. >>> >>> This is with django version 3.0.12. >> >> >> django.utils.six was removed in Django 3.0. See >> <https://pypi.org/project/django-utils-six/> for a work around >> replacement. I.e. in your venv do >> >> pip install django-utils-six > > > OK, that got me a step further. Then I needed to do a “pip install xapian-bindings” and now I am up and running. One last note on this for the next person who searches the list archives: I also ran into the “Key too long” error while re-indexing. Applying the patch linked here fixed it: https://gitlab.com/mailman/hyperkitty/-/issues/322 - Mark ----- mark(a)pdc-racing.net | 408-348-2878

4 years, 9 months

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

by David Partain

On Tue, 2021-03-02 at 13:43 -0800, Mark Sapiro wrote: > > This is all because you are using the Ubuntu 18.04 package which is > about 4 years out of date and is from the era where HyperKitty, > Postorius and django_mailman3 still ran under Python 2.1.7. > > 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... 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? Cheers, David

4 years, 9 months

[MM3-users] Re: Mailman3 doesn't send Mails to users (Debian12 with Plesk)

by Marcus Bautze

Hallo, Am 27.05.2024 um 14:33 schrieb Mark Sapiro: > Enabling archivers is done in mailman.cfg similarly to > ``` > [archiver.hyperkitty] > class: mailman_hyperkitty.Archiver > enable: yes > configuration: /opt/mailman/mm/mailman-hyperkitty.cfg Thank you, archiver is now starting. Now there's another problem: In mailman.log i'm finding: "Jun 06 10:16:16 2024 (3556489) ACCEPT: <d3072553-2f52-4bd7-b14a-2701863812c7@***> Jun 06 10:16:17 2024 (3556492) HyperKitty failure on https://[URL]/mailman3/hyperkitty/api/mailman/urls: <html> <head><title>403 Forbidden</title></head> <body> <center><h1>403 Forbidden</h1></center> <hr><center>nginx</center> </body> </html> (403)" in mailman-hyperkitty.cfg there is: base_url: https://[URL]/mailman3/hyperkitty/api/mailman/urls an in mailman-web.py ALLOWED_HOSTS = [ #"localhost", # Archiving API from Mailman, keep it. # "lists.your-domain.org", # Add here all production URLs you may have. '*' ] MAILMAN_ARCHIVER_FROM = '*' (only for test, if it works i will use my domains/IPS) If i try lynx https://[URL]/mailman3/hyperkitty/api/mailman/urls i'm getting "The archiver key must be sent over the Authorization HTTP header." an no forbidden What's the problem? Where i have to change something to get it working? (I'm using plesk) CU -- Marcus Bautze marcus(a)mbautze.de

1 year, 6 months

[MM3-users] Re: Moving existing lists to a new domain

by Jeremy Stanley

On 2024-11-21 14:22:27 -0800 (-0800), Mark Sapiro wrote: > 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. Yeah, I was planning to address all of those with additional SQL update queries, just wanted to make sure I found all relevant references to the domain name. > > 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. Awesome, thanks again, as always! -- Jeremy Stanley

1 year

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

by Shashikanth Komandoor

Dear Mark, As I already said, your suggestion worked well on one list. But when I tried to implement the same trick on another list, I found the below error messages in the mailman.log. > * Sep 23 18:31:31 2020 (22951) Uncaught runner exception: [Errno > 2] No such file or directory: > '/var/lib/mailman/mailman/var/lists/press.dpr-pb.lsmgr.nic.in/digest.mmdf > <http://press.dpr-pb.lsmgr.nic.in/digest.mmdf>'* > > > *Sep 23 18:31:31 2020 (22951) Traceback (most recent call last):* > * File "/usr/lib64/python3.6/mailbox.py", line 581, in __init__* > * f = open(self._path, 'rb+')* > *FileNotFoundError: [Errno 2] No such file or directory: > '/var/lib/mailman/mailman/var/lists/press.dpr-pb.lsmgr.nic.in/digest.mmdf > <http://press.dpr-pb.lsmgr.nic.in/digest.mmdf>'* > *During handling of the above exception, another exception occurred:* > *Traceback (most recent call last):* > * File "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 173, > in _one_iteration* > * self._process_one_file(msg, msgdata)* > * File "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 266, > in _process_one_file* > * keepqueued = self._dispose(mlist, msg, msgdata)* > * File "/var/lib/mailman/mailman/src/mailman/runners/pipeline.py", line > 37, in _dispose* > * process(mlist, msg, msgdata, pipeline)* > * File "/var/lib/mailman/mailman/src/mailman/core/pipelines.py", line 50, > in process* > * handler.process(mlist, msg, msgdata)* > * File "/var/lib/mailman/mailman/src/mailman/handlers/to_digest.py", line > 47, in process* > * with Mailbox(mailbox_path, create=True) as mbox:* > * File "/usr/lib64/python3.6/mailbox.py", line 893, in __init__* > * _mboxMMDF.__init__(self, path, factory, create)* > * File "/usr/lib64/python3.6/mailbox.py", line 585, in __init__* > * f = open(self._path, 'wb+')**FileNotFoundError: [Errno 2] No such > file or directory: > '/var/lib/mailman/mailman/var/lists/press.dpr-pb.lsmgr.nic.in/digest.mmdf > <http://press.dpr-pb.lsmgr.nic.in/digest.mmdf>'* > > I ran in both the ways you suggested i.e. through "mailman shell" and "mailman remove". But no luck. Could you please suggest me at this point ? <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Tue, Sep 22, 2020 at 10:29 PM Shashikanth Komandoor < shashikanth.komandoor(a)gmail.com> wrote: > > Thank you Mark a lot. > > It worked awesome. You don't know how much you helped me. > > Thank you once again. > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. > www.avast.com > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> > <#m_8502129290396208734_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > On Sat, Sep 19, 2020 at 8:56 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 9/19/20 4:32 AM, Shashikanth Komandoor wrote: >> > >> > But I am trying to delete a list on an urgent basis. Because of which I >> am >> > getting the above said errors. I tried to delete >> > through the interface, through curl command and through "mailman shell" >> but >> > nothing led me to a >> > positive result. Is there any work around to delete the list ? >> >> What have you tried in Mailman shell? This should do it. >> >> $ mailman shell -l list.example.com >> Welcome to the GNU Mailman shell >> Use commit() to commit changes. >> Use abort() to discard changes since the last commit. >> Exit with ctrl+D does an implicit commit() but exit() does not. >> The variable 'm' is the list.example.com mailing list >> >>> getUtility(IListManager).delete(m) >> >>> commit() >> >> So should just >> >> $ mailman remove list.example.com >> >> What happens if you do those? >> >> -- >> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, >> San Francisco Bay Area, California better use your sense - B. Dylan >> _______________________________________________ >> Mailman-users mailing list -- mailman-users(a)mailman3.org >> To unsubscribe send an email to mailman-users-leave(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> > > > -- > Thanks & Regards, > Shashi Kanth.K > 9052671936 > > > > -- Thanks & Regards, Shashi Kanth.K 9052671936

5 years, 2 months

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

by Gilles Filippini

Mark Sapiro a écrit le 15/06/2020 à 21:58 : > On 6/15/20 12:37 PM, Gilles Filippini wrote: >> >> There are 4 emails stored into this folder. 3 of them are spam, and the >> last one is a legitimate email. This is annoying that such emails could >> accumulate and stay into var/archives/hyperkitty/spool/ forever, causing >> more and more hyperkitty errors. >> >> Any idea how to make their processing more error proof? > > > Change the offending .encode() method to add errors='replace'. > > The traceback from the error should tell you where it is. > > You could also open an issue at > <https://gitlab.com/mailman/hyperkitty/-/issues> for us to look at. If > you do that, please include an error traceback if possible. If there is > not a traceback in mailman.log associated with the error, there might be > one in HyperKitty's log (configured in Django's settings). Also, > including enough of a message to duplicate the issue is very helpful. I've now deleted the offending messages. Will open an issue with related details the next time this error occurs. Thanks a lot, _g.

5 years, 5 months

[MM3-users] Re: Welcome message template errors

by Mark

>> On 2024-04-23 11:33, Mark Sapiro wrote: >> That URI should have been; >> >> https://lists.mydomain.com/mailman3/api/templates/list/mytestlist.lists.myd… > I think you are saying the what you reported originally was not > correct and the URL in the template table was in fact the latter URL. I meant when I typed the URL in my first email I had unintentionally omitted the name of the list (mytestlist) when I redacted the real domain name to 'lists.mydomain.com'. ...emplates/list/lists.mydomain.com/list:user:noti... I should have written ...emplates/list/mytestlist.lists.mydomain.com/list:user:noti... >> If I go to the above URL, the text of the list's Custom welcome >> message displays on an otherwise empty webpage. > > > And that's what is expected. So you can go to that URL and get the > template, but when Mailman Core tries to do the same thing, it gets a > timeout. Is there some firewall or other security software blocking > this access? #ufw disable Firewall stopped and disabled on system startup Then restarted everything... # ufw status verbose Status: inactive And still getting the error in the Postorius webpage ... HTTP Error 400: HTTPSConnectionPool(host='lists.mydomain.com', port=443): Read timed out. (read timeout=5)

1 year, 7 months

[MM3-users] Re: Header Filter madness

by Brian Carpenter

On 1/11/21 8:48 PM, Mark Sapiro wrote: > On January 11, 2021 5:50:04 PM MST, Brian Carpenter <brian_carpenter(a)emwd.com> wrote: >> I have a client whose header filters seemed to have stop working. No >> matter what I try, it seems none of their header filters are being >> applied. Other lists on the same server that use header filters, are >> working fine. This particular header is the subject header. I can >> duplicate their problem but only with their list. If I create the exact >> >> same header on a test list using the exact same subject line, the >> header >> filter does its job (moderate). Just not with this one list. > Is the poster's moderation action or the list's moderation action set to accept? Moderation action accept (rather than default processing) will bypass header filters an many other rules. > > The "Default action to take when a member posts to the list " is set to Default Processing for the problematic list. The list members moderation action is set to "List Default" for the problematic list. I duplicated the same settings using another list. Header filters works fine on the test list, does not on the production list. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 11 months

[MM3-users] Re: clearing pending db

by Morris Jones

On 8/8/25 11:48 AM, Mark Sapiro wrote: > On 8/8/25 09:59, Morris Jones wrote: >> >> But pendingdb.evict() doesn't seem to clear the list. For example, on >> one of my lists: >> >> >>> from mailman.interfaces.pending import IPendings >> >>> >> >>> from zope.component import getUtility >> >>> >> >>> pendingdb = getUtility(IPendings) >> >>> pendingdb.count() >> 5040 >> >>> pendingdb.evict() >> >>> pendingdb.count() >> 5040 >> >>> > > > pendingdb.evict() only deletes expired pendings, but by default > subscriptions pending confirmation expire after 3 days, but this is set > by pending_request_life in the [mailman] section of mailman.cfg. Have > you set that to a long time? > > On the other hand in Mailman 3.3.2, subscriptions pending approval were > pended with a 10 year lifetime. This was changed in 3.3.5 to a new > moderator_request_life setting (default 180 days). > > If you just want to delete all pendings you could do > ``` > pendingdb = getUtility(IPendings) > for pending in pendingdb: > pendingdb.confirm(pending[0], expunge=True) > # and if doing this in mailman shell > commit() > Perfect, thank you Mark. :) Mojo -- Morris Jones, Monrovia, CA

4 months

[MM3-users] Re: Can't subscribe on new site/domain

by Flo

On 10/10/25 04:13, Mark Sapiro wrote: > >> I have deleted site - group - list now. And created the site again. If >> I go to 'view site' I see all mailing lists on the server and not only >> from this site/domain. This is the first thing where it shows >> irregularities. > > I'm not sure what you mean by `view site` but if you mean the VIEW SITE > link at the top of the Django admin UI, that is just a link to the host > site. I.e., if the Django admin page is https://www.example.com/admin/ > site/, its VIEW SITE link just goes to https://www.example.com/ and it's > always the same link regardless of what Django admin page you are on. > The url of the Django view is lists.example.com/mailman3/admin. The 'VIEW SITE' is in the header on the right side. It's a link to lists.example.com/mailman3 which apparently gets redirected to lists.example.com/mailman3/postorius/lists. The difference I am talking about is that lists.example1.com/postorius/lists shows only its mailing lists while lists.example2.com/postorius/lists shows all mailing lists on the server (ie. also mailing lists of example1.com) Flo

2 months

[MM3-users] Re: integrating mm3 with postfix / lmtp

by Abhilash Raj

On Fri, Nov 3, 2017, at 08:29 AM, Fabian A. Santiago wrote: > October 26, 2017 11:07 PM, "Mark Sapiro" <mark(a)msapiro.net> wrote: > > > On October 26, 2017 7:30:35 PM PDT, "Fabian A. Santiago" <fsantiago(a)garbage-juice.com> wrote: > > > >> That was it. Perfect. I manually modified my regexp map and it works > >> now. Excellent and Thank you. You're the man. Does mm3 ever refresh > >> those maps or only as I add new domains / lists? > > > > Only when you make changes to domains or lists. > > > > -- > > Mark Sapiro <mark(a)msapiro.net> > > Sent from my Not_an_iThing with standards compliant, open source software. > > Mark, > > I've noticed that even simply restarting the mm3 components those alias > maps get rewritten and the problem returns until I can manually edit it. Yeah, that is true. Transport maps are re-generated everytime the container restarts. I don't think think there is any way around this right now :( > > -- > > Thanks, > > Fabian S. > > OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- Abhilash Raj maxking(a)asynchronous.in

8 years, 1 month

[MM3-users] Re: UnpicklingError on mailman lists command

by Bryan Loniewski

Okay, so the issue has been fixed by updating the data to an empty list equivalent (after finding, confirming and copying another lists empty value): MySQL [mailman]> SELECT accept_these_nonmembers INTO @newatn FROM mailinglist WHERE list_name='foo_is_a_good_list_with_emptyval'; MySQL [mailman]> UPDATE mailinglist SET accept_these_nonmembers=@newatn WHERE list_name='the_borked_list'; Query OK, 1 row affected (0.02 sec) Rows matched: 1 Changed: 1 Warnings: 0 Thanks for the help on troubleshooting that! Based on your import21 comments, I'm realizing the issue may be caused by multiple runs of import21. I have been (although I've stopped it for some time now) running import21 nightly to sync up my Mailman3 list data with Mailman2. I've been doing the same for archiving as well. I've noticed now that some lists have duplicate acceptable alias entries (looks to be like <number of aliases> x <number of import21 runs>) and the same goes for *_these_nonmembers entries. Is this a symptom of running the old(er) import21 command pre-3.3.2? Will the 3.3.2 import21 work as expected w/out the duplications if I was to clear out the appropriate lists col data (i.e., is it okay to run import21 multiple times)? I tried to figure out if there were any other duplicative data, but did not come across any. Is there more that I'm missing? ________________________ Bryan Loniewski Rutgers University OIT:EAS:Messaging and Collaboration Services System Administrator ________________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, August 3, 2021 12:28 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: UnpicklingError on mailman lists command On 8/3/21 7:35 AM, Bryan Loniewski wrote: > Okay, that helped identify possible culprits. Three of our lists are hitting/over the max BLOB length (65,535 bytes) for accept_these_nonmembers. I executed this SQL command for each of the BLOB cols you referenced and only accept_these_nonmembers is borked: > > MySQL [mailman]> SELECT list_name, OCTET_LENGTH(accept_these_nonmembers) as howManyBytes from mailinglist where OCTET_LENGTH(accept_these_nonmembers) > 64000; > +---------------+--------------+ > | list_name | howManyBytes | > +---------------+--------------+ > | <snip> | 65535 | > | <snip> | 65535 | > | <snip> | 65535 | > +---------------+--------------+ > 3 rows in set (0.01 sec) > > So, putting aside *why* these lists are so large wrt that column, can or should I alter the col type(s) to MEDIUMBLOB? If yes, would that remain on suite upgrades? If no, is there a better alternative? Or some recommendation in between? Modifying the column type at this point will not help because the data has already been truncated and the missing piece is gone. It may help avoid future issues, but I suspect it's not necessary. It would probably 'stick' on an upgrade as long as there were no new migration affecting those columns, but if there were such a migration, it could fail due to the existing type not being as expected. I suspect these lists were imported from Mailman 2.1 with the `mailman import21` command. The goal of that is to import the addresses as non-members with the appropriate action and put only the regexps in the MM 3 *_these_nonmembers. Prior to Mailman 3.3.2, import21 would add the entire 2.1 *_these_nonmembers and then delete the non-regexps. Possibly something went wrong in that process because of the truncation and left the new *_these_nonmembers in a broken state. Or possibly you just have a huge number of regexps in these list's accept_these_nonmembers. I suggest you use mysql to update this column's data for these three lists. to a value which unpickles as an empty list. This value is the python bytes b'\x80\x04\x5d\x94\x2e' (i.e. 5 bytes with hex values 80, 04, 5d, 94 and 2e). I'm not sure how that is stored in a MySQL BLOB, but I'm sure you can determine that. This will allow you to actually access those lists in Mailman. Also note that beginning with Postorius 1.3.3, the *_these_nonmembers settings are exposed on the List Settings -> Message Acceptance form. If you still have the original MM 2.1 config.pck files, you can examine them with Mailman 2.1's bin/dumpdb command to see what was in accept_these_nonmembers, and then see if the appropriate MM 3 nonmembers were created and if the remaining regexps are not too long, add them. If you need help with this, I will help. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

4 years, 4 months

[MM3-users] Re: mailman 3 adding extraneous /var/ to pid path?

by Barry Warsaw

On Sep 21, 2017, at 18:35, Abhilash Raj <maxking(a)asynchronous.in> wrote: > > On Thu, Sep 21, 2017, at 02:42 PM, Mark Sapiro wrote: >> On 09/21/2017 01:29 PM, Andrew Hodder wrote: >>> >>> I keep getting around this by creating symlinks to the pid file and then >>> the stop works, but it's getting silly. It seems like mailman just assumes >>> CWD + /var/ + master.pid must be the location. Once I realized this, I >>> found I can do "mailman stop" so long as I'm only in /opt/mailman/ (since >>> it'd then add /var/master.pid). But that seems a little nonsensical. >> >> That is the normal expected behavior if devmode is enabled. Check your >> configs for this. > > I don't think `devmode` has anything to do with this, it only disables > sending out emails by accident and routes all emails to a pre-defined > address. Haven't looked at the relevant portion of the source so I might > be wrong. That’s correct. The [paths.*] sections are what control the file system layout, and [mailman]layout is what defines which of the [paths.*] sections to use. Cheers, -Barry

8 years, 2 months

[MM3-users] Re: Apache+mod_wsgi issue

by Guillermo Hernandez (Oldno7)

I top post just for confirming that all your recommendations worked well and I am aplying them in the rest of servers Thanks a lot and all of you have a happy new year. El 27/12/22 a las 9:23, Guillermo Hernandez (Oldno7) via Mailman-users escribió: > > El 26/12/22 a las 23:57, Mark Sapiro escribió: >> ... >>> I don't want to put more noise in the list. But I'm confused because >>> I always updated via pip the apache mod_wsgi thinking is was needed >>> for my configuration. If it is not, I will stop updating it. >> >> Based on the above you ARE using Apache mod_wsgi and if you are still >> also running uwsgi as >> >> /usr/local/bin/uwsgi --ini /usr/local/mailman3/uwsgi.ini & >> >> that is unnecessary. > > It clarifies a pair of things. Thanks a lot. > > I'll try deactivating that in one of my servers (the "quieter" one) > and see how it goes. > > Again, thanks for your kind support. > > > > -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

2 years, 11 months

[MM3-users] Re: MM3 Docker

by Odhiambo Washington

On Wed, 9 Jan 2019 at 19:25, Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/8/19 10:50 PM, Odhiambo Washington wrote: > > > Now that has clarified the matter for me. That even when I am logged out, > > the scripts do the neccessary > > to activate the venv to run things. > > > As mentioned before, a virtualenv is not like a container. It is only a > directory that contains among other things a bin/ directory with > activate scripts and easy_install, python, pip and wheel commands. > > When you activate a virtualenv in your shell, all it really does is add > a deactivate command, modify the command prompt and insert its bin/ > directory at the beginning of its PATH. > > What this means is whether or not a virtualenv is "active", running a > command from the bin/ directory in the virtualenv is using the virtualenv. > Thank you very much for the elaboration. What used to confuse me was the early stage documents which detailed how to run MM3 in a virtual environment - I am talking about the BETA days. I think from this point onward, I have the complete foundation information to move forward. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

6 years, 11 months

[MM3-users] Re: Moderate mails from owner

by Malcolm Austen

On Wed, 20 Mar 2019 18:42:10 -0000, Mark Sapiro <mark(a)msapiro.net> wrote: > However, this is apparently not relevant because both the Member and > Non-Member actions are Hold. Thus, the post should be held unless it has > an Approved: header with the list's moderator_password attribute if > there is one, or it matches a Header filter rule with an accept action. At the risk of getting this really wrong - I have only limited MM3 knowledge - I will ask what is, I fancy, a closely related question ... My only experience of MM3 is with Ancestry's 'RootsWeb' installation. From the emails I can see a header "X-Mailman-Version: 3.1.0" but I can't find anything to identify Postorius which is the only interface I have to the system. From symptoms seen and described by others, I have deduced that the Postorius admin-per-user moderation options of "Default processing" and "List default" mean that a user may be set (by default on the rootsweb system!) to use the system default moderation settings rather than the list default settings. Are my deductions correct? And if so, could this be the explanation of the issue detailed in this thread? Apologies if I'm barking up entirely the wrong tree, Malcolm. -- Malcolm Austen <malcolm.austen(a)weald.org.uk>

6 years, 8 months

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

by Andreas Schamanek

Thanks Mark, Your support is unparalleled. On Tue, 4 Apr 2023, at 10:44, Mark Sapiro wrote: > On 4/4/23 09:53, Andreas Schamanek wrote: >> All "<" and ">" in old and new messages are shown as "<" and ">" in >> message views _however_ they are shown correctly in overview abstracts e.g. >> at //server/mm3/hyperkitty/list/testlist@server/latest > > I don't think I've ever seen this. Certainly it is not the case on this list > with either current messages such as those in this thread > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> I tried to dig deeper and realized that on my test list "<" and ">" are only mangled when they surround email addresses as e.g. in <user(a)example.net> (ie. < user @ example . net >) I see that lists.mailman3.org renders such addresses as e.g. <a target="_blank" href="mailto:user@example.net">user(a)example.net</a> whereas my Hyperkitty shows them as <user(a)example.nett> But I have not yet found the responsible code or setting since it seems this is related to the option to obscure addresses. Or is my Hyperkitty 1.3.4 simply too old? -- -- Andreas :-)

2 years, 8 months

[MM3-users] Re: Mailman stops processing....... where to start looking for root cause?

by Stephen J. Turnbull

Mark Sapiro writes: > One of the runners has died, most likely the `out` runner, but > possibly another. The missing messages are stuck in a queue. Do ``` > ls -laR /opt/mailman/core/var/queue ``` to see in which queue the > messages are. The runner that processes that queue is gone or > possibly stuck. I have seen "stuck", in a multisite installation where Mailman's smarthost ended up being about 1000 miles from Mailman. I'm not sure what the issue is (we fixed the DNS, not Mailman :-), but every once in the while the connection would hang. In that case nothing showed up in the log. The only symptoms were the buildup in the out queue and a stale connection to port 25 on the smarthost. If your smarthost is not "network far" from the Mailman host, this is quite unlikely from my experience, although Mark may know better. In any case, I think the best way to start diagnosis is to check the Mailman and MTA queues for stuck messages. Of course in normal operation you will often see messages in the queue, but long queues or messages older than a minute are 99% a dead or stuck queue runner. Steve

1 year, 8 months

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

by Mark

On 2025-07-31 03:31, Mark Sapiro wrote: > Anything is possible, it's only code ;) > > You could make your own user_adapter.py which is modified like > > and set that as the ACCOUNT_ADAPTER. This depends on whatever is > proxying to Django setting the appropriate HTTP_HOST header. Thank you Mark. It's so close. After wrangling your solution a bit it's working a treat on my test server (wrangled solution below) . When I add it to the production server (same OS, MM installation, etc) I'm getting a "Bad gateway" error page and the log reports ... ... raise self.model.DoesNotExist( django.contrib.sites.models.Site.DoesNotExist: Site matching query does not exist. I cannot for the life of me get my head around that. I suspect it's something to do with what you said -- "whatever is proxying to Django setting the appropriate HTTP_HOST header." -- which I don't understand. Any additional advice gratefully received. ================================== /opt/mailman/venv/lib/python3.11/site-packages/django_mailman3/views/user_adapter.py ================================== COMMENT OUT THESE 2 LINES... # def is_open_for_signup(self, req): # return False REPLACE WITH THE FOLLOWING... def is_open_for_signup(self, req): if req.META['HTTP_HOST'] == 'lists.mydomain.com': return False else: return True ================================== /etc/mailman3/settings.py ================================== Append the following ... ACCOUNT_ADAPTER = 'django_mailman3.views.user_adapter.DisableSignupAdapter' ================================== systemctl restart mailman3 systemctl restart mailmanweb ==================================

4 months, 1 week

[MM3-users] Re: UnicodeEncodeError: 'ascii' codec can't encode character

by Marvin Gülker

Hi, Am 13. Dezember 2019 um 17:10 Uhr -0800 schrieb Mark Sapiro: >key is the <message-id> of the request message >request_type is 1 for a held message >mailing_list_id is a numeric index into the mailinglist table > >The issue is there are still held message requests there for the >messages you removed. You need to delete those entries from the _request >table. Thank you again for your valuable help. I've now taken the easy route and ran DELETE FROM _requests WHERE request_type=1; , i.e. I cleared the entire held messages queue. As it turned out, there were no requests of any other type than type 1. I've deleted all remaining files below /var/lib/mailman3/messages as well (after seeing it was only spam anyway, this time non-broken spam, but still spam). Now, finally, I can go to the held messages queue in Postorius again without a 500 error. The list of held messages there is now empty, but this is obviously expected. Let's hope that disabling SMTPUTF8 prevents the problem from further occuring. In any case, I've asked a friend report the problem to the Ubuntu tracker: https://bugs.launchpad.net/ubuntu/+source/mailman3/+bug/1856181 I'm back on track now. Thanks everyone! Marvin -- Blog: https://mg.guelker.eu

5 years, 11 months

[MM3-users] Re: Installing MM3 via pip fails…

by Patrick Ben Koetter

* Mark Sapiro <mark(a)msapiro.net>: > On 2/18/20 10:45 AM, Patrick Ben Koetter wrote: > > Has anyone managed to install MM3 recently using pip on Ubuntu 18? > > > > I followed the instructions at > > https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst…. > > As soon as I get to the Django part things get hairy. It seems Django requires > > something that was removed from it. > > > What exactly is the issue? I just tried following the doc starting at > <https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-setup> > and doing everything through > > (venv)$ python3 manage.py runserver > > and I encountered no issues. One possibility is the Ubuntu 18.04 box on > which I did this already had ruby-sass and python3-dev globally installed. > > sudo apt install ruby-sass > sudo apt install python3-dev > > Did you install these? Yes, I did. But to be sure I'll try on a vanilla VM and see how it goes if I install ruby-sass and python3-dev beforehand. p@rick -- [*] sys4 AG https://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG,80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief Aufsichtsratsvorsitzender: Florian Kirstein

5 years, 9 months

Search results for query "sapiro"