Search results for "Postorius" - Mailman-users

Re: Fwd: Re: Removing a mail addresses and users

by Abhilash Raj

On Sun, Jun 14, 2020, at 12:45 PM, Allan Hansen wrote: > All, > > Thank you for your thoughtful responses to my call for a removal of the > core vs. Django disconnect. From your responses it appears that my > suggestion my issues were caused by the Mailman Core was not based in > reality. Instead, the issue is how Postorius interacts with the Core. > My apologies for overreaching, as the cause of my issues is not an > issue to me. Keeping Core a simple list manager is fine, if Postorius > is easy to use and does the expected. > > As a Subscriber, you are able to do switch emails in subscriptions from > your options page. The URL to which is displayed in the List's Summary > page when you are logged in. Yes, it requires an approval if the list's > settings are set to moderate but that is going to be fixed, see this > issue[1]. It is quite simple IMO to fix this one, if someone wants to > take this up. > > Well, it’s more than that. Based on the current setup, I have asked my > subscribers who want to change their subscription addresses to: > a. Create an account if you do not already have one. > b. Go to the user profile page. > c. Select ‘E-mail Addresses’. > d. Add the new e-mail to the user profile. > e. Wait for the verification notice and verify the new address. > e1. If it does not show send email to hansen(a)rc.org > <mailto:hansen@rc.org> to get the email verified manually. > f. Sign in to the account again and to the user profile (or refresh > the page if not signed out). > g. Select the new address as the primary address. > h. Click on ‘Manage Lists’ > i. For each list you are subscribed to: > i1. Select the list > i2. Click ‘List Options Page.’ > i3. Pull down the ’Select Email’ menu. > i4 Select your new email. > i5. Press ‘Change email used for subscription. > i6. When the moderator contacts you, explain that you are just > changing your email. > i6.1. If the moderator is late, send a reminder or send email to > hansen(a)rc.org <mailto:hansen@rc.org> to bypass the moderator. So, a-f is something we still always want to keep since we aren't going to deal with un-verified email addresses. Now, Primary Address is something interesting in Mailman 3, which wasn't utilized until now in Postorius. I recently added a new feature to Postorius which allows users to subscribe via their Primary Address and it switches the delivery address when you switch your primary address. You can play with how it looks at https://lists.mailman3.org (Mailman instance serving this list) where you will see "Primary Address (myprimaryemail(a)example.com)" as an option when subscribing/switching address. This is still somewhat new feature and there are gaps to it, but it will grow over time. For example, as as admin, you can only subscribe a User's address and not their Primary Address (from Mass Subscription page, or through the CLI commands). As a User, you are able to switch to using your primary address and then every time you switch your primary address, all your subscription shifts to that new address without any extra steps. Also, I just created a fix for i6[1], so switching email addresses won't require approvals anymore. I am still debating if this should be configurable by list owners. [1]: https://gitlab.com/mailman/postorius/-/merge_requests/532 > > Most people choke on these instructions, so I have unfortunately > resorted to just asking them to subscribe the new address and forget > about the old. This is not good for our reputation when the old > addresses start bouncing. So, in more detail: > > I would like to ask my subscribers who want to change their address to: > a. Create an account if you did not already have one. > b. Go to the user profile page. > c. Select ‘E-mail Addresses’. > d. Select an existing address e-mail listed the user profile. > e. Press new button ‘Change address’. > f. When page refreshes, enter the new e-mail address. > g. Press ‘Apply.' > d. Wait for the verification notice. > d1. If it does not show send email to hansen(a)rc.org > <mailto:hansen@rc.org> to get the email verified manually. > > In other words, in addition to ‘Make Primary’ and ‘Re-send > Verification’ and ‘Remove’, another button says: ‘Change Address’ or’ > ‘Replace Address’ or some such. > > This button brings up another page that looks the same, but instead of > ‘Add E-mail Adress’ is says : Enter New E-mail Address’ > and instead of ‘Add E-mail’ is says: ‘Apply’. Then the page refreshes > back to the original page, but the new address is now > replacing the old address. Optionally, it can show the old address > still with a ‘pending change’ until verification. I am still thinking about a few implementation details of this one, I've created an issue[2] [2]: https://gitlab.com/mailman/postorius/-/issues/435 I am thinking we could minimize changes by retaining the same workflow for adding and verifying new address, but add a new workflow of some sort to switch subscriptions to a new address with a single button click. This should simplify the Loop of going to each option page and switching addresses. Finally, the old address can be removed. Another train of thought is that when you Delete your email address, you get an option to switch all the subscriptions on that address to some other address. I could do this by adding a page after you click on "Remove" button. Although, this would restrict the ability to switch subscriptions by only deleting the original one, which I don't want. Maybe I'll end up implementing both of these. What do others think about this? > > Further, when the new address is verified, all lists get updated with > the new address replacing the old > address and all settings associated with the old address are now > associated with the new address. No moderator or admin > involvement needed (other than d1). The fix[1] I mentioned above should already resolve this issue. > > You are able to sign in via web and manage your email and > subscriptions. The preferences also work exactly how you described > above where the lower level override the default and/or upper level > settings. > > To some extent that is true, Abhilash, and I appreciate that. The above > (address change) is a missing piece in that picture and I look forward > to seeing it added, if you have time. > > Yours, > > Allan Hansen > hansen(a)rc.org > > > > > > On Jun 14, 2020, at 0:19 , Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > > > > Mark Sapiro writes: > > > >> Then the people who developed the web based management UI (Postorius) > >> and archive UI (HyperKitty) chose to develop those within a Django > >> framework and Django has its own concept of User separate from Mailman > >> Core and that is where the disconnect occurs. > >> > >> It's not that Mailman Core lacks what you want. It's that Django doesn't > >> use it. > > > > I think that's mostly right, in terms of the features that users miss. > > However, as far as I know, Mailman core does lack facilities for > > identification, authentication, and authorization of connections to > > the REST API. And that means that the front ends have to handle > > this. I would guess that's why the web interfaces are built around > > Django user authentication. > > > > I think it would be possible to have somewhat tighter integration > > between the Django "web users" and the Mailman core User objects, but > > it's not necessarily going to be trivial. > > > > I see that Abhilash is pretty optimistic, but I fear this this is > > going to be a long-tail situation where we're going to be seeing core > > user vs. web-gui user integration issues in 2030 (maybe by then only 1 > > every 450 days ;-). I have some ideas, maybe in a couple weeks I can > > sketch them out. > > > > Steve > > _______________________________________________ > > 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/ > > _______________________________________________ > 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, Abhilash Raj (maxking)

