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

[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, 5 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, 4 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

1 year, 8 months

[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

11 months, 4 weeks

[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, 1 month

[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/

8 years, 8 months

[MM3-users] Re: migration

by Dave McGuire

On 7/30/21 3:48 PM, Mark Sapiro wrote: >> Is there a way that I can "dump" the configuration from an existing >> mailman3 server, and "import" it into a new instance? I'd really like >> to avoid re-doing all of the configuration, etc, as there are quite a >> few lists and everything is set up pretty much the way I want it. > > If you use the same database manager it should be no problem to get a > dump of the existing Mailman database to load into the new instance, or > if these are on the same server, just point the new instance to the > existing database. In either case, the database should be loaded and the > Django commands `migrate`, collectstatic`, `compress` and > `compilemessages` run[1] before starting Mailman services. Mailman core > will run any necessary updates to its database upon startup. > > You may also need to rebuild the HyperKitty search index with the > `update_index` Django command, but you may be able to use the existing > one if the search engine is the same. > > [1] See > https://docs.mailman3.org/en/latest/install/virtualenv.html?highlight=colle… > et seq. Understood. I am not at all fluent in django interactions (I'm still not entirely sure of what django actually *is*) so I have some reading to do. Any pointers on "django wrangling for n00bs" would be great. As I mentioned, I've not been hacking on mm3, just using it. I'm an accomplished programmer, but embedded C and assembler are a few galaxies away from python and web services! -Dave -- Dave McGuire, AK4HZ New Kensington, PA

4 years, 8 months

[MM3-users] Re: Don't start nntp runner by default - was: Mailman3 doesn't send Mails to users (Debian12 with Plesk)

by Odhiambo Washington

On Fri, May 24, 2024 at 11:25 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/24/24 3:37 PM, admin(a)bclug.ca wrote: > > > > Is nntp common enough these days to be a useful default runner? > > > > I disabled it in mine when I noticed it, but it seems (IMHO) a waste of > > resources (yet another Python interpreter running) for a fairly edge > > case of mailing list <--> nntp transits. > > > You raise an interesting point. By default, the runner runs, but if > there are no lists gating to usenet, its queue is always empty and it > mostly sleeps between waking, finding its queue empty and going back to > sleep. A more significant use of resources is every (default) 5 minutes > spawning `mailman gatenews` which goes through a startup process and > then looks at every list figuring out there's nothing to do. > > We could default mailman.cfg to contain `start: no` in the runner.nntp > section so people would need to enable it if they wanted it. What do > others think? > I last heard of usenet in the late 90's. Do they still exist, even? -- 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: [NON-INTERNAL] Re: Missing Archived emails - Hyperkitty - CERT Issue

by Willie Castillo

Sure. the file was updated and MM3 restarted. Looks like the modification to the /etc/mailman3/mailman-hyperkitty.cfg file did the trick. We are now able to see the July 25th message in the archives. Thank you Odhiambo and Mark for your assistance. ________________________________ From: Odhiambo Washington via Mailman-users <mailman-users(a)mailman3.org> Sent: Tuesday, July 29, 2025 8:54 AM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: [NON-INTERNAL] Re: Missing Archived emails - Hyperkitty - CERT Issue CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. PS: I beg you to put your responses below the last one. Makes the hierarchy look better. Now, have you edited your /etc/mailman3/mailman-hyperkitty.cfg and restarted MM3? On Tue, Jul 29, 2025 at 3:18 PM Willie Castillo < Willie.Castillo(a)caemilusa.com> wrote: > Odhiambo, long time no hear from you. Hope you are doing well. > > The last archived post for that specific list is July 3rd. 2025. We do not > see the one for July 25th. Also, I just noticed something else in the logs, > apparently the server is still having "SSLCertVerificationError" issues > even after updating the DigiCert, CA-Certificate,etc. I must be missing > something else. > > Based on that, looks like the archiving is failing still due to the > "SSLCertVerificationError". > > The spool directory now has 8 *.pck files in it. However, I do not see the > original ones from 7/25 > > ~# ll -t /opt/mailman/mm/var/archives/hyperkitty/spool/ > -rw-rw---- 1 mailman mailman 14725 Jul 29 08:07 > 1753790859.2498085+320096cb9852779b55a4cbb1e4f9603736ebd78d.pck > -rw-rw---- 1 mailman mailman 15122 Jul 29 08:07 > 1753790859.2437658+7fddf881d592f27be60e32aa5b3c34c7077b9988.pck > -rw-rw---- 1 mailman mailman 6399 Jul 29 08:07 > 1753790859.2370558+ee410eb31691bf2854cca46c64e80e3bf61c3523.pck > -rw-rw---- 1 mailman mailman 26619 Jul 29 08:07 > 1753790859.230345+b2e70f5b65900731895bbee5a3d83401f1500567.pck > -rw-rw---- 1 mailman mailman 15676 Jul 29 08:07 > 1753790859.2225533+82371c8a0202d62eaa046dd3633a23d6837d7a80.pck > -rw-rw---- 1 mailman mailman 98273 Jul 29 08:07 > 1753790859.2136636+8ee9273fbbaf4352d482e69d177e2eb2824078a5.pck > -rw-rw---- 1 mailman mailman 98109 Jul 29 08:07 > 1753790859.2026713+49d82ecd57eda7eaa582ba925449e2343bea5c56.pck > -rw-rw---- 1 mailman mailman 88479 Jul 29 08:07 > 1753790859.191489+162aa89dcac50ca6f5463ce1098c828728af12d1.pck > > > > > ------------------------------ > *From:* Odhiambo Washington <odhiambo(a)gmail.com> > *Sent:* Tuesday, July 29, 2025 7:59 AM > *To:* mailman-users(a)mailman3.org <mailman-users(a)mailman3.org>; Mark > Sapiro <mark(a)msapiro.net> > *Cc:* Willie Castillo <Willie.Castillo(a)caemilusa.com> > *Subject:* Re: [MM3-users] Re: [NON-INTERNAL] Re: Missing Archived emails > - Hyperkitty - CERT Issue > > > CAUTION: This email originated from outside of the organization. Do not > click links or open attachments unless you recognize the sender and know > the content is safe. > > > > On Tue, Jul 29, 2025 at 2:25 PM Willie Castillo < > Willie.Castillo(a)caemilusa.com> wrote: > > The issue started right after the site's CERT expired. The CERT expired on > 7/8/25. This is what's in the log... > > Jul 16 15:19:45 2025 (3777209) Connection to HyperKitty failed: > HTTPSConnectionPool(host='XXX.com', port=443): Max retries exceeded with > url: /hyperkitty/api/mailman/urls?mlist=jmats-versions%40XXX.com (Caused by > SSLError(SSLCertVerificatio > nError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: > certificate has expired (_ssl.c:1000)'))) > > The CERT has been updated but the 7/25 message is not archived still. > > > While at it, also edit your /etc/mailman3/mailman-hyperkitty.cfg to what > is documented so that the issue doesn't recur: > ``` > [general] > base_url: https://urldefense.us/v3/__http://127.0.0.1:8000/archives/__;!!E8b8mVbrrfWV… > <https://urldefense.us/v3/__http://127.0.0.1:8000/archives/__;!!E8b8mVbrrfWV…> > api_key: Secret_Hyperkitty_API_Key > ``` > > PS: I haven't seen your responses to @Mark Sapiro <mark(a)msapiro.net>'s > questions quoted below: > ``` > Did the new post get archived? If so, why is last post at still July 25, > 2025? If no, why not. The post must go to the archiver to cause the > queue to be processed. > > If the post was archived and the July 25 messages are still queued, > what's in Mailman's mailman.log. There should be error messages and > tracebacks indicating the issue. > ``` > > -- > 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: > https://urldefense.us/v3/__http://www.catb.org/*esr/faqs/smart-questions.ht… > <https://urldefense.us/v3/__http://www.catb.org/*esr/faqs/smart-questions.ht…> > ] > -- 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: https://urldefense.us/v3/__http://www.catb.org/*esr/faqs/smart-questions.ht… ] _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://urldefense.us/v3/__https://lists.mailman3.org/mailman3/lists/mailma… Archived at: https://urldefense.us/v3/__https://lists.mailman3.org/archives/list/mailman… This message sent to willie.castillo(a)caemilusa.com

8 months, 2 weeks

[MM3-users] Re: Problems after upgrading from bullseye to bookworm

by Eggert Ehmke

Hello Mark, thank you. I did change that entries, and now my mailman runs fine on Debian Bookworm. I did a complete reinstall of the venv directory to have a clean start. Maybe this was not needed. What's missing in the documentation: -the directiories web/logs have to be created manually with the ownership mailman. -The debian package pkg-config must be installed. -the package psycopg2-binary can/must be installed without version restriction on Bookworm Maybe this info helps some other people. Cheers, Eggert Am Montag, 26. Juni 2023, 22:22:37 CEST schrieb Mark Sapiro: > On 6/26/23 12:35 PM, Ken Alker wrote: > > I'm brand new to this, so take this with a grain of sale, but, I had a > > similar problem a few days ago, however, mine was "flufl.i18n>=3.2". > > Perhaps the same thing is happening with flufl.lock (but that didn't bite > > me). > > > > I solved my problem by following this: > > <https://gitlab.com/mailman/mailman/-/issues/1085> and, ultimately > > modifying > > "$VENV_ROOT/lib/$PYVERSION/site-packages/mailman-3.3.8.egg-info/requires. > > txt" per that thread (see > > <https://gitlab.com/mailman/mailman/-/issues/1085#note_1442207929> by > > Thomas Ward section called "The WORKAROUND"). Maybe you need to do the > > same thing, but for flufl.lock. > Yes, the same issue now affects flufl.lock as well as flufl.i18n. You > will need to change both flufl.lock->flufl_lock and flufl.i18n->flufl_i18n. ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

2 years, 9 months

Search results for query "sapiro"