Search results for "Postorius" - Mailman-users

Re: Error -- postorius Un-handled exception

by Odhiambo Washington

On Wed, Jan 24, 2024 at 8:48 AM Mark <imark(a)posteo.net> wrote: > > Hi All, > > I've just installed MM3 on a fresh Debian 12 using the Virtualenv > method. > > (venv)...$ mailman info > GNU Mailman 3.3.9 (Tom Sawyer) > Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0] > What is the complete output of this: venv> mailman info Reduct the passwords. Also please share the contents of all the files in /etc/mailman3/ - with passwords reducted. I have a Debian 12 setup on a VM (my test platform) and would like to compare your files with mine because it has no difference with what is at https://docs.mailman3.org/en/latest/install/virtualenv.html and all is fine. Well, I use Apache, not Nginx. That's the only deviation. -- 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, 4 months

Re: problem configuring mailman3 on debian bullseye

by Mark Sapiro

On 3/15/23 09:55, Odhiambo Washington wrote: > On Wed, Mar 15, 2023 at 7:10 PM Servizio Informatico U.I.C.I. Sezione > territoriale di Brescia <servizioinformatico(a)uicibrescia.it> wrote: > >> Hi, >> >> I created a template but after some tests I deleted it. >> >> Now I created only a standard list without modifying any templates. >> >> So they are the standard templates coming with the distribution. I did not >> change also the language >> > Maybe you can start by deleting any templates in postorius_emailtemplate > table in the DB? There shouldn't be any, but if the issue is with accessing postorius templates, that might make it worse. If you want only the system default templates, you could do this database query to remove any non-defaults: DELETE FROM templates; That will ensure that you aren't accessing Postorius for any templates. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

Re: Can't subscribe on new site/domain

by Mark Sapiro

On 10/9/25 2:39 PM, Flo via Mailman-users wrote: > > In this case I see that I have permanently troubles with this software > (OS-packages) so your suggestion is worth to consider. > > Is there a possibility to export all members including real names. It > doesn't work with Postorius, yet, is there another possibility? If I > have my user data exported, I could delete everything and start from > scratch. Maybe this is the most reasonable ... You can install mailman following https://docs.mailman3.org/en/latest/install/virtualenv.html and keep your existing database(s) which will include all lists and memberships. The current released versions of Postorius include only emails in the csv export. This is fixed for the next release by https://gitlab.com/mailman/postorius/-/merge_requests/993 You can currently get a list of members with display names with the `mailman members` command. See `mailman members --help`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 2 weeks

Re: How to edit default 'Reject (with notification)' message

by Mark Sapiro

On 5/26/23 7:57 AM, Zaheer Abbas wrote: > > I have created a template with the option, "Notice sent to a poster when > their message has been rejected by the list’s moderator." but it only works > if message acceptance is set to 'Hold for Moderation' and then the > moderator rejects the post manually. > > Is there any source file, which I can modify to replace the default > rejection text mentioned above? The template you want is described in Postorius as [list.user.notice.rejected] Notice sent to a poster when their message has been rejected automatically You can set it in Postorius per list or per domain or you can set it sitewide by putting it in Mailman's var/templates/site/en/list.user.notice.rejected.txt and if you do that, be sure the Mailman user has access to read it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

Re: Avoiding non-members to be saved.

by Guillermo Hernandez (Oldno7)