5 years, 2 months

Database running VERY hot

by Darren Smith

Hello all, We had an old installation of Mailman 2.1 across three servers with over 32,000 mailing lists on them. Due to circumstances beyond my control, we had to shut them down and quickly set up Mailman 3 on a new server. We have Mailman3 set up on a single server this time, as we were having problems with a 3-server setup and Hyperkitty and archives. Long story short, it is up and running, and our users are starting to come back. However, we do not have very many users hitting Postorius and Hyperkitty yet, and we are seeing a distressing number of 504 gateway timeouts. We noticed that there is a significant number of queries to the API whenever hitting Postorius's front page to load the mailing lists, and then on every load. It looks as if it makes a single call to the API to get information about a single list, and does this 10 times - once for each list - to render the page. This gets much worse when users set the view to 200 per page, as they are inclined to do with 32,000 mailing lists... What we've done, actually, is to override the front page and point the users to a different set of static pages where we have all of our lists categorized and searchable, and when they find the list they are looking for, we have a link back to postorius. It has taken a lot of the stress off of the server. However, I still see where the database at times can run VERY hot. We have set up this server to run with PostgreSQL. When I do a ps aux | grep postgres, I find a lot of processes that have been spawned to take care of mailman - a dozen or so. However, one of the threads is taking up about 85% of the load, another thread about 14%, and little dribbles here and there from the rest of the threads. Here are the questions: 1) Has anyone run into problems like these? I would think that maybe this is an issue having so many mailing lists, but honestly there aren't that many people using the system yet. It is going to ramp up as the users realize that we are live again, but we aren't getting that much traffic. 2) Is there any configuration that I can set, especially with regards to the database, so that it can be used more efficiently and not throttle through one or two threads? Please let me know what further information I can provide. Thanks in advance for any help or advice! Silas

