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

[MM3-users] Re: How to disable the password reset email, from being sent to an address not in our database?

by Mark Sapiro

On 11/26/25 11:21 AM, mrl(a)psfc.mit.edu wrote: > Hi - Someone just requested a password reset, for an email address not in the mailman database. Mailman sent a message to them, but the email was invalid. I would like to disable an email from being sent to a user not in the mailman database. How to do this? Thanks. - Mark There are Mailman users and Django users. Mailman users are people known to Mailman as members, nonmembers, moderators or owners of lists. Django users are people who've signed up for web accounts. Django users don't have to be Mailman users and vice versa. You can prevent Django-allauth from sending mail to unknown Django accounts with the ACCOUNT_EMAIL_UNKNOWN_ACCOUNTS setting - see https://docs.allauth.org/en/latest/account/configuration.html#sending-email Also, there is an example script at https://www.msapiro.net/scripts/clean_users.py that can be used to remove Django users for which there is no corresponding Mailman user. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months

[MM3-users] Re: Postorius performance with over 1000 pending users

by Mark Sapiro

On 6/8/19 9:13 AM, Nick W wrote: > I've got a couple things I need help with: The Symptom and The Problem. > > The Symptom: > > Postorius has gotten quite slow to load, taking more than 30s to load the > Subscription Requests tab. Having zero pending subscription requests (I'm on > v1.2.5), I started investigating unconfirmed subscriptions. > > I followed the commands from here[1] and got this: > > mailman shell -l your.list.id > util = getUtility(IPendings) > print(len(list(util.find(mlist=m,pend_type='subscription')))) > 1816 > > Wow, 1816 pending subscription requests. I can say for certain that my list is > not popular so these requests must have been submitted by bots. Let's get there > in The Problem. > > How can I "purge" this list? I'm willing to assume that none of these requests > are valid and would reject all unconfirmed user requests. mailman shell -l your.list.id util = getUtility(IPendings) for token, data in util.find(mlist=m, pend_type='subscription'): util.confirm(token, expunge=True) -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 8 months

[MM3-users] Re: Wrong info in moderation mail when held due to match of a header rule

by Mark Sapiro

On 10/17/20 1:31 PM, tlhackque via Mailman-users wrote: > > I might also add the rule number or config filename:line, as in > > Header "{name}": rule in {file}:{n} matched value "{value}" > > This would be helpful when backtracking from a rejected message to the > cause. > > A sample expansion might be: > > Header "X-Spam": rule in foo.conf:83 matched value "yes" These rules are not in a configuration file. They are in the headermatch table in the database and the rules for a particular list are exposed on the Header filters tab in Postorius or at the REST lists/LISTNAME/header-matches endpoint. Perhaps something like {name}: header match rule, pattern "{pattern}" matched value "{value}" example: subject: header match rule, pattern "sex|long|list|of|other|bad|words" matched value "This is a post about filtering based on words like sex in the subject." but that could be just adding more clutter. -- 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

[MM3-users] Re: List is down - RemovedInDjango30Warning

by Mark Sapiro

On 2/15/21 9:07 PM, Mark Dadgar wrote: > So I did the latest mailman upgrades within my venv (per the instructions got from Brian Carpenter when he installed it for me) to the latest version. I had a strange CPU pegging issue that turned out to be mailman struggling with a malformed message but in the process of debugging that I downgraded to the previous mailman release. > > The resulted in a broken web interface. > > Today, while debugging, I did a pip install --upgrade of all the components as listed in a previous thread. Now none of the mailman3 processes will start. > > Doing a bin/mailman-post-update results in the error message below, which are consistent with the issues I saw earlier when trying to access the web interface. > > Anyone got a solution to this? From the tracebacks it looks like Django is broken. I would suggest starting over with a new venv. I.e., just move /opt/mailman/mm/venv/ aside and create a new venv virtualenv /opt/mailman/mm/venv/ and then activate it and pip install everything. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: Permission denied for fulltext_index

by Mark Sapiro

On 11/27/22 00:35, Jan Eden via Mailman-users wrote: > > – but the existing directory /opt/mailman/fulltext_index (and its > contents) are readable and writeable by mailman:mailman: > >> drwxrwxr-x 2 mailman mailman 4096 Nov 27 08:00 fulltext_index/ >> >> -rw-rw-r-- 1 mailman mailman 4473 Nov 27 08:00 _MAIN_65.toc >> -rw-rw-r-- 1 mailman mailman 15456 Nov 27 08:00 MAIN_bc0cs2aohovftat6.seg >> -rw-rw-r-- 1 mailman mailman 15454 Nov 27 06:00 MAIN_brbo8i8edmlz0za4.seg >> -rw-rw-r-- 1 mailman mailman 15462 Nov 27 07:00 MAIN_ewnemc7lsnodd3y7.seg >> -rw-rw-r-- 1 mailman mailman 157324 Nov 27 04:00 MAIN_qag60g1rrumshtc2.seg >> -rw-rw-r-- 1 mailman mailman 15459 Nov 27 05:00 MAIN_w6e0ohurasusy61d.seg >> -rwxrwxr-x 1 mailman mailman 0 Nov 24 16:00 MAIN_WRITELOCK* > > I fail to see where haystack tries (and fails) to create the directory. > FWIW, deleting threads is not a problem. It is uwsgi trying to do this. What user is it running as? Maybe you need to add that user to the `mailman` group. Deleting threads is not an issue, apparently because it doesn't try to update the search index. -- 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: SMTPSenderRefused - howto enable STARTTLS for local mail drop

