Search results for "Postorius" - Mailman-users

Re: Internal server error instead of web interface

by Christian H. Kuhn

Solved: service mailmanweb did not start automatically. systemctl enable mailmanweb (which i obviously did forget) did the job. Am 05.11.2025 um 11:44 schrieb Christian H. Kuhn: > Hi all, > > https://lists.qno.de/mailman3 shows an internal server error. > > I followed https://docs.mailman3.org/en/latest/install/virtualenv.html > with MariaDB instead of PostgreSQL. > > Python 3.13.0 > pip 25.3 > mailman 3.3.11b > mailman-web 0.0.10.dev14?g0997bd > postorius 1.3.13 > > Services mailman3, mailmanweb, apache2, uwsgi up and running. uwsgi > listens on [::1]:8000, apache2 is configured accordingly. Ports show up > in netstat. > > No errors show in logs. > > If /mailman3 was a directory, i would have thought of user permission > problems. But not with TCP ports. > > As :8000 is available, i would have thought that there is a problem with > uwsgi. Requests arrive there and are processed: > > [pid: 3185672|app: 0|req: 10/17] ::1 () {28 vars in 409 bytes} [Mon Nov > 3 13:24:05 2025] GET /mailman3/ => generated 5038 bytes in 28 msecs > (HTTP/1.0 200) 8 headers in 261 bytes (1 switches on core 0) > > So uwsgi gets the request and delivers data. The problem seems that > apache2 does not get the result, and i cannot find any reason. Any help? > > TIA > QNo

6 months

Re: Advice on upgrading..

by Stephen J. Turnbull

Mark Sapiro writes: > On 8/3/26 6:41 AM, Stephen Daniel wrote: > > > > I'd like advice on how to migrate mailing lists and archives from > > the old install to the new one. Is there a standard procedure? > > Just point the new installation to the existing database(s) and run > the django admin migrate command. You will get a working installation with all your lists in place with this simple approach. There are a few caveats that probably do NOT apply to you: 1. You need your config files to be outside of Mailman's installation tree. (Most people have them in /etc/mailman3, so no problem.) 2. You may have edited some template files in place in $var_dir. These edits need to be merged into the new ones, which may have changed. (Most people use Postorius to customize email templates, which are saved in the database rather than the file system. More installations have customized Postorius's own templates and CSS for corporate logos and disclaimers, etc., which need merging.) 3. You may have customized the code, most likely by using an external text indexer for HyperKitty. Any code to link the indexer to KyperKitty will need to be installed by hand in the new venv. (This is pretty likely, in fact, since Whoosh is very inefficient and no longer recommended for production.) > > My current implementation uses the Python venv installation > > method. I'd prefer a more container-focused installation, but > > since I don't believe Mailman 3 has official container images > > yet, I plan to continue with the venv approach. Please let me > > know your thoughts. > > See https://docs.mailman3.org/en/latest/install/docker.html I take it from your (OP's) preference for containers that you're familiar with them. I'm a Docker newbie, and found the documentation confusing. I think because there are aspects (like use of environment variables in config files) that must have been implemented in Mailman but are not commonly used in plain venv installations. There are a number of comments in the docker-compose.yaml(s) and Dockerfile that are bitrotted, and docker itself emits some deprecation warnings. I'd have to say this is not ready to be promoted to "supported" for those reasons, but they're mostly cosmetic. FWIW, I do think the implementation itself is detailed and solid. It appears to be getting quite a lot of attention from beta testers, including patches. The only thing I should warn is that mail routing demands a lot of the network admin. The most common complaints I've seen about the package is that trying to integrate with a larger network of containers gets messy. If Mailman suite is isolated in its own network, it should be straightforward, Steve -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

1 month, 3 weeks

Re: List users from different domains getting blocked.

by Mark Sapiro

On 12/14/23 14:19, bob B via Mailman-users wrote: > I am running MM3 and have a list that has users from different organizations and email domains. > > So let's say I am orga.com and hosting mailman > Bill is borg.com > Cindy is mew.com > > When Bill sends a message to my MM3 list it gets sent out, However, cindy's email system rejects it cause it sees the message is sent from Bill(a)borg.com but it came from my MM3 server which is under orga.com, so it rejects it. You need to apply DMARC mitigations. Normally mitigations are only applied if the From: domain publishes DMARC p=reject or p=quarantine, but recently this has become problematic. For example, gmail.com pubpishes DMARC p=none yet google servers effectively apply p=reject to mail From: gmail.com. Mailman >= 3.3.9 and Postorius >= 1.3.9 allow setting dmarc_addresses to a list of email addresses and regexps matching addresses and domains to which DMARC mitigatations will be applied regardless of puublished policy. For older releases and for cases where domains are not known in advance one can always set dmarc_mitigate_unconditionally True to apply mitigations to all mail. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