7 years, 5 months

Re: Verification Failed Error

by Odhiambo Washington

Hi Abhilash, Can I use the instructions at https://github.com/maxking/docker-mailman with a MySQL database instead of PostgreSQL? I am looking at the following block in docker-compose.yaml: database: environment: POSTGRES_DB: mailmandb POSTGRES_USER: mailman POSTGRES_PASSWORD: mailmanpass restart: always image: postgres:9.6-alpine volumes: - /opt/mailman/database:/var/lib/postgresql/data networks: mailman: ipv4_address: 172.19.199.4 I'd like to change those to use MySQL. Maybe you should also add an example on the site for these?? On Fri, 21 Dec 2018 at 03:25, Abhilash Raj <maxking(a)asynchronous.in> wrote: > > > On Thu, Dec 20, 2018, at 4:05 PM, brian(a)emwd.com wrote: > > Abhilash Raj wrote: > > > It should be pointing to Exim running on host, so > > > > > > EMAIL_HOST = 172.19.199.1 > > > > That fixed the network not found error. Thank you for your help there. > > > > Now I am back to the verification error: > > > > "smtplib.SMTPRecipientsRefused: {'brian(a)emwd.com': (550, b'Verification > > failed for <postorius(a)host.name.com>\nUnknown user\nSender verify > > failed')}" > > > > I am at a lost on how to get exim to allow mail sent from > > postorius(a)host.name.com. Obviously host.name.com is the mm3 domain that > > I am using. > > A quick search says that Exim is trying to verify that ` > postorius(a)host.name.com` > is a real mailbox (which I am assuming it is not), and rejecting the email > coming > from Postorius. > > You probably have > > verify = sender > > somewhere in your exim.conf, which is causing this. You can either modify > the > > DEFAULT_FROM_EMAIL > > in your settings_local.py so that it is a real address that Exim can > verify, or, > you can remove verify = sender from your Exim configuration. 2nd option > might > not be the best if you want to properly combat spam. > > Exim experts would be able to help you better with this. > > > > > Brian > > _______________________________________________ > > 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, > Abhilash Raj (maxking) > _______________________________________________ > 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/ > -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

6 years, 7 months

Re: Mailman3 not working following distribution upgrade from Debian 10 to 11.

by gordon＠dickens.com

