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

[MM3-users] Re: If I manually add email addresses to a list and then delete them, how do i permanent delete them from Users?

by Mark Sapiro

On 4/25/23 3:02 AM, Andrew Hodgson wrote: > Mark London wrote: > >> I added some email addresses manually to a mailing list and then removed them. But now I can't find how to totally remove them from mailman3. They show up in the Users list. > > You may find this script useful: > https://www.msapiro.net/scripts/clean_users.py That script will only delete Django users and optionally the Mailman user corresponding to the deleted Django user. I think the OP wants to delete Mailman users that are not members of any lists even if there is no corresponding Django user. That script won't do that. Mailman Users can be deleted from the Postorius Users view, but it's a one at a time process, and there's no indication that the User has memberships unless you first go to `Manage` to check. I will modify the script to enable deleting Mailman users with no memberships even if they aren't Django users and post here when it's done. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

[MM3-users] Re: Domain defaults for new lists

by Mark Sapiro

On 1/29/26 14:04, Peter Chubb via Mailman-users wrote: > > Hi Folks, > Is there a simple way to set up the defaults for any newly created > lists? > We've had a few cases recently where in the time between creating a mass-populated > list and making it private it's been inundated with spam. > > I'd like to change the defaults so newly-created lists are private and have > private archives, new members are moderated, etc., to give time for > the list to be set up completely before announcing it to the world. Actually, I think the 'private-default' list style does almost all you want except for new members moderated. https://gitlab.com/mailman/mailman/-/issues/871 asks for that to be changed, however the 'private-default' list style sets the subscription policy to confirm then moderate so spammers can't subscribe and post without their subscriptions being approved by a moderator. You can implement a new list style to do exactly what you want. See https://gitlab.com/mailman/example-mailman-plugin for information about implementing a plugin to do that. Also see https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/styles/doc… for general information on list styles. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 3 weeks

[MM3-users] Re: List nonmembers

by Mark Sapiro