Re: Invalid FilterAction: discard. Treating as discard

by Mark Sapiro

On 5/8/19 4:45 AM, Henrik Rasmussen wrote: > Mark Sapiro wrote: > >> I'll post a follow-up with how to change pass_types via mailman shell >> when I work it out. > > Look forward to that, thanks. OK. in mailman shell with your list as 'm' >>> list(m.pass_types) ['multipart/mixed', 'multipart/alternative', 'text/plain'] >>> m.pass_types = ['multipart', 'text/plain', 'text/html'] >>> commit() >>> list(m.pass_types) ['multipart', 'text/plain', 'text/html'] >>> If you want to allow text from forwarded messages, add 'message/rfc822' in the pass_types list above. This setting will allow inspection of all elementary parts within any multipart parts ant will accept only text/plain and text/html. Then if collapse_alternatives is True (settable here or in Postorius), any multipart/alternative parts will by replaced by the first, presumably text/plain, sub-part. Finally, if convert_html_to_plaintext is True (settable here or in Postorius), any remaining text/html parts will be converted to plain text by lynx or whatever is configured as html_to_plain_text_command in mailman.cfg. This will ensure that filter_action is applied only to those messages which have no text/plain or text/html parts. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 4 months

Re: Update a member's display_name

by Mark Sapiro

On 7/8/20 11:08 AM, rongxinliu(a)cs50.harvard.edu wrote: > Hi Mark, I'm not the only developer on this list. > I would like to know if there is a way to update the display_name of the member in a mailing list via REST API? > > Having tried updating the display_name of a user but did not seem to work. The display_name did change, but the mailing list still displaying the old name. By "the mailing list still displaying the old name" do you mean the membership list in Postorius or something else? And to what REST endpoint did you post the display_name? The bottom line is a user can have multiple display names. Each user has a User record with a display_name attribute, one or more 'addresses', one of which is it's preferred_address. Each one of the addresses is an Address record with it's own email address and display_name. Now, a member of a list can be either a User or an Address. If it's a User, its display_name is that of the user and it's email address is that of the preferred_address, but if it's an Address, its email and display_name are those of the Address. -- 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

Re: How to store additional information about lists?

by Stephen J. Turnbull

Andreas Barth writes: > Currently it is "list public" vs "subscribers only". I need something > inbetween, so that some (i.e. most) people have access to the > restricted audience lists but not just everybody. That much is clear. The problem is that "access to list" can mean a lot of things: can subscribe, can post, can admin, can view archives, can view list in listinfo, can view subscriber list, and there are probably others. What permissions are needed for what general classes of users? > Just as an idea, how about always one "custom attributes" field. So > that from a database pov this field is always there. We could do that, but then we'd have to support it. I'm thinking of situations like admin A populates the field, then leaves the organization, and we add (some of) the supported features, and admin B wants to migrate that. I don't see any good coming of that for us. As Mark says, a separate table seems like the way to go for custom attributes. > It could be done in postorius - the restriction that subscribing by > mail needs moderators action would be ok (or if it annoys me, this > part be move to a cron job). OK. I'll think about this. Steve

5 years, 4 months

Re: Question: What happens if I delete a user from all lists and that user is sole owner of some list?

by Odhiambo Washington

On Wed, Apr 3, 2024 at 6:58 PM David Partain <david.partain(a)ericsson.com> wrote: > On Wed, 2024-04-03 at 15:14 +0300, Odhiambo Washington wrote: > > > My question is: If one of these users is the sole owner of a list, what > > > will happen? Will the user be deleted and that list now owner-less? > > > Will mailman refuse to delete that user until I add a new owner? > > > > > > Thanks in advance for your feedback. > > > > 1. Create a testlist > > 2. Assign an owner to it > > 3. Delete the owner via the CLI or Postorius > > > > Give us your feedback :) > > I'll happily do so, and thanks for the idea. Try stuff, David! > > Cheers, > > Daudi Mwisho, as my mom liked to call me > Aah. Mswahili :-) -- 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]