Thanks Mark! Here is the Traceback from the error: Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.9/site-packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/opt/mailman/venv/lib/python3.9/site-packages/django/core/handlers/base.py", line 115, in _get_response response = self.process_exception_by_middleware(e, request) File "/opt/mailman/venv/lib/python3.9/site-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailman/venv/lib/python3.9/site-packages/django/views/generic/base.py", line 71, in view return self.dispatch(request, *args, **kwargs) File "/opt/mailman/venv/lib/python3.9/site-packages/postorius/views/generic.py", line 74, in dispatch return super(MailingListView, self).dispatch(request, *args, **kwargs) File "/opt/mailman/venv/lib/python3.9/site-packages/django/views/generic/base.py", line 97, in dispatch return handler(request, *args, **kwargs) File "/opt/mailman/venv/lib/python3.9/site-packages/postorius/views/list.py", line 326, in get primary_email = set_preferred(request.user, mm_user) File "/opt/mailman/venv/lib/python3.9/site-packages/postorius/utils.py", line 64, in set_preferred primary_email = EmailAddress.objects.get_primary(user) File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/managers.py", line 30, in get_primary return self.get(user=user, primary=True) File "/opt/mailman/venv/lib/python3.9/site-packages/django/db/models/manager.py", line 82, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File "/opt/mailman/venv/lib/python3.9/site-packages/django/db/models/query.py", line 419, in get raise self.model.MultipleObjectsReturned( Exception Type: MultipleObjectsReturned at /mailman3/lists/testing.dickens.com/ Exception Value: get() returned more than one EmailAddress -- it returned 3!\ Thanks for your help! Gordon

3 years, 5 months

Help request, almost got it going, but ....

by Claus-Justus Heine

First: thanks for all those development work, I am aware of the fact that this is free software and most of the development probably happened in someones spare-time. I have some problems: - I tried to install mailman v3. "Read the (non) docs" was of little help, but I got to some partly success following the commands in the scripts in the docker image at https://github.com/maxking/docker-mailman Things seemed to work out, I generated a test-list "Playground" and now I am just in the progress to click through all the configuration options in the the postorius Web-GUI. So far so good Now I read the "Message Acceptance" tab AND here is the problem: Seemingly, at some point in the deep dungeons of the source code the "Acceptable aliases" Text-Box is not interpreted correctly. Specifically, at the start it contains the string [] When then changing something int the "Message Acceptance" tab, an error shows up in the web-page (but no-where in the logs) "An error occured: []" and the bogus [] is restored. I tried to dig into the source code, and well, the data source of the text-field is an array or list of acceptable email-adresses. But seemingly finally at some point in the source code an empty list is not converted to the empty string, but to the string []. I can get rid of the error message "An error occured: []" by inserting an email-at '@' at just some place in the input box, this yields (clicking "Save changes" again and againg ...): [u"[u'@']"] [u'[u\'[u"[u\\\'@\\\']"]\']'] [u'[u\'[u\\\'[u\\\\\\\'[u"[u\\\\\\\\\\\\\\\'@\\\\\\\\\\\\\\\']"]\\\\\\\']\\\']\']'] and so on. Unfortunately, I did not find the location of this bug, although I was finally able to add some "foobar" string to the already bogus web-output. Any help would be appreciated. BTW: * where is the bug-tracker for mailman3? * The documentation is really, well, close to non existent. Personally, I think the name of the URL "read-the-docs" is almost cynical. Guess I give up on it, it just does not seem to be ready for production. This was (following the docker stuff at githb) with Pythong3: mailman==3.1.0 mailman-hyperkitty==1.1.0 Python2: mailmanclient==3.1.0 postorius==1.1.0 hyperkitty==1.1.1 django-mailman3==1.1.0 Here I realize a slight version difference between the hyperkitty stuff. But this is a bug in postorius. So what. Thanks for any help, cheers Claus -- Claus-Justus Heine himself(a)claus-justus-heine.de http://www.claus-justus-heine.de/ Schatzmeister der Camerata Academica Freiburg e.V. --- www.cafev.de

7 years, 11 months

120 gmail users removed from lists !

by Stephen J. Turnbull

elemac(a)free.fr writes: > Hello, on 15th October, 120 users with gmail address where suddenly > removed from lists in mailman3, something changed in google ? Google is evil, who knew? Google decided to publish a DMARC policy of "p=none". This announces to the world that you have to decide for yourself whether to accept mail from Gmail with a broken DKIM signature from gmail.com. Gmail has decided that they will not accept such email from themselves, even though they know more about the sender than anyone else, and even have access to the original sender copy. Mark has a patch that applies your preferred DMARC mitigation to Gmail authors unconditionally. I think it's in the new version just released 3.3.9, so you can upgrade. The name of the variable is dmarc_addresses, and in Postorius it will be in the same settings group as other DMARC settings, with a similar tag. If for some reason you strongly prefer not to upgrade immediately but want this feature, it's commit #8532f751b6b8bfee3210c1327d755756f99d99ac (you can shorten that to 8532f). I do not recommend this. It probably is independent of other changes in 3.3.9 from other releases. But if not you could have issues. I think you also need the patches in Postorius, but I don't think they've been released yet. "Coming soon" as they say. The relevant commit is #770add1ebf27fd335c675607f26bb8f7cf313ddd, If you search back in the archives, I think Mark posted a link to his original patches. Steve

1 year, 9 months

Re: Error -- postorius Un-handled exception

by Mark

> > The issue you're dealing with in that case is this change in > > PostgreSQL-15 discussed in this blog: > > > https://www.cybertec-postgresql.com/en/error-permission-denied-schema-publi… ********************** > If you have a Mailman-only host, with a Mailman-only PostgreSQL, or > The Cabal of equally responsible maintainers are the only people who > work on the Postgres cluster, the two approaches are basically > equivalent. > > My take is that the default "right thing" is to transfer ownership of > the 'mailman' database to the 'mailman' user, and use "GRANT ALL ON > SCHEMA public TO fred" in the case that you don't want to give "sudo > mailman" to Fred. > > Rationale: I believe there are a number of things that the 'postgres' > user can do that other users cannot, and you probably don't want > random contractors or new volunteers to have those privileges. On the > principlee that 'postgres' should only do those things that only > 'postgres' can do, you want to make the 'mailman' user the owner of > the 'mailman' database (and 'mailmanweb' too if you go that route). > Then if you have a user 'fred' who may be working on both mailman and > non-mailman databases in a session, then instead of giving sudo > mailman to Fred, 'mailman' can grant all on schema public in mailman > to 'fred'. > > It's a really fine difference, and probably will matter to almost > nobody running Mailman 3. I do think > > user 'mailman' owns the 'mailman' database > > is conceptually simpler than > > user 'postgres owns the 'mailman' database and 'mailman' has ALL > privilege on the PUBLIC schema > > Right? ************************* === From the blog === ...almost any privilege escalation attack on a PostgreSQL database requires the attacker to create malicious objects. ... The public schema is the perfect vector for such a privilege escalation attack. ... In version 15, only the database owner can create objects in the public schema. === The user mailman has its plain text password written into the mailman.cfg file. If that is a potential weakness, would making mailman NOT the owner reduce vulnerability by a degree (in that objects could not be created in the public schema by using mailman's credentials)? Of course I would have a whole world of other problems if those credentials were misused, so I guess it's a bit theoretical anyhow.

