Search results for "Postorius" - Mailman-users

Re: Postorius claims 2 messages held when there are none - out of sync

by Mark Sapiro

On 6/26/23 12:01 AM, Ken Alker wrote: > When I view a list via Postorius the "Held Messages" menu item has an inverse-red-"2" next to it, as if there are two held messages. There are, in fact, no messages in "/opt/mailman/mm/var/queue/*" (assuming the held messages should be in "pipeline" subdirectory). When I click on "Held Messages" I get "Something went wrong" followed by "HTTP Error 500: {"title": "500 Internal Server Error"}". How do I fix this? The held messages are not in any queue. They are stored in Mailman's var/messages/ hierarchy. They can be examined with `mailman qfile` Also, there is a long thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… and maybe others that might be relevant. -- 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

New Mailman web package releases

by Abhilash Raj

Hello Everyone, I have just released Postorius 1.3.13 and Hyperkitty 1.3.12. These can be downloaded from PyPI: https://pypi.org/project/HyperKitty/1.3.12/ https://pypi.org/project/postorius/1.3.13 Note that due to some mistakes on my part, last 2 releases for Postorius & Hyperkitty were yanked since their builds uploaded to PyPI weren't correct due to some mis-configurations migrating from setuptools to pyproject.toml (with pdm) based package configuration. So, when updating from last installed versions, please look at the changelogs from older versions too for both these packages. Their changelogs are available in the usual places: https://docs.mailman3.org/projects/postorius/en/latest/news.html https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html Since PyPI doesn't accept signatures anymore, I have uploaded packages and their signatures to Gitlab releases in their respective repositories too. A note for people using my signature for verification: I had to extend my gpg key's validity, so you'll need to refresh my public keys to validate the signature this time. -- thanks, Abhilash Raj (maxking)

8 months, 2 weeks

Re: Moderate mails from owner

by Mark Sapiro

On 3/21/19 3:02 AM, Malcolm Austen wrote: > > My only experience of MM3 is with Ancestry's 'RootsWeb' installation. > From the emails I can see a header "X-Mailman-Version: 3.1.0" but I > can't find anything to identify Postorius which is the only interface I > have to the system. Isn't there a footer at the bottom of wach page with something like: Postorius Documentation • GNU Mailman • Postorius Version 1.2.5 > From symptoms seen and described by others, I have deduced that the > Postorius admin-per-user moderation options of "Default processing" and > "List default" mean that a user may be set (by default on the rootsweb > system!) to use the system default moderation settings rather than the > list default settings. New (non-)members always have Moderation set to List default. This means their posts are governed by the applicable Settings -> Message Acceptance settings. Setting a user's Moderation to Default Processing means that users posts will not be held/rejected/discarded/accepted immediately based on "Default action to take when a (non-)member posts to the list", but additional checks will not be bypassed. See <https://mailman.readthedocs.io/en/latest/src/mailman/rules/docs/rules.html>. > Are my deductions correct? And if so, could this be the explanation of > the issue detailed in this thread? Setting a user's Moderation to Default Processing (or Accept) would bypass the list defaults and could be the explanation of this issue. When the non-member owner first posts to the list that address becomes a non-member of the list. I.e. it is in the roster of known non-members of the list and that non-member record could have had its Moderation set to Accept or Default Processing at some point which would explain why the posts are accepted. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

Struggle on upgrading mailman3-web to new version - Not Found: /mailman//

by Stefan Bauer

Dear Users, I recently upraded mailman3 from Ubuntu 18 to 20. After accessing the web-interface via https://my.mailinglistserver.local/mailman3/postorius/lists/ I receive Not Found: /mailman//postorius/lists/ [pid: 1346851|app: 0|req: 4/4] 10.254.253.12 () {70 vars in 1369 bytes} [Mon Oct 25 10:39:59 2021] GET /mailman3/postorius/lists/ => generated 2821 bytes in 12 msecs (HTTP/1.1 404) 5 headers in 155 bytes (1 switches on core 1) Where does the wrong path come from (mailman vs. mailman3) After enabling Debug, i see in the browser the following: Page not found (404) Request Method: GET Request URL: https://my.mailinglistserver.local/mailman//postorius/lists/ Using the URLconf defined in urls, Django tried these URL patterns, in this order: ^$ ^postorius/ ^hyperkitty/ ^user-profile/delete$ [name='mm_user_account_delete'] ^user-profile/$ [name='mm_user_profile'] ^accounts/ ^admin/ The current path, /postorius/lists/, didn't match any of these. You're seeing this error because you have DEBUG = True in your Django settings file. Change that to False, and Django will display a standard 404 page. My apache configuration is very simply: # more /etc/apache2/conf-enabled/mailman3.conf 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> I dont see where the path gets traversed in the wrong way. Any help is greatly appreciated. thank you. Stefan

3 years, 7 months

Re: Message of migrated list showing "unsubscribe@%(host_name)s" in footer

by Mark Sapiro

