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

[MM3-users] Re: migration

by Dave McGuire

On 7/30/21 3:48 PM, Mark Sapiro wrote: >> Is there a way that I can "dump" the configuration from an existing >> mailman3 server, and "import" it into a new instance? I'd really like >> to avoid re-doing all of the configuration, etc, as there are quite a >> few lists and everything is set up pretty much the way I want it. > > If you use the same database manager it should be no problem to get a > dump of the existing Mailman database to load into the new instance, or > if these are on the same server, just point the new instance to the > existing database. In either case, the database should be loaded and the > Django commands `migrate`, collectstatic`, `compress` and > `compilemessages` run[1] before starting Mailman services. Mailman core > will run any necessary updates to its database upon startup. > > You may also need to rebuild the HyperKitty search index with the > `update_index` Django command, but you may be able to use the existing > one if the search engine is the same. > > [1] See > https://docs.mailman3.org/en/latest/install/virtualenv.html?highlight=colle… > et seq. Understood. I am not at all fluent in django interactions (I'm still not entirely sure of what django actually *is*) so I have some reading to do. Any pointers on "django wrangling for n00bs" would be great. As I mentioned, I've not been hacking on mm3, just using it. I'm an accomplished programmer, but embedded C and assembler are a few galaxies away from python and web services! -Dave -- Dave McGuire, AK4HZ New Kensington, PA

5 years, 1 month

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

by Willie Castillo

Sure. the file was updated and MM3 restarted. Looks like the modification to the /etc/mailman3/mailman-hyperkitty.cfg file did the trick. We are now able to see the July 25th message in the archives. Thank you Odhiambo and Mark for your assistance. ________________________________ From: Odhiambo Washington via Mailman-users <mailman-users(a)mailman3.org> Sent: Tuesday, July 29, 2025 8:54 AM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [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. 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: https://urldefense.us/v3/__http://127.0.0.1:8000/archives/__;!!E8b8mVbrrfWV… > <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: > https://urldefense.us/v3/__http://www.catb.org/*esr/faqs/smart-questions.ht… > <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: https://urldefense.us/v3/__http://www.catb.org/*esr/faqs/smart-questions.ht… ] _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://urldefense.us/v3/__https://lists.mailman3.org/mailman3/lists/mailma… Archived at: https://urldefense.us/v3/__https://lists.mailman3.org/archives/list/mailman… This message sent to willie.castillo(a)caemilusa.com

1 year, 1 month

[MM3-users] Re: Don't start nntp runner by default - was: Mailman3 doesn't send Mails to users (Debian12 with Plesk)

by Odhiambo Washington

On Fri, May 24, 2024 at 11:25 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/24/24 3:37 PM, admin(a)bclug.ca wrote: > > > > Is nntp common enough these days to be a useful default runner? > > > > I disabled it in mine when I noticed it, but it seems (IMHO) a waste of > > resources (yet another Python interpreter running) for a fairly edge > > case of mailing list <--> nntp transits. > > > You raise an interesting point. By default, the runner runs, but if > there are no lists gating to usenet, its queue is always empty and it > mostly sleeps between waking, finding its queue empty and going back to > sleep. A more significant use of resources is every (default) 5 minutes > spawning `mailman gatenews` which goes through a startup process and > then looks at every list figuring out there's nothing to do. > > We could default mailman.cfg to contain `start: no` in the runner.nntp > section so people would need to enable it if they wanted it. What do > others think? > I last heard of usenet in the late 90's. Do they still exist, even? -- 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]

2 years, 3 months

[MM3-users] Re: Non-ascii characters missing from Pipermail archive txt and gz downloads

by Mark Dale

