Search results for "Postorius" - Mailman-users

Re: Welcome Message

by Mark Sapiro

On 4/16/19 9:18 AM, brian(a)emwd.com wrote: > Thanks Mark. I added the POSTORIUS_TEMPLATE_BASE_URL to my settings: > > /opt/mailman/web/settings_local.py > > Now I get the following errors: ... > requests.exceptions.SSLError: HTTPSConnectionPool(host='mailman3.emwd.com', port=443): Max retries exceeded with url: /postorius/api/templates/list/testlist.mailman3.emwd.com/list:user:notice:welcome (Caused by SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:841)'),)) > Apr 16 15:38:44 2019 (28) 172.19.199.3 - - "POST /3.1/members HTTP/1.1" 500 59 > > I am confused by the SSL errors. I have a valid SSL certificate installed on mailman3.emwd.com. These errors occur whether the POSTORIUS_TEMPLATE_BASE_URL is using http or https. I'm confused too. What happens if you just do in a python3 interactive session >>> import requests >>> response = requests.get('https://mailman3.emwd.com/postorius/api/templates/list/testlist.mailman3.em…') and if you get this far >>> response.status_code >>> response.text -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 3 months

Re: FutureWarning: Use `header_id_prefix` instead

by Andreas Vetter

Am Tuesday, 28 July 2026, 11:06:42 Central European Summer Time schrieb Andreas Vetter: > Am Tuesday, 28 July 2026, 10:40:51 Central European Summer Time schrieb > > Andreas Vetter: > > Hi, > > after a recent update of the prerequisites using: > > pip install -U --upgrade-strategy eager mailman postorius django-mailman3 > > hyperkitty mailman-web > > > > I get warnings from the cronjobs: > > > > /opt/mailman/venv/lib64/python3.11/site-packages/readme_renderer/ > > markdown.py:44: FutureWarning: Use `header_id_prefix` instead > > > > gfm_extension_options.header_ids = _HEADER_ID_PREFIX > > > > What would be the best way to silence the warnings? Google does not find > > the warning message yet. > > > > Cheers, > > > > Andreas > > Quick fix is to change line 44 in /opt/mailman/venv/lib64/python3.11/site- > packages/readme_renderer/markdown.py from > gfm_extension_options.header_ids = _HEADER_ID_PREFIX > to > gfm_extension_options.header_id_prefix = _HEADER_ID_PREFIX > > Greetings, > Andreas Since this is a readme_renderer issue, I opened an issue there: https://github.com/pypa/readme_renderer/issues/380 Andreas

1 week, 3 days

Re: Wrong info in moderation mail when held due to match of a header rule

by tlhackque

On 17-Oct-20 18:40, Mark Sapiro wrote: > On 10/17/20 1:31 PM, tlhackque via Mailman-users wrote: >> I might also add the rule number or config filename:line, as in >> >> Header "{name}": rule in {file}:{n} matched value "{value}" >> >> This would be helpful when backtracking from a rejected message to the >> cause. >> >> A sample expansion might be: >> >> Header "X-Spam": rule in foo.conf:83 matched value "yes" > > These rules are not in a configuration file. They are in the headermatch > table in the database and the rules for a particular list are exposed on > the Header filters tab in Postorius or at the REST > lists/LISTNAME/header-matches endpoint. > > Perhaps something like > > {name}: header match rule, pattern "{pattern}" matched value "{value}" > > example: > > subject: header match rule, pattern "sex|long|list|of|other|bad|words" > matched value "This is a post about filtering based on words like sex in > the subject." > > but that could be just adding more clutter. > I considered including the regex in each message, but that seemed redundant - and potentially long. Thus the pointer. Perhaps number the rules for each list, and use that index? The ROWID would seem to be a candidate for the number. Then Postorius could simply number the rules in its tab; the REST API can add the ROWID as a rule_ID field in the returned JSON. (The fact that it's a ROWID rather than an index or unique name is an implementation detail.) If many rules are anticipated, it might want an endpoint or option to fetch a rule by ID. Then it would be easy to drill down on a specific event for diagnosis. e.g. shunt_reason: (or whatever) { cause: "header_match" header: "subject" header_value: "This is a post about filtering based on words like sex in the subject." rule_id: 47 /* or pattern_id? */ } displays as subject: header match rule 47, matched value "This is a post about filtering based on words like sex in the subject." and lists/LISTNAME/header-matches/47 returns { rule_id: 47 pattern: "sex|long|list|of|other|bad|words" position: 3 /* Whatever else is in your table... I haven't looked since I postponed using MM3. eg */ comment:"Required by policy 869.202" last_updated_by: "Corporate Prude" last_updated_on: "1-Apr-1762" }, while lists/LISTNAME/header-matches returns an array of those structures, presumably as today. With those capabilities, the UI can be enhanced so that clicking on a shunted message gives the summary reason, and clicking on the summary gives the regex. I expect that the header and value will be sufficient for understanding an issue most of the time. Looking at the regex is less common, and only necessary when it needs to be updated... I still think that it is more readable and less verbose to order the message as a declarative sentence: Header "subject": rule 47 matched value "sex" but that may be a matter of personal taste. The UI can sort that out... Note that from your description, using ROWID may cause rules in a particular list to have gaps in the rule numbering. I don't think that's a big issue, though Postorious could paper that over - perhaps use the position attribute. Doesn't seem worth doing something more complex. The advantage is that it doesn't require any DB change now. But aliasing it to "rule_id" allows for any future demand to name the rules or use some other numbering scheme. I may have some details wrong - I found mm3 not ready for my needs and am thus out of date - but I hope the high level approach that I outlined is useful.

5 years, 9 months

Re: Strange error in uwsgi-error.log

by brian＠emwd.com

