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

[MM3-users] Re: Cannot connect to SMTP server

by Mark Sapiro

On 8/13/22 15:14, mkummini(a)cmi.ac.in wrote: > > However, I get the following line each time I do a restart > Aug 14 03:19:57 2022 (4096859) Cannot connect to SMTP server localhost on port 587 > I tried to specify the name of the postfix server, though it runs on the same machine as mailman3, and the different ports : 25, 465 and 587; they all raise the same error. You only see this message once at startup because it is only issued once until there is a successful delivery. This error can occur for reasons other than an inability to connect to the smtp server. In particular, if there are errors in decorating the message with a header and/or a footer because of permissions or other problems in retrieving a list:member:regular:header or list:member:regular:footer template, this will occur. Have you put templates in Mailman's var/templates directory (possibly named /var/lib/mailman/templates in the debian package). If so, can the Mailman user (I think `list` in a debian package) find and read them? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

[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, 8 months

[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

1 year, 1 month

[MM3-users] Re: Reject with notification not working

by Mark Sapiro

On 3/24/26 11:30 AM, MegaBrutal via Mailman-users wrote: > I'm creating a newsletter style mailing list where only one address is > allowed to send e-mails, members just receive them, but they shouldn't be > able to post to the list. Still I want to send a friendly notification if > members accidentally try to post to the list, so I set "Reject (with > notification)" as "Default action to take when a member posts to the list", > but it doesn't work: my test address didn't receive any notification when I > tried to send a message to the list. What is the moderation action for the address you posted from? > I tried to define the > "list:user:notice:rejected" template for the list, but to no avail. What do you mean by no avail? Do you mean the template you defined wasn't honored. If so, how did you define it? Or do you just mean that didn't get you the rejection email? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 3 weeks

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

by Mark Sapiro

On 01/30/2018 11:38 PM, Peter Münster wrote: > 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? It's not a MUST, just a SHOULD, but RFC 5322, sec 3.6.4 says Though listed as optional in the table in section 3.6, every message SHOULD have a "Message-ID:" field. >> 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 ... Which says only every 10th message will be VERPed. You want verp_delivery_interval = 1 to VERP every message. >> 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. The message does appear in the mail log, but until the issues below are fixed, even if Mailman receives it, you won't see it. >> 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? They should be processed by Mailman and scored as bounces for the recipient if recognized and forwarded if not (depending on settings), but they currently are only stored. >> 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)? I have filed <https://gitlab.com/mailman/mailman/issues/448> for this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 8 months

[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

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

[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

4 years, 7 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

4 years, 3 months

Search results for query "sapiro"