On 7/8/21 13:55, Stephen J. Turnbull wrote: > Guillermo Hernandez (Oldno7) via Mailman-users writes: > > > Yesterday I had a problem with a private list. A spammer sent a mail > > forging one address that was a non-member (in fact was an "accept this > > no subscriber mails" from mailman 2.1 import) with very bad intentions > > and it was distributed. > > If you upgrade from Mailman 2 to Mailman 3, the accept_these_nonmembers > list for each list is grandfathered into the Mailman 3 list (from > rules/moderation.py): > > # Check the '*_these_nonmembers' properties first. XXX These are > # legacy attributes from MM2.1; their database type is 'pickle' and > # they should eventually get replaced. > for action_name in ('accept', 'hold', 'reject', 'discard'): > legacy_attribute_name = '{}_these_nonmembers'.format( > action_name) > > > There were no list of "accept this non members" in the Postorius > > config > > If there is no such list in Postorius, I would guess that some > developer thought "OK, this is a legacy feature and I'll get back to > it when we move it to the proper database" (unfortunate, but most of > us have open-subscription member-posts-only lists, and the current > workflow seems to work well, so this feature may not be so salient). > > > I think it is solved now (deleting all and putting to hold just the > > non-members addresses that I would want to pass messages on) > > This should not be necessary, unless there were pre-approved addresses > that are no longer appropriate. But Mailman can't know that! > > > The fact is that any sender address of mails sent to the list is saved > > as a "non member", and it make me nervous as it will grow despite it is > > a legitimate message or not. > > As far as I can see there is no other rule except that legacy rule > (and the rule that accepts all posts, which is rarely used) that will > accept a post from nonmembers. > > > Anybody knows if there is a per list config to avoid saving all that > > addresses as non members? o a overall config? > > No, there isn't, and there never will be. This is a basic design > decision about the representation of "people who participate in any > way in mailing lists". The only way to prevent creation of an Address > object for the sender of an email is to reject or discard the post (in > which case the "create an Address" path isn't entered), and don't set > a moderation action on the sender. Obviously if you set a moderation > action, that will create an Address in the database. > > The problem you encountered is not preventable by any means > whatsoever: a malicious actor discovered an address that is allowed to > post. The specific case you're worried about, that nonmembers will > automatically be allowed to post, is not possible. Well, as I couldn't locate which legacy accepted to post non-member addresses were permitted, I solved it deleting all of them (thanks again Mark) and adding via Postorius to the list of "hold these non-members messages" that I will examine and decide if it is a legitimate send. Thanks a lot for your detailed explanation. I can do better decisions now adjusting the configuration as needed. > The only way to > get on the list of "accept_these_nonmembers" is to be inherited from > accept_these_nonmembers on the parent Mailman 2 list, or an explicit > decision by a moderator. > > The fact that this list is not exposed in Postorius is a bug, but I > can't say when it might be fixed. It appears that the current process > (the moderator can set the sender's persistent moderation action > separately from approving or rejecting a particular post) works fine, > since this is the first time I've heard of this issue, and as you > present it, Mailman is doing the best it can since Somebody Authorized > put that sender on the approved list in Mailman 2. > > If a particular nonmember becomes a problem, you can access that > User or Address in Postorius and set them to Hold, Reject, or Discard. > > The process of deleting all nonmembers has been more difficult than it > should be, but this is being fixed, IIRC in the next release. > > Steve > --

4 years, 10 months

Re: Topics - Tags

by Mark

On 2024-03-23 06:36, Mark Sapiro wrote: > On 3/21/24 21:10, Mark wrote: >> Hi, >> >> I'm reading the docs on "Message tagging" >> (https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/handlers/d…) >> as saying shell access is needed to: (a) enable topics, and (b) write >> the keywords. >> >> In Mailman 2 there is an Admin web UI for "Topics". Is there such a >> web UI that can be enabled in Mailman 3 so that the list owners can >> create topics (tags) in their lists? > > > At this point, topics are not exposed in REST. Managing them via > Postorius first requires updating the REST API to read and set the > topic attributes and then updating Postorius to display/set them. > > Further, there is currently no implementation for list member topics > of interest either in Mailman core or the REST API. I.e., there is no > way for a list member to indicate topics of interest. > Thank you for this information Mark. Best, Mark

2 years, 3 months

Re: mailman addmember/syncmember commands print undecoded UTF-8 [ADD] or [DEL] mail addresses in its messages like "[ADD] =?utf-8?q?John_=....."