2 years, 5 months

Re: 502 bad gateway when unsubscribing users

by Jered Floyd

Hi Laura, This indicates a problem an error occurring within the specific install of Mailman that your university is running, and it will be very difficult to diagnose without access to the error logs. Is this something you can escalate with an IT administrator? They'll be in the best situation to figure out what's wrong -- it's definitely not anything that you are doing as a moderator. Regards, --Jered ----- On Aug 21, 2024, at 12:02 PM, laura thomas laura_thomas(a)fas.harvard.edu wrote: > Hi everyone, > > I moderate several email lists for a university using Postorius 1.3.4.1. I've > been trying to update our lists by removing members who have left the > department. However, when I click on a name and then "Unsubscribe Selected," I > always get a 502 Bad Gateway message, and I'm unable to remove any users from > the list. This has happened on every attempt across multiple users on multiple > mailing lists. Does anyone know what might be going on? I appreciate the 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 jered(a)convivian.com

2 years, 1 month

Re: Custom templates (was: Re: Re: nginx configuration on a multitasking server)

by David Newman

On 1/14/22 6:35 PM, Mark Sapiro wrote: > On 1/14/22 6:11 PM, David Newman wrote: >> On 1/14/22 4:54 PM, Mark Sapiro wrote: >>> >>> It should work. I suspect you need to go to the list's Settings -> >>> Automatic Responses and set `Admin immed notify` to Yes. >> >> >> It's enabled. I think this triggers notifications only for new >> subscription requests, not pending ones. > > > Yes. That will send a single notification at the time of the request > using the `list:admin:action:subscribe.txt` template. Notices of pending > requests are sent by the `mailman notify` command using the > `list:admin:notice:pending.txt` template. > > ... >>> You can test `mailman notify` at any time by running it by hand. >> >> >> Thanks. This still isn't working as intended. I took these steps: >> >> 1. Created the file >> '/opt/mailman/mm/var/templates/lists/test.lists.domain.tld/en/list:admin:action:pending.txt' > > > The template name is `list:admin:notice:pending.txt`, not > `list:admin:action:pending.txt`. Thats why it didn't work. Bingo. Thanks -- the template works as intended now. > > ... >> 2. Restarted the mailman3 and mailmanweb services > > > You only needed to restart Mailman core. OK > > > ... >> What I'm trying to do here is replicate a feature from MM2.1, where >> pending notifications had URLs embedded in the message. That's not >> available out of the box in MM3, and if there's a place for feature >> requests I'd be glad to ask that this be made the default. > > > The place for feature requests for Mailman core (which this is) is > https://gitlab.com/mailman/mailman/-/issues, however, this is not > straightforward as Mailman core doesn't know if you even have Postorius > or some other web management UI installed or what the URL to access it > might be. Thus it's not just a simple matter of editing templates. It > would also require a configuration setting for the base URL for the web > admin UI and changes in logic to provide an appropriate replacement > depending on whether or not the base URL was configured. Understood, thanks. Although this distinction is very important for server admins, it's likely not meaningful for many list owners and moderators. For them, MM2.1 sent an email saying "go here" and MM3/Django/Postorius/Hyperkitty doesn't, at least not out of the box. There is some pending template in use by default, just not one with a URL included. Is this something better handled in the venv and/or Web installation docs? Or should I file a feature request for core, or Postorious or someplace else? Thanks very much! dn > >

4 years, 8 months

Re: If I manually add email addresses to a list and then delete them, how do i permanent delete them from Users?

by Mark Sapiro

On 4/25/23 3:02 AM, Andrew Hodgson wrote: > Mark London wrote: > >> I added some email addresses manually to a mailing list and then removed them. But now I can't find how to totally remove them from mailman3. They show up in the Users list. > > You may find this script useful: > https://www.msapiro.net/scripts/clean_users.py That script will only delete Django users and optionally the Mailman user corresponding to the deleted Django user. I think the OP wants to delete Mailman users that are not members of any lists even if there is no corresponding Django user. That script won't do that. Mailman Users can be deleted from the Postorius Users view, but it's a one at a time process, and there's no indication that the User has memberships unless you first go to `Manage` to check. I will modify the script to enable deleting Mailman users with no memberships even if they aren't Django users and post here when it's done. -- 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

Mailman-users search results for query "Postorius"