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

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Onyeibo Oku

On Mon, 31 Oct 2022 09:38:37 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/31/22 00:17, Onyeibo Oku wrote: > > > > It is not finding the logger file. The other django project on this > > machine is running fine. I can confirm that the logger plugin is > > installed. I must be missing something. > > If you are following > https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-configu… > take note of > ``` > # Make sure that this directory is created or Django will fail on > start. LOGGING['handlers']['file']['filename'] = > '/opt/mailman/web/logs/mailmanweb.log' > ``` > ` [Reviving this thread]. I abandoned the hyperkitty setup for a while and returned to it again today. I made progress. It turns out that I needed the uwsgi-logger-file rpm package and It wasn't installed with the uwsgi server. I adapted the settings also, since I was using Emperor mode (recall that there are other Django projects on the box). Currently, mailman, uwsgi and nginx are all running. They all seem to be happy until I assess the mailman-web home URL (e.g. http://my.server.com) The outcome: "502 Bad Gateway" Nothing shows in the logs except at /var/log/nginx/error.log: 2022/12/08 15:35:10 [error] 5879#5879: *7 upstream prematurely closed connection while reading response header from upstream, client: 105.113.33.89, server: my.server.com, request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.0.1:8000/favicon.ico", host: "my.server.com", referrer: "https://my.server.com/". Something seems to be wrong between uwsgi and mailman, but I don't know where to look. Regards Onyeibo

3 years, 9 months

[MM3-users] Re: Uncaught runner exception: 'str' object has no attribute 'decode'

by Henrik Rasmussen

> Fra: Mark Sapiro [mailto:mark@msapiro.net] > Sendt: 2. oktober 2017 17:26 > Emne: [MM3-users] Re: Uncaught runner exception: 'str' object has no attribute 'decode' > >> Is there some kind of workaround, I can give my users or something that the list admins can do as a workaround? > > There is no user or list admin workaround, but the defense is a fairly > simple patch. See the MR at > <https://gitlab.com/mailman/mailman/merge_requests/322> and the commit > at > <https://gitlab.com/mailman/mailman/commit/37b3f62afdf225a8e29b66fcefcdb56b9…>. > The commit changes 7 files, but only two are needed. The rests are tests > or reverting <https://gitlab.com/mailman/mailman/issues/256> which isn't >necessary. > > The only changes you need are those to mailman/email/message.py and > mailman/mta/connection.py. I am using Docker-mailman (not yet very familiar Docker and version control). I would expect I have to wait for a Docker-mailman release including this change, right? I have at least five+ lists which almost haven't been working since my switch from Mailman 2.1 to Mailman 3.1 (Docker-mailman 0.1.1), and I am desperate trying to figure out whether it is best to fall back to the Mailman 2 server, for the time being, where the lists came from, or it is better to wait for an update to the Docker-image. Will https://github.com/maxking/docker-mailman/milestone/2 fix my problems regarding failed mail handling and will it become available soon (when?) (https://github.com/maxking/docker-mailman/issues/147)? -- Henrik Rasmussen <her(a)adm.ku.dk> University of Copenhagen, Danmark

8 years, 11 months

[MM3-users] Re: mailing list aliases

by Abhilash Raj

On Fri, 2018-01-19 at 16:30 -0800, Mark Sapiro wrote: > On 01/19/2018 03:09 PM, Dmitry Makovey wrote: > > Not sure whether to mark this "SOLVED" yet - but when I manually updated > > postgres DB with the aliases I wanted - everything started to work as > > expected. > > > > so it does sound like a bug in mailman-core 3.3.0 . Shall I file it or > > was it already fixed in 3.3.1 (anouncement page didn't list that fix) > > > As far as I know, this is not a bug in core. It is > <https://gitlab.com/mailman/postorius/issues/58> however, this may in > fact be a bug in the REST API in which case I don't think it's fixed in > API 3.3.1 I guess we are all talking about the same thing, but just to mention, 3.1.1 is the latest release (instead of 3.3.1). > > > > 2. Related to #1 - we've migrated our mailing lists from foo(a)my.com to > > > foo(a)lists.my.com however we've preserved old addresses. But in new setup > > > mail sent in gets stopped for moderation with: "X-Mailman-Rule-Hits: > > > implicit-dest" . What's the best course of action here to get mailing > > > list respond to multiple email addresses? > > > acceptable_aliases is the way to address this, but as you note, it can't > be properly set via Postorius and possibly via REST. > > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- thanks, Abhilash Raj

8 years, 7 months

[MM3-users] Re: Opinions wanted.

by John Price

On Sat, Mar 07, 2026 at 05:00:43PM -0800, Mark Sapiro wrote: > On 3/7/26 15:42, Thomas Hochstein wrote: > > John Price wrote: > > > > > For any setting N items per page, if actualy number of items is less > > > than or equal to N, no need to render, no need for dropdown. Don't > > > show it. > > > > Wouldn't that result in a situation where you can use the dropdown to > > show more entries, but would often not be able go back to show less > > entries, as the dropdown won't be displayed? > > > That's the main argument against it. The counter argument is you can use the > browser's back button or refetch the URL without the count= fragment, but > there is concern that there could be circumstances where that doesn't work. I see now what the problem is and Thomas has changed my mind. Always show pulldown. It's janky to have to use the back button after changing the number per page larger, and it goes away. No one wants janky. :) -- "All of the people in my building are insane. The guy above me designs synthetic hairballs for ceramic cats. The lady across the hall tried to rob a department store... with a pricing gun... She said, "Give me all of the money in the vault, or I'm marking down everything in the store..." Have a great day and don't forget to laugh! http://www.gcfl.net (The Good, Clean Funnies List): Good, clean daily funnies you can safely tell your Mom!

6 months

[MM3-users] Re: Subscription issue with ghost confirmations

by Brian Carpenter

On 10/31/20 10:28 AM, Brian Carpenter wrote: > Hi Mark, > > This has occurred again. A person sends an email to listname-subscribe@listdomain and the subscription policy of said list is set to moderate only. Instead of honoring this, a confirmation email is sent out. Now the email address that made this request does not show up at all in any of my logs. There is no record of them making a previous subscription attempt before the subscription policy was changed to moderate. Here are some observations: > > 1. The two occurrences of this happening was to Gmail users. > 2. The two occurrences of this happening was when an email is being sent to the listname-subscribe@listdomain address. > 3. This is only happening on 1 list. > > This may have no bearing on the issue but the list address of this problematic list is ******-owners@listdomain. I know there is an alias created for each list that is listname-owner@listdomain. Just throwing that out there. > > <princess-leia-voice>Help me Obi-Wan Sapiro. You are my only hope.</princess-leia-voice> > _______________________________________________ > 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/ So I confirmed this happening on another MM3 server. Setting a subscription policy to open/moderate and sending an email to listname-subscribe@listdomain from an email address that has no previous interaction with the MM3 server results in a confirmation email being sent out. So the question now is: Is this a bug? Or an intentional design? -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 10 months

[MM3-users] Re: Strange messages after upgrading Mailman3

by Allan Hansen

Thank you, Mark, as always. We upgraded to the latest versions: Mailman Core Version GNU Mailman 3.3.7 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.9.2 (default, Feb 28, 2021, 17:03:44) [GCC 10.2.1 20210110] Also, I don't have any umbrella lists. Yours, Allan On 12/4/22, 20:33 , "Mark Sapiro" <mark(a)msapiro.net> wrote: On 12/4/22 20:09, Allan Hansen wrote: > Hi all, > > I have been getting a few of these messages after my Mailman 3 was upgraded: > > "The content of this message was lost. It was probably cross-posted to > multiple lists and previously handled on another list." > > The messages appear to come from list members and are distributed to the relevant lists, but with nothing of the original contents. > They have appeared on different lists with, apparently different senders (unless spoofed). > Other messages are going through the system unchanged. > > Anyone has any ideas? To what version did you upgrade? This is most likely https://gitlab.com/mailman/mailman/-/issues/955 which was fixed in Mailman core 3.3.6, but it could be https://gitlab.com/mailman/mailman/-/issues/1027 if the posts are to umbrella lists (lists with other lists as members). -- 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: mailman-users(a)mailman3.org <https://lists.mailman3.org/archives/list/<a href=>/message/PTXMXLRL4XLU5O7VW6X347FMQ3DLLXIK/">https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to hansen(a)rc.org

3 years, 9 months

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

by IEM Network Operation Center (IOhannes m zmölnig)

thanks both Mark and Odhiambo (who replied off-list) for your answers. On 8/6/24 18:40, Mark Sapiro wrote: > On 8/6/24 01:43, noc(a)iem.at wrote: >> >> 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. > urgh. while this will (hopefully) work with a fresh installation, i'm somewhat afraid whether this will also work for: - migrating a single list from one instance to another (at least, if you (like me) do not have have an intimate knowledge about the db layout) - importing lists into an instance that is already populated with other lists (things like changed db schemas come to my mind) right now my task is to move both some MM3 lists (from an old MM3 instance) and some MM2 lists onto a single server with a fresh installation, so i guess i will be fine. my worries are mostly about future migrations. is a feature-request warranted, or am i worrying too much? gfasmdr IOhannes PS: thanks for finding and fixing the issue with my PGP signature not allowing me to post! ___________________________________________ Die Inhaltsfilterung von Mailman hat die folgenden MIME-Teile aus dieser Nachricht entfernt. Content-Type: application/pgp-keys Name: OpenPGP_0xB65019C47F7A36F8.asc

2 years, 1 month

[MM3-users] Re: Prototype import [was: Re: Setup Question: Disk-Layout (Migrating from Mailman 2.1)]

by Mihai Moldovan

* On 4/20/25 02:26, Mark Sapiro wrote: > This appears to be a bug in mailbox.mbox. To work around it, try this: > ``` > [...] > ``` Thanks, that works! > Those headers are added by the rfc_2369 handler based on the archivers > configured for the list. They will never point to the prototype archiver > or the message in the prototype archive. > > Normally they will point to HyperKitty and to the archived message in > HyperKitty. This is the case even for messages in the prototype archiver > as those messages are just the message as delivered to the list members > absent any personalization. Yes, it iterates through all archivers and gets the permalink and archiver's URL, adding it to the message if the data is non-empty. > Note that the generation of these headers by the rfc_2369 handler > depends on this script being run in an installation that has hyperkitty > and mailman-hyperkitty installed and the hyperkitty archiver enabled for > the list. There is one other thing that caught me off-guard: I had the Hyperkitty archiver enabled, of course, but the service was not running (I essentially turned off everything, including the cron jobs, for the migration, to make sure that no new data is coming in). In order for mailman to query the required data, it has to communicate with the archivers (like Hyperkitty) and that in turn means that the archiver must be running. After starting Hyperkitty, the headers magically gained proper values! Thank you very much for your help. Mihai

1 year, 4 months

[MM3-users] Re: Weblate spanish translation of templates (was: Re: spanish localization)

by Guillermo Hernandez (Oldno7)

On 18/2/21 9:13, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > On 14/2/21 2:42, Abhilash Raj wrote: >> You can actually translate the templates in Weblate too. That is >> actually the whole >> reason to go with monolingual template format in Mailman Core. >> >> Mailman uses the template file's name as the msgid for translations >> and all in-tree >> templates are copied into English's .po file when we re-generate them. >> >> For example in here: >> https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/messages/es/LC… >> >> >> The english .po file is considered as reference in Weblate and used >> for source string. > > I want to contribute making it via Weblate, since it is already done > via gitlab repository (thanks to Mark Sapiro for approving the merge > requests), making a revision and editing them if needed, but I cannot > see how to make it in a consistent way, as I cannot determine how to > edit each template in the Weblate UI. I've tried to access via the > file name (accessing via msgid as for your example) of the > template... but I cannot access them by this way, or I'm missing > something. > > Can you, please, point me in the right direction on how to do it? Forget this, I've just found how to do it. Selecting by "key/context" and the name of the file seems to do the trick. Movin' on Sorry for the noise.

5 years, 6 months

[MM3-users] Re: Whitelist non subscriber

by Mark Ziranski

Hi, thanks for your reply. Can I set the moderation_action on this member? I cannot figure out the API command. All posts of other members should be moderated. POST: http://localhost:8001/3.1/members role=nonmember list_id=something.localhost subscriber=someone@localhost moderation_action=accept Reply: Unexpected parameters: moderation_action Thanks. Gesendet: Donnerstag, 10. August 2017 um 22:05 Uhr Von: "Mark Sapiro" <mark(a)msapiro.net> An: mailman-users(a)mailman3.org Betreff: [MM3-users] Re: Whitelist non subscriber On 08/10/2017 07:12 AM, Mark Ziranski wrote: > > I want to whitelist an email address on all lists to bypass moderation. > The email address is not a subscriber. On google I > found accept_these_nonmembers but I do not know how to use it. > Please show me some examples how to whitelist someone(a)example.org. Since this is a Mailman 3 list, I assume you are asking about MM 3. Mailman 3 defines the list attribute accept_these_nonmembers, but it is not currently implemented to actually have any effect, nor is it exposed in Postorius. At the present, I think you would have to create a user record with the address and add that user to all lists with role nonmember and moderation_action 'defer' to apply subsequent tests or 'accept' to unconditionally accept posts from that address. (In MM 2.1, accept_these_nonmembers is a list of addresses and regexps matching addresses whose posts are to be accepted, subject to subsequent tests, and is exposed in the web admin UI) -- 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 [1]https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org / References 1. https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

9 years, 1 month

Search results for query "sapiro"