Search results for "Postorius" - Mailman-users

Re: hello， Discussion on how to subscribe to themailing list

by Stephen J. Turnbull

朱超 writes: > 1. It is not the MTA that refuses to send emails because the > recipient's mailbox is too long, but the MUA that refuses to > send the email because the recipient's mailbox is too long. That's still non-conforming to RFC 821, published in 1982. Seriously, those mail clients are garbage and I have no sympathy for their users. We're certainly willing to make some changes to Mailman to make things a little easier for mailing list owners who have to deal with such users, but there's no excuse for using those MUAs in 2023. > https://www.example.com/mailman3/lists/$list_id/confirm/?token=$token, > but he reported 404. If you mean that literally, of course it did. example.com, and its siblings in the org, net, and edu domains, as well as all subdomains, are domains reserved for examples in documentation. They all resolve to the same IP (owned by IANA), which simply provides a web page explaining what those domains are for. There's no Mailman there. :-) For that to get a response from Postorius, at minimum you need to substitute your Mailman web host for "www.example.com", and the list's ID (usually the same as the posting address with "." substituted for the "@") for $list_id. You may also need to change the URL path, depending on the top-level urls.py you use for Postorius. > 2. It is recommended to modify postorius, in order to keep the > logic function of the underlying mailman-core unchanged, More important than the detailed functions of mailman-core are the original requirements and design. Core should handle email (both in and out), and Postorius should handle web requests. It's asking for trouble to have core send mail to confirm subscription requests by mail, and Postorius to send mail to confirm subscription requests by web. Among other things it violates "Don't Repeat Yourself": if we (or you) change the confirmation template in core, we (or you) need to also change the confirmation template in Postorius. But it's very easy to forget, and an annoyance for reviewers to check. It's possible that the other core devs will overrule me on this, but you shouldn't hold your breath waiting for that. I've been very good at channeling the consensus of the devs for around 20 years now. :-) Steve

2 years, 11 months

Re: Adding Mass Subscribe custom template error

by Mark Sapiro

On 1/28/25 12:31, Arte Chambers via Mailman-users wrote: > > I'm getting the following error when using mass subscription on a testing > list with a custom template loaded for [list:user:notice:welcome] > ``` > HTTP Error 400: HTTPConnectionPool(host='localhost', port=8000): Read timed > out. (read timeout=5) > ``` It appears you are setting the template in Postorius and there is an issue with your setting for POSTORIUS_TEMPLATE_BASE_URL. It looks like this is something like ``` POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000/' ``` and that connection is timing out. Try setting just the scheme and host for access to Postorius. I.e., if you access Postorius at a URL like https://www.example.com/mailman3/, try ``` POSTORIUS_TEMPLATE_BASE_URL = 'https://www.example.com/' ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 2 weeks

Re: Moderation action "None" is misleading

by Mark Sapiro

On 2/4/25 02:51, Markus Grandpré wrote: > Dear List, > > I find the use of the term 'None' (or 'Kein' in the German translation; > see attachments) in the 'Moderation action' column of the member list > misleading, as the term suggests that no moderation action is applied to > the respective member. > > However, this is not necessarily the case. If you check a member’s > "Administration options / Moderation" setting, a moderation action, such > as "Moderation" or "List default", may be in effect. This is https://gitlab.com/mailman/postorius/-/issues/577 fixed in Postorius 1.3.9 by https://gitlab.com/mailman/postorius/-/merge_requests/811 See the UI changes at https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-9 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 1 week

Hyperkitty stuck files

by zoltan＠circle-interactive.co.uk

