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

[MM3-users] Re: Issues with @gmail.com addresses

by Mark Sapiro

On 9/5/23 12:59, Mohsen Masoudfar wrote: > Hi, > > since 8/1/2023 I get complains from users with @gmail.com addresses, that they are not getting any emails. > I checked the logs and I see that the emails are going out: > > to=<xxxx(a)gmail.com>, relay=email-smtp.us-east-1.amazonaws.com[35.169.171.20]:587, delay=0.46, delays=0.03/0.06/0.13/0.24, dsn=2.0.0, status=sent (250 Ok xxx ) > > But it seems the users are getting email delivered to them. > I’ve advised them to check their spam, promotions, and social folders and to add the list address to their email safe-senders lists, but still no success. > Is there any way to help this list members? Even though gmail publishes a DMARC policy of none, it has recently started enforcing a stricter policy for mail From: the gmail.com domain. You need to apply DMARC mitigations to mail From: the gmail.com domain. There are two ways to do this. One way is to set DMARC Mitigations -> DMARC Mitigate unconditionally to Yes (and set DMARC mitigation action appropriately) The other way requires upgrading Postorius and Mailman core to the heads of the GitLab branches (core=3.3.9b1, postorius=1.3.9b1). Doing this enables a DMARC Addresses setting which can be set to `^.*(a)gmail\.com$` to apply DMARC mitigatations to mail From: the gmail.com domain regardless of it's published policy. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[MM3-users] Re: Handling of Mail from non-subscribers

by Mark Sapiro

On 5/8/20 5:32 PM, Peter Adebahr via Mailman-users wrote: > > May 09 01:22:38 2020 (1235) SHUNTING: 1588980158.3151...... > > But immediately before I find the "module 'time' has no attribute > 'clock'" which I remember from a thread a couple of days ago, though I > cannot remember a solution when mm3 has not been installed from source > but via apt-get. > > My core is V 3.2.2, core python 3.8.2, by the way. That is exactly the issue. Mailman 3.2.2 is not compatible with Python 3.8. This is a Debian/Ubuntu packaging bug. What has happened is the post encountered the exception shown in the Traceback that preceded the SHUNTING message and the message that triggered the exception was placed in the shunt queue. The thread you remember is <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> The fix is to patch your Mailman installation with the changes at <https://gitlab.com/mailman/mailman/-/merge_requests/552/diffs?commit_id=ea0…>. Or, at the very least change x = random.random() + right_now % 1.0 + time.clock() % 1.0 to x = random.random() + right_now % 1.0 + time.process_time() % 1.0 in mailman/utilities/uid.py. After doing that and restarting Mailman core you can do `mailman unshunt` to reprocess the message or if you prefer, `mailman unshunt --discard` (or just remove it from the shunt queue) to discard it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 3 months

[MM3-users] Re: Moderation not working?

by Mark Sapiro

On 11/24/20 12:30 PM, peter(a)chubb.wattle.id.au wrote: > > Hi Folks, > Running a shiny new instance of mailman3, as per the Debian package > (version 3.2.2) but the moderation doesn't seem to work. WE got > hit by a heap of spammers overnight, even though the 'hold for > moderation' bit is set for non-members (and now for members too). If the action for member posts was accept ot default processing at the time, perhaps the spam spoofed a member address in one of From:, Reply-To:, Sender: or the envelope sender, > Emails seem just to get straight through. Even now with both member and non-member actions set to hold? > Any advice on how to debug this? Would upgrading to a later version > using pip help? An upgrade probably won't help. This should work in your version. For one of the mail's, check all 4 addresses, From:, Reply-To:, Sender: and the envelope sender (available in the MTA logs). Note that Reply-To: and/or Sender: may have been modified by the list. Then see if any of those addresses matches a member or a non-member and what the specific moderation action is for that address. Also check the list's accept_these_nonmembers which is probably not exposed in your version of Postorius but which you can see via `mailman shell`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

[MM3-users] Re: Header Filter madness

by Brian Carpenter