On 7/8/19 6:50 PM, Andrew Bernard wrote: > Under Users for a list, there is a category for List nonmembers. What does this term mean? [It's rather curious philosophically when you think about it, because I would have thought that the category [all humans - list members] fits that category term.] > > But seriously, I don't understand it. I have several email addresses there and I don't know what do with them, if anything. Non-members are email addresses that are not members but have some connection to a list. Mailman 2.1 lists have attributes named accept_these_nonmembers, hold_these_nonmembers, reject_these_nonmembers and discard_these_nonmembers. These are lists of non-member addresses and regexps matching addresses, and posts from a non-member address in one of the lists will be accepted, held, rejected or discarded respectively. Mailman 3 does this differently. An address can be a non-member and that non-member record has a moderation setting to determine how a post from that non-member is handled. An address can become a non-member by being imported from Mailman 2.1 or by posting to the list. If a non-member posts to the list, a non-member record is created regardless of the disposition of the post. See <https://mailman.readthedocs.io/en/latest/src/mailman/chains/docs/moderation…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 11 months

[MM3-users] Re: Strange password problem

by Mark Sapiro

On 9/22/23 09:50, Eggert Ehmke via Mailman-users wrote: > > -I try to log in as admin > -rejected because of wrong password (password is stored in browser) > -used forgotten password function, using my email address > -reset password to the stored value from browser > -login works now. Works also when logged out/in again > -however, the next day this behaviour repeats. So apparently the issue is that although you reset your login password to a known value, it doesn't stick and reverts overnight to some other value. > Can we try to catch this bug now, which is most likely in my configuration? Which is: > > Debian 12.1 Bookworm > Mailman in venv running with dedicated mailman user Is this the Debian package or installed following https://docs.mailman3.org/en/latest/install/virtualenv.html or something else. All I can think of is some cron may be resetting the password. If that's it, it's probably a Debian thing. Can you see if there's any cron running the Django admin changepassword command? If you set the password with the Django admin changepassword command, does it stick? Can you create another superuser with the Django admin createsuperuser command and does that user's password stick? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

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

by Mark Sapiro

On March 27, 2026 4:15:00 AM GMT+09:00, MegaBrutal wrote: > >OK, well, would be convenient to use my native language, but many templates >have no translation. This is an empty file: > ... >As a matter of fact, most of my templates are empty! > ... >I don't see why it's packaged like this – I know that translations don't >come easy. I picked up the maintenance of the SMF forum engine's >translations, and it's brutal how many hours it took to get it to a decent >state. However, Mailman could use English as a fallback for missing >translations; getting the notifications in English is still better than >getting empty messages which is confusing. Translations are done on weblate <https://hosted.weblate.org/projects/gnu-mailman/mailman/>. We would welcome your contribution. A non-existent template will fall back to English, but an empty template will not. That said, the issue is related to how the templates are handled by weblate. Instead of having a msgid of the English template content with a msgstr of the translation, the msgid is just the template name, and the POT contains that msgid and an empty msgstr which results in an empty template rather than a missing template. -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

2 months, 3 weeks

[MM3-users] Re: Solved Re: after last upgrade I've got a CSRF failed verification

by Mark Sapiro

On 10/27/22 03:04, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > Since I made all the mailman3 enviroment wide server open (not using > venv) I already executed the migration doing a > > su -m mailman3 -c "python3 manage.py collectstatic" > su -m mailman3 -c "python3 manage.py migrate" > > Being mailman3 the user who runs all of mailman3 related stuff > > I had problems doing the migrate part, showing an error of lacking > perms. I solved it running the migration under root (I know it could be > trouble after, but...) It would be much better to identify the problem files/directories and adjust their ownership. It is possible that running stuff as root in the past left things owned by root causing the issue. > > After that the compress part showed errors... but the postorius web > maintenance was working well except for the CSRF error verification. I > will trace the compress errors and will try to find the problem later. Do you have `COMPRESS_ENABLED = True` in your settings? If that's not the issue, it may be in the settings for COMPRESS_PRECOMPILERS -- 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: Debian Package Install - Ownership and Permissions

by Mark Sapiro

On 4/7/23 14:58, Dave Hall via Mailman-users wrote: > On Fri, Apr 7, 2023 at 5:47 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 4/7/23 13:43, Odhiambo Washington wrote: >>> On Fri, Apr 7, 2023 at 8:09 PM Andreas Schamanek < >>> as2020+github(a)fam.tuwien.ac.at> wrote: >>>> >>>> I am running MM2 und 3 in parallel without problems, I do have a >>>> special MTA setup though (Sendmail). Can't speak for Postfix etc.. >>>> >>> >>> Your setup can handle list1(a)domain1.name via MM2 and MM3, >> simultaneously, >>> right? :-) >> >> It is possible to have an MM2 `list1` and an MM3 `list1(a)domain1.name` >> simultaneously on the same server, but what is the MTA going to do with >> incoming mail to `list1(a)domain1.name`. I suppose it could deliver it to >> both MM2 and MM3, but I don't see any practical use case for this. >> >> I run Exim4 on my servers so I can comment from this perspective. Exim > had a concept of 'routers' which are stacked and processed in order of > appearance. There is a router for MM2 and one for MM3 that pick off > incoming mail based on whether the email address matches a list name. WIth > this setup, you could have the same list name in both MM2 and MM3, but it > would go to whichever router appears first and the second one would never > see it. So I have the MM3 router first, and as I migrate my lists from > MM3 the email for those lists no longer gets to MM2. And mail.python.org which currently has 189 Mailman 3 lists and 223 Mailman 2.1 lists does something very similar in it's Postfix configuration and also prefers Mailman 3. However, maybe I misunderstood Odiambo's question about simultaneous support for a Mailman 2.1 and Mailman 3 list of the same name. We could certainly have that on mail.python.org, and even have both MM 2.1 and MM 3 web UIs for those lists, but as soon as the MM 3 list is created during migration, mail is only delivered to the MM 3 list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

[MM3-users] Re: Starting from scratch

by Mark Sapiro

On 04/09/2018 10:01 AM, Benjamin Ragheb wrote: > > The two alternatives I am weighing right now are: > > 1. Stay the course, and see if I can fix this by learning more about Python, Pip, Django and tinkering with the configuration. > > 2. Ride the bleeding edge, and install postorius and hyperkitty from git. (I'll probably stick with Mailman Core from Pip, since that seemed to work just fine.) > > Right now I'm leaning toward #2, because it means I'll be in a better position to patch things if I need to, and it seems like Mailman 3 is still rough enough that I will need to. Also, it looks like the master branches of both postorius and hyperkitty are now Python 3 compatible, which could save me from managing two different versions of Python. > > Which is the least crazy option? If you are comfortable with 2), I think that's the better option. After PyCon in May when we release 3.2 and the rest of the suite, you should be able to install everything with pip and have it work. I'm not sure what the issues are now with a pip install. There is a 3rd option. See <https://packages.debian.org/stretch-backports/mailman3-full> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 2 months

[MM3-users] Re: Rerun emails in the queue/bad

by Mark Sapiro

On 11/20/18 8:20 AM, Kaleb White wrote: > How do I run the emails in the queue/bad again? I need to see why the failed and get them to work. Thanks. There should be error messages in the 'mailman' log for each preserved file. These would be like 'Skipping and preserving unparseable message: ....psv' 'Unpickling .bak exception: <error msg> Preserving file: ....psv' '.bak file max count, preserving file: ....psv' The first of these indicates an error in retrieving the message from it's original queue. The others have to do with how message loss is avoided. When a .pck file in a queue is processed, it is read and renamed to a .bak. Then if processing is interrupted by a crash, upon restart the .bak file will be processed. The second error above indicates a problem in unpickling the .bak and the third says the same .bak has already been tried too many times. You may be able to examine the files by pointing 'mailman qfile' at them. If that fails, either 'cat' or 'strings' may produce something useful. If they appear to be good, you can reprocess them by renaming to .pck, moving to queue/shunt and running 'mailman unshunt'. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 7 months

[MM3-users] Re: translating templates (was: Re: spanish localization)

by Mark Sapiro

On 2/16/21 2:59 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > /usr/local/lib/python3.7/site-packages/mailman # ls templates/es > domain:admin:notice:new-list.txt list:member:regular:header.txt > help.txt list:user:action:invite.txt > list:admin:action:post.txt list:user:action:subscribe.txt > list:admin:action:subscribe.txt list:user:action:unsubscribe.txt > list:admin:action:unsubscribe.txt list:user:notice:goodbye.txt > list:admin:notice:disable.txt list:user:notice:hold.txt > list:admin:notice:removal.txt list:user:notice:no-more-today.txt > list:admin:notice:subscribe.txt list:user:notice:post.txt > list:admin:notice:unrecognized.txt list:user:notice:probe.txt > list:admin:notice:unsubscribe.txt list:user:notice:refuse.txt > list:member:digest:header.txt list:user:notice:rejected.txt > list:member:digest:masthead.txt list:user:notice:warning.txt > list:member:generic:footer.txt list:user:notice:welcome.txt > > But mailman isn't aware of them (I restarted the server). May I have to > execute some process as "compilemessages" to mailman be capable to use > them? Now mailman is using the "en" templates for sure. Does Mailman have permission to search the templates/es directory and read the templates? Are there overriding templates in Mailman's var/templates/ directory? Are you sure your tests access the templates in a Spanish language context? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

Search results for query "sapiro"