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

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

by Jeremy Stanley

On 2024-09-18 16:36:50 -0700 (-0700), Mark Sapiro wrote: > On 9/18/24 10:13, Jeremy Stanley wrote: [...] > > Since all the lists for the given domain will be moving to the > > same unused new domain on the existing server, and can move at > > the same time, I suppose this could be done through (offline if > > necessary) backend database update queries. [...] > For the mailing list, the only changes needed are to the > mailinglist table; but this leaves the question of list_id. > According to RFC 2919, section 4, the list_id should not change, > but this is problematic in that if it isn't changed, [...] > so to reduce confusion, it may be better to update the list_id > values [...] > For HyperKitty, similar changes need to be made to the > hyperkitty_mailinglist table. [...] Thanks! This looks even more straightforward than I'd hoped. -- Jeremy Stanley

1 year, 11 months

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

by Odhiambo Washington

On Fri, Nov 22, 2024 at 11:28 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 11/22/24 11:02, Joshua Bushe wrote: > > Unsure where these hide inactive or hide private boxes are located. > Looked through all settings. > > > They are at the top of the main Hyperkitty overview page. E.g. like > https://lists.mailman3.org/archives/ My lists are public, and I have nothing to hide, so let me expose my issue—which I believe is similar to that of the OP. https://mm3-lists.kictanet.or.ke/archives/ - is empty, but there is this active list, which has archives: https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.k… I have been wondering why. -- 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, 8 months

[MM3-users] Re: Heads up: settings.ACCOUNT_AUTHENTICATION_METHOD is deprecated

by Andreas Vetter

On Montag, 10. Februar 2025 20:26:26 CET Mark Sapiro wrote: > On 2/10/25 01:07, Andreas Vetter wrote: > > That is unfortunately not enough to get rid of the Warning, because > > venv/lib/ python3.11/site-packages/mailman_web/settings/mailman.py > > contains the old ACCOUNT_AUTHENTICATION_METHOD and allauth is complains > > about it. > > In the recommended virtualenv installation, the settings that Django > sees are /etc/mailman3/settings.py. That in turn contains > ``` > from mailman_web.settings.base import * > from mailman_web.settings.mailman import * > ``` > but if following those imports you have > ``` > del ACCOUNT_AUTHENTICATION_METHOD > ``` > Django won't see it and won't complain. Did you actually try this? If > so, did you put the `del ACCOUNT_AUTHENTICATION_METHOD` after `from > mailman_web.settings.mailman import *` in /etc/mailman3/settings.py? You are right, it is enough, when one does not have a typo in it. My fault. Thanks a lot, Andreas

1 year, 6 months

[MM3-users] Re: Pck files stuck in out queue

by Lieuallen, Thomas Otis