On 10/8/23 16:03, alex(a)presland.net wrote: > > We migrated a number of mailman lists last weekend and I spotted this evening that an email from the list contained a footer along the lines of the following (all bits in CAPITALS were successfully representing the list. > > ===== > LISTNAME mailing-list -- LISTNAME@DOMAIN > To unsubscribe, email LISTNAME-unsubscribe@%(host_name)s > ===== > > 1) I don't know why %(host_name)s hasn't been automagically substituted > 2) I can't find anywhere to change this footer in the Mailman3 Postorius interface The `mailman import21` process creates templates for existing 2.1 regular and digest headers and footers in Mailman 3's var/templates/lists/LIST_ID/LC/ directory. LIST_ID is the list's id like listname.example.com and LC is the language code for the list's preferred language. These have names like list:member:regular:header.txt, list:member:digest:header.txt, list:member:regular:footer.txt and list:member:digest.footer.txt. These are based on the mailman 2.1 lists regular and digest headers and footers with replacements translated to the appropriate Mailman 3 equivalents. However, there are various reasons why some replacements can't be translated, and these are left as is. in your case you need to edit those files and change %(host_name)s to $(domain}, or, since the default mailman/templates/en/list\:member\:generic\:footer.txt is ``` _______________________________________________ $display_name mailing list -- $listname To unsubscribe send an email to ${short_listname}-leave@${domain} ``` just deleting the var/templates/lists/LIST_ID/en/list:member:regular:footer.txt file will probably do what you want. Note that templates defined in Postorius are handled differently, and if a template is currently undefined in Postorius, starting to define it in Postorius starts with an empty template instead of the current file system template. See https://gitlab.com/mailman/postorius/-/issues/366 -- 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

Re: Log Owner/Moderator actions ban address matching.

by Mark Sapiro

On 5/1/25 04:02, Stephen J. Turnbull wrote: > Odhiambo Washington via Mailman-users writes: > > > So this issue can be addressed by making Postorius to log user logins, > > right? > > However, I don't have the patch :) > > I would guess it's probably possible to get Django to do this, quite > possibly using standard configuration to do so. I just don't know > where to look offhand. Postorius can't log logins because it's not Postorius (or HyperKitty) that does the logging in. It is django-allauth. You can see the `Last Login` info for a user in the Django admin web UI under Authentication and Authorization -> Users django-mailman3 does have some involvement with logging in and it might be possible to add logging there, but I don't offhand know where. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 1 week

Re: Django logins for new subscribers

by Abhilash Raj

On Fri, Jan 12, 2018, at 8:41 AM, Alex McLean wrote: > Hi all, > > I'm moving our groups to mailman3 (http://we.lurk.org) Enjoying it so far! > > I've mass-subscribed people via postorius. However the subscribers don't > have django (postorius/hyperkitty) logins. It seems they only exist on > the mailman side, not the django side. > > If they go through the process of creating an account in postorius, they > can configure their mailing list subscriptions, but this is a bit > fiddly. > > Is this expected behaviour? It would be great if they could be sent a > temporary link to set a password and go. Yes, that is the expected behavior. Postorius is just one of the front-end for Mailman (and only one, for now), so we didn't think it would make sense to create account for every Mailman User in Postorius as well. So, basically everyone has to go through the sign-up process, which isn't really hard if you choose one of the social logins. It wouldn't be very hard to write a script that "creates" User accounts for everyone and then users go through the "Forgot Password" workflow to set their passwords. You'd get the list of all users from Mailman's API and then do a `get_or_create()` on each one of them (simplest of all approaches, you can ofcourse better ways to do the same). -- Abhilash Raj maxking(a)asynchronous.in

7 years, 4 months

Re: Templates do not work

by Mark Sapiro

On 4/28/22 02:50, Eggert Ehmke wrote: > I created some templates in Postorius to get > personalized notifications when there are > moderator requests. The notifications I get seem to > be the standard texts. When I look into mailman/ > mm/var/templates > the directory is empty. Nevertheless, the templates I > create in Postorius seem to be stored (where?), they > just do not work. As Steve said the templates are stored in the database. I suspect the issue is and incorrect value for `POSTORIUS_TEMPLATE_BASE_URL` in your Django settings. This is used to construct the URI to retrieve the template. The URI is stored in the `template` table in the database. It is normally just `http(s)://host.name/` If this is the issue, after correcting the setting and restarting the web service, you will need to delete and re-enter the template in Postorius to correct the `template` table entry. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 1 month

Re: combine postorius and hyperkitty into one Apache vhost

by Mark Sapiro

On 12/29/22 05:51, Wolfgang Rosenauer wrote: > Hi, > > I'm in the process to set up a new mailman3 site. > (Migrating from mailman2) > > There are RPMs for my distribution which integrate postorius and > hyperkitty with uwsgi. I think you'll be much happier if you don't use the distro's RPMs which are probably out of date and instead follow <https://docs.mailman3.org/en/latest/install/virtualenv.html>. Those instructions use uWSGI as a WSGI interface, but Gunicorn <https://gunicorn.org/> is what is used on the site supporting this list. The advantages of Gunicorn are it's already installed as a dependency of Mailman core, and it's what the Mailman developers are more familiar with. I'll work on updating <https://docs.mailman3.org/en/latest/install/virtualenv.html> to include Gunicorn as an alternative. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

Re: Internal Server Error, Need 2 values to unpack in for loop; got 1

by Mark Sapiro

On 7/11/24 11:06 AM, Elias Rudberg wrote: > Hello! > > I am using mailman3 (version 3.3.8) and it mostly works fine, but > sometimes (usually several times every day) the error below appears. > > Any suggestions for what could be done about this? ... > Here is what the error message looks like: > ------------------------------------------- > > [Django] ERROR (EXTERNAL IP): Internal Server Error: > /mailman3/postorius/lists/ > > Internal Server Error: /mailman3/postorius/lists/ > > ValueError at /postorius/lists/ > Need 2 values to unpack in for loop; got 1. Can you get the page at /mailman3/postorius/lists/ and /mailman3/postorius/lists/?all-lists If those are OK, look in your web server access logs for `GET /mailman3/postorius/lists/` messages with the same timestamp as those errors. Is there some bogus query fragment on those? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 4 weeks

Mailman-users search results for query "Postorius"