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

[MM3-users] Re: DMARC Munging

by Mark Sapiro

On 1/26/20 4:43 PM, Allan Hansen wrote: > All, > > The munged From: header in MM3 still says > 'name' via ‘listname’ <‘listaddress’> > > This caused me and my subscribers a lot of grief in MM2: > Some mail clients use the first part up to the From for future key-ahead for new email to ’name’, hiding the address, so what they think is a personal message for ’name’, instead goes to the entire list. Red faces all around. > > Stephen Thurnbull earlier suggested further munging by replacing the list address in the From: header like this: > > 'name' via ‘listname’ <‘whoopsieaddress’> > > Which will return an automated reply explaining the issue. I like this option. How can I get that in? You can file an issue at <https://gitlab.com/mailman/mailman/issues>. That will at least get it on the table, but there are no guarantees as to if/when it would be implemented. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 6 months

[MM3-users] Re: Apple Mail encoding again

by Mark Sapiro

On 4/21/22 04:53, tlhackque via Mailman-users wrote: > > Note that MailMan is encapsulating a multipart/signed message in a > multipart/mixed in order to append it's footer, and reports that it > removed the signature part of the multipart/signed. This makes the > signed message format invalid. So at least, MM3 needs to handle signed > messages better: either include the signature or remove the signature > headers (an unwrapping exercise to convert the message to unsigned)... > Note that this can be recursive where a signed message contains a > message/rfc822 part that contains a signed message, that.... This was an issue with Mailman's content filtering for the mailmanusers(a)mailman3.org list. Pass types was: multipart message/rfc822 text application/pgp-signature So the application/x-pkcs7-signature part was removed. I have just updated Pass types to: multipart message/rfc822 text application/pgp-signature application/x-pkcs7-signature to not remove application/x-pkcs7-signature parts going forward. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users] Re: Recently active discussions - Hyperkitty

by Mark Sapiro

On 6/3/24 8:55 AM, Sam Darwin wrote: > > Try this: > > systemctl reload mailman3-web > or > systemctl restart mailman3-web > > The "Recently Active Discussions" listing is refreshed! That fixes it. > > --- > > Related issue, #2 > > On the "Recently Active Discussions" page, click on a message, a test message, and then "Delete this thread". It's deleted. > > Now "Recently Active Discussions" hangs. A spinning icon, indefinitely. In the logs file: "hyperkitty.models.thread.Thread.DoesNotExist: Thread matching query does not exist." > Re-running recent_threads_cache, and restarting Django, fixes it. However in production you wouldn't want to wait 24 hrs, and also manually restart the web. As you say, these issues may be related. The latter is already reported at https://gitlab.com/mailman/hyperkitty/-/issues/504 and as it says there, I am unable to duplicate it; it may be related to which database manager you use. -- 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: when on particular person sends a message to the list dozens of OTHER users have their bounce score incremented

by Mark Sapiro

On 8/30/24 14:34, Ken Alker wrote: > I just found and then changed the "Settings/Alter Messages/Replay goes > to list" from "No Munging" to "Reply goes to list" to combat the reply > issue I mentioned above. I suppose this means that if someone sent a > specific Reply-to: in their original email, it gets overwritten. I > suppose there is no perfect solution. If `Reply goes to list` is set to `Reply goes to list`, the list posting address is added to the Reply-To: header. I.e., if there is a Reply-To: in the incoming message, The resultant Reply-To: contains the original plus the list posting address unless `First strip Reply-To` is `Yes` in which case it contains only the list posting address. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

[MM3-users] Re: MM2 to MM3 Archives Loading

by Mark Sapiro

On 12/4/24 12:45, Joshua Bushe wrote: > > This link is an example you sent earlier: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/ > > This link is above is the page where i can't see any of my lists outputs on my mailman3 gui. All i visually see is three loading icons spinning. Also, mark said it will only show threads with post in the last 30 days. so i made a test list and made a new thread and still the problem persists. Still see the three loading icons spinning. I've manually added the test list and also did it through the gui. Same outcome. We've seen issues like this before? Are you running the django cron tasks <https://docs.mailman3.org/en/latest/install/virtualenv.html#cron-jobs-for-m…>. Sometimes the `daily` jobs fix this. Also if you haven't done so, restarting the WSGI server (uWSGI, gunicorn, Apache mod_wsgi) may help. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

[MM3-users] Re: Problem with perms on /etc/mailman3/mailman.cfg while following https://docs.list.org/en/latest/install/virtualenv.html on new mailman3 Debian 12 installation

by Mark Sapiro

