Search results for "Postorius" - Mailman-users

Re: Upgrade-path from Ubuntu18LTS to recent mailman release

by Stephen J. Turnbull

Stefan Bauer writes: > thanks alot. That looks promising. Can we just copy the current > mailman3-database and take the configurations or is there a specific > migration path we have to follow? Much of the documentation on mailman.readthedocs.io discusses migrations and upgrades. You should read those for general hints. The distro Mailman to venv Mailman case is more discussed here on the mailing list than in those documents. I don't have pointers to those threads or the time to look offhand, maybe over the next few weeks as I work on our GSoC project. If you do find any, and would post them here, I'll make sure they get into the docs. The main thing is to backup Mailman configs (probably in /etc/mailman or /etc/mailman3) and the backend database (core, Postorius, possibly HyperKitty depending on configuration, and the django-mailman auth stuff) before trying to migrate. (For the backend database I would just dump the RDBMS unless non-Mailman content is really huge.) The nature of the virtualenv install is such that it *will not* overwrite any of the distro files at all (as long as you put it in /usr/local or /opt). However, you want to preserve the configs and database and reuse them, so those *must* be backed up. > We are currently running 3.1.1-9 (Ubuntu 18). Ubuntu 18 is probably old enough that you need to be careful about MySQL and its derivatives. The specific problems are (1) you need to specify the right UTF-8 variant for the coding system, and (2) more recent versions of Mailman tend to make certain records overflow. If you're using PostgreSQL these caveats *do not* apply. If you're using sqlite3 (I doubt it, but just for completeness) you should change to PostgreSQL or MySQL. If you're using something else (same caveat), I can't really say. Probably somebody out there is using Oracle or whatever, but we don't know about that. :-) Steve

3 years, 11 months

Re: Digests not working correctly

by Mark Sapiro