On 1/13/21 3:05 PM, Mark Sapiro wrote: > On 1/12/21 9:57 PM, Mark Sapiro wrote: >> On 1/11/21 6:14 PM, Brian Carpenter wrote: >>> On 1/11/21 8:48 PM, Mark Sapiro wrote: >>>> On January 11, 2021 5:50:04 PM MST, Brian Carpenter >>>> <brian_carpenter(a)emwd.com> wrote: >>>>> I have a client whose header filters seemed to have stop working. No >>>>> matter what I try, it seems none of their header filters are being >>>>> applied. Other lists on the same server that use header filters, are >>>>> working fine. This particular header is the subject header. I can >>>>> duplicate their problem but only with their list. If I create the exact >>>>> same header on a test list using the exact same subject line, the >>>>> header >>>>> filter does its job (moderate). Just not with this one list. >> >> What's in the X-Mailman-Rule-* headers of the post that should be but >> isn't held? >> >> Are there other header filter rules besides the one that doesn't work? > Also, on your test list, did you copy/paste the regexp or retype it. If > the latter, there is possibly trailing whitespace that breaks it. Thanks Mark. I am currently waiting for feedback from my client. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 7 months

[MM3-users] Re: Subscription request cannot be moderated: 404 Not Found

by Mark Sapiro

On 1/16/21 9:46 AM, Eric Broens via Mailman-users wrote: > Hi Mark, > Unfortunately the provided options didn't work out either: > > 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. > The variable 'm' is the ************* mailing list >>>> ISubscriptionManager(m).confirm('4d6b4b11266c7332684c5a492eb3f92c531f761b') > Traceback (most recent call last): > File "<console>", line 1, in <module> > File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/subscriptions.py", line 578, in confirm > workflow.restore() > File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman/app/workflow.py", line 142, in restore > raise LookupError(self.token) > LookupError: 4d6b4b11266c7332684c5a492eb3f92c531f761b It appears that although the token was in the pended table, it wasn't in the workflowstate table. I have no clue how this happened. > I noticed that the mail address was also listed as a non-member. > After deleting it there, I could not accept the subscription either. > Next, I have rejected the subscription and added it using the mass subscription option in the WebUI. > > I'll monitor if such cases will happen again. Hopefully it won't happen again, but at least you have a workaround. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

[MM3-users] Re: Mailman3 is wrongly display name a list member

by Mark Sapiro

On 1/11/22 9:24 AM, Allan Hansen wrote: > Thank youi, Stephen. > > Oops. When I wrote below that I set the name 'B' in the account, I did describe it wrongly. Sorry. > The member just wants one name, 'A' for all her subsriptions. Somehow the 'B' got into the system when we upgraded from Mailman 2 to Mailman 3. > > I removed the address from all the lists, set the account display name to 'A' in Django, verified that she was not subscribed to any list at all, and then resubscribed her again as 'A'. In other words, no 'B' anywhere - straight 'A's. > Nevertheless, the new subscriptions still show up as 'B'. A user has a user record and one or more address records. Each of these has a display name. Removing users from lists does not remove these records. If you have recent Postorius, you should have a `users` item at the top of Postorius pages. Go there, find the user and click "Manage". You can change Display Name there. Otherwise, in `mailman shell` for example ``` >>> usr = getUtility(IUserManager).get_user('user(a)example.com') >>> usr.display_name = 'First Last' >>> for adr in usr.addresses: ... adr.display_name = 'First Last' ... >>> commit() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

[MM3-users] Re: A few more MM3 questions

by Mark Sapiro

On 5/29/24 9:48 AM, Marc SCHAEFER wrote: > > May I just modify those files, and is there any way to see, in the web GUI, > where those files are referenced? Yes, you may modify them. The search algorithm for templates is described at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/i18n… however, this is only for templates which have no entry or a mailman:/// entry in the template table in the database. Also see https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… > In the database itself, the template table is empty (as seen in the GUI) and I > did not see the text "web_page_url" in a dump of the database, so I have some > issues to understand how this is used by Mailman (except direct file access > to /var/lib/mailman3/templates?) It is by direct access following the search algorithm. If you are looking at templates in Postorius, these can be created and will place the template in the postorius_emailtemplate table in the database and an entry in the templates table with a URI beginning with the POSTORIUS_TEMPLATE_BASE_URL setting to retrieve the template via the Postorius API. The Postorius template UI should show the current value for a template not yet set in Postorius, but it doesn't. See https://gitlab.com/mailman/postorius/-/issues/366. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: Cannot Run Web Frontend

by Mark Sapiro

On 12/23/25 10:18, dap1--- via Mailman-users wrote: > I'm having trouble getting my web frontend working. When I try to access http://localhost/mailman3 I get a 503 error and the following in the apache2 error.log: > > [Tue Dec 23 13:08:41.584412 2025] [proxy:error] [pid 132768] (111)Connection refused: AH00957: http: attempt to connect to 127.0.0.1:8000 (127.0.0.1:8000) failed > [Tue Dec 23 13:08:41.584578 2025] [proxy_http:error] [pid 132768] [client 2600:1700:5cac:4600:fc36:9a27:6e66:44b:49658] AH01114: HTTP: failed to make connection to backend: 127.0.0.1 Is mailman-web running? If so, what is the content of /etc/mailman3/uwsgi.ini if you are using uwsgi or /etc/mailman3/gunicorn.conf if you are using gunicorn? What do you get from `http://127.0.0.1:8000/mailman3`? > This is the relevant part of apache2's 000-default.conf: > > <IfModule mod_proxy.c> > ProxyPreserveHost On > ProxyPass "/mailman3" "http://127.0.0.1:8000/mailman3" > ProxyPass "/archives" "http://127.0.0.1:8000/archives" > ProxyPass "/accounts" "http://127.0.0.1:8000/accounts" > ProxyPass "/admin" "http://127.0.0.1:8000/admin" > ProxyPass "/user-profile" "http://127.0.0.1:8000/user-profile" > </IfModule> > > What is a bit confusing but probably unrelated is this is in the virtual section for port 80 rather than port 443. I don't see any errors anywhere else. It needs to be there to support http://localhost/mailman3, but for https://localhost/mailman3, it needs to be in the port 443 section. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months, 4 weeks

