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

[MM3-users] Re: Mailman shutting down Hyperkitty: Request too large

by Mark Sapiro

On 1/31/25 21:44, Stephen J. Turnbull wrote: > > I don't think that's the best we can do, though. Especially if > Convert HTML to plain is also yes, we want to preserve the HTML part > and convert it, don't we? Not if we're collapsing alternatives. If we're collapsing a multipart/alternative part with text/plain and text/html alternatives to just the first alternative we don't keep the text/html part. The only html parts we keep and possibly convert to plain text are ones that aren't a second or later alternative in a multipart/alternative part. > I think a better (or additional) strategy > would be to check the selected alternative for blank, and if so, drop > it and try again for an appropriate type. The collapsing of a two part multipart message with an empty first part into a single part message with just the second part is the last thing that's done after all other content filtering. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] Re: 2.1 -> 3 migration without mboxes?

by Mark Sapiro

On 9/12/25 09:25, David Romerstein via Mailman-users wrote: > Hey, folks. I've searched the list archive but haven't found a relevant thread yet. Any pointers would be helpful. > > I have a handful of lists in a 2.1 instance for which I have web archives but not original .mbox files. Is there a way to migrate those lists, including the years of archives, to 3? Ideally you would have Mailman's archives/private/LISTNAME.mbox/LISTNAME.mbox files which is all you need. If tho don't have those, but you have the periodic archives/private/LISTNAME/*.txt files, you could concatenate those for a list into one mbox file. In some cases the From: headers will be munged. I.e., they may be like From: user at example.com (user name) and you would at least want to replace ` at ` with `@`. If you don't have even those, you would have to somehow process the HTML files into messages for a mbox. There is no way to import the HTML directly into HyperKitty. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 2 weeks

[MM3-users] Re: Good choice of defaults for content filtering?

by Mark Sapiro

On 7/30/20 5:00 PM, hansen(a)rc.org wrote: > Hi all, > > I had MM2 set to the default filtering that I think came OOTB. MM3 has none such and I was wondering: > a. What were those MM2 defaults (My MM2 server is long gone now). You will find the content filtering defaults beginning at <https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/Mailman…>. These have been the defaults for new lists since Mailman 2.1.21. Prior th that, the the default for pass_mime_types was ['multipart/mixed', 'multipart/alternative', 'text/plain'] > b. Is there a better set today. I know that MIME types can be faked, but they have worked. I want to avoid anything that can contain malicious code while also allowing simple text to go through. If you go with the current defaults, except of course for setting filter content on, you can add text/html to pass_types and any html parts that aren't collapsed out by collapse alternatives will be kept and converted to plain text. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: Internal Server Error on installing Mailman 3 using PIP

by Mark Sapiro

On 10/28/20 11:04 AM, Shashikanth Komandoor wrote: > Dear Mark, > > As you have suggested in my earlier issue, I have implemented > the latest stable version of mailman 3 through the URL > https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… > . > > But after the installation through the above URL, when I > tried running the command *elinks http://localhost:8000/postorius/lists > <http://localhost:8000/postorius/lists>* or *elinks > http://localhost:8000/admin <http://localhost:8000/admin>*, I got the error > as *Internal Server Error*. > > I don't find any specific log in mailman.log or in > mailmansuite.log. > > Is there any way to solve this issue ? > You need to hire a consultant who understands Mailman 3 installation to help you with this. The help you need is beyond the scope of this list. I am not available as a paid consultant. I do not do that work. See <https://wiki.list.org/x/4489296> for a partial list of people who do. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: Subscription request cannot be moderated: 404 Not Found

by Mark Sapiro

On 1/14/21 3:43 PM, Eric Broens via Mailman-users wrote: > Hi Mark, > The link that shows the subscription request pending approval is as follows: 'https://<host_url>/postorius/lists/<listname>.<domain>/subscription_requests' > > The link behind the accept button is as follows. 'https://<host_url>/postorius/lists/<listname>.<domain>/handle_subscription_request/4d6b4b11266c7332684c5a492eb3f92c531f761b/accept' > > I have checked if there is already a subscription with that email address, but that's not the case. I don't know why that would 404 unless the token 4d6b4b11266c7332684c5a492eb3f92c531f761b didn't exist, but since it came from a "current" view, it should be good. I have seen occasional issues where two moderators attempt to handle the same request in close succession - i.e. both get the pending request and try to handle it and the second fails because the request is gone, but that appears not to be the case here. You might check the web server logs, the Django log and Mailman's logs to see if there is any more of a clue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

[MM3-users] Re: re-sending confirmation mails (was Re: Re: pending subscriptions lost?)

by Mark Sapiro

On 3/15/22 12:22, IEM Network Operation Center (IOhannes m zmölnig) wrote: > > hmm. > the list-url (e.g. where you can subscribe to the list) for my instance > looks like https://$domain/postorius/lists/$list_id/ (that is: it spells > "postorius" rather than "mailman3"). > so i guess the URL should be > https://$domain/postorius/lists/$list_id/confirm/?token=$token, which > unfortunately returns 404. > > also, my postorius/urls.py does not contain an url-pattern for > "confirm", unlike the current one as found on > <https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/urls.py#L83> > > > > so i guess this was not possible yet with postorius 1.2.4 Yes, This was added in Postorius 1.3.4 (over a year ago) > yes. > the *current* template. > but not the template that came with mailman3 3.2.1 Which is over 3 years old. You should really be taking up these issues with Debian. Maybe if they got enough pressure from users, they would update their package. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] {Spam?} Re: Monthly mailman-web job using a lot of memory

by Mark Sapiro

On 7/1/22 1:40 AM, Andy Smith wrote: > > In the job list I see: > > appname - jobname - when - help > -------------------------------------------------------------------------------- > hyperkitty - update_and_clean_index - monthly - Update the full-text index and clean old entries > > so I'm guessing it's that, but there is also: > > hyperkitty - update_index - hourly - Update the full-text index > > which hasn't been noitceably a problem so I wonder why the "and > clean old entries" bit is so much more heavyweight, what exactly it > dopes and if there's any way to make it lighter on resources? The difference is the update_and_clean_index job calls hyperkitty.search_indexes.update_index() with remove=True See https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/search_index…. The comments say "Setting remove to True is extremely slow, it needs to scan the entire index and database." I second Mark Dadgar's comment to replace whoosh with xapian. It will help, although it requires rebuilding the entire search index. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Re: migrate MM3 list from an old server to a new one

by Mark Sapiro

On 8/6/24 01:43, noc(a)iem.at wrote: > > there *is* documentation about migrating MM2 to MM3; and my understanding is that `mailman-web migrate` can be used to upgrade a given MM3 instance to a new version. No. the mailman-web migrate command will apply relevant migrations for various django projects. You do need to rin it after upgrading things like hyperkitty, postorius and django-mailman3 and other dependencies which may have defined migrations for various database schema changes, but this will do nothing for your data. For that, you need to dump the mailman and mailmanweb databases on the old server and import them on the new server. > but how can i export an entire MM3 list (including 20 years of archives) to some serialization format, and import it again in another instance? With the dump and other utilities from your database manager. Almost everything is in the database. There are some things in Mailman's var/ directory, but those can simply be moved. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

[MM3-users] Re: MTA setup

by Mark Sapiro

On 12/24/24 09:31, Arte Chambers via Mailman-users wrote: > Looks like the from header is the email address I am using for testing: From: > Arte Chambers <paul.m.robey(a)gmail.com> I'm not sure what's going on. Previously, I said > Presumably it has previously requested and received the list_url and > the permalink to put in the message headers. This can be confirmed by > the presence of List-Archive: and Archived-At: headers with values > in the messages from the list. but they aren't there. ... > Archived-At: <> > List-Archive: <> I was able to add that message to a test list with no problem, so now it looks like the issue is possibly mailman_hyperkitty not able to communicate with hyperkitty, although the log messages aren't consistent with that. Possibly the issue is not with the message you sent, but with the first message in var/archives/hyperkitty/spool/. Is /1734973370.5060537+806f73d2a296b0293228a9489b81129740d7afea.pck the first file in a listing of var/archives/hyperkitty/spool/? If not, what does `mailman qfile` show for the first one? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 2 months

[MM3-users] Re: Implementing threading [was: hyperkitty failed to create a thread]

by Mark Sapiro

On 2/12/19 8:09 AM, Stephen J. Turnbull wrote: > > I suppose HyperKitty uses References (it works for messages that have > proper Message-IDs ;-), but I don't know what algorithm it uses. > Might be worth looking into, as well as considering a more Postelian > parsing of Message-IDs. Specifically, take the field body, unfold it, > strip leading and trailing whitespace and leading "<" and trailing > ">", and whatever's left is the message ID. Hyperkitty uses In-Reply-To: and if absent falls back to the last item in References: to determine a message's parent. I haven't looked at what happens if the parent is not in the archive but arrives later. We could look at earlier References: items to try to find one we know, but this could result in bad threading if a later reference arrives after we think we've determined the parent. The unfolding of Message-ID: is now correct. See <https://gitlab.com/mailman/hyperkitty/merge_requests/125>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years

Search results for query "sapiro"