Search results for "Postorius" - Mailman-users

Re: How to store additional information about lists?

by Mark Sapiro

On 5/25/21 12:28 AM, Stephen J. Turnbull wrote: > Andreas Barth writes: > > > private: hand-selected people, think about e.g. board or steering > > committees internal discussions. Of course, the archive (if there is > > any) should be restricted to the actual members. Posting to these > > lists is currently not restricted, so no derivation needed from the > > current set in postorius. > > This is already possible by requiring admin approval, or by setting > the ban list to something that matches everything like "^.". The ban list can't be used in this way. A banned address can't be subscribed by any means including admin action. And even if an admin temporarily removes the ban, subscribes the address and then restores the ban, the now banned member can't post. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

Re: Posterious membership listing for non-owner/moderators?

by Mark Sapiro

On 3/11/21 4:58 AM, Duane Raymond wrote: > Hi, > > I'm configuring my new mailman3 lists and one option I wish to use is a membership listing (which list members can opt-in/out of via their preferences). The only problem is, via the web interface (Posterious / Hyperkitty) I can't find that listing when logged in as an ordinary member. Am I missing something or is this not built in yet? > > I have my test list setting under List Identity -> Members List Visibility set to "Only mailinglist members", but all I can find in terms of members is the side-listing of posters to the list/thread. > > (as usual before asking the question I explored a lot and searched the archives/documentation). Maybe you should also check issues. This is <https://gitlab.com/mailman/postorius/-/issues/369> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

Re: Hyperkitty performance problem

by Odhiambo Washington

On Fri, Nov 22, 2024 at 9:59 AM Tobias Diekershoff <tobiasd(a)fsfe.org> wrote: > Hey all, > > so far we could not find the reason behind the problem. However while > reviewing the installation process one one our team mentioned that he > read the installation instructions for Hyperkitty different then the > rest of the team. > > Are Mailman3/Postorius and Hyperkitty supposed to run in separated > databases, or are they supposed to use the same database? > > Thanks in advance for clarification! > Tobias > The official documentation specifies two DBs - one for Mailman Core and the other for Mailmanweb. As far as I know, there are no conflicts in the tables so you could use the same DB for both. -- 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]

9 months, 3 weeks

Re: Outgoing messages fro Mailman fails DMARC

by Henrik Rasmussen

> On 04/10/2018 06:53 PM, Mark Sapiro wrote: > > I'm not sure I understand what you are saying. Mailman's (both 2 and 3) > DMARC mitigations allow modifying the outgoing message in some or all > cases so the From: domain is the list's domain so the message won't be > dealt with by the recipient MTA according to the original From: domain's > DMARC policy. > > See <https://wiki.list.org/DEV/DMARC>;. Also, > <https://wiki.list.org/x/17891458> may be of interest. Thanks you for the links. According to https://wiki.list.org/DEV/DMARC the MM3 list setting "DMARC mitigation action" (which actually say "Replace From: with list address" in Postorius) should change the From: header. This doesn't seem to work if I don't also set "DMARC Mitigate unconditionally" to Yes, but does if I do. Where do I change defaults for all lists, instead of a per list change in settings/dmarc_mitigations ? Henrik Rasmussen

7 years, 4 months

Can't Start Mailman3 Core on Fresh Install

by Mail Person