Hi, I have a mailman3 setup in venv with python 3.11.2 mailman 3.3.9 mailman-hyperkitty 1.2.1 I feel I have read a lot about issues with stucked files in spool directory still I am not able to proceed with debugging in my case. Ideas would be welcome and appreciated. Thanks This is the error in archiver.log Jul 09 10:56:12 2024 (47531) HyperKitty archiver processing queued filebase: 1720522497.980487+a88492922feca24ced15594a5ec16556195 6f3ad Jul 09 10:56:12 2024 (47531) hyperkitty archiver: sending message <B9E91239-ED71-4CC6-8FFF-3308C5C4DE2E(a)me.com> Jul 09 10:56:12 2024 (47531) HyperKitty failure on http://127.0.0.1:8000/archives/api/mailman/archive: <!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> (500) Jul 09 10:56:12 2024 (47531) Could not archive the message with id <B9E91239-ED71-4CC6-8FFF-3308C5C4DE2E(a)me.com> Jul 09 10:56:12 2024 (47531) archiving failed, re-queuing (mailing-list act.lists.contextualscience.org, message <B9E91239-ED71-4CC6-8FFF-3308C5C4DE2E(a)me.com>) Jul 09 10:56:12 2024 (47531) 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 09 10:56:12 2024 (47531) 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: <!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>

1 year, 6 months

Re: Held messages page not rendering the message

by Andreas Schamanek

On Sat, 25 Mar 2023, at 17:32, Mark Sapiro wrote: > On 3/25/23 10:01, mike-mailman(a)earth.li wrote: >> >> This seems like maybe its a CSS issue? The class of the held-message-modal >> is "modal fade show" but I am not sure where that is or should be defined >> (or even if I'm looking at completely the wrong thing. >> >> Anyone able to suggest where to look? > > This is bootstrap. See > https://www.w3schools.com/bootstrap/bootstrap_modal.asp > > One possible issue is if you have older bootstrap cached in your browser it > could cause problems. It's unlikely considering you've tried different > browsers, but try clearing your browser cache. I had the exact same issue. As you guessed, Mark, it was related to bootstrap, though not from the browser cache but a mixup of versions served by the server. Also thanks to your research, Mike, I found that my Apache server has Alias /mailman3/static /var/lib/mailman3/web/static /var/lib/mailman3/web/static included a directory "postorius" which served bootstrap.min.css v3.3.5 whereas on my server v4.0.0 is included in python3-django-postorius 1.3.4-2+deb11u1 cd /var/lib/mailman3/web/static mv postorius postorius.bak ln -s /usr/share/python3-django-postorius/static/postorius fixed it for me. There's also a Debian bug report for it: https://bugs.debian.org/1010273 -- -- Andreas :-)

2 years, 9 months

postorius / adjusted settings menu

by Andreas Barth

Hi together, I want to adjust the settings menu to reduce to the options really needed. The easiest way would be to edit src/postorius/views/list* but I don't think that's a good idea. So what comes to my mind is to have some variable in the configuration that contains the menu items and - if set - the submenus. E.g. the following: { 'list_identity': ['!gateway_to_mail', '!gateway_to_news', '!linked_newsgroup', '!newsgroup_moderation', '!nntp_prefix_subject_too' ], 'automatic_responses', 'alter_messages', 'dmarc_mitigations', 'digest', 'message_acceptance', 'archiving', 'subscription_policy', 'bounce_processing' } would express: default menu and just remove the mentioned items. Of course, something like ['advertised', 'description', 'info', 'display_name', 'subject_prefix'] would work as well. Resorting should also be possible, so something like { 'list_identity': ['advertised', 'description', 'info', 'personalize'] } would give a very small list of items to select from. What do you think about the idea? Andi

4 years, 10 months

Re: Changes in Django admin interface are not syncing to postorius gui /database

by Odhiambo Washington

On Mon, Nov 11, 2024 at 3:17 PM Ulf R. <ulf.rapphahn(a)offis.de> wrote: > Thank you (also for Odhiambo) > Now remains one question: We have a (internal) Active Directory (AD) > Authentication for Mailman3. > So everyone who wants to work as an owner nor moderator must be an AD-User. > In hyperkitty I am able to assign these list rights directly to > AD-Loginnames. > With the logic above I have to assign these rights in postorius too by > assining the mail address of the users AD-Account? (I see no AD-Data here). > Or would it works to assing the mail address of the users AD-Account first > an then the allocation will automaticly synced to hyperkitty - maybe using > the mail address as key? > What would be the best practice for owner/moderator user management? > Thank you! > Hi, TBH, I am clueless about MM3 integration with LDAP/AD. Google leads me to a feature request: https://gitlab.com/mailman/django-mailman3/-/issues/27 But the Devs have the final say on the available possibilities. -- 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]

1 year, 2 months

Re: Installing MM3 requires Django<1.11

by Mark Sapiro

On 04/12/2017 02:22 AM, Henrik Rasmussen wrote: > Two questions regarding Mailman 3 installation: > > 1) > The Mail server setup at http://docs.mailman3.org/en/latest/devsetup.html#set-up-a-mail-server isn't described yet. Instead it refers to https://docs.djangoproject.com/en/1.10/topics/email/#topic-email-backends, but it doesn't say which file I have to change. That link doesn't belong there. Mailman doesn't use Django to send mail. > According to https://www.webforefront.com/django/setupdjangoemail.html the file is called settings.py, but the only settings.py I can find at this stage is the /opt/mailman/postorius/example_project/settings.py file. > > According to http://docs.mailman3.org/en/latest/devsetup.html#set-up-and-run-postorius, "Postorius and HyperKitty both come with example_project directories with basic configuration so you can try them out. For this tutorial, however, we'll be using a project that combines both instead.". > > In what file should I change the mail settings then? Nothing in <https://docs.djangoproject.com/en/1.10/topics/email/#topic-email-backends> or <https://www.webforefront.com/django/setupdjangoemail.html> is relevant to Mailman. A more appropriate discussion is at <http://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html> > 2) > While installing Hyperkitty*) I got the error message "Django 1.11rc1 is installed but Django<1.11 is required by {'django-haystack'}". > > As I have slavishly followed the installation guide including http://docs.mailman3.org/en/latest/devsetup.html#set-up-django-mailman3, I wonder why a non-supported Django version was installed. > > *) http://docs.mailman3.org/en/latest/devsetup.html#set-up-and-run-hyperkitty This is an issue. The various setup.py files for django-mailman3, hyperkitty and postorius all have Django>=1.8 as a requirement. Only postorius also has Django<1.11. django-mailman3 and hyperkitty should have that restriction too. I have submitted <https://gitlab.com/mailman/django-mailman3/issues/4> and <https://gitlab.com/mailman/hyperkitty/issues/128> 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, 8 months

