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

[MM3-users] Re: Can't subscribe on new site/domain

by Mark Sapiro

On 10/10/25 12:15 PM, Flo via Mailman-users wrote: > > > On 10/10/25 20:47, Mark Sapiro wrote: >> >> What do you get from the following database query >> >> SELECT * from django_mailman3_maildomain JOIN django_site ON site_id = >> django_site.id; >> > > A while ago I have done a bit of database programming, however here I am > lost, please help, where should I place this query to get a result? I think you said your database is sqlite. If so, in the Debian package it is probably at /var/lib/mailman/data/mailman.db. You can point the sqlite3 command at the database and issue the query at the prompt. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 1 week

[MM3-users] Re: MM2.1 -> MM3.3 migration. To hold or not hold

by Mark Sapiro

On 11/18/24 16:54, mark(a)suburbia.org.au wrote: > Once again, thanks for taking time to reply. > > Mark Sapiro wrote: >> On 11/18/24 04:12, mark(a)suburbia.org.au wrote: >> This should not happen. In the message as delivered to the list what do >> you see in the X-Mailman-Rule-Misses: header and the >> X-Mailman-Rule-Hits: header if any? > > ``` > X-Mailman-Version: 3.3.8 > X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address > X-Mailman-Rule-Hits: member-moderation This says it was held for moderation. Is there an X-Mailman-Approved-At: header which would say it was approved by a moderator? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Mark Sapiro

On 1/2/23 11:56, Onyeibo wrote: > On Mon, 2 Jan 2023 09:57:45 -0800 > Mark Sapiro <mark(a)msapiro.net> wrote: >> >> curl -urestadmin:restpass http://localhost:8001/3.1/lists >> >> It should return JSON with information about your lists. >> > > I get the following: > {"start": 0, "total_size": 0, "http_etag": > "\"678678567346533573674563786538\""} That is the expected response if you have no lists yet. So connection to Mailman's REST API works via curl, so why doesn't it work via mailmanclient? If Mailman core was running, it should work. I don't know why it doesn't. Perhaps you have some kind of firewall that's blocking it. -- 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

[MM3-users] Re: How to store additional information about lists?

by Mark Sapiro

On 5/26/21 8:23 AM, Stephen J. Turnbull wrote: > Mark Sapiro writes: > > > As far as I know, none of this has ever been migrated to Mailman 3. > > It has been migrated to Mailman 3, there were at least two related > GSoC projects, and the repo was on GitHub, but it's not at the same > URL now. Not sure if they've stopped using it, I haven't mentored > there for four or five years. Let me look around. Their lists at https://systers.org/mailman/listinfo/ are still based on Mailman 2.1.12. I have tried to find their stuff in the recent past, and all I could find were broken links. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: How to upgrade to 3.10

by Mark Sapiro

On 3/4/26 16:11, Paul Tomblin via Mailman-users wrote: > > > On Tue, Mar 3, 2026, at 4:31 PM, Mark Sapiro wrote: > >> pip install git+https://gitlab.com/mailman/mailman@master >> ``` >> That version is compatible with Python 3.13. > > Ok, that works. Now what do I need to do to get base_url and the dependent template text variables set? Is it just the same with mailman-web@master ? Updating mailman-web from gitlab won't do it because you need to update postorius and mailman-client from gitlab and an update of mailman-web will pull those from PyPI. You need to do ``` pip install git+https://gitlab.com/mailman/mailman-client@master pip install git+https://gitlab.com/mailman/postorius@master ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 months, 2 weeks

[MM3-users] Re: How to prevent members to attach executables (exe, bat, ...) to the emails sent to list

by Mark Sapiro

On 10/1/20 6:12 PM, Mark Sapiro wrote: > >>>>> m.filter_types = ['application/pdf'] >>>>> commit() >>>>> print(list(m.filter_types)) >> ['application/pdf'] > > > This should allow ONLY the PDF and nothing else, not even the text/* > message body parts. Sorry, my statement above is wrong. That should also remove the pdf, but it's redundant given that 'application/pdf' is not in pass_types. > Actually, what's m.filter_content? I suspect it's False which means > don't do any content filtering. I think this is the issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

[MM3-users] Re: Issues with cross posted emails after upgrading to mailman 3.3.6

by Mark Sapiro

On 11/4/21 1:30 PM, Mark Sapiro wrote: > > Thanks for filing the issue. I'll work on a solution. My current > thinking is to add a `count` column to the message table, set the count > to 1 when initially adding a message-id, increment the count when adding > an existing message-id, decrement the count when deleting a message-id > and only delete the entry and message when the count reaches 0. I wound up taking a different approach. I check for other references to the message in the message store and only delete the message if there are none. The fix is at https://gitlab.com/mailman/mailman/-/merge_requests/932/diffs -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: Post-installation documentation?

by Mark Sapiro

On 11/24/21 10:17 PM, David Newman wrote: > On 11/24/21 2:36 PM, Mark Sapiro wrote: >> >> To import archives run the Django admin command with arguments >> >> hyperkitty_import -l alist(a)example.com >> /path/to/mailman2.1/archives/private/alist.mbox/alist.mbox > > Good up to here, but ... hyperkitty_import not found. > > This wasn't covered in the venv docs: It is covered at https://docs.mailman3.org/en/latest/migration.html#upgrade-strategy Your issue is probably that the Django admin command you ran is not accessing your `settings.py`. You may need to do ``` export DJANGO_SETTINGS_MODULE=settings export PYTHONPATH=/path/to/directory/containing/settings.py ``` before running the Django admin command. These can also be given as --settings and --pythonpath options to the Django admin command. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[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, 8 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, 5 months

Search results for query "sapiro"