by Mark Sapiro

On 8/5/25 12:13, Wikinaut wrote: > I have such entries again in the postorius list "=?utf-8?q?Alexandro....", even after having deleted the user twice (there were no entries), the text file has nothing special, uchardet says "UTF8". Presumably these are being picked up from an email header that has the display name properly RFC 2047 encoded but then not decoded for the database address or user record. This could be a bug, but without knowing the exact scenario that results in these encoded display names, it's difficult to know where the bug might be. In what postorius list (members or non-members) are you seeing these? Are there log messages about them in the subscribe log (by default written to mailman.log)? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 2 weeks

Re: Timeout in Postorius when trying to approve or reject moderated messages

by Sebastian Hagedorn

Am 27.08.20 um 18:05 schrieb Mark Sapiro: > On 8/27/20 8:07 AM, Sebastian Hagedorn wrote: >> >> Right now everything is running as root (except for Apache). I realized >> too late that I should've used a mailman user. Could that be the reason >> for the issue? > > Since you have determined it was a browser issue, that probably isn't > the reason, but running Mailman as root is a bad idea in general for > security reasons. Thanks, I'm aware, and I'm not going to on a production system. This installation is just a trial run. > I don't know if it's relevant or not, but I have just recently had > issues with Firefox not working properly on two different (not mailman) > web sites, and these issues were fixed by clearing cookies and cached > data from the affected sites and restarting Firefox. I can confirm that that worked in my case as well.

5 years, 9 months

Re: Held messages: Long time waiating for response of the Mailman API

by Mark Sapiro

On 1/18/22 06:24, Stephan Krinetzki wrote: > Hello, > > We are using Mailman 3.3.5 with Hyperkitty 1.3.5. Mailman 3 is installed in a venv and deployed using Apache and uwsgi. This works quite well so far, only withheld messages cause us a problem: If we try to approve them via Postorius, the message is delivered to the list immediately, but the success message in Postorius takes a long time - on average the process hangs for three minutes until the message is no longer displayed. We have already adjusted the timeout in gunicorn.cfg, but this does not improve the situation. Are there any tips on how we can speed up the REST API? Or is it even a configuration error? There are two steps in handling the POST for a held message. The first step is accepting, rejecting or discarding the message. This is happening immediately. The second step is handling the poster's moderation action based on the choice from the Set member moderation dropdown in the view of the held message. This is processed by the code at <https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/views/list…>. If no selection has been made, the default value POSTed for moderation_choice is `no-action` and that code is skipped. If it is one of the choices `Hold for moderation`, `Reject (with notification)`, `Discard (no notification)`, `Accept immediately (bypass other rules)` or `Default processing` that is processed. So presumably a selection has been made and processing is stuck on getting the member or setting the member's moderation action. Possibly the logs of your database manager will have information. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

Re: Core, Hyperkitty and Postorius releases

by Mark Sapiro

On 5/14/21 12:50 PM, Odhiambo Washington wrote: > On Fri, May 14, 2021 at 7:04 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 5/14/21 5:02 AM, Odhiambo Washington wrote: >>> On Fri, May 14, 2021 at 2:52 PM Jeff Steele <jeff(a)steele.com> wrote: >>> >>>> >>>> >>>> On May 14, 2021, at 7:49 AM, Odhiambo Washington <odhiambo(a)gmail.com> >>>> wrote: >>>> >>>> /bin/sh: sass: Permission denied* ... >> Try `which sass` >> > > root@gw:/usr/home/wash # su mailman3 > (venv) [mailman3@gw /usr/home/wash]$ which sass > (venv) [mailman3@gw /usr/home/wash]$ > > There is no sass. There has to be. You can't get a permissions error on sass if it doesn't exist (well, maybe if you don't have permission to search a superordinate directory, but that's unlikely). Try `find /usr -name sass` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

Mailman-users search results for query "Postorius"