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

[MM3-users] Re: Broken web UI after upgrade

by Mark Sapiro

On 12/16/22 22:21, Mark Sapiro wrote: > > I suggest you look at ownership and permissions. > > ``` > find /opt/mailman/mm/static/ -not -user mailman > find /opt/mailman/mm/static/ -not -perm -u+rw > find /opt/mailman/mm/static/ -type d -not -perm -u+x > ``` > and the same on > /opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/ > > >> If the above doesn't reveal anything substantial, then let me know and I >> can bump up the verbosity. > > > I don't know if --verbosity 3 will reveal anything or not. You could try. Did you see the post at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>? Have you tried ``` django-admin clear_cache ``` -- 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: Migration from old server to new server failed

by Mark Sapiro

On 2/23/24 09:28, Mark Sapiro wrote: > On 2/22/24 21:51, Stephen J. Turnbull wrote: >> If I'm correct, I think you'll >> find the offending message in $var_dir/archive/hyperkitty or some >> subdirectory, it's a regular queuefile, and you can read it with the >> showqfile utility to see if it's spam. Otherwise you need to edit the >> [] out of the message ID. > > The directory is $var_dir/archive/hyperkitty/spool/ and the command to > view the queue entry is `mailman qfile path/to/file`. BTW, the issue with bogus [] delimited Message-IDs is "fixed" (actually worked around) in Mailman 3.3.9 by https://gitlab.com/mailman/mailman/-/merge_requests/1099/ -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

[MM3-users] Re: If I manually add email addresses to a list and then delete them, how do i permanent delete them from Users?

by Mark Sapiro

On 4/25/23 2:44 PM, Mark Sapiro wrote: > On 4/25/23 2:14 PM, Andrew Hodgson wrote: >> >> Why aren't we seeing the actual address here? ... > > I actually started with the preferred_address.email code above, but in > testing, I got the 'no_preferred_address' result with the one deleted > user so I, perhaps erroneously, went with the representation of the > user. I'll probably update the script again. I have updated the script again. It now displays: User: "Junk Mail" <junk_mail(a)example.com> deleted from Mailman -- 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

[MM3-users] Re: m3 database sizing

by Mark Sapiro

On 1/22/25 3:49 PM, Mark Sapiro wrote: > > mail.python.org has 195 lists with 53394 members. Its PostgerSQL > database is currently 18 gigabytes. PostgreSQL not PostgerSQL and likewise below. I neglected to mention the Xapien search index which is 41 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. And the Xapien search index here is 382 megabytes. I.e., in both cases the Xapien search index is on the order of twice as big as the PostgreSQL database. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 1 month

[MM3-users] Re: Multi-domain oddities in Hyperkitty and Postorius

by Mark Sapiro

On 2/15/23 18:35, Mark Sapiro wrote: > > $ django_admin shell > >>> from django.contrib.sites.models import Site > >>> new_site = Site(id=5, domain='5.example.com', name='display_name') > >>> new_site.save() > > Of course the values are up to you and you can omit the id= to have > Django assign the first available.. Also note that the above is a django_admin shell interaction. You can also do this in python, but you need to precede the above with ``` >>> import os >>> import sys >>> sys.path.insert(0, '/path/to/directory/containing/settings.py') >>> os.environ['DJANGO_SETTINGS_MODULE'] = 'settings' >>> import django >>> django.setup() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

[MM3-users] Re: Immediate notification to the administrator

by Mark Sapiro

On 11/2/23 10:05, Stephen J. Turnbull wrote: > Mark Sapiro writes: > > > This Mailman 3.2.2 cron/crontab.in.in file is is an artifact from > > Mailman 2.1. Nothing there is relevant to any Mailman 3 version > > So there was no daily notification at all in Mailman 3.2.2? Correct. There was no daily notification at all prior to Mailman 3.3.0. See https://gitlab.com/mailman/mailman/-/issues/258 > That kinda sucks for this user. Yes it does. I *think* the user could just copy <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/commands/cli_n…> to the installed mailman/commands/ directory to implement the `mailman notify` command. This also requires copying <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/templates/en/l…> to the installed mailman/templates/en/ directory. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: Disable "confirmation emails"

by Mark Sapiro

On 09/18/2018 03:01 PM, Jonas Meurer wrote: > Am 18.09.2018 um 23:25 schrieb Mark Sapiro: >> >> Where are you seeing these? There were changes in this area in Mailman >> core v. 3.2.0 and I think these now should only be sent in response to >> mail to the -request address that contains a command other than >> (un)subscribe or confirm. > > I can confirm that these mails are sent in response to messages to > -subscribe (not only to -request) with Mailman 3.2. I experienced the > same as Hagen and I also wonder how to turn them of. Yes, the 3.2 changes addressed only part of this issue. I have filed a new issue at <https://gitlab.com/mailman/mailman/issues/516> for this. -- 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: HTML post only showing as attachment

by Mark Sapiro

Mark Sapiro wrote: > On 7/4/19 7:13 AM, andrew.bernard(a)gmail.com wrote: >> I have a post come in that is in HTML and has an >> image attached. It is distributed fine to email subscribers. Hyperkitty shows a blank >> message, with the in an html attachment, and the image as a jpg attachment. >> >> Why doesn't the text show in Hyperkitty? > > Because there is no plain text. Non text/plain parts including text/html > parts are "scrubbed" and stored aside. If in Postorius on the list's Settings -> Alter Messages page, Filter Content and Convert html to plaintext are both Yes, the HTML should be converted to plain text and that should appear in HyperKitty. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 7 months

[MM3-users] Re: Is there a "global" max_message_size?

by Mark Sapiro

On 6/20/20 3:51 PM, skenny(a)scss.tcd.ie wrote: > Mark Sapiro wrote: > >>> Mailman's lmtp runner which implements the server that receives mail via >> LMTP uses the aiosmtpd.lmtp.LMTP class to implement the server. This has >> a default size limit of 33554432 bytes (32 MB) and that's where the "552 >> Error: Too much mail data" comes from. > > Ah - fantastic! I had tried a fairly crude trawl through the mailman-core container files (not knowing what exactly to look for really), but failed to come up with anything. Presumably the files in the container contain a file like aiosmtpd-1.2-py3.7.egg (modulo versions), but that file is zip compressed so grep won't find anything in it. -- 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: Subscription issue with ghost confirmations

by Mark Sapiro

On 10/29/20 8:51 AM, Brian Carpenter wrote: > > On 10/29/20 11:33 AM, Mark Sapiro wrote: >> The real question is if a user has a subscription waiting confirmation >> and the policy is changed to moderate, is a second request rejected >> because of the request waiting confirmation. If so, I think this is a >> bug which should be fixed. >> > Do you think this is a bug with Mailman core or my system? If the current policy is moderate and the user has a prior request waiting confirmation and a new request is rejected because of the prior request waiting confirmation, I think that is a bug in core, but I don't know if that is the case or not. -- 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

Search results for query "sapiro"