Search results for "Postorius" - Mailman-users

Re: Message Personalization: embed User name in header/footer‏

by Asaf Ohayon

Thanks I edit the file mailman/core/var/templates/site/en/list:member:generic:footer.txt : _______________________________________________ Thanks $user_name $display_name mailing list $fqdn_listname https://mailman.sysbind.biz/lists/$fqdn_listname/ FOOTER All the variables are expanded correctly when i recieve the email, but $user_name remains unexpanded Is there any option to enable in order for $user_name to be available ? ‫בתאריך יום א׳, 6 במאי 2018 ב-17:27 מאת ‪Mark Sapiro‬‏ <‪mark(a)msapiro.net ‬‏>:‬ > On 5/6/18 7:16 AM, Asaf Ohayon wrote: > > Thanks, > > I understand those features are not available (yet) on Postorius > We're working on getting template editing in Postorius for release later > this month. > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- Asaf Ohayon SRE | SysBind M: +972 547920828 P: + 972 3 5096219 E: asaf(a)sysbind.co.il Rothschild 60, Bat Yam www.sysbind.co.il

7 years, 10 months

Re: A new issue with installation

by Abhilash Raj

On Sat, Feb 20, 2021, at 8:51 AM, Brian Carpenter wrote: > As usual, a new issue has arisen with installing Mailman 3. It seems > Postorius and Hyperkitty want to install a module called cryptography. > Which I am unable to install because of this: > > error: Can not find Rust compiler You need to install a Rust compiler. Depending on which distro you are using, you can run `sudo apt install rustc` or same command with `yum`. > > Question 1: Is cryptography a new addition to Hyperkitty/Postorius? Or > was cryptography always included and something else is different about > my installation process? It was always included. The recent change has been in the underlying security library to use Rust language in some parts of it. That has resulting in 100s and 1000s of applications/CI and other stuff failing. The fix is quite simple in most cases, just install rust compiler. > > "Building wheels for collected packages: hyperkitty, django-haystack, > django-mailman3, mailmanclient, robot-detection, rcssmin, > django-allauth, cryptography" > > Question 2: Will Hyperkitty/Postorius work without cryptography? I > haven't proceed with this installation once I received the above error. It is a transitive dependency for P/HK and is required by django-allauth. I don't think you can skip it. > > Question 3: Are there any Mailman 3/Postorius/HK documentation that > addresses with the installation of cryptography? Since this issue arose about 2 weeks ago, there isn't anything there yet. > > > > -- > Brian Carpenter > Harmonylists.com > Emwd.com > _______________________________________________ > 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/ > -- thanks, Abhilash Raj (maxking)

5 years

Re: Postorius fails to show list because of a large message being held

by Brian Carpenter

On 7/14/20 6:49 AM, Gilles Filippini wrote: > Mailman Core logs: > [2020-07-14 10:41:21 +0000] [36] [CRITICAL] WORKER TIMEOUT (pid:49) > [2020-07-14 10:41:21 +0000] [49] [INFO] Worker exiting (pid: 49) > [2020-07-14 10:41:22 +0000] [50] [INFO] Booting worker with pid: 50 I am pretty sure that timeout is related to gunicorn. If it is, then increasing the worker out timeout setting for gunicorn should work. You tend to get such errors when doing an export of a large membership roster. This is the first time I have seen it related to a held message. I have this in my setup: mailman.cfg: [webservice] configuration: /opt/mailman/mm/gunicorn.cfg gunicorn.cfg: [gunicorn] workers = 4 timeout = 900 You will need to restart gunicorn after adjusting the timeout setting. -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

5 years, 8 months

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, 1 month

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

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

5 months, 1 week

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

2 years, 9 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

1 year, 11 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

7 months, 1 week

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, 7 months

Mailman-users search results for query "Postorius"