On 6/4/23 18:35, Joel Lord wrote: > > The periodic digests do seem to be coming out. I also now have > confirmation that the one message in this morning's digest that was from > May 4th was also included in the last digest back on May 4th, so it > seems that the one message was left behind in the digest queue when the > periodic digest was sent. I don't see how that can happen. The process that sends a digest renames the var/lists/<list-id>/digest.mmdf mailbox file in which the messages are accumulated to var/lists/<list-id>/digest.<volume>.<issue>.mmdf, where <volume> and <issue> are the volume and issue numbers of that digest, and then queues a message in the `digest` queue to tell the digest runner to create the digest from the messages in that mbox and send it. Thus, it leaves no var/lists/<list-id>/digest.mmdf mailbox file behind and that is created anew when the next post arrives. Further, if there is a non-empty digest.mmdf file, its messages should be sent no later than the next 11 PM `cron digests`. > There was one earlier message to the list > back on May 4th, before the one that got duplicated, but I can't tell if > that triggered a size-based digest to be sent: the logs aren't clear > enough on that detail for me to tell. OK > Just to inform things: > > (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep mailman > django-mailman3==1.3.9 > mailman==3.3.8 > mailman-hyperkitty==1.2.1 > mailman-web==0.0.6 > mailmanclient==3.3.5 > (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep hyper > mailman-hyperkitty==1.2.1 Actually, it's HyperKitty, not hyperkitty, but I assume HyperKitty is up to date as are the others. > (venv) lists@host2:~/mailman/venv/bin$ pip freeze | grep post > postorius==1.3.8 > > -- 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

Re: Mailman 3 - Header Filter

by Henrik Rasmussen

Mark Sapiro wrote: > On 4/22/19 2:34 PM, Thomas Lehker wrote: > > I am a Mailman neophyte and need help with filtering posts based on the subject field. We have a few list owners that want 'Out of Office' replies discarded. When using the below syntax in Postorius/Header filter the post is not discarded but ends up in 'Held Messages'. Is there any syntax I am missing or a setting in the lists that needs to be disabled/enabled to get these posts dropped? Any help is much appreciated. > The issue may be that in Mailman core's 'builtin' chain, the checking of > header_matches occurs after the check for member moderation so if the > member moderation check results in the message being held, the > header_matches aren't checked. There may me a newer thread about this, but I haven't found it. In my case I would be more interested in holding or discarding mails with subject 'Out of Office' if the mail would otherewise be send the to the list members due to a non-moderated list. I would emagine that the order of "check for member moderation" and header_matches would not be significant if holding or discarding the mail due to header_matches, am I right? 🤞🏻 If so, I would think that Header "subject:" or "subject" with Pattern "^(?i)(.*)autosvar(.*)" - without the double quotes - and Function "Hold for moderation" or "Discard" should either hold or discard any message with "Autosvar" (danish word for "Out of Office reply") somewhere in the subject, but that doesn't happen. What is the correct syntax? I know that filtering out Out of Office replies is just as hard as spam filtering, since it varies, but at least there is some kind of consistency in the wording, so I would give it a try. *) In a prevous mail I was told that ^ would tell Mailman that it is a regex. -- Henrik Rasmussen her(a)adm.ku.dk Copenhagen, Denmark

2 years, 7 months

Re: Message does not appear in archive

by Mark Sapiro

On 09/03/2018 06:13 PM, Paul Arenson wrote: > Hi again. I take it the lack of responses mean I should wait it out a little longer? It's of course up to you, but I recommend Mailman 3. There are still some rough edges, and there are a number of settings not yet exposed in Postorius, but we are working on it and it is quite usable today. > I was considering, as mentioned, Fed Forum (but not much help in setting up), Slack and Flock. Would all mean more work than I can afford. > > Which is why upgrading from Mailman 2 to 2 still seems like the best idea. > > We would then have the perfect upgrade to Mailman 2, where people could more easily find their topics (aided by a lot of nudging to be proactive in choosing the topic to post in and not doing thread hijacking). Do you mean Mailman 3? > I looked to see if there was anyone doing this sort of service. All I could find is someone doing their own hosting called https://mailman3.com/. mailman3.com is a Mailman 3 hosting service unaffiliated with the GNU Mailman project. > I would much prefer to upgrade my C-Panel installation of the lists, which by the way are here: > > https://gale-sig.org/mailman/listinfo/galemembers_gale-sig.org > https://gale-sig.org/mailman/listinfo/galeexec_gale-sig.org > > Any estimate on if/when I would be able to upgrade these c-panel forums (or possibly get someone to help me move them?) I suspect it will be some time before Cpanel offers Mailman 3. It is fairly straightforward to migrate an existing Mailman 2.1 list and it's archives to Mailman 3, but it requires access to the underlying Mailman 2 file system which you may not have in a hosted cPanel environment. See <http://docs.list.org/en/latest/migration.html> for more on migration. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 7 months

Re: 404 on fresh install (Debian11)

by David Newman

On 3/22/23 3:42 AM, thomas--- via Mailman-users wrote: > Hello, > very new to mailman3, I used to manage mailman2 on a Debian 10 server. > The server has been upgraded to Debian 11 and mailman2 disappear… > > I try fresh install of mailman3, prerequisite to data migration, but without success. > If some can help, I would be really greatful. > > Here is my path: > - `mailman3-full` install with apt. MySQL config since I have this DBMS The packaged version included with Debian 11 is out of date. You would be much better off installing Mailman3 and mailmanweb in a virtual environment using pip: https://docs.mailman3.org/en/latest/install/virtualenv.html https://docs.mailman3.org/en/latest/config-web.html dn > - `python3-pymysql` install with apt after seeing errors in logs > - Apache2 configuration (other virtual hosts are present) > > ```apache2 > <VirtualHost *:80> > ServerName newsletter.mydomain.tld > > Alias /static /var/lib/mailman3/web/static > Alias /favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico > > DocumentRoot /var/lib/mailman3/web/static > <Directory "/var/lib/mailman3/web/static"> > Require all granted > </Directory> > > ProxyPassMatch ^/static ! > ProxyPass / http://localhost:8001/ > ProxyPassReverse / http://localhost:8001/ > > ErrorLog ${APACHE_LOG_DIR}/newsletter_error.log > CustomLog ${APACHE_LOG_DIR}/newsletter_access.log combined > </VirtualHost> > ``` > > And now I have a 404 answer when consulting my http page. > > When trying to access `/static` sub-path, I get `Cannot serve directory /var/lib/mailman3/web/static/admin/: No matching DirectoryIndex found`. > > I also tried `ProxyPass / unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost` but also fails with `No protocol handler was valid for the URL / (scheme 'uwsgi')` > > I am a bit lost with that. > > Thanks for your help > _______________________________________________ > 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 dnewman(a)networktest.com

3 years, 1 month

Re: New messages not being archived

by Mark Sapiro

On 7/15/21 12:55 PM, Sarah H wrote: > > The log is mostly these three errors repeatedly with the same above wall of html between them, some of them end with (404) after the last html tag indicating url not found and browsing to them gives the same custom 404 page for postorius. The code is if result.status_code != 200: logger.error("HyperKitty failure on %s: %s (%s)", url, result.text, result.status_code) raise ValueError(result.text) > Jul 15 12:37:08 2021 (471314) HyperKitty failure on http://lists.client.org/hyperkitty/api/mailman/archive: So the above log entry should be followed by result.text and result.status_code. The next entry below is from the `raise ValueError(result.text)` What do you get from curl http://lists.client.org/hyperkitty/api/mailman/archive and what if you change the scheme in the base_url setting to https? > Jul 15 12:37:08 2021 (471314) Traceback (most recent call last): > File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message > url = self._send_message(mlist, msg) > File "/opt/mailman/venv/lib64/python3.6/site-packages/mailman_hyperkitty/__init__.py", line 210, in _send_message > raise ValueError(result.text) > ValueError: And this one below is is because of the above exception. > Jul 15 12:37:08 2021 (471314) Exception in the HyperKitty archiver: > > I was able to find (about 5000 lines up in the log for a single post attempt... it's a bit excessive to print the html response every error) this when I dug through instead of tailing the last 500 lines. > > [15/Jul/2021:12:37:06 -0700] "GET /3.1/addresses/sarah.h@email HTTP/1.1" 200 380 "-" "GNU Mailman REST client v3.3.2" > > and at the start of the block: > > [15/Jul/2021:12:37:03 -0700] "GET /3.1/lists/admin.lists.client.org/member/sarah.%40email HTTP/1.1" 200 516 "-" "GNU Mailman REST client v3.3.2" > Jul 15 12:37:05 2021 (471317) ACCEPT: <162637782380.3116.619498070458942231@sysname> These are from the Mailman REST API and are not relevant to your issue. -- 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

Re: Hyperkitty no longer archiving

by Mark Sapiro

First, my apologies for not taking note of your MAILMAN_ARCHIVER_FROM setting in your OP. On 11/22/22 08:52, Hirayama, Pat wrote: > Steve wrote: >> 2. Does settings.py have "from settings_local import *" in it? > > Yes. I assume that overrides the MAILMAN_ARCHIVER_FROM and other related settings defined at the top of the settings.py file? Or should I update settings.py based on what is in settings_local.py? Assuming the `from settings_local import *` is at the end of settings.py, anything defined in settings_local.py will override the definition in settings.py. There's no need to change settings.py. >> 3. Are there multiple copies of settings.py lying around? > > Well, there are these: > > ./usr/local/lib/python3.8/site-packages/rest_framework/settings.py > > ./usr/local/lib/python3.8/site-packages/postorius/doc/settings.py > > ./usr/local/lib/python3.8/site-packages/django_q/tests/settings.py > > ./usr/local/lib/python3.8/site-packages/django_extensions/settings.py > > ./usr/local/lib/python3.8/site-packages/mailmanclient/restobjects/settings.py > > ./usr/local/lib/python3.8/site-packages/example_project/settings.py > > > Only the last has MAILMAN_ARCHIVER_FROM defined in it, but I was assuming from the example_project subdirectory name that this was just a sample file, and besides, "from settings_local import *" is also set in it. Yes, those are all samples. The ``` ERROR 2022-11-22 00:25:40,365 7 hyperkitty.views.mailman Access to the archiving API endpoint was forbidden from IP 172.31.0.1, your MAILMAN_ARCHIVER_FROM setting may be misconfigured ``` message comes from https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/views/mailma… which only occurs if '172.31.0.1' is not in MAILMAN_ARCHIVER_FROM. Given that it is in MAILMAN_ARCHIVER_FROM as defined in settings_local.py, the only thing I can conclude is that the Django settings actually used is not the settings.py you think it is. I don't know offhand even what wsgi service is used in the docker container or how it is configured, but it needs to set its working directory to the directory containing 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 years, 5 months

Re: How to remove Held Unsubscriptions

by Mark

No joy. There is no menu entry for that page ( ".../unsubscription_requests") and when entering the URL manually I get: Page not found This page either doesn't exist, or it moved somewhere else. The menu item and page for ".../subscription_requests" display okay: Subscriptions pending approval (0) There are currently no subscription requests for this list. On 2024-01-06 04:35, Jered Floyd wrote: > I see these under "Subscription requests > Unsubscription requests", > or at the URI (matching your sample) > > https://lists.domain.com/postorius/lists/listname.domain.com/unsubscription… > > Does this menu entry appear for you? > > --Jered > > ----- On Jan 5, 2024, at 12:30 PM, Mark imark(a)posteo.net wrote: > >> Hi >> >> As a moderator I receive an email each day for "Held Unsubscriptions" >> for a subscriber that was unsubscribed by the Owner sometime ago >> (using >> "Mass operations"). >> >> +++++++++++++++++++++++++++++++ >> The listname(a)domain.com list has 1 moderation requests waiting. >> >> Held Unsubscriptions: >> User: bart(a)example.com >> >> Please attend to this at your earliest convenience. >> +++++++++++++++++++++++++++++++ >> >> There is nothing showing under "Subscription requests > Pending >> approval". >> >> Could anyone tell me how I can stop these email notifications? I have >> access to the mailman shell and the databases. >> >> Thanks, >> Mark >> >> >> _______________________________________________ >> 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 jered(a)convivian.com > _______________________________________________ > 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 imark(a)posteo.net

2 years, 3 months

Hyperkitty tracebacks: possible DB corruption?

by peter＠chubb.wattle.id.au

Hi Folks, Just recently I've started seeing backtraces from Django when trying to view old threads in hyperkitty. They say that more than one LastView is being returned, and at a later date cannot delete a LastView. I'm using the Debian-packaged hyperkitty and postorius, but this code hasn't changed from upstream. The backtraces come when a logged in used revisits a thread. So I see: Internal Server Error: /hyperkitty/list/devel(a)sel4.systems/thread/XP2GFYGXOXBC3QBKKZQLZ6STSHQHK6K2/ MultipleObjectsReturned at /hyperkitty/list/devel(a)sel4.systems/thread/XP2GFYGXOXBC3QBKKZQLZ6STSHQHK6K2/ get() returned more than one LastView -- it returned 2! Then later on I see: LastView.objects.delete(pk=del_id) ^^^^^^^^^^^^^^^^^^^^^^^ AttributeError: 'Manager' object has no attribute 'delete' Here are the backtraces: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 47, in inner response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 181, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/lib/view_helpers.py", line 137, in inner return func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/views/thread.py", line 162, in thread_index last_view_obj, created = LastView.objects.get_or_create( File "/usr/lib/python3/dist-packages/django/db/models/manager.py", line 85, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 581, in get_or_create return self.get(**kwargs), False File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 439, in get raise self.model.MultipleObjectsReturned( and Internal Server Error: /hyperkitty/list/devel(a)sel4.systems/2022/1/ AttributeError at /hyperkitty/list/devel(a)sel4.systems/2022/1/ 'Manager' object has no attribute 'delete' Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 47, in inner response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 181, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/lib/view_helpers.py", line 137, in inner return func(request, *args, **kwargs) File "/usr/lib/python3/dist-packages/hyperkitty/views/mlist.py", line 127, in archives return _thread_list(request, mlist, threads, extra_context=extra_context) File "/usr/lib/python3/dist-packages/hyperkitty/views/mlist.py", line 173, in _thread_list LastView.objects.delete(pk=del_id)

2 years, 1 month

Re: where to configure max_days_to_hold on MM3 GUI interface?

by Shashikanth Komandoor

Hello Mark, Thanks for helping me for moving ahead in my project. Troubling you again, I would like to put another request at you. As per your suggestion, I am trying to configure my list configuration through REST API for specially the parameter like max_days_to_hold as it is not available through interface and I am following the official links of mailman 3 i.e https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/listconf.html But I am getting "name is not defined" sort of errors as below: *>>> dump_json('http://localhost:9001/3.0/lists/ <http://localhost:9001/3.0/lists/>','ant(a)example.com/config <http://ant@example.com/config>',dict(display_name='My List'),'PATCH')Traceback (most recent call last): File "<stdin>", line 1, in <module>NameError: name 'dump_json' is not defined>>>* Actually I am new to REST API but hope this is the only issue that is preventing me to go ahead. Could you please help me by saying how should I handle this so that I should be able to configure *max_days_to_hold* of a list or multiple ? On Wed, Jan 29, 2020 at 11:20 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/28/20 8:42 PM, Shashikanth Komandoor wrote: > > > > But I could see that parameter value configurable on MM2 GUI > > interface in General Options but I don't see the same on the MM3 GUI > > interface. > > > There are many core settings not (yet) exposed in Postorius. > max_days_to_hold. is one of them. It can be set via `mailman shell` or > via the REST API > < > https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/rest.html#re… > >. > > -- > 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/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

6 years, 2 months

Mailman-users search results for query "Postorius"