Search results for "Postorius" - Mailman-users

Re: Setting moderation_action when approving a message from a non-member fails

by Mark Sapiro

On 6/13/23 05:15, Tom Smyth wrote: > > When a message is held due to it being from a non-member, I notice that > Mailman creates a non-member record for the sender automatically. This is > great! > > But if I try to set their moderation action while approving the message in > Postorius, I get: > > Failed to set moderation action: xxx(a)gmail.com is not a member address of > xxx(a)xxx.org > > Is this expected? I would like to be able to set the moderation action for > the non-member that has already been created. > > I am on Postorius v1.3.2. This is <https://gitlab.com/mailman/postorius/-/issues/448>, apparently filed by you, fixed in Postorius 1.3.4 by <https://gitlab.com/mailman/postorius/-/merge_requests/558>. Until you upgrade, you will have to set the non-member's moderation action separately from handling the held message. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

More Mailman releases!

by Abhilash Raj

Hello Everyone, I am pleased to announce several new releases for GNU Mailman project. Thanks to all the contributors for making these releases possible! 1. Postorius 1.3.10 [1] 2. Hyperkitty 1.3.8 [2] 3. Django-mailman3 1.3.10 [3] 4. Mailman-web 0.0.7 [4] All the releases are published to PyPI and you can find links to all the PyPI projects: https://docs.mailman3.org/en/latest/ A full list of change logs are available below: [1]: https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-10 [2]: https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-8 [3]: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst [4]: https://gitlab.com/mailman/mailman-web/-/blob/master/README.rst Do note that for Postorius, I released 1.3.9, but I forgot to update dependency metadata to require `django-mailman3>=1.3.10` (which is required for the new bootstrap 5 upgrade across packages) and so I also released Postorius 1.3.10 just after. Installation documentation is available at https://docs.mailman3.org/en/latest/install/install.html and if you are upgrading an existing virtualenv install you can refer https://docs.mailman3.org/en/latest/upgrade-3.2.html If you find any issues, you can report them at the respective bug tracker for the projects. The links to issue trackers are available at https://docs.mailman3.org/en/latest/. Finally, similar to Mailman Core, note that PyPI doesn't accept signatures anymore so each packages' release page now has the tarball uploaded to them along with the signature: Django-mailman3: https://gitlab.com/mailman/django-mailman3/-/releases/v1.3.10 Hyperkitty: https://gitlab.com/mailman/hyperkitty/-/releases/v1.3.8 Postorius: https://gitlab.com/mailman/postorius/-/releases/v1.3.10 Mailman-web: https://gitlab.com/mailman/mailman-web/-/releases/0.0.7 -- thanks, Abhilash Raj (maxking)

1 year, 7 months

Re: Problems getting started with postorius

by Mark Sapiro

On 11/13/24 16:46, Alain D D Williams wrote: > > I eventually tracked it down. The problem was that I had signed in with an > account "addw@localhost". That, for some reason, failed validation above. > I hacked the database and changed to "addw(a)localhost.localdomain" and creating > the new domain worked. > > I could send email to addw@localhost - so at the MTA level it is correct. > > So please can the initial account creation do the same validation as does > adding a new domain. Mailman doesn't allow local, unqualified addresses, see https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/email/validate… and https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/emai… On the other hand, Account creation/validation is done by django-allauth over which we have no control. > I have looked but cannot find any documentation on postorius than > https://docs.mailman3.org/projects/postorius/en/latest/ > which is not helpful for a user or system admin. Can you point me to something > better. Unfortunately, there is not user/list owner documentation for Postorius. As I said at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… You just have to page through the settings to see what's there. Hopefully the various categories are clear enough that if you're looking for something specific, you can find it easily. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 months, 3 weeks

performance report - mailman 3.3.1rc1 / postorius 1.3.1

by sunil soprey

Hi all - I just wanted to share my perf-load results of Mailman3. Hopefully community finds helpful. I realized mailman3 cannot run on AWS t3a* ( 2cpu or 4cpu @ 8 gigs ) Specs: AWS EC2 - m5a.xl and c5.xl Version: mailman 3.3.1rc1 What: Duration load test of 30k emails across 200 lists. Some lists have a depth of 9k users, other lists have 100 emails address. * create 200 lists of random names Results * Postorius kept hanging on vanilla AWS LTS and LTS2 image. I had to tune the kernel settings ( somax, syslimits, tcp wmem) * gunicorn.cfg must be created and workers/threads property must be added. I noticed hanging python and tcp/socket errors * Total run time = 50mins for fresh-load

5 years

Problems getting started with postorius

by Alain D D Williams

I am having another go with mailman3, being a long time MM2 user, but am getting increasingly frustrated. I am using on Debian 12 (Bookworm) and have installed the various Debian packages - mailman3-full does that. I have successfully started the mailman3 and mailman3-web services. I went to: http://localhost/mailman3/postorius/domains/new/ 'Add a new domain' I enter a 'Mail Host' -- a domain that does exist on this machine I choose a Web host from the drop down list -- same as Mail Host I click on 'Create Domain' and the page refreshes with the same information but under the Mail Host I see in red: {"title": "500 Internal Server Error"} I eventually tracked it down. The problem was that I had signed in with an account "addw@localhost". That, for some reason, failed validation above. I hacked the database and changed to "addw(a)localhost.localdomain" and creating the new domain worked. I could send email to addw@localhost - so at the MTA level it is correct. So please can the initial account creation do the same validation as does adding a new domain. I have looked but cannot find any documentation on postorius than https://docs.mailman3.org/projects/postorius/en/latest/ which is not helpful for a user or system admin. Can you point me to something better. Regards -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