Mark, You were (of course), absolutely on target, thank you! I have a remaining issue that baffles me. With my test list, I created a template for ‘list:member:regular:header’. It just has text in it, keeping it simple. I create it and see the entries in the database tables and they are correct. However, when I send a test email, my template text is not inserted, but instead another simple text: “testing hello”. I do the same with list:member:regular:footer, and it works just fine. It is just the header that is working incorrectly. When I remove that postorius header template for the list, that ‘testing hello’ goes away. So, it’s only appearing when I have a postorius template setup for that list. I have searched on the file system for any such templates and only see the default ones; all zero length files. There are no templates defined for the domain in postorius – but if there were, I’d expect to see that test header all the time. I’m just baffled. Any clues? I’m a relative newbie to mailman3. When I first set it up, I tried the postorius templates for the domain. They didn’t work (had to have been due to the POSTORIUS_TEMPLATE_BASE_URL being wrong. So, I scrapped that and went with templates in the file system. Thank you Tom Lieuallen From: Mark Sapiro <mark(a)msapiro.net> Date: Thursday, February 6, 2025 at 3:46 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Pck files stuck in out queue [This email originated from outside of OSU. Use caution with links and attachments.] On 2/6/25 15:21, Lieuallen, Thomas Otis via Mailman-users wrote: > Mark, > > There were no apparent permissions problems on templates. I was getting the ‘Cannot connect to SMTP server’ message in mailman.log. > > I did end up applying the patch to decorate.py and messages went through. I’ve since removed the patch, as I’m still looking for an answer and might as well let it queue up again. Per the above, template access is definitely the problem. > The only thing that is making me ponder at the moment is that the list owners setup a template for list:member:regular:footer in postorius. It appears that each list has a copy of that file. The modifications I see in postorius are not in their …/templates/list/<listname>/en/list:member:regular:footer.txt file. Are their modifications stored somewhere else and causing the problem? Templates set in Postorius are stored in the database in the postorius_emailtemplate table. At the same time an entry is made in the template table with a uri to retrieve the template from a Postorius API. The uri is something like http(s)://host/mailman3/api/templates/list/LIST-ID/list:member:regular:footer where the http(s)://host part is from the setting for POSTORIUS_TEMPLATE_BASE_URL. The issue is that uri is not retrievable probably because the setting for POSTORIUS_TEMPLATE_BASE_URL is wrong. You should look at the uris in the template table in the database and figure out what they should be, probably by trying to retrieve one in a browser with the scheme and host what you actually use to access Postorius. Once you figure out what the correct uri is you can set POSTORIUS_TEMPLATE_BASE_URL appropriately, but this won't fix the existing template table entries. You can fix those manually in the database or you can delete and recreate the templates in Postorius after fixing POSTORIUS_TEMPLATE_BASE_URL and restarting the Mailman web service. -- 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://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to lieualth(a)oregonstate.edu

1 year, 6 months

[MM3-users] Re: Hyperkitty_import.py Error

by Brian Carpenter

On 2/7/21 2:40 PM, Mark Sapiro wrote: >> I am trying to import some old archives (going back to 2003) into a >> Mailman 3 list. The import job is terminating very early in the process >> with the following error: >> >> IndexError: string index out of range >> >> 1. Is there a way to fix a mbox file that is generating this type of error? > Yes, but you need to understand what message is causing the error and > why. The full traceback from the error can help. So can the script at > <https://www.msapiro.net/scripts/check_hk_import>. > Hi Mark, I wanted to follow up to say that I solved the import error by updating to the latest stable version of MM3/Hyperkitty. You actually had a fix recently to address the "IndexError: string index out of range" error specifically. Your other comments were also very helpful. Thank you! -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 6 months

[MM3-users] Re: Migrating archives from Mailman21 to Mailman3

by Odhiambo Washington

On Tue, Sep 24, 2024 at 7:38 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 9/24/24 05:49, Markus Grandpré wrote: > > Dear List, > > > > I have a question about migrating archives from Mailman21 to Mailman3: > > Is it possible to migrate only the archive of a list, but not the list? > > > Yes. There is no requirement that archives have a matching list in > Mailman core. So the documentation at https://docs.mailman3.org/en/latest/migration.html needs revision as it creates the impression that a matching list needs to be there: ``` $ python manage.py hyperkitty_import -l foo-list(a)example.com $var_prefix/archives/private/foo-list.mbox/foo-list.mbox ``` -- 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: Invalid FilterAction: discard. Treating as discard

by Henrik Rasmussen

Mark Sapiro wrote: > Then if collapse_alternatives is True (settable here or in Postorius), > any multipart/alternative parts will by replaced by the first, > presumably text/plain, sub-part. > > Finally, if convert_html_to_plaintext is True (settable here or in > Postorius), any remaining text/html parts will be converted to plain > text by lynx or whatever is configured as html_to_plain_text_command in > mailman.cfg. > This will ensure that filter_action is applied only to those messages > which have no text/plain or text/html parts. Great, that helped for the content. Thanks. Still, attachments (PDF) is removed by Mailman. I as the list admin to send a new mail, but hold it back, to see what type it is. If that doesn't work, we have talked about deleting the list and add it from scratch. Is the any prolems (with left overs from the old imported list), when deleting the list from Postorius? /Henrik Rasmussen

7 years, 2 months

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

by Odhiambo Washington

On Mon, Jan 23, 2023, 23:09 Mark Sapiro <mark(a)msapiro.net> wrote: > 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' > Doesn't this follow the same rules of getting the settings.py from gitlab? > >

3 years, 6 months

[MM3-users] Re: Hyperkitty Recommended mySQL Database Setup & Archive Importing

by matthew＠alberti.us

5 years, 8 months

[MM3-users] No e-mail distribution after import of archive

by Markus Grandpré

Dear Mr. Sapiro, on our test system we noticed the problem that after importing a mailing list archive from a Mailman system v2.1 into a Mailman system v3.3.8, e-mails are no longer distributed via this mailing list. E-mails that are written to the list find their way into the archive, but they are not sent to any member of the list. Before the archive was imported, writing an e-mail to the list and distributing this e-mail via the list was not a problem. Unfortunately, we cannot find any indication of this issue in the log of the mailman system v3.3.8. Please help us to further analyze and solve this problem, as we are planning to import 188 archives into our new productive mailman system v3.3.8 during the next months. With kind regards, Markus Grandpré -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342

1 year, 9 months

Search results for query "sapiro"