Hi Ruth, Apologies for the late response. I posted my message to the MM3 list in error and have since reposted it to the MM2 list. However, thank you for taking the trouble to reply. The problem lies outside the choice of editor as both files are being viewed in the same editor -- with one correct and the other not. Mark Sapiro has explained (on the MM2 list) what is causing the problem. Armed with that information I just have to now find a way .... Regards, Mark -------- Original Message -------- From: Ruth Ivimey-Cook [mailto:ruth@ivimey.org] Sent: Friday, April 9, 2021, 15:24 UTC To: mark(a)postmark.io, Mailman users Subject: [MM3-users] Non-ascii characters missing from Pipermail archive txt and gz downloads > Hi Mark > > I'm not sure, but I think the problems are to do with the program you are using to view the txt file. > > A modern mail reader understands the Content-type: header and will adjust its character processing accordingly, but a .txt file has no default character encoding, so any text editor will have to "use its best judgement". Some will default to utf-8, because that is compatible with 7-bit ASCII (NOT Latin1) while others will just put characters out and hope for the best (esentially leaving the result to the encoding of the font). > > In theory, a UTF-encoded text file can begin with the "BOM" marker, a sequence of characters which is supposed to indicate which variety of Unicode is in use, but this is rarely present, especially for UTF-8. > > Try looking at your text file with a UTF-8 capable text editor **and ensure that you tell the editor to use the UTF-8 encoding**. I expect it will look ok then. > > > Hope this helps, > > Ruth > > > On 09/04/2021 13:52, Mark Dale via Mailman-users wrote: >> Mailman 2.1.34 >> Debian 10 >> Postfix >> >> Hi >> >> I'm hoping someone can shine a light on character encoding issue I've encountered. >> >> A plain-text email with non-ascii characters in the body gets posted to the list. >> >> As per Mark Sapiro's guide I've captured the incoming message to file. >> >> - https://www.mail-archive.com/mailman-users@python.org/msg73469.html >> >> The message is received by Mailman with the non-ascii characters displaying correctly. >> >> The header of that message has: >> >> User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 >> Thunderbird/78.9.0 >> MIME-Version: 1.0 >> Content-Type: text/plain; charset=utf-8 >> Content-Language: en-AU >> Content-Transfer-Encoding: 8bit >> >> In the list's mbox file and archive webpage, the message displays the non-ascii characters correctly. >> >> In the archive's downloaded .txt (and also .gz) file, the non-ascii characters are missing and displayed as "?". >> >> I've copied the message text in below, from both the correct one from the email and the erroneous .txt file. Hopefully they won't get scrambled up when I send this. >> >> Any advice on getting the non-ascii characters written into the archive .txt file would be gratefully received. >> >> Thanks, >> Mark >> >> >> === Message text as okay in mbox and as shown on the archive webpage === >> >> If one goes by the definition of veḷippaṭai as given in the Tamil Lexicon that the meaning of an ambiguous word should be disambiguated by a qualifying word, then aruvi āmpal does not conform to that definition since in the case of aruvi āmpal in Patiṟṟuppattu 63, aruvi is really made up of aru+vi, a compound. Moreover, the expression aṭai aṭuppu aṟiyā is already there to clarify that āmpal is a number and not a flower. Thus, aruvi simply provides information in addition to aṭai aṭuppu aṟiyā that āmpal is not a flower. The modern commentator Aruḷampalavaṉār also does not call it veḷippaṭai. >> >> === >> >> === Message text with missing characters in te archive's txt and gz downloads == >> >> If one goes by the definition of ve?ippa?ai as given in the Tamil Lexicon that the meaning of an ambiguous word should be disambiguated by a qualifying word, then aruvi ?mpal does not conform to that definition since in the case of aruvi ?mpal in Pati??uppattu 63, aruvi is really made up of aru+vi, a compound. Moreover, the expression a?ai a?uppu a?iy? is already there to clarify that ?mpal is a number and not a flower. Thus, aruvi simply provides information in addition to a?ai a?uppu a?iy? that ?mpal is not a flower. The modern commentator Aru?ampalava??r also does not call it ve?ippa?ai. >> >> === >> _______________________________________________ >> 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/ >

5 years, 4 months

[MM3-users] Re: Problems after upgrading from bullseye to bookworm

by Eggert Ehmke

