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

[MM3-users] {Spam?} Re: Monthly mailman-web job using a lot of memory

by Mark Sapiro

On 7/1/22 1:40 AM, Andy Smith wrote: > > In the job list I see: > > appname - jobname - when - help > -------------------------------------------------------------------------------- > hyperkitty - update_and_clean_index - monthly - Update the full-text index and clean old entries > > so I'm guessing it's that, but there is also: > > hyperkitty - update_index - hourly - Update the full-text index > > which hasn't been noitceably a problem so I wonder why the "and > clean old entries" bit is so much more heavyweight, what exactly it > dopes and if there's any way to make it lighter on resources? The difference is the update_and_clean_index job calls hyperkitty.search_indexes.update_index() with remove=True See https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/search_index…. The comments say "Setting remove to True is extremely slow, it needs to scan the entire index and database." I second Mark Dadgar's comment to replace whoosh with xapian. It will help, although it requires rebuilding the entire search index. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

[MM3-users] Re: migrate MM3 list from an old server to a new one

by Mark Sapiro

On 8/6/24 01:43, noc(a)iem.at wrote: > > there *is* documentation about migrating MM2 to MM3; and my understanding is that `mailman-web migrate` can be used to upgrade a given MM3 instance to a new version. No. the mailman-web migrate command will apply relevant migrations for various django projects. You do need to rin it after upgrading things like hyperkitty, postorius and django-mailman3 and other dependencies which may have defined migrations for various database schema changes, but this will do nothing for your data. For that, you need to dump the mailman and mailmanweb databases on the old server and import them on the new server. > but how can i export an entire MM3 list (including 20 years of archives) to some serialization format, and import it again in another instance? With the dump and other utilities from your database manager. Almost everything is in the database. There are some things in Mailman's var/ directory, but those can simply be moved. -- 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: MTA setup

by Mark Sapiro

On 12/24/24 09:31, Arte Chambers via Mailman-users wrote: > Looks like the from header is the email address I am using for testing: From: > Arte Chambers <paul.m.robey(a)gmail.com> I'm not sure what's going on. Previously, I said > Presumably it has previously requested and received the list_url and > the permalink to put in the message headers. This can be confirmed by > the presence of List-Archive: and Archived-At: headers with values > in the messages from the list. but they aren't there. ... > Archived-At: <> > List-Archive: <> I was able to add that message to a test list with no problem, so now it looks like the issue is possibly mailman_hyperkitty not able to communicate with hyperkitty, although the log messages aren't consistent with that. Possibly the issue is not with the message you sent, but with the first message in var/archives/hyperkitty/spool/. Is /1734973370.5060537+806f73d2a296b0293228a9489b81129740d7afea.pck the first file in a listing of var/archives/hyperkitty/spool/? If not, what does `mailman qfile` show for the first one? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

[MM3-users] Re: bounces with empty message-id

by Mark Sapiro

On 01/30/2018 11:38 PM, Peter Münster wrote: > On Tue, Jan 30 2018, Mark Sapiro wrote: > >> The underlying issue is the orange.fr domain is sending DSNs without a >> Message-ID: header. > > Yes. Is a Message-ID header required in a DSN by any RFC? It's not a MUST, just a SHOULD, but RFC 5322, sec 3.6.4 says Though listed as optional in the table in section 3.6, every message SHOULD have a "Message-ID:" field. >> If you used VERP (i.e. set verp_delivery_interval = 1 in the [mta] >> section of your config), this log message > > I have verp_delivery_interval = 10 ... Which says only every 10th message will be VERPed. You want verp_delivery_interval = 1 to VERP every message. >> would contain to=<test-bounces+user=example.com(a)my-domain.org> and you >> could identify the bouncing address (user(a)example.com in this case) that >> way. > > Yes, that's my intention, but first of all, mailman must receive the DSN. The message does appear in the mail log, but until the issues below are fixed, even if Mailman receives it, you won't see it. >> Beyond that, there are still other issues, the biggest of which is >> currently, Mailman is not processing bounces other than storing them in >> the database. See <https://gitlab.com/mailman/mailman/issues/343>. > > Shouldn't the DSNs be forwarded to the owner of the list? They should be processed by Mailman and scored as bounces for the recipient if recognized and forwarded if not (depending on settings), but they currently are only stored. >> if a recipient MTA can't create a DSN that has a Message-ID:, would >> you trust what else it does? > > I don't know. The question for me is: does the remote MTA needs a fix > (i.e. the Message-ID is required by some RFC), or mailman (i.e. a DSN > without Message-ID should be acceptable)? I have filed <https://gitlab.com/mailman/mailman/issues/448> for this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 6 months

[MM3-users] Re: Implementing threading [was: hyperkitty failed to create a thread]

by Mark Sapiro

On 2/12/19 8:09 AM, Stephen J. Turnbull wrote: > > I suppose HyperKitty uses References (it works for messages that have > proper Message-IDs ;-), but I don't know what algorithm it uses. > Might be worth looking into, as well as considering a more Postelian > parsing of Message-IDs. Specifically, take the field body, unfold it, > strip leading and trailing whitespace and leading "<" and trailing > ">", and whatever's left is the message ID. Hyperkitty uses In-Reply-To: and if absent falls back to the last item in References: to determine a message's parent. I haven't looked at what happens if the parent is not in the archive but arrives later. We could look at earlier References: items to try to find one we know, but this could result in bad threading if a later reference arrives after we think we've determined the parent. The unfolding of Message-ID: is now correct. See <https://gitlab.com/mailman/hyperkitty/merge_requests/125>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 6 months