by Mark Sapiro

On 12/6/21 2:51 AM, Stefan Bauer wrote: > Need to bring this up again. Django now sends with STARTTLS, but mailman > itself, does still only drop mails in cleartext. > Dec 6 11:47:33 al01 postfix/lmtp[7598]: A6422600510: > to=<remote-party@remote>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.01, > delays=0.01/0/0/0.01, dsn=2.0.0, status=sent (250 Ok) > Dec 6 11:47:33 al01 postfix/qmgr[29156]: A6422600510: removed > Dec 6 11:47:35 al01 postfix/smtpd[8092]: disconnect from localhost[::1] > ehlo=1 mail=2 rcpt=2 data=2 commands=7 > > No starttls=1 at all :( > > Does the above settings work for anyone? > > etc/mailman3/mailman.cfg > [mta] > incoming: mailman.mta.postfix.LMTP > outgoing: mailman.mta.deliver.deliver > > smtp_host: localhost > smtp_port: 25 > smtp_user: > smtp_pass: > smtp_verify_hostname: false > smtp_verify_cert: false > smtp_secure_mode: starttls This should work. What do you see in Mailman's smtp.log if you add ``` [logging.smtp] level: debug ``` to mailman.cfg. However, do you really need this. It will only affect delivery from Mailman to Postfix via the loopback interface on the localhost. -- 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: Poor rendering of disabled registration page

by Mark Sapiro

On 12/22/24 04:16, Torge Riedel via Mailman-users wrote: > > 1. The page has a poor rendering, as far as I can see not css is referenced > 2. A would prefer that I am able to hide the registration button > > Is either of this possible to be fixed in the future? The lack of styling is fixed for django-mailman3 1.3.16 by https://gitlab.com/mailman/django-mailman3/-/merge_requests/303 You can fix it by adding the django_mailman3/templates/account/signup_closed.html file as in this patch: ``` diff --git a/django_mailman3/templates/account/signup_closed.html b/django_mailman3/templates/account/signup_closed.html new file mode 100644 index 0000000..bc83950 --- /dev/null +++ b/django_mailman3/templates/account/signup_closed.html @@ -0,0 +1,11 @@ +{% extends "account/base.html" %} + +{% load i18n %} + +{% block head_title %}{% trans "Sign Up Closed" %}{% endblock %} + +{% block content %} +<h1>{% trans "Sign Up Closed" %}</h1> + +<p>{% trans "We are sorry, but the sign up is currently closed." %}</p> +{% endblock %} ``` Disabling the signup button on the resultant page is trickier as that currently comes from the hyperkitty/templates/hyperkitty/base.html which is used all over. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 2 months

[MM3-users] Re: Cannot request password reset: "The e-mail address is not assigned to any user account"

by Mark Sapiro

On 1/26/22 22:21, dave--- via Mailman-users wrote: > > Using the web API, I have created several mailing lists and I have added members to these lists also using the web API (most relevant: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…) specifying that each member is already pre_verified, pre_confirmed, and pre_approved. The lists themselves seem to be working fine. > > The problem is when our staff try to reset their password (through Postorious) to get access and do moderation tasks. The error message "The e-mail address is not assigned to any user account" displays no matter which email address I enter (except the one from MAILMAN_ADMIN_USER which works). The password reset is for a Django user, which is distinct from a Mailman user. The users you added via the web API are Mailman users, but in order to access their lists via the web UI they have to `sign up` to create a Django account. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

[MM3-users] Re: Mails sent by mailman-web runjobs hourly

by Mark Sapiro

On 6/16/22 03:44, Eggert Ehmke wrote: > I get lots of mails originating from the mailman-web runjobs hourly. They are > sent to mailman@<mytld>. The content looks like > > 07:00:03 [Q] INFO Enqueued 12571 > 07:00:03 [Q] INFO Enqueued 12572 > 07:00:03 [Q] INFO Enqueued 12573 > > How can I disable these emails? These message come from Django Q, https://django-q.readthedocs.io/en/latest/ I don't think there is a way to disable those specific messages which occur at times when tasks are queued instead of started immediately. They are sent to `mailman` because `mailman` owns the crontab and the crontab has no MAILTO=. You can redirect these and all other messages from hourly jobs by surrounding the hourly jobs command in the crontab with MAILTO= as in ``` MAILTO=other(a)example.com @hourly /opt/mailman/mm/bin/django-admin runjobs hourly MAILTO=mailman ``` or possibly discard them with something like ``` @hourly /opt/mailman/mm/bin/django-admin runjobs hourly > /dev/null ``` but either of these could redirect or discard other messages from hourly jobs which you might want. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

[MM3-users] Re: Expire non-members

by Mark Sapiro

On 2/8/26 18:36, John Price wrote: > I notice that a lot of the non-members (I didn't look at all ~230) don't > seem to be in the master user list. Maybe until they confirm the user > record is not created yet? If the address was just added from a nonmember post, it won't have a user record. As I said before, there is no pending confirmation for the nonmember. The address has been added as a nonmember and that's it. They won't be added as a member unless they request subscription at which point they will have to confirm if the list's subscription policy requires it. > Anyway, I'd love a subscribe timestamp so I could calculate how long it > has been, but I can rig something up with a daily cron job and a simple > DB of emails and the date it noticed them on the non-members list and > delete them after a few days. Thanks for the info! For the nonmember, nonmember.address.registered_on is probably the timestamp you are looking for. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 weeks, 4 days

Search results for query "sapiro"