Derek Lambert wrote: > Brian, > > When I was seeing this, new lists weren't showing in HyperKitty. > > I was migrating from 2.1, so they were all new lists and was preventing HyperKitty from > functioning. I had to drop the constraint to get the lists in. None of them have a > description now. > > Was this working for you in the past? If so, did you do any updates recently? > > Derek Lambert Hi Derek, Actually you are right. None of my new lists are showing in http://mailmam3domain/hyperkitty/. However if you go directly to each lists' archives then you can access their archives via HK. I also recently did an update when Postorius 1.2.3 came out. I am using the Docker images for my Mailman 3 install. How do you drop the constraint? DId that fix the error message? So this seems to be a new bug that was introduced in the recent updates? It's weird because I know Hyperkitty was not touched. Brian

7 years, 6 months

Cannot setup announce-only mailing list

by Alberto Granzotto

Dear all, I don't understand how to set up an "announce only" mailing list using Postorius Version 1.2.4. What I do is the following: - Click on "Create New List" - From "List Style", select "Announce only mailing list style." - Fill all other fields in the form - Click "Create list" At this point people can subscribe to the newly created announce mailing list. If they add themselves they end up in "List Members", and if they email the announce mailing list, their email is relayed to all other members, just like a normal mailing list :/ Moreover, subscribers get this message, inviting them to post to the announce only mailing list: > Welcome to the "Test-announce" mailing list! > > To post to this list, send your email to: > > test-announce(a)lists.dist0rtion.com Of course, I want to keep this mailing list "read only" for members, and I want only selected people to post to that mailing list. Any idea on how to achieve that? Best, Alberto

6 years, 6 months

Re: How to run 'manage.py update_index_one_list' command.

by Brian Carpenter

On 2/25/20 7:09 PM, Mark Sapiro wrote: > The issue is we don't in general know exactly how Django has been > installed or what the management command is, byt hyperkitty_import > should be able to figure out how it was invoked and use that. I did their installation for them basically using your setup listed at: https://wiki.list.org/DOC/Mailman%203%20installation%20experience I used a venv and pip to install the various components: pip install mailman pip install hyperkitty pip install postorius pip install mailman-hyperkitty -- 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/ Mailman 2 & 3 Hosting https://www.mailmanhost.com -- 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/

6 years, 5 months

Re: [Mailman-Developers] Mailman 3.1 beta coming soon

by Mark Sapiro

On 12/10/2016 12:52 AM, Barry Warsaw wrote: > > Please do rebase and if you can, remilestone the MR to 3.1. We'll get it in. Done. There is one "temporary" commit in my MR to work around <https://github.com/sphinx-doc/sphinx/issues/3212> and get "docs" to pass. >> I can also work on Postorius. Also in this vein I have a question. >> Should the DMARC settings be added to the Alter Messages tab in the List >> Settings view or would it be better to have a separate DMARC Mitigations >> tab. > > My gut reaction is to add a separate DMARC Mitigations tab, but Florian and > Terri have final say I think. I have a WIP MR at <https://gitlab.com/mailman/postorius/merge_requests/194> that adds a tab. Maybe Florian and Terri can look at that and chime in. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 7 months

Re: Email to list owner on list creation only sent when using mailman create --notify command

by Mark Sapiro

On 6/9/24 5:26 PM, Perry Kollmorgen wrote: > Hi, > > This is only a minor issue, however as a nicety for new list owners I am hoping there is work around or something I have missed. > > I have the following file: templates/domains/<fqdn_listname/en/domain:admin:notice:new-list.txt > > When I use the mailman create command with the --notify option the new owners receives an email with the correct template info from the above file. > > However when I use mailmanclient python bindings or Postorius to create an list, there is no email sent. This is a bug. Currently only `mailman create` sends this notice, but as you note, list creation via rest should do it too. I have created https://gitlab.com/mailman/mailman/-/issues/1156 for this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

Re: Mailing list welcome message won't update

by Mark Sapiro

On 1/9/25 13:58, via Mailman-users wrote: > > I have updated the welcome message for a mailing list by directly updating the file at: > file:///var/lib/mailman3/templates/lists/[redacted].lists.[redacted].org.au/en/list:user:notice:welcome > > I then restarted theses services: mailman3, mailman3-web and nginx. > > But when I test subsribe to the mailing list, the welcome message does not update. > > GNU Mailman 3.1.1 (Between The Wheels) > Postorius Version 1.1.2 These are extremely old - over 7 years. This may have something to do with the issue. There may be an issue in that the template table in the database is saying to look elsewhere. What do you get for a database query like ``` SELECT uri FROM template WHERE name = 'list:user:notice:welcome' AND context = '[redacted].lists.[redacted].org.au'; ``` where `[redacted].lists.[redacted].org.au` is the actual list-id. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

Re: Templates

by Barry Warsaw

On Sep 23, 2017, at 10:36, David Krantz <gazorg(a)gmail.com> wrote: > > 1. I do not know how to force a cache invalidation on a template. So > only way to change is to set a new name on the file and change the uri > there. Unpractical. No, restarts do not work. With Mark’s help you figured out how to use file templates, which is probably best for your use case. URL templates will be best when using a CMS or other system that allows you to upload templates into them. I can imagine Postorius one day supporting this feature. The way to do cache invalidation for the template you added to the database would be (let’s say for mailing list alpha(a)example.com) $ mailman shell -l alpha(a)example.com Welcome to the GNU Mailman shell The variable 'm' is the alpha(a)example.com mailing list >>> getUtility(ITemplateManager).delete('list:member:generic:footer', m.list_id) More information is provided here: https://gitlab.com/mailman/mailman/blob/master/src/mailman/interfaces/templ… http://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/templates.html Cheers, -Barry

8 years, 10 months

Mailman-users search results for query "Postorius"