1 year, 6 months

Re: Your Dashboard

by Allan Hansen

All, Our site has over 50 lists and several moderators are responsible for multiple lists. In addition to a dashboard like described here I would like to have a ‘comment’ field next to each request, so tha the moderator can keep track of the status of each. Our approval process involves multiple steps. Time to visit gitlab? Yours, Allan Hansen hansen(a)rc.org > On Feb 11, 2020, at 12:26 , Mark Sapiro <mark(a)msapiro.net> wrote: > > On 2/11/20 11:00 AM, Mark Dadgar wrote: >> On Feb 11, 2020, at 10:32 AM, Torge Riedel <torgeriedel(a)gmx.de> wrote: >>> everytime I receive a mail for moderation it says: >>> >>> At your convenience, visit your dashboard to approve or deny the >>> request. >>> >>> So, I am wondering where this "dashboard" might be. We are managing 11 different lists (small scenario I think) and currently we have to navigate to each list and its page of mails to moderate. > > > There's no overall dashboard per se. The message actually refers to > whatever web UI you use to manage the list. The default template for > this message is non-specific because it comes from Mailman core, and > core doesn't know if you are using Postorius or some other web > management system or non at all, and even if it were to assume > Postorius, it doesn't know the URL. > > >>> I like the idea of a "dashboard" were you can see a summary of mails to moderate and other stuff to have an eye on. And directly do this from this dashbard. Which is convenience. >>> >>> If it is already there, where do I find it? If not, do others also find such a dashboard helpful? > > > As I said, there is no overall dashboard in Postorius, just the > individual list management pages. > > >> This is actually a regression from Mailman 2.x. That train included a link to the relevant dashboard in the email, which I miss terribly. > > > I explained above why this is the case, but you can fix it. You do so by > making a sitewide template for this message. In the case of this list, > we have a template in Mailman's var/templates/site/en/ directory (the > default directory for sitewide english templates. This template is named > list:admin:action:post.txt and its content on this site is: > >> As list administrator, your authorization is requested for the >> following mailing list posting: >> >> List: $listname >> From: $sender_email >> Subject: $subject >> >> The message is being held because: >> >> $reasons >> >> At your convenience, visit >> https://lists.mailman3.org/mailman3/lists/$list_id/held_messages > > > Of course, in your case the <https://lists.mailman3.org/mailman3/> part > of the URL will be different. > > See > <https://wiki.list.org/DOC/Mailman%203%20installation%20experience#Templates> > for the other templates I also install. > > You can also put domain specific templates in > var/templates/domains/$domain/$lc/ which override site templates for the > domain and list specific templates in var/templates/lists/$list_id/$lc/ > which override site and domain templates for the list, and you can also > set list templates via 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/

5 years, 6 months

moving list from mm3 -> mm3

by Jens Günther

Hey there, I'm still trying to figure out, how to move a bunch of lists from one mm3-instance to another. If somebody has a working solution, I would be really glad to hear from it. I came across this thread, but I don't think it tackles my question: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… (or maybe I missed the right parts) We have equal setups and versions: - maxxking docker install 0.4.5 - Core 3.3.8 - API 3.1 - Postorius 1.3.8 ## Config So I found the possibility to get the config of a list via REST-API: curl -u restadmin:restpass localhost:8001/3.1/lists/$short.$domain/config | jq > short.domain This is a nice collection of the configuration of a certain list. Does anybody know how I would get this data back to the newly created list in the second working mm3-instance? Shouldn't it be possible via POST command? I thought of something like: curl -u restadmin:restpass -d @short.domain -H "Content-Type: application/json" localhost:8001/3.1/lists/&short.&domain/config But it returns {"title": "405 Method Not Allowed"} and I don't know where to look in the docs, since it shows almost always a way through mailman shell. Here I found something about POST: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… -> but how would it work exactly? ## Members, moderators, owners To export all members I normally run within mm-core-container as user mailman the following command: mailman members &short.&domain > &short.txt To fill them back in, it can be done in Postorius (or is there a way through API?). What I would love to know is how to get out Owners of the corresponding lists and reimport them in the new one (which will be the same at the end :-D but different instance). ## registered users This part is somehow tricky, since I have no clue how to do it. Some of the mailinglist-admins don't want to bother their list-owners again with registering newly on the other system. Is there a way to export all users (I think I found them in the DB in the table auth_users, somehow in combination with account_emailaddress) and get them over to the new instance (actually I just need part of them, but that's another question that I might solve lateron on my own). Maybe the answer is already here: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… -> but can somebody help to get this working (import/export)? Thank you in advance, I hope it's not too much or too nooby :-) Jens.

1 year, 8 months

Hyperkitty error - not archiving

by Odhiambo Washington

I am seeing the error below and wondering what's the cause: Jul 25 13:35:05 2025 (944) Could not archive the message with id < CO1PR06MB798076961F096CAA4DB9A2FCBB59A(a)CO1PR06MB7980.namprd06.prod.outlook.com > Jul 25 13:35:05 2025 (944) archiving failed, re-queuing (mailing-list testlist.my.domain, message < CO1PR06MB798076961F096CAA4DB9A2FCBB59A(a)CO1PR06MB7980.namprd06.prod.outlook.com >) Jul 25 13:35:05 2025 (944) Exception in the HyperKitty archiver: <!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <meta name="viewport" content="width=device-width, initial-scale=1"> <title>Server Error</title> <link rel="shortcut icon" href="/static/postorius/img/favicon.ico"> <link rel="stylesheet" href="/static/postorius/libs/bootstrap/css/bootstrap.min.css"> <link rel="stylesheet" href="/static/django-mailman3/css/main.css"> <link rel="stylesheet" href="/static/postorius/css/style.css"> </head> <body> <div class="container"> <h1>Server error</h1> <div class="alert alert-danger">An error occurred while processing your request.</div> </div> </body> </html> Jul 25 13:35:05 2025 (944) Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.11/site-packages/mailman_hyperkitty/__init__.py", line 158, in _archive_message url = self._send_message(mlist, msg) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.11/site-packages/mailman_hyperkitty/__init__.py", line 228, in _send_message raise ValueError(result.text) ValueError: -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

3 weeks, 1 day

Mailman-users search results for query "Postorius"