Hello Mark, thank you. I did change that entries, and now my mailman runs fine on Debian Bookworm. I did a complete reinstall of the venv directory to have a clean start. Maybe this was not needed. What's missing in the documentation: -the directiories web/logs have to be created manually with the ownership mailman. -The debian package pkg-config must be installed. -the package psycopg2-binary can/must be installed without version restriction on Bookworm Maybe this info helps some other people. Cheers, Eggert Am Montag, 26. Juni 2023, 22:22:37 CEST schrieb Mark Sapiro: > On 6/26/23 12:35 PM, Ken Alker wrote: > > I'm brand new to this, so take this with a grain of sale, but, I had a > > similar problem a few days ago, however, mine was "flufl.i18n>=3.2". > > Perhaps the same thing is happening with flufl.lock (but that didn't bite > > me). > > > > I solved my problem by following this: > > <https://gitlab.com/mailman/mailman/-/issues/1085> and, ultimately > > modifying > > "$VENV_ROOT/lib/$PYVERSION/site-packages/mailman-3.3.8.egg-info/requires. > > txt" per that thread (see > > <https://gitlab.com/mailman/mailman/-/issues/1085#note_1442207929> by > > Thomas Ward section called "The WORKAROUND"). Maybe you need to do the > > same thing, but for flufl.lock. > Yes, the same issue now affects flufl.lock as well as flufl.i18n. You > will need to change both flufl.lock->flufl_lock and flufl.i18n->flufl_i18n. ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

3 years, 2 months

[MM3-users] Re: Hyperkitty "All Threads" results in error

by Mark Dadgar

On Oct 14, 2020, at 4:37 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/14/20 11:12 AM, Mark Dadgar wrote: >>> On Oct 4, 2020, at 10:34 AM, Mark Dadgar <mark(a)pdc-racing.net> wrote: >>> >>> So I have been wrestling with this problem for a while now. Most times, but not every time, when someone clicks on the All Threads link in hyperkitty, a 500 error is generated. > > > Does this happen on all lists, only some lists or only one list? > > >>> I googled it, obviously, and at first I thought it was related to this issue, but that has not proven to be the case: >>> >>> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > What did you google? This query gets a lot of stuff with some hints, but > nothing definitive. > > django render raises VariableDoesNotExist("Failed lookup for key " > > One thing I noted at > <https://askbot.org/en/question/3095/django-error-variabledoesnotexist-faile…> > was > > models out of date - run python manage.py syncdb and python manage.py > migrate > > You could try that. Note that your django admin command might be > something other than `python manage.py`. Also note syncdb has been > removed from Django >=1.9. Currently, the above becomes `makemigrations` > followed by `migrate`. > > I also suggest running the django admin commands > > `collectstatic --clear --noinput` > and > `compress` My re-install seems to have fixed this issue as well. BONUS! - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 6 months

[MM3-users] Re: Dealing with hyperkitty spool files (was Re: Re: Fwd: [Django] ...)

by David Partain

> On Wed, 2021-03-03 at 08:29 -0800, Mark Sapiro wrote: > > 1. Am I correct in assuming that I can just use my favorite editor > > (vi) to remove the offending characters from the file? > No. The file is a Python pickle and you can't edit it. You would need > to get the message and the metadata from the pickle (you could at least > view it with the `mailman qfile` command), edit the message and then > re-pickle the message and metadata. And, in my impatience, I tried it before receiving your response and now I seem to have done silliness in my database :( New error in mailman-web.log: AttributeError: 'NoneType' object has no attribute 'subject' Sigh. Stupid me. If you have suggestions on fixing that... Right now, my plan is simply to remove the first message in the queue (since I assume it'll be the "broken" one) and it'll just not be in the archive. Life's hard. Even if I unpack 'em to edit, I'll find mail in, for example, in base64, and I'm not going to fix the mail by decoding, editing, re-encoding, ... Nope. > > 3. Can I do something to make hyperkitty go through the spool? > > > > I don't know what you mean. Sorry I wasn't clear. I simply meant, "Is there a way to start hyperkitty going through the spool manually?" It sounds like, though, that I don't need to do that if it's going to happen that often anyway. Cheers, David

5 years, 6 months

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

by David Newman

On 12/22/21 7:29 PM, Mark Sapiro wrote: > On 12/22/21 6:20 PM, David Newman wrote: >> >> 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. > > > This looks like a uwsgi issue as discussed at > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > although that's with apache and not nginx so it may not be. If I'm reading the thread correctly, it's Apache workarounds to an underlying Debian issue, so I agree it may not apply with nginx. > > >> Adding a stanza for 'location /mailman/' to the nginx config above >> clears the 404 error, but Postorius returns "Page not found" with no >> entry in the web or MM3 logs, and a 200 OK in the Nginx logs. >> >> I think the URL is supposed to go to the list page in Postorius. How >> to configure this so that list owners and moderators get a valid URL >> for list management? > > > I'm not sure what the solution is in this case, but a workaround would > be to add > > url(r'^mailman/', include('postorius.urls')), > > to the urlpatterns list in urls.py. There are 260 files named 'urls.py' under /opt/mailman, mostly for socialaccount stuff. Where does that change go? All files? Or just this one: /opt/mailman/venv/lib/python3.9/site-packages/postorius/urls.py Or somewhere else? Thanks again. dn

4 years, 8 months

[MM3-users] Re: Python 3.13 compatibility

by Washington Odhiambo

On Sun, Mar 29, 2026 at 6:11 PM Thomas Krichel <krichel(a)openlib.org> wrote: > Mark Sapiro writes > > > If you do that and it results in a working system, you can then patch > > mailman/utilities/i18n.py as follows > > Thank you. This works, and I can successfully import a first > list configuration. > > > However there are other incompatibilities between the released Mailman > > versions and Python 3.13. > > Hmm https://docs.mailman3.org/en/latest/install/virtualenv.html > states "3.13 is recommended as it is the latest version of Python > with which Mailman is tested." > > > At the moment, until updated packages are > > released, in a Python 3.13 environment it is best to install all of > mailman, > > django-mailman3, postorius, hyperkitty and mailman-web from the heads of > the > > gitlab branches. > > I would love to see a command line for that. When I go to the gitlab > page, https://gitlab.com/mailman/, I see a bunch of project that > don't immediately correspond to pip package names. > pip install git+https://gitlab.com/mailman/mailman@master pip install git+https://gitlab.com/mailman/mailmanclient@master pip install git+https://gitlab.com/mailman/mailman-hyperkitty@master pip install git+https://gitlab.com/mailman/hyperkitty@master pip install git+https://gitlab.com/mailman/django-mailman3@master pip install git+https://gitlab.com/mailman/postorius@master pip install git+https://gitlab.com/mailman/mailman-web@master -- 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]

5 months, 2 weeks

[MM3-users] Re: Hyperkitty download mbox

by Andrew Hodgson

Mark Sapiro wrote: >On 4/26/21 2:00 AM, Andrew Hodgson wrote: > >> Yep there is a problem with an imported mbox which seems to be present somewhere in the archive on all the lists which I imported using that method. Here is a recent trace from the download option: [...] >Thanks for the traceback. The issue appears to be with folded headers that should either be unfolded before storing in HyperKitty's database or upon retrieval for this process. This is probably because of outlook.com folding Message-ID: headers. See >https://gitlab.com/mailman/mailman/-/issues/844 for one manifestation of this. >I think if you replace the >``` > msg["Message-ID"] = "<%s>" % self.message_id ``` line at 178 in /opt/mailman/venv/lib/python3.7/site-packages/hyperkitty/models/email.py >with >``` > msg["Message-ID"] = "<%s>" % self.message_id.strip(' <>\r\n') ``` it will avoid this issue. I tried this but get the same error, hope I did the modification correctly. [2021-04-30 19:56:31 +0000] [22104] [ERROR] Error handling request Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.7/site-packages/gunicorn/workers/sync.py", line 180, in handle_request for item in respiter: File "/opt/mailman/venv/lib/python3.7/site-packages/hyperkitty/views/mlist.py", line 335, in stream_mbox msg = email.as_message() File "/opt/mailman/venv/lib/python3.7/site-packages/hyperkitty/models/email.py", line 178, in as_message msg["Message-ID"] = "<%s>" % self.message_id.strip(' <>\r\n') File "/usr/lib/python3.7/email/message.py", line 409, in __setitem__ self._headers.append(self.policy.header_store_parse(name, val)) File "/usr/lib/python3.7/email/policy.py", line 145, in header_store_parse raise ValueError("Header values may not contain linefeed " ValueError: Header values may not contain linefeed or carriage return characters Thanks. Andrew.

5 years, 4 months

Search results for query "sapiro"