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

[MM3-users] Re: Turned on archiving and it is not working

by Mark Sapiro

On 6/9/22 12:09, bob B via Mailman-users wrote: > > Jun 09 18:49:10 2022 (28) Exception in the HyperKitty archiver: <html><title>Auth required</title><body> > <h1>Authorization Required</h1><p>The archiver key is now > File "/usr/lib/python3.8/site-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message > <h1>Authorization Required</h1><p>The archiver key is now > <h1>Authorization Required</h1><p>The archiver key is now The full message is <h1>Authorization Required</h1><p>The archiver key is now required to be sent over the Authorization HTTP header. You need to upgrade the mailman-hyperkitty package to 1.2.0 or newer. > HyperKitty version 1.3.5. As indicated in the above message, HyperKitty >= 1.3.5 requires mailman-hyperkitty >= 1.2.0 If your mailman-hyperkitty is < 1.2.0, you need to upgrade it. If it is 1.2.0, there is some issue with the http headers being dropped in the request from mailman-hyperkitty to HyperKitty. See the last two posts in the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… -- 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: hyperkitty failed to create a thread

by Mark Sapiro

On 2/17/19 2:13 AM, Danil Smirnov wrote: > > Could you advise how to rebuild the failing threads please? I've done index > update with 'django-admin update_index' command but it seems irrelevant to > the issue, I still have all those messages separated: > https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org/2019/2/ I've not tried it and have no idea if it will work, but the query select message_id, message_id_hash, in_reply_to from hyperkitty_email; will show those things. You will see some (most) entries have a message_id of the form 'left-part@right-part' with no angle brackets, but some are of form ' <left-part@right-part>'. In those cases where 'left-part@right-part' of in_reply_to is in a message_id of form ' <left-part@right-part>', you could try altering that in_reply_to to ' <left-part@right-part>' After doing this, you probably need to run 'django-admin runjob thread_order_depth'. Obviously, make backups before you start. An alternative might be to 'fix' the message_id which may or may not require recomputing message_id_hash. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

[MM3-users] Re: mailman3 vs postfix

by Mark Sapiro

On 4/29/20 7:35 AM, Ralf Wiegand wrote: > hey Mark, that worked. Thank YOU. Got one step ahead. So after > creating a admin account and logging in via the GUI, I get this error > message: > > > IntegrityError at /accounts/login/ > > UNIQUE constraint failed: account_emailaddress.email > > Request Method: POST > Request URL: http://192.168.0.27:8000/accounts/login/ > Django Version: 2.2.12 > Exception Type: IntegrityError > Exception Value: > > UNIQUE constraint failed: account_emailaddress.email > > Exception Location: > /opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/db/backends/sqlite3/base.py > in execute, line 383 > Python Executable: /opt/mailman/venv-3.6/bin/python > Python Version: 3.6.8 > > What does this mean? I think it means you have more than one Django account with the same email address. If you can log in to your django admin interface as the superuser, you may be abl to go to 'Users' and delete one. If you can't log in to your django admin interface as the superuser for this reason, you will probably need to create another superuser. -- 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 Unshunt Specific Message ?

by Mark Sapiro

On 8/11/20 9:55 PM, Shashikanth Komandoor wrote: > Hahahaha. > > Looks like a work around. Yes, it's a workaround. > I understood "moving out of the shunt queue" means "Moving the files from > /var/lib/mailman/mailman/var/shunt directory to any other directory say > /opt/...." in my environment. Because I installed mailman software inside > /var/lib/mailman only. It means first understand why the messages were shunted and fix whatever the underlying issue is or they will just be shunted again. You should look at each message in the shunt queue with `mailman qfile` and determine which ones you don't want at all, which ones you want to save for later and which ones you want to unshunt now. Just remove the ones you don't want at all. For the ones you want to save for later, move them to any other directory at all. Then run `mailman unshunt` for the remaining ones after which you can move the saved ones back or leave them where you moved them to. -- 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: only show mail domains from web host on web-host-url

by Mark Sapiro

On 3/19/21 6:38 AM, Jens Günther wrote: > Thank you for your answer. I should have seen that in the Docs, but > somehow missed it: https://docs.mailman3.org/en/new/prodsetup.html > > I set it in the corresponding file, but unfortunately it doesn't work > :-( I tried other setting to prove, that the file is used (ALLOWED_HOSTS > works, changed here from '*' to 'localhost' and my example-domains, this > works). It seems to be the same as this user describes (a while ago): > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… FILTER_VHOST is problematic. It works fairly well for HyperKitty, but not so well for Postorius. In particular with Postorius it doesn't work if there is more than one mail host domain with the current web host. See these issues and MRs for more detail. https://gitlab.com/mailman/hyperkitty/-/issues/254 https://gitlab.com/mailman/hyperkitty/-/merge_requests/243/diffs https://gitlab.com/mailman/hyperkitty/-/merge_requests/244/diffs https://gitlab.com/mailman/postorius/-/issues/394 https://gitlab.com/mailman/postorius/-/merge_requests/500/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, 3 months