[MM3-users] Re: urls.py location on venv install

by Mark Sapiro

On 8/9/26 00:30, Torsten wrote: > > the traceback is this: > > Traceback (most recent call last): > File > "/opt/mailman/web/venv/lib/python3.13/site-packages/django/core/handlers/wsgi.py", line 124, in __call__ > response = self.get_response(request) > File > "/opt/mailman/web/venv/lib/python3.13/site-packages/django/core/handlers/base.py", line 139, in get_response > set_urlconf(settings.ROOT_URLCONF) > ^^^^^^^^^^^^^^^^^^^^^ > File > "/opt/mailman/web/venv/lib/python3.13/site-packages/django/conf/__init__.py", line 104, in __getattr__ > val = getattr(_wrapped, name) > > Where should mailman_web.urls be located, also in /etc/mailman3 or > rather in the venv of mailman_web in /opt/mailman...? How did you install Mailman? If you followed <https://docs.mailman3.org/en/latest/install/virtualenv.html>, you should have /etc/mailmasn3/settings.py which is similar to <https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-configu…>. In particular, it should have near the beginning ``` from mailman_web.settings.base import * from mailman_web.settings.mailman import * ``` The import from mailman_web.settings.base defines ``` ROOT_URLCONF = 'mailman_web.urls' ``` which points to mailman_web/urls.py in the venv's site-packages directory. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 week, 6 days

[MM3-users] Re: Migration advice

by Mark Sapiro

On 08/28/2018 06:42 PM, Quanah Gibson-Mount wrote: > Hi, > > I'm looking at migrating from an old server running mailman 2.1.15 > (Debian wheezy) to a new Ubuntu 18.04 LTS system. I'd like to upgrade > to mailman3 as a part of this migration. I was reading the migration > docs (<http://docs.mailman3.org/en/latest/migration.html>), which seem > to require both mailman2 and mailman3 be installed concurrently on the > same system. Is that correct, or can I rsync the mailman2 list > information onto the new server without mailman2 itself being present, > and import from there? Short answer - Yes. You need only a Mailman 3 installation. You also need a copy of the Mailman 2 lists/LISTNAME/config.pck file for input to 'mailman import21' and a copy of the Mailman 2 archives/private/LISTNAME.mbox/LISTNAME.mbox file for input to the Django management hyperkitty_import command. It would be good to check the archives/private/LISTNAME.mbox/LISTNAME.mbox file with the Mailman 2 bin/cleanarch command, but you can do that on the Mailman 2 system before copying the mbox. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 11 months

[MM3-users] Re: Using REST with CLI using curl .... help needed

by Mark Sapiro

On 12/8/20 2:01 AM, Krešimir Mihalj wrote: > Hi ! > I need simple add/delete member to list using rest ..... but all documentation is for python and not helpfull for me, .... and I need these in CLI using curl command .... Have you seen <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…> > To add member using CLI i tried this command: > > curl -d "{'list_id' : 'list.domain.com', 'subscriber' : 'user(a)email.com'}" -H 'Content-Type: application/json' --user restadmin:restpass http://localhost:8001/3.0/members Try this: > curl --user restadmin:restpass --data-raw 'list_id=list.domain.com&subscriber=user(a)email.com' http://localhost:8001/3.0/members > Also, if someone is willing to give example: delete user: user(a)email.com from list: list(a)domain.com First find the member_id with something like > curl -urestadmin:restpass http://localhost:8001/3.0/lists/list.domain/member/user@email.com which will return json including the value of member_id Then you can do > curl -urestadmin:restpass -X DELETE http://localhost:8001/3.0/members/xxxx where xxx is the member_id. -- 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: Problem with redirection when entering alias without a / at the end

by Mark Sapiro

On 3/19/21 3:12 PM, Jens Günther wrote: > > > -> the first one works and leeds to > https://mailman.xyz.de/mailman3/postorius/lists > -> the second one redirects to > https://mailman.xyz.de/mailman/postorius/lists > -> which does not exist, since Apache-alias is only for mailman3 Sorry, I missed that it was mailman vs mailman3. > > I only use the apache-conf given in the documentation: > > <code> > Alias /mailman3/favicon.ico > /var/lib/mailman3/web/static/postorius/img/favicon.ico > Alias /mailman3/static /var/lib/mailman3/web/static > > <Directory "/var/lib/mailman3/web/static"> > Require all granted > </Directory> > > <IfModule mod_proxy_uwsgi.c> > ProxyPass /mailman3/favicon.ico ! > ProxyPass /mailman3/static ! > ProxyPass /mailman3 > unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > </IfModule> > </code> I don't use uwsgi so I can't advise on its configuration, but do you have USE_X_FORWARDED_HOST = True SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https') in your Django settings? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

[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

4 years, 2 months

Search results for query "sapiro"