Re: Postorius permissions granularity

by Liam Reilly

Odhiambo Washington wrote: > On Thu, Dec 11, 2025 at 12:07 PM Liam Reilly <l.reilly(a)ucl.ac.uk> wrote: > > The issue is we don't want first line support staff to have superuser > > permissions, just the ability to assist end user list owners by being able > > to administer all lists. So something that is lower level than full > > superuser would be ideal. > > I'm considering a cron job that adds a web account as Owner to all lists > > but this feels like a bit of a bodge. > > I see. The permissions that can be granted in relation to Postorius are > quite limited. > PS: Is it possible that you could retain content that comes in the form of > responses to your posts, so the hierarchy is maintained? You seem to be > deleting everything, which make your post look like a new one, except for > the subject. > -- > 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] Apologies, I have been using the "Reply" button in the UI and have not been quoting the post I'm replying to. Does it look better now?

1 month

KeyError: 'get_requests_count' after an upgrade

by Guillermo Hernandez (Oldno7)

I've just upgrade mailman 3 installation following Mr. Sapiro advice: did a pip install --upgrade django-mailman3 hyperkitty mailman mailmanclient mailman-hyperkitty postorius I did a "python3 manage.py migrate" after, too. And all seemed to run well. All the lists showed in postorius via web, but when I try to accesss into one of them the browser shows an error. In the log you can see: *-*-*-*-*-*-* Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 119, in __getattr__ return self._get(name) File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 86, in _get raise KeyError(key) KeyError: 'get_requests_count' ... (And after all the traceback lines) AttributeError: 'MailingList' object has no attribute 'get_requests_count' *-*-*-*-*-*-*-* The lists seem to be distributing messeages well.. but I cannot acces via web administration (django/postorius) Can anyone point me in the right direction to solve this, please?

4 years, 11 months

Mailman-users search results for query "Postorius"