Hi Everyone. I'm installing Mailman3 on a Ubunu 18.03 server using MySQL as the backend. After installing using the mailman3-full package and configuring it, I'm getting the following error when trying to start the mailman3 service: l 21 04:28:44 eps mailman3[81963]: packet.raise_for_error() Jul 21 04:28:44 eps mailman3[81963]: File "/usr/local/lib/python3.8/dist-packages/pymysql/protocol.py", line 221, in raise_for_error Jul 21 04:28:44 eps mailman3[81963]: err.raise_mysql_exception(self._data) Jul 21 04:28:44 eps mailman3[81963]: File "/usr/local/lib/python3.8/dist-packages/pymysql/err.py", line 143, in raise_mysql_exception Jul 21 04:28:44 eps mailman3[81963]: raise errorclass(errno, errval) Jul 21 04:28:44 eps mailman3[81963]: sqlalchemy.exc.OperationalError: (pymysql.err.OperationalError) (1045, "Access denied for user 'mailman3'@'127.0.0.1' (using password: YES)") Jul 21 04:28:44 eps mailman3[81963]: (Background on this error at: http://sqlalche.me/e/e3q8) I'm not sure why the access issue is happening. Mailman3-web is running fine and I can see the site at mailman3/postorius/lists (but it says Page Not Found).

3 years, 1 month

Change the default value for the General Archive Policy

by Markus Grandpré

Dear list, currently, when I create a new mailing list with MM3 the value for "Archive policy" is always set to "Public archives". I'd like to change the default value for "Archive policy" to "Do not archive this list". How can I do this? In Debian 12 I find in </usr/lib/python3/dist-packages/postorius/forms/list_forms.py>: mlist_properties = ['archivers'] archive_policy_choices = ( ('public', _('Public archives')), ('private', _('Private archives')), ('never', _('Do not archive this list')), ) archive_rendering_mode_choices = ( ('text', _('Plain text')), ('markdown', _('Markdown text')), ) archive_policy = forms.ChoiceField( choices=archive_policy_choices, widget=forms.RadioSelect, label=_('Archive policy'), help_text=_('Policy for archiving messages for this list'), ) but have no idea how to change the settings here. Your help is very appreciated. Best regards, Markus Grandpré -- Markus Grandpré Universität Konstanz Kommunikations-, Informations- und Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur Sachgebiet Diensteadministration Tel: ++49 7531 88 4342

2 months, 3 weeks

Re: Link another address

by Quanah Gibson-Mount

--On Tuesday, May 19, 2020 1:13 AM +0000 Brian Carpenter <brian_carpenter(a)emwd.com> wrote: > I am thinking about incorporating the following Postorius/Django account > feature into Affinity: > > Other emails: (no other email) Link another address > > However I cannot think of a serious real-world need for this. What are > the developers' reasoning behind this? Was this feature highly demanded > by Mailman 3 users? Just trying to find out what I am missing here. Here's one use case: I've worked on an open source project for nearly 20 years. Over the course of those years, I've had a variety of different email addresses. The nice thing about being able to link all of them together under my single user ID is that I can find every email I've ever sent to the project lists, regardless of what my address was at the time. Regards, Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

5 years, 3 months

Re: Error downloading CSV for 1,300 members

by Odhiambo Washington

An alternative is to just use the CLI to get the list. Afterall, all you need is the addresses, or no? On Thu, Feb 23, 2023, 21:46 Jose Bernal <jbernal.web.dev(a)gmail.com> wrote: > Any suggestions on troubleshooting downloading a modest-size CSV file for a > list with 1,300 members? Clicking "CSV Export" on smaller lists works > fine, but on this larger list I get this error in mailman-web.log: > > Thu Feb 23 10:03:32 2023 - uwsgi_response_write_body_do(): Broken pipe > [core/writer.c line 429] during GET /mailman3/postorius/lists/ > members.list.ocdla.org/csv_view/ (172.31.54.89) > OSError: write error > > > --------------------- > José Bernal > Web/Application Engineer > Cell 541-228-8481 > jbernal.web.dev(a)gmail.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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to odhiambo(a)gmail.com >

2 years, 6 months

Re: Held messages showing a reason not in English on the Postorious

by Mark Sapiro

On 6/25/24 20:13, Alan KT So (ITSC) wrote: > We just notice a held message from a user's list showing the held reason in Ukrainian, but the interface is in US English and the list's preferred language is English (USA). We could not repeat the issue. What can be the reason behind? > > [cid:image001.png@01DAC7B9.AF2B0400] I'm assuming the image that content filtering removed was a screen shot of the held message view in Postorius. was the sender of the message a list member with preferred language Ukranian? There may be an issue here. The line at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/chains/hold.py… calls format_reasons which will translate the reasons in whatever the current language context is. It should probably explicitly specify the list's preferred language. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 2 months

Re: Header settings and Gmail

by Mark Sapiro

On 7/29/24 12:25, erik(a)dante.de wrote: > > As a preventive measure, it helps to use DMARC mitigation action with “Replace From: with list address” and “ DMARC Mitigate unconditionally ”. But now some users are unhappy with the From header " Username via Test-liste <test(a)test-liste.org>". They would rather have their email address in it. If your Mailman core version is >=3.3.9 you can add `^.*(a)gmail\.com` to dmarc_addresses (DMARC addresses in Postorius) to apply the mitigation to gmail.com addresses instead of unconditionally, but this won't help your gmail users. > Is there a solution with which Google delivers the mailing list messages without complaining, but the sender email address is also in the “From:”? No. This is just one example of Google/gmail behaving oddly. gmail.com publishes a DMARC policy of none, yet they require incoming email From: the gmail.com domain to pass DMARC -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 1 month

Mailman-users search results for query "Postorius"