6 months, 3 weeks

Re: What's the difference between (purpose of) reject and ignore

by denis.bitouze＠univ-littoral.fr

Mark Sapiro wrote: > On 6/23/22 12:37, denis.bitouze(a)univ-littoral.fr wrote: > > > > What is the Postorius version and is it installed from source, pip or as > > package and if as package, what package? - Postorius 1.3.4 - Here are some details: ┌──── │ $ apt-cache show mailman3-full │ Package: mailman3-full │ Source: mailman3 │ Version: 3.3.3-1 │ Installed-Size: 48 │ Maintainer: Debian Mailman Team <pkg-mailman-hackers(a)lists.alioth.debian.org> │ Architecture: all │ Depends: mailman3, mailman3-web, python3-mailman-hyperkitty │ Description-en: Full Mailman3 mailing list management suite (metapackage) │ This is GNU Mailman, a mailing list management system. This metapackage │ depends on all components of the full Mailman3 suite: │ . │ * mailman3: The core Mailman3 delivery engine │ * mailman3-web: Django project integrating Mailman3 postorius and hyperkitty │ * python3-mailman-hyperkitty: Mailman3 server plugin for Hyperkitty archiver └──── > The choices should be Accept, Reject and Discard. There should be no > Ignore choice, but I'm guessing you see them in French where the > translation of Discard is Ignorer. See > https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/locale/fr/L.... Indeed, sorry for the misleading translation from French to English. Maybe I'll suggest another word to the French translation team. > The difference between Reject and Discard is Reject notifies the > sender of the rejection whereas Discard just discards the message > without notification. IMHO, even in English, “Reject” and “Discard” are not self-explanatory. BTW, no clue about an automatic banishment of emails from discarded messages?

2 years, 11 months

Postorius confirmation mails shown in uwsgi-error.log but not sent

by Ralph Seichter

I have struggled for hours but cannot seem to figure it out. After registering new user accounts in Postorius, the "confirm your address" emails don't get sent via SMTP (my MTA does not even log connection attempts), but their content is displayed in uwsgi-error.log. I think I disabled developer mode in Core and Postorius: $ mailman conf | grep devmode [devmode] enabled: no [devmode] recipient: [devmode] testing: no [devmode] wait: 60s $ grep ^DEBUG settings.py DEBUG = False Users can subscribe via list-join(a)domain.tld, including confirmations. Account registration using the WebUI works as well, it's just the emails that don't get sent. What am I missing, I wonder? -Ralph

5 years, 2 months

Re: duplicate SITE_IDs and broken /postorius/lists/ display; Mailman Client

by Mark Sapiro

On 3/24/22 01:11, Stanisław Findeisen via Mailman-users wrote: > Hi > > I am having 4 different virtual domains (FILTER_VHOST = True). However on the domain list page in Postorius: https://.../postorius/domains/ I can see only 3 different SITE_IDs: 1,1,4,3. If I recall correctly, the "3" and "4" were created manually using the Postorius Web UI, whereas the two "1"s were created using the Mailman Client: > > client.create_domain(name) > > Is this a bug? Or did I mess something up? > What significance do those SITE_IDs have? The issue is client.create_domain doesn't support setting a Web Host. Web Hosts are the sites in the django_site table and SITE_ID is the id of the table entry. See `sites` in the Django admin UI. So when you create a domain with client.create_domain it gets arbitrarily assigned to a `site` > What I also noticed is that in the Postorius Web UI: https://.../postorius/lists/ both "1" domains display the lists contained in "3", whereas both "3" and "4" display correctly their lists. Except the "3", all domains are empty at the moment (no lists) (so "4" correctly displays no lists). Not sure if this is related?... FILTER_VHOST = True is imperfect. Lists have no Web Host attribute, only a Mail Host. Thus, with FILTER_VHOST = True, we get the Mail Host from the domains that have a Web Host matching the host in the http request. If that results in only one Mail Host, we limit the display to only those lists with that Mail Host, but otherwise we don't limit by domain. In other words, FILTER_VHOST = True only works if each Mail Host domain has a unique Web Host. If you have multiple Mail Host domains with the same Web Host (SITE_ID), FILTER_VHOST won't work for that Web Host. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

Re: Github auth deprecated API

by Mark Sapiro

On 5/14/20 8:11 AM, Quanah Gibson-Mount wrote: > The version of mailman3 I'm running apparently uses a deprecated API for > GitHub authentication. Does anyone know if this has been fixed? I > couldn't find an issue for it on the postorius issue tracker. It's not in the Postorius tracker because it's not a Postorius issue. The issue is with django-allauth in the current 0.41.0 release. It is fixed in the django-allauth GitHub repository by <https://github.com/pennersr/django-allauth/pull/2458> You can apply the patch from that PR to your django-allauth installation to fix this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

Mailman 3 Core user assistance

by Stephen J. Turnbull

Tony Deshields writes: > I currently have a docker mailman stack that utilizes Django LDAP > backend for authentication. I have my users attributes mapped as > you see below in my settings.py file. Whenever a user logs into > postorius with their 'uid', mailman-core uses their 'uid' as their > email address instead of the 'email' attribute. I don't think Mailman core is doing that, Mailman core just takes the token passed by Postorius verbatim. It's the Django LDAP auth module. You need to have that module pass the email value as the user identity token to Postorius rather than uid. There may be a way to configure that in settings.py. Check the module docs.

1 year, 4 months

Mailman-users search results for query "Postorius"