On March 25, 2025 1:20:22 AM GMT+07:00, Philip Bondi <pjbondi(a)systemdatabase.com> wrote: > >The instructions https://docs.list.org/en/latest/install/virtualenv.html#installing-mailman-… do not say what to do with existing file. > >root@shackleton12:~# ls -alF /etc/mailman3/mailman.cfg >-rw-r--r-- 1 root list 11119 Mar 20 11:45 /etc/mailman3/mailman.cfg > >Should we move the /etc/mailman3/mailman.cfg out of the way and create new file as user and group mailman:mailman ? How did that file get there? It looks like at some point you installed the Debian package. If you are following <https://docs.list.org/en/latest/install/virtualenv.html you shouldn't install the Debian package. In any case, just remove the file. Probably it's best to remove the Debian package completely and start over. -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

1 year, 4 months

[MM3-users] Re: content filtering in version 3.1

by Mark Sapiro

On 5/11/21 8:45 PM, Simon Handfield via Mailman-users wrote: > Hi everyone, > > I'm sorry to resurrect this thread from so long ago but it appeared to provide exactly the answer I was looking for, trying to manage pass_types in 3.1.1 on Ubuntu 18.04. > > GNU Mailman 3.1.1 (Between The Wheels) > > Unfortunately when I run: > > ./bin/mailman shell -l [list address] > > I receive: > > usage: mailman [-h] [-v] [-C CONFIG] > {help,aliases,conf,create,digests,import21,info,inject,lists,members,qfile,remove,reopen,restart,shell,start,status,stop,unshunt,version,withlist} > ... > mailman: error: unrecognized arguments: -l > > Can anyone advise how I can use the -l switch to manage this setting for a list? Older versions of Mailman core did not support the -l/--listspec option for mailman shell. They expected the listname as an argument as in ``` mailman shell list(a)example.com ``` What does ``` mailman shell --help ``` show in your case? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

[MM3-users] Re: FW: [Django] ERROR (EXTERNAL IP): Internal Server Error: /user-profile/

by Mark Sapiro

On 10/16/21 9:52 AM, Christian Stalberg via Mailman-users wrote: > When I go to https://.../admin/ I get a Django Administration screen and in > the upper right hand corner I see > > WELCOME, <username>. VIEW SITE / CHANGE PASSWORD / LOG OUT And my point was if you go to Users under Authentication and Authorization you should find that alekos.pantazis is a user. If you go to your own https://www.grizz.org/user-profile/ page, do you see a gravatar to the right of the Username, First name, Last name boxes, and does going there produce the same error in the logs. If that's all OK, then I don't know what produced the original error, but I think you can ignore it. If that produces the same error in the logs, then something is wrong with your django-mailman3 installation, but I don't know what. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

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

by Mark Sapiro

On 9/20/22 14:50, Dan Caballero wrote: > > 2022-09-20 14:44:17 [FALCON] [ERROR] GET /3.1/lists/jewishlife(a)caltech.edu/held?count=10&page=1 => Traceback (most recent call last): > File "falcon/app.py", line 365, in falcon.app.App.__call__ > File "/opt/mailmanve/lib/python3.9/site-packages/mailman/rest/post_moderation.py", line 182, in on_get > resource = self._make_collection(request) > File "/opt/mailmanve/lib/python3.9/site-packages/mailman/rest/helpers.py", line 182, in _make_collection > entries = [as_dict(resource) for resource in collection] > File "/opt/mailmanve/lib/python3.9/site-packages/mailman/rest/helpers.py", line 182, in <listcomp> > entries = [as_dict(resource) for resource in collection] > File "/opt/mailmanve/lib/python3.9/site-packages/mailman/rest/post_moderation.py", line 173, in _resource_as_dict > assert resource is not None, resource > AssertionError: None This is most likely a race condition between two browsers, one of which handles the held message while the other is getting the held messages. Check Mailman's access.log entries with time stamps around 2022-09-20 14:44:17. -- 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

[MM3-users] Re: (venv) mailman-web migrate (as explained) fails with "django.core.exceptions.ImproperlyConfigured: allauth.account.middleware.AccountMiddleware must be added to settings.MIDDLEWARE"

by Mark Sapiro

On 10/19/23 13:15, Wikinaut wrote: > > However myserver/mailman3 page is throwing > > Erfolgreich als Admin angemeldet. > Something went wrong >>>> HTTP Error 401: REST API authorization failed > > Even when the API keys are unchanged from my previous installation. Any idea what can be wrong here? what does the command `mailman info` show for REST credentials? The defaults for these are REST credentials: restadmin:restpass set by admin_user: restadmin admin_pass: restpass in the [webservice] section of mailman.cfg and the corresponding defaults for Django settings are: MAILMAN_REST_API_USER = 'restadmin' MAILMAN_REST_API_PASS = 'restpass' If you have something different, is it set in both mailman.cfg and settings.py? Is there more information in /opt/mailman/mm/var/logs/mailman.log or /opt/mailman/web/logs/mailmanweb.log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

Search results for query "sapiro"