[MM3-users] Re: Missing bits of French translation

by Mark Sapiro

On 5/12/26 17:30, iMark wrote: > > 3. Page text fails. eg. > ENGLISH: You have to sign in to visit the archives of this list. > FRENCH: Is in English. > > Looking at the .po file ... > > /opt/mailman/venv/lib/python3.11/site-packages/mailman/messages/fr/LC_MESSAGES/mailman.po > > "PO-Revision-Date: 2024-06-25 17:09+0000\n" That file is out of date. It may or may not be from the latest Postorius released version but it has been subsequently updated for the next release. That particular string is marked fuzzy in the current .po - see <https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/locale/fr/…> It is marked fuzzy because the msgid was changed at some point from ``` msgid "You have to login to visit the archives of this list." ``` to ``` msgid "You have to sign in to visit the archives of this list." ``` The translations are managed at Weblate. The particular French translation for Postorius is at <https://hosted.weblate.org/projects/gnu-mailman/postorius/fr/>. The above string is one of 19 that are marked for edit. You are more than welcome to create an account at Weblate and fix whatever needs fixing in the French translation and Weblate will submit a merge request to update the .po on GitLab. We would be grateful for your help. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 1 week

[MM3-users] Re: 500 error on Held Messages page

by Mark Sapiro

On 9/20/22 19:54, Dan Caballero wrote: > I'm getting an unexpected error when I try to clear all the held messages. Any ideas what could be wrong here? > ``` > (mailmanve) mailman@11f52637274a:/var/www/mailman-www$ mailman shell -l jewishlife(a)caltech.edu > 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. > The variable 'm' is the jewishlife(a)caltech.edu mailing list >>>> from mailman.app.moderator import handle_message >>>> requestdb = IListRequests(m) >>>> for req in requestdb.held_requests: > ... if req.request_type == RequestType.held_message: > ... handle_message(m, req.id, Action.discard) > ... > Traceback (most recent call last): > File "<console>", line 3, in <module> > File "/opt/mailmanve/lib/python3.9/site-packages/mailman/app/moderator.py", line 112, in handle_message > key, msgdata = requestdb.get_request(id) > TypeError: cannot unpack non-iterable NoneType object ``` There is a corrupt request with a request id that doesn't exist. Try something like: ``` >>> from mailman.interfaces. >>> requestdb = IListRequests(m) >>> for req in requestdb.held_requests: ... if req.request_type == RequestType.held_message: ... if not requestdb.get_request(req.id): ... print(f'Bad request id: {req.id}, deleting') ... requestdb.delete_request(req.id) ... ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

Search results for query "sapiro"