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

[MM3-users] Re: Mailman3 reinstall fail, need some help

by Yvan ♞

Finally succeed to reinstall with a very precious help !!! /etc/mailman3 folder was removed before the mailman3 package was supressed, apt noticed it and he believed that it was a modification of the configuration of mailman that was wanted, so each time the debian mailman3 package was reinstalled, he did not put the conf in /etc/mailman3, which caused the package installation to crash, and therefore the app install on ynh Le 03/04/2022 à 12:53, Odhiambo Washington a écrit : > On Sun, Apr 3, 2022 at 12:06 PM Yvan ♞<elemac(a)free.fr> wrote: > >> Hello every body >> I have progress to try to reinstall mailman3 on yunohost server but I >> still have an error, if somebody can help me as I don't understand the log >> https://paste.yunohost.org/raw/ugijepuyuv >> Sincerely. >> Yvan >> > Hi Yvan, > > As previously advised by Mark Sapiro, you are better off taking to the > YunoHost support people for help. > They will most likely help you with the failing dependencies issue. > > But I also wonder - why don't you follow the virtualenv method to install? >

4 years, 4 months

[MM3-users] Re: Postfix SMTP REJECT non-subscribers

by Matthew Blissett

On 11/07/2024 04:11, Mark Sapiro wrote: > On 7/10/24 12:26 AM, Matthew Blissett via Mailman-users wrote: >> >> With Mailman 2, I have configuration and scripts to reject >> non-members from posting to lists _during the SMTP connection_. This >> is better than bouncing (no backscatter), better than discarding >> messages (the user finds out) and better than moderation (spammy >> messages aren't forwarded to external email systems). >> >> >> The configuration and scripts are described here: >> https://code.launchpad.net/~jimpop/mailman/check_subscriber >> >> >> Is anything like this built-in to Mailman 3? I cannot find it in >> Gitlab. > > No. nothing similar is built in to Mailman 3, but it shouldn't be > difficult to implement. It could be done with a milter as in the above > implementation, or it could be done by modifying the _handle_RCPT > function in mailman/runners/lmtp.py to check if the sender is a member > of the recipient list. Thanks. I have implemented it by adapting the Mailman 2 script to use the REST API of Mailman 3: https://gist.github.com/MattBlissett/c1f58dcc182423f48e2305b3d91ea44d -- Matt

2 years, 1 month

[MM3-users] Re: How to Increase outgoing mail volume for Mailman 3

by Mark Dadgar

On Nov 10, 2020, at 1:40 PM, Mark Sapiro <mark(a)msapiro.net> wrote: >> Brian specified: >> >> verp_personalized_deliveries: no >> >> Doesn’t that default back to regular mass delivery, as opposed to individualized VERPed envelopes, which mandates individual deliveries? > > > That depends on the setting of verp_delivery_interval. If > verp_delivery_interval = 1, every message will be VERPed regardless of > verp_personalized_deliveries. If verp_delivery_interval = 0 and > verp_personalized_deliveries = no, deliveries won't be VERPed as you > note. If verp_delivery_interval = 0 and verp_personalized_deliveries = > yes, only personalized deliveries (i.e. individual messages, not > digests, from lists with Personalization enabled) will be VERPed. > > The theory is VERPing has a cost because it requires a separate message > sent to each recipient rather than a single message with multiple > recipients, but personalization also requires a separate message sent to > each recipient, so those can be VERPed at no extra cost. > > But to be clear, automated bounce processing does not require VERP. It > just works a tiny bit more reliably with VERP. Great explanation - thank you. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 9 months

[MM3-users] Re: Howto discard all pending unsubscription requests in a list?

by Andreas Vetter

On Tuesday, 19 May 2026 20:15:47 CEST Mark Sapiro wrote: > On 5/19/26 2:54 AM, Andreas Vetter wrote: > > Is there a script to discard all tose requests and get the members back on > > the list? > > A mailman shell interaction like this should do it. > > $ mailman shell > Welcome to the GNU Mailman shell > Use commit() to commit changes. > Use abort() to discard changes since the last commit. > Exit with ctrl+D does an implicit commit() but exit() does not. > > >>> pendings = getUtility(IPendings) > > >>> for token, data in pendings.find(pend_type='unsubscription'): > ... if data and data['list_id'] == 'the_list.example.com': > ... pendings.confirm(token, expunge=True) > ... > > >>> commit() > > In the above, replace the_list.example.com with the actual list_id (the > list posting address with '@' replaced with '.') > > If there are no other lists with pending unsubscriptions, you can omit > the `and data['list_id'] == 'the_list.example.com'` check. This works like a charm. Thanks a lot, Andreas

2 months, 4 weeks

[MM3-users] Re: Footer from templates not working - DB issue?

by Hans Mayer

Hi Mark, many thanks for this hint. I updated table "template" and replaced "localhost" with the real name and it worked. // Hans -- On 25.09.22 19:28, Mark Sapiro wrote: > On 9/25/22 05:26, mailman--- via Mailman-users wrote: >> Dear All, >> I have a similar issue. Also on Debian 11. Also installed as Debian >> PKG. It's version GNU Mailman 3.3.3 (Tom Sawyer) >> I am using sqlite3. When I do the SQL-query I get an URI which is in >> multiple reasons wrong >> http://localhost/mailman3/postorius/api/templates/list/....../list:member:r… >> > > The initial part of that URL is set from the Django setting > `POSTORIUS_TEMPLATE_BASE_URL`. If that is set to > `http://localhost/mailman3/`, it should probably be just > `http://localhost/`. > > >> OK - the hostname could be changed but the path is not existing at all. >> There is no file "list:member:regular:footer" on the complete >> filesystem. > > It's not a file. It refers to an entry in the postorius_emailtemplate > table in the database which is retrieved via the Postorius API. >

3 years, 10 months

[MM3-users] Re: hyperkitty threads by month question

by Bryan Fields

On 7/9/24 3:39 PM, Mark Sapiro wrote: > See this post and maybe more of that thread which may help. > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… Thanks Mike, I've been looking into this, and I don't think it's that. What I did find is that our mbox from the mailman2 list is actually a amalgamation of mailman2, and majordomo archives. The mbox is not in order, but the start of the mbox starts in 2007 (coinciding with the last displayed month). Later on in the mbox file, the archives going back to 1992 from majordomo are present. There is no errors in the check_hk_import for this, and the messages are present in the index when I search for them and there are no errors during import. mailman 2.1 archives works just fine with this mbox file. Here's a link to the server in question, it's just a text box as we work through this. There's about 14k people on this list, so we want to get it right before cut over. https://nanog-mm3.keekles.org/archives/list/mm2-mm3@nanog-mm3.keekles.org/ Any ideas? -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net

2 years

[MM3-users] Re: Username being set to givenname for socialaccount login

by Andreas Barth

* Mark Sapiro (mark(a)msapiro.net) [210922 20:46]: > On 9/22/21 11:22 AM, cfarley(a)iastate.edu wrote: > >I have a new mailman3 install setup with Okta as a social application. This is working well for logins and data comes through as expected, but for some reason the username is being set at to a lowercase version of the given_name. The Extra data on the social users in the admin interface looks good, so I don’t think it’s a problem with the attributes coming from Okta. > > > >We have tried a number of variations on the below setting, but that all of them other than the default of “username” end up with the username being empty. > >ACCOUNT_USER_MODEL_USERNAME_FIELD = “email” > > > >Any direction would be welcome. > > This is an issue for Django allauth > <https://django-allauth.readthedocs.io/en/latest/index.html>. > Mailman has no control over this. The username is part of Django's > login and is not used by Mailman at all. Does that mean, not having an user name would work for mailman? I always thought having an user name was required Regards, Andi

4 years, 10 months

[MM3-users] Re: Mass subscription: HTTP Error 400: 'pathlib._local.PosixPath' object does not support the context manager protocol

by Stephen J. Turnbull

Flo via Mailman-users writes: > On 6/23/26 4:02 PM, Mark Sapiro wrote: > > On June 23, 2026 2:11:59 AM PDT, Flo via Mailman-users <mailman-users(a)mailman3.org> wrote: > >> HTTP Error 400: 'pathlib._local.PosixPath' object does not support the context manager protocol > > Current Mailman does not support python 3.14. > It looks like I am using Python 3.13.5 . That's consistent with Debian 'trixie', for sure. > Nevertheless I ran into the issue Steve pointed to. Pretty sure this is a known issue with Python 3.13, and Mark mentioned that in the thread I cited. We got two or three of these when Debian promoted 'stable' to 'trixie' because that upgrade promoted Python to 3.13. Dunno if Mark was thinking about a different issue or if it was an off-by-one error, but he's definitely the author of the patch you used! Steve -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

1 month, 3 weeks

[MM3-users] Re: [Mailman-Developers] Mailman 3.1 beta coming soon

by Barry Warsaw

On Dec 09, 2016, at 09:37 AM, Mark Sapiro wrote: >I understand you need to feel comfortable about everything going into >the core and this takes time and energy to review all the MRs, but I >think it is pretty important to get the DMARC mitigations into the core. >If there's anything I can do to help with this, let me know. > >I will rebase my branch again and possibly make one minor tweak, but I >think it should be OK. Thanks for pushing back on this Mark. Obviously, I have a high degree of trust in your work, but yeah, my compulsive behavior is showing through. ;) Please do rebase and if you can, remilestone the MR to 3.1. We'll get it in. >I can also work on Postorius. Also in this vein I have a question. >Should the DMARC settings be added to the Alter Messages tab in the List >Settings view or would it be better to have a separate DMARC Mitigations >tab. My gut reaction is to add a separate DMARC Mitigations tab, but Florian and Terri have final say I think. Cheers, -Barry

9 years, 8 months

[MM3-users] Re: Time Zone Issue in Postorius

by Stephen J. Turnbull

Henrik Rasmussen writes: > > Fra: Mark Sapiro <mark(a)msapiro.net> > > It should be TIME_ZONE = 'UTC' > > > > Times passed from Mailman core are naive times, I.e. they don't have > > time zone info, but they are in UTC. Mark is saying that Mailman core converts to UTC. All times that come out of Mailman core in the relevant API are UTC. > As stackoverflow.com/questions/29311354/how-to-set-the-timezone-in-django > seems to say otherwise ("You can use TIME_ZONE = 'Europe/Istanbul'"), > to make sure, am I right to understand it as for Mailman, Danish time > should be stated as "TIME_ZONE = 'UTC+1' " with use of "USE_TZ = True"? No, USE_TZ=True means "hey Django, you need to add a time zone to this datetime." And you use TIME_ZONE=UTC (exactly), because this variable is *not* the local time zone, it's the time zone that Postorius tells Django to add to datetime objects that don't carry their timezone with them. There is a setting somewhere else that tells Django what time zone should be used for I/O. Steve

4 years, 6 months

Search results for query "sapiro"