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

[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

6 years, 11 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, 4 months

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

by matthew＠alberti.us

5 years, 5 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, 6 months

[MM3-users] Re: outgoing.py mailman@example.com issue

by dancab＠caltech.edu

Mark Sapiro wrote: > On 11/7/21 1:22 AM, Stephen J. Turnbull wrote: > > dancab(a)caltech.edu writes: > > I deployed Mailman3 last night and today we've had some "bounced" > > messages with headers referencing mailman(a)example.com. This has > > only happened with a few lists. Any ideas what causes this? > > ... > > Mark may have a better idea. > > This is a fake DSN that is generated when Mailman's attempt to send a > bounce probe results in a failure from the MTA to which Mailman > delivers. See code at > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/outgoin... > and around > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/outgoin... We do have mailman(a)caltech.edu configured with valid members/owners. We're using Postfix for the MTA. Is it possible there's a misconfiguration there? We've been testing the system with a handful of lists for months. -- Dan

4 years, 6 months

[MM3-users] Re: Unable to update templates

by Mark

************************************************** > On 5/27/25 18:54, Mark wrote: >> >> However when I update the template, the databases are updated >> correctly but the Welcome message is still sent with the old template >> content. >> >> mailman.templates >> mailmanweb.postorius_emailtemplate >> >> Additionally, if I delete the template and create a new one the old >> content still gets sent. >> >> I cannot find where this content is written or is being cached. ************************************************** On 2025-05-28 02:34, Mark Sapiro wrote: > The content is stored in the mailmanweb.postorius_emailtemplate table. > As far as Mailman core and Postorius are concerned, that's the only > place. > ... If the template is deleted, the > mailman.template table entry is deleted and at that point Mailman core > will get the template from the file system following it's normal > search rules, ************************************************** Where does Mailman core search for the file if the table entry is deleted?

1 year

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

by Flo

On 10/11/25 18:54, Mark Sapiro wrote: > > Possibly sqlite displays them in a different order. To be sure you could do > > SELECT mail_domain, domain FROM django_mailman3_maildomain JOIN > django_site ON site_id = django_site.id; > > which will display only the mail_domain and the site domain. > I did it and it's like I described below. Unfortunately no news. >> For each of the lines mail_domain (field 2) is the same as the domain >> name (field 6, if I am right). >> Any domain name (and mail_domain, which has the same value) differs >> from the ones in any other line. >> >> So they are unique. > > Anyway, if all 3 mail_domain values are unique, that doesn't explain the > issue. I can only guess that this is a Debian package issue. > So I have to install directly without Debian packages ... Thank you for your help. Flo

7 months, 2 weeks

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

by Mark

On 2025-08-04 21:37, Mark Sapiro wrote: > What happens if you put > ``` > ACCOUNT_ADAPTER = 'allauth.account.adapter.DefaultAccountAdapter' > ``` > in settings.py. > Hi Mark, Putting that in the settings.py file allowed the SignUp page to display as expected. So that was kind of back to square one. But following the clue of "DefaultAccountAdapter" -- I edited that adapter.py file by using your code and hey presto: success -- the SignUp page for that one domain is now disallowed. It's happy days. Thank you very much for your help in cracking this little chestnut. Best, Mark ========================================== @@ /opt/mailman/venv/lib/python3.11/site-packages/allauth/account/adapter.py @@ Line 271 ... def is_open_for_signup(self, request): """ Checks whether or not the site is open for signups. Next to simply returning True/False you can also intervene the regular flow by raising an ImmediateHttpResponse """ - return True + if request.META['HTTP_HOST'] == "lists.mydomain.com": + return False + else: + return True ... ==========================================

9 months, 3 weeks

[MM3-users] Re: unknown encoding: windows-874

by Stephen J. Turnbull

Mark Sapiro writes: > Python doesn't recognize windows-874 as known charset. iso-8859-11 is a known character set for Thai, with a few missing punctuation marks. If the message turns out to be not Thai, but mostly ASCII with a few broken characters that are probably punctuation (including directed quotes, ellipsis, and the EURO SIGN), any Windows-12xx character set (IIRC, Windows-1252 is closest to Latin-1) should have those in the same positions. > You can move it aside, and if it looks like something you actually want > to archive, you might be able to fix it, but that's tricky. The file in > var/archives/hyperkitty/spool/ is I think a pickled email message > object. You can view it with `mailman qfile`, but editing is tricky. If any of the above codecs seem to work, just editing the charset parameter in Content-Type header(s) should do the trick. Sorry, can't help with the editing process itself, though. Steve

6 years

[MM3-users] Re: per domain SITE_ID views?

by David Newman

On 12/28/21 1:30 PM, Mark Sapiro wrote: > On 12/28/21 1:14 PM, David Newman wrote: >> Using FILTER_VHOST, I have two domains set up and working with MM3, >> Postorius and Hyperkitty. However, because SITE_ID in settings.py >> points to one of the domains, that domain name always appears on >> Postorius and Hyperkitty pages. > ... >> How to get the correct domain to appear on that domain's Postorius and >> Hyperkitty pages? > > > I don't think the domain is actually displayed on Postorius pages. You are almost certainly correct. I saw dom1.tld on a login page, but hadn't realized that login page comes from Hyperkitty and not Postorious. > If > I'm wrong, on what Postorius view do you see it? As far as HyperKitty is > concerned, please file an issue for this at > https://gitlab.com/mailman/hyperkitty/-/issues/new Opened an issue here: https://gitlab.com/mailman/hyperkitty/-/issues/404 dn

4 years, 5 months

Search results for query "sapiro"