[MM3-users] Re: Auto discard after max_days_to_hold not working.

by Hitashi mancho

Thank you so much, Mark and Stephen, for the quick action and response. Waiting for the next release. On Tue, Apr 29, 2025 at 10:52 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 4/28/25 10:55, Mark Sapiro wrote: > > > > `mailman import21` will import the setting, but per the above comment, > > it doesn't yet work. The setting exists and is exposed in REST, but it > > appears it is not actually implemented. > > > This is now implemented for the next release. See > https://gitlab.com/mailman/mailman/-/issues/1215 and > https://gitlab.com/mailman/mailman/-/merge_requests/1346 for Mailman > core and https://gitlab.com/mailman/postorius/-/issues/628 and > https://gitlab.com/mailman/postorius/-/merge_requests/1001 for Postorius. > > -- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to huhamails(a)gmail.com >

1 month, 4 weeks

[MM3-users] Re: Full-text searching: why Haystack instead of PostgreSQL?

by Mark Sapiro

On 6/10/25 02:33, admin(a)bclug.ca wrote: > I've been asked to give a presentation on a recent migration from MMv2 to MMv3 and one of the items in my notes is the question about why Haystack is used for full-text searching instead of PostgreSQL? > > Can someone shed some light on that decision? The people who developed HyperKitty are no longer actively involved with Mailman and I can't speak with any authority about their design decisions. That said, both Django and Mailman core support multiple databases including PostgreSQL, MariaDB, MySQL, Oracle and SQLite whereas Django's full text search relies on PostgreSQL specific features and without some custom implementation, which may not even be possible, would not allow other DBMs. Haystack on the other hand provides a unified API that works with multiple backends. As far as I know, no one has developed a Haystack backend for PostgreSQL full text search, but as Sam notes in another reply, there are supported backends for Solr, ElasticSearch, Whoosh and Xapian. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 weeks, 4 days

[MM3-users] Re: Strange problem in user lists

by Mark Sapiro

On 12/16/21 2:25 AM, Gelpi Andrea wrote: > > I cant' understand why, but I have two members with the wrong name. > > "A B" <C(a)dom.tld> > "D E" <F(a)dom.tld> > > My problem is that A and B must be associated with F(a)dom.tld and vice-versa. > > I tried to delete the user member and recreate it, but it has always the > wrong name. Because the display name is associated with the Mailman user and unsubscribing the user from the list doesn't change the user. > Is it possible to correct those errors? How? The user can log in to the web UI and go to the Account link in the dropdown at the username at the upper right and change the first and last name there. If you have a recent enough Postorius, a site admin can go to the Users link at the top of a page find the user, click Manage and change the Display Name. Otherwise, you can do this in `mailman shell` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Re: Error 500 on held_messages page

by Mark Sapiro

On 2/4/22 04:57, Stephan Krinetzki wrote: > > we have fixed the issue now: Good. > mailman shell -l list(a)lists.example.com > > Welcome to the GNU Mailman shell > Use commit() to commit changes. > Use abort() to discard changes since the last commit. > Exit with ctrl+D does an implicit commit() but exit() does not. > Die Variable 'm' ist die list(a)lists.example.com Mailingliste > >>> lr = IListRequests(m) > >>> for req in lr.held_requests: > ... if lr.get_request(req.id) is None: > ... print(req.id) > ... > 32598 > 22449 > 66937 > 68261 > 92927 > >>> > > With this IDs > > DELETE FROM _request WHERE id IN (32598, 22449, 66937, 68261, 92927); > > And the 500 error is gone. I'm glad you were able to fix it. Do you happen to have the content of those rows in the db before you deleted them? It would be interesting to know what that was to try to determine how that situation happened in the first place. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

[MM3-users] Re: Verification emails 'helo' rejected

by Mark Sapiro

On 10/14/24 12:42, Greg Newby via Mailman-users wrote: > > Here are the corresponding logfile entries from mailmanweb.log: > smtplib.SMTPRecipientsRefused: {'redacted(a)gmail.com': (504, b'5.5.2 <mail>: > Helo command rejected: need fully-qualified hostname')} > > and from mail.log: > Oct 14 12:06:26 domain postfix/smtpd[722764]: NOQUEUE: reject: RCPT from > localhost[127.0.0.1]: 504 5.5.2 <mail>: Helo command rejected: need > fully-qualified hostname; from=<root(a)lists.domain.tld> to=<root@localhost> > proto=ESMTP helo=<mail> > > lists.domain.tld is the domain for Mailman3. I don't know why it's trying > to send email from root@. I think the mail.log entry is for the DSN for the failure. The issue is the HELO/EHLO command. Try the following in your venv ``` (venv) ...:~$ python Python 3... Type "help", "copyright", "credits" or "license" for more information. >>> import socket >>> socket.getfqdn() ``` If that returns `localhost`, that's the issue. I think you can fix it by putting a fully qualified domain name in /etc/hostname. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 1 week

Search results for query "sapiro"