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

[MM3-users] Re: Feature request, hyperkitty, low volume lists

by Mark Sapiro

On 1/9/25 06:07, Alain D D Williams wrote: > > For an example see: > > https://fridayfolk.phcomp.co.uk/mailman3/hyperkitty/list/announce@fridayfol… The above URL and also https://fridayfolk.phcomp.co.uk/mailman3/hyperkitty/list/announce@fridayfol… and even https://fridayfolk.phcomp.co.uk/mailman3/hyperkitty/ all give a 500 internal server error response. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 1 week

[MM3-users] Re: m3 database sizing

by Mark Sapiro

On 1/22/25 6:22 AM, Alexander Inzinger-Zrock via Mailman-users wrote: > B) > has some empirical values and would like to share? mail.python.org has 195 lists with 53394 members. Its PostgerSQL database is currently 18 gigabytes. This includes HyperKitty archives, some of which are quite large. The hyperkitty_email table together with the hyperkitty_attachment table contain the contents of every message in the archive. lists.mailman3.org has only one significant list with 658 members and currently archives 2267 messages not counting this one. Its PostgerSQL database is currently 193 megabytes. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 4 weeks

[MM3-users] Re: mailman3-web postorious error "invalid request block size: 14056 (max 4096)...skip"

by Mark Sapiro

On 1/28/25 09:15, Frederik via Mailman-users wrote: > > Any idea what could be wrong or how to debug this further? > > I'm using mailman3-full 3.3.8-2~deb12u2 and mailman3-web 0+20240312-1 packages. I have no ideas, but please see https://wiki.list.org/x/12812344 and report this to Debian. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 3 weeks

[MM3-users] Re: Adding Mass Subscribe custom template error

by Mark Sapiro

On 1/29/25 09:41, Arte Chambers via Mailman-users wrote: > Where can I find the setting > ``` > POSTORIUS_TEMPLATE_BASE_URL > ``` It is in your Django settings. Where these are depends on your installation, but these are usually in files named settings.py and settings_local.py. If you installed following https://docs.mailman3.org/en/latest/install/virtualenv.html the default is in mailman_web/settings/mailman.py but you would override the default in /etc/mailman3/settings.py -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 3 weeks

[MM3-users] Re: Adding Mass Subscribe custom template error

by Mark Sapiro

On 1/29/25 11:58, Arte Chambers via Mailman-users wrote: > > Bonus question: how should I calculate how many workers I should have on my > system? On lists.mailman3.org (server for this list) we use 4. on mail.python.org (server for about 200 lists) we use 6. Those numbers are pretty arbitrary. See https://docs.gunicorn.org/en/latest/design.html#how-many-workers for their recommendation. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 3 weeks

[MM3-users] Re: Occasionally "The content of this message was lost."

by Mark Sapiro

On 1/29/25 23:47, Frank Richter wrote: > Hello, > > occasionally we face the problem "The content of this message was lost." > when handling a message on hold. This is probably https://gitlab.com/mailman/mailman/-/issues/1162 [1] fixed by https://gitlab.com/mailman/mailman/-/merge_requests/1212/diffs to be release in Mailman core 3.3.10. [1] In particular, see https://gitlab.com/mailman/mailman/-/issues/1162#note_2113461048 for a fix for earlier releases. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 3 weeks

[MM3-users] Re: One-click unsubscribe?

by Mark Sapiro

On 2/4/25 20:24, Jered Floyd wrote: > > I'm having a lot of problems with GMail delivery due to lack of "one-click unsubscribe" -- however that is quantified, which is not clear. One other thing. Gmail in its, to paraphrase Steve, "enshittifiedness" while publishing a DMARC policy of none, treats mail From: gmail.com as though the DMARC policy is reject. This means you need to add `^.*(a)gmail\.com$` to your list's setting for DMARC Addresses (requires Postorius >= 1.3.9). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 2 weeks

[MM3-users] Re: Pck files stuck in out queue

by Mark Sapiro

On 2/6/25 17:07, Stephen J. Turnbull wrote: > Lieuallen, Thomas Otis via Mailman-users writes: > > > I was getting the ‘Cannot connect to SMTP server’ message in > > mailman.log. > > I believe this is unrelated, but you should look into that. It is definitely related. That (very uninformative) message is logged once only after the out runner is started the first time calls the decorate handler and the handler can't access a template. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 2 weeks

[MM3-users] Re: Heads up: settings.ACCOUNT_AUTHENTICATION_METHOD is deprecated

by Mark Sapiro

On 2/7/25 03:19, Andreas Vetter wrote: > > Changing ACCOUNT_AUTHENTICATION_METHOD to ACCOUNT_LOGIN_METHODS in > /etc/mailman3/settings.py is not enough. One has to edit > venv/lib/python3.11/site-packages/mailman_web/settings/mailman.py You can do this in /etc/mailman3/settings.py only without editing venv/lib/python3.11/site-packages/mailman_web/settings/mailman.py by adding ``` del ACCOUNT_AUTHENTICATION_METHOD ACCOUNT_LOGIN_METHODS = {'email', 'username'} ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 2 weeks

[MM3-users] Re: REST API: potential bug

by Mark Sapiro

On 2/14/25 23:30, Peter Knowles via Mailman-users wrote: > > Basically providing the "mail_host" param, but leaving it empty causes the command to return successful, therefore creating an "empty" domain entry. > > Ideally the REST API should check to see if the param is empty, or for that matter "valid" before accepting it. > > Another test just run with "-d mail_host=test(a)test.com" also returned successful, therefore allowing an "invalid" domain. Thanks for reporting. I have filed https://gitlab.com/mailman/mailman/-/issues/1202 for this. -- 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

Search results for query "sapiro"