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

[MM3-users] Re: Add an extra option for "Delivery status" for users?

by Mark Sapiro

On 11/19/25 12:50 PM, Thomas Ward via Mailman-users wrote: > > We have a unique case where we have a user we want to disable for mail > receiving, etc. for the reason "Disabled by IT Security Team" but I > don't even know if it's possible to add a delivery status that is that > custom. At a minimum, you would need to add that choice to the DeliveryStatus(Enum) in mailman/interfaces/member.py and the choice and its description to the DELIVERY_STATUS_CHOICES tuples in postorius/forms/fields.py. I don't know offhand if that would be sufficient, or if more would be required. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 months

[MM3-users] Re: Mass subscribe operation fails with http error

by Mark Sapiro

On 4/29/26 8:01 AM, b.watts(a)ucl.ac.uk wrote: > > I have updated the config in: > /etc/mailman3/settings.py > to contain: > POSTORIUS_TEMPLATE_BASE_URL = 'https://mailinglists.ucl.ac.uk' > > After adding that item, I've recreated the template and resubmitted the subscribe. > But still get the same error. > > What could I try next? If you can access the database directly do SELECT name, uri FROM template WHERE context = 'list-id'; where list-id is the mailing list's list-id, i.e. the list posting address with the `@` replaced by `.`. Can you get the uri in a web browser or via, e.g., curl or wget? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 3 weeks

[MM3-users] Re: Clearing webserver cache - Nginx

by Mark Sapiro

On 8/6/24 14:27, Mark Sapiro wrote: > > Is this with only one browser? It's a long shot, but clearing browser > cache might work. Actually, I see the same issues from my browsers, so it's not a browser caching issue. The only thing left is nginx caching, but, while I know very little about nginx, I think it doesn't cache by default and I don't see where in your posted config it's enabled. Perhaps there's more in your config that you didn't post. If there is a proxy_cache_path directive in your config try find /the/proxy/cache/path -type f -delete to clear the cache. As a last resort, your /opt/mailman/mm/static/CACHE/ directory should contain a css/ directory with 3 files and a js directory containing one file and a manifest.json file with a template for the `link` directives referencing those files. The js/ directory is easy as its only one file, so your server is looking for /static/CACHE/js/output.3aaa7705d68a.js and you could create a symlink in the js/ directory from output.3aaa7705d68a.js to the actual file. For the css directory, your server is looking for output.158acc288604.css and output.6dab123e4897.css, and I don't see the third file in the logs you posted, but if I go to pages in your archive that I see as unstyled and look at the stylesheet references, they are to output.44ea6c55e917.css, output.e68c4908b3de.css and output.9efeb5f3d52b.css so you could just symlink those to the actual files, it doesn't matter which as all three are loaded on each page. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

[MM3-users] Re: Auth question

by Mark Sapiro

On 1/3/19 11:00 AM, kelly.close(a)lrewater.com wrote: > Hi David, > > Did you ever find a resolution to these Authorization errors? I'm experiencing the same problem in a new setup. Would love to know if you figured it out! The code that produces that error is: if request.GET.get("key") != settings.MAILMAN_ARCHIVER_KEY: return HttpResponse( """<html><title>Auth required</title><body> <h1>Authorization Required</h1></body></html>""", content_type="text/html", status=401) I.e., the key in the request which comes from the [general] api_key: setting doesn't match the key set as MAILMAN_ARCHIVER_KEY. Do you have quotes around the api_key setting? That would be a mistake. See <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 5 months

[MM3-users] Re: What is the recommended format for mailbox interchange as files?

by Mark Sapiro

On 6/21/19 10:05 PM, Andrew Bernard wrote: > > This issue could very well go in an FAQ for mailman. Can I add a topic > somehow? Many others will hit the same problem. There is a FAQ article at <https://wiki.list.org/x/4030689>. If you wish to edit that or create a new article, see the first paragraph at <https://wiki.list.org/> about obtaining write permission. There is also some documentation of hyperkitty_import at <https://hyperkitty.readthedocs.io/en/latest/install.html#importing-the-curr…>, the source for which is at <https://gitlab.com/mailman/hyperkitty/blob/master/doc/database.rst>. You could create a merge request to update that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years

[MM3-users] Re: Migration from 2.1 to 3

by Mark Sapiro

On 1/3/20 7:55 AM, brunol(a)agro.uba.ar wrote: > I've found something, the imported list preferred language is Spanish (es), changing it to 'en' : ... > seems to fix everything, as soon as i hit ctrl+d the messages are delivered properly. > > Even when i set it to french which has the same charset as spanish it works as expected. Any ideas why? Actually, since Mailman 3.2.1, the default charset for 'fr' is utf-8, not iso-8859-1, although I don't offhand understand why the language would affect this even if the encoding is different. In any case, at this level the message should be pure ascii with any non-ascii having been base64 or quoted_printable encoded. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 5 months

[MM3-users] Re: Mailman web Stopped working after upgrade

by Mark Sapiro

On 3/3/20 12:33 PM, David Krantz wrote: > > I think that this might be due to some kind of python misfeature where > compiled code behaves slightly differently to interpreted code, that > might explain the delay in it working initially before breaking. I > have no idea of how to solve this. I have tried to uninstall and > reinstlall psycopg2 in different versions without any luck. You need to activate your virtualenv and do pip install psycopg2-binary it must be psycopg2-binary, not just psycopg2. It's probably best to do pip uninstall psycopg2 first. As far as it working for a while, did you restart your wsgi service (gunicorn, uwsgi, ??) after upgrading? -- 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: migration plan and auto responder

by Mohsen Masoudfar

Thank you so much Mark! It worked perfectly. Mohsen -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, July 21, 2020 6:21 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: migration plan and auto responder [EXTERNAL EMAIL] On 7/21/20 3:13 PM, Mark Sapiro wrote: > > You probably also want to set Privacy options... -> Sender filters -> > member_moderation_action to Discard and on Membership Management... -> > Membership List under Additional Member Tasks, set everyone moderated. I answered a bit too quickly. Just s/probably/definitely/ in the above. This works because the autoresponses are sent before the moderation checks. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

5 years, 10 months

[MM3-users] Re: [SOLVED] Re: Re: Newbie question 2: Rewriting issue for bounced emails

by Mark Sapiro

On 12/27/21 4:05 PM, William Oliver wrote: > > Again, a quick DuckDuckGo search reveals that this has come up a couple > of times. It required that I modify /etc/postfix/main.cf to add the > non-localhost ip4 address of the box to the mynetworks line: > > mynetworks = 127.0.0.0/8 10.0.0.0/24 > > to > > mynetworks = 127.0.0.0/8 10.0.0.0/24 2.56.57.28 > > > I assume that means that postfix uses localhost for regular mail, but > mailman3 uses the 2.56.57.28 address. Because you set smtp_host: mail.libertyfp.org in mailman.cfg. If you leave the default settings smtp_host: localhost smtp_port: 25 you won't have this issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

[MM3-users] Re: Moderate first postings of new members

by Mark Sapiro

On 11/3/22 13:39, peter(a)chubb.wattle.id.au wrote: > > If you've set the default processing to 'hold for moderation' won't > this just continue to moderate the member? Ive been selecting 'Accept > immediately' in the dialog. "Default action to take when a member posts to the list" will only continue to be applied to the member if you select "List default". The difference between "Default processing" and "Accept Immediately" is "Default processing" passes the moderation check but continues to check other rules which are header-match, administrivia, implicit-dest, max-recipients, max-size, news-moderation, no-subject, digests and suspicious-header. "Accept immediately" bypasses all those additional checks. -- 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

Search results for query "sapiro"