Search results for "Postorius" - Mailman-users

Equivalent of listadmin Perl script for Mailman 3?

by Stephen J. Turnbull

Philip Colmer writes: > We're preparing to migrate about 4 Mailman 2 servers to Mailman 3. In doing > so, one of our list administrators has informed us that he uses "listadmin" > Does anyone know if there is an equivalent tool that works with Mailman 3? I don't know of one, but perhaps someone does. It probably wouldn't be hard to write a bare-bones workalike if the admin has shell access to the mailman host. UIn theory, shell access could be restricted to running the tool by using a 'command' option in the sshd authorized_keys file for the user's key. But I'm not competent to judge how secure that could be in principle, and of course if the tool is buggy in certain ways, all bets are off.) I can't estimate how hard it would be to write one without shell access, as I'm not sure how amenable the Postorius web UI is to scripting. Steve

4 years, 2 months

Re: Issues with @gmail.com addresses

by Allan Hansen

Once this gets handled, Mohsen, Google has another issue with list servers: If a subscriber who uses GMail posts a message to a list, then that subscriber will not get his/her own message from the server - Google eats it. All other subscribers will get it, but not the author. My subscribers run into this all the time and are up in arms over it. I tell them to complain to Google. Yours, Allan On 9/5/23, 13:18, "Mark Sapiro" <mark(a)msapiro.net <mailto:mark@msapiro.net>> wrote: On 9/5/23 12:59, Mohsen Masoudfar wrote: > Hi, > > since 8/1/2023 I get complains from users with @gmail.com addresses, that they are not getting any emails. > I checked the logs and I see that the emails are going out: > > to=<xxxx(a)gmail.com <mailto:xxxx@gmail.com>>, relay=email-smtp.us-east-1.amazonaws.com[35.169.171.20]:587, delay=0.46, delays=0.03/0.06/0.13/0.24, dsn=2.0.0, status=sent (250 Ok xxx ) > > But it seems the users are getting email delivered to them. > I’ve advised them to check their spam, promotions, and social folders and to add the list address to their email safe-senders lists, but still no success. > Is there any way to help this list members? Even though gmail publishes a DMARC policy of none, it has recently started enforcing a stricter policy for mail From: the gmail.com domain. You need to apply DMARC mitigations to mail From: the gmail.com domain. There are two ways to do this. One way is to set DMARC Mitigations -> DMARC Mitigate unconditionally to Yes (and set DMARC mitigation action appropriately) The other way requires upgrading Postorius and Mailman core to the heads of the GitLab branches (core=3.3.9b1, postorius=1.3.9b1). Doing this enables a DMARC Addresses setting which can be set to `^.*(a)gmail\.com$` to apply DMARC mitigatations to mail From: the gmail.com domain regardless of it's published policy. -- Mark Sapiro <mark(a)msapiro.net <mailto:mark@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 <mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org <mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org <mailto:mailman-users@mailman3.org>/message/WZY5IC3OVHVBHIGDT4TE3EWSSGMF6CYI/ This message sent to hansen(a)rc.org <mailto:hansen@rc.org>

2 years, 4 months

Re: "Private archives" aren't private

by Simon HANNA

On July 28, 2017 10:55:43 AM GMT+02:00, cyp(a)trojina.si wrote: >Hi, > >I'm having the same problem: changes to the "Archive policy" settings >in postorius are not reflected in hyperkitty. Trying to use >mailman_sync to fix this gave me the same BaseCommand traceback as >above, but "mlist_object.update_from_mailman()" works. So luckily we >have a workaround, thanks. But I suspect that there's some >misconfiguration or permission problem on our server that's blocking >the automatic synchronisation from taking place. Any advice to >resolving this would be appreciated. :) It's fixed in master, and just needs a release. https://gitlab.com/mailman/hyperkitty/issues/135 @abompard what's the policy on bug fix releases? If mailman 3 should get adopted, I guess pushing such fixes quickly shows people that even if they encounter bugs, they get fixed right away... Otherwise they would just wait for it to "mature" cheers Simon -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

8 years, 5 months

Re: Disable archives per list

by Mark Sapiro

On 2/25/21 1:57 AM, Bernd Wurst wrote: > > Can I as the server admin disable archiving (or set other list options) > in a way that the list admin can not change it via postorious? As the server admin, you can enable/disable archivers sitewide. See <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.…> et seq. Note that the prototype archiver, if enabled, stores messages in the file system in maildir format. Normally a list admin can select which of the enabled archivers is active for that list via Postorius. To prevent this, you would have to modify Postorius. It would be easy enough to just remove settings from the relevant templates. > Can I have custom archiver settings per list or per domain > (customer-specific hyperkitty)? I'm not sure what you mean by "custom archiver settings", but other than enable/disable and public/private, probably not. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

Re: My list has been switched from public to private archives, but they are still visible

by Enrique Terrazas

Thank you Abhilash, I appreciate your prompt response. What about the once private archives becoming public after setting a list to “Do not archive this list”? Regards, Enrique On Sep 19, 2019, at 1:38 PM, Abhilash Raj <maxking(a)asynchronous.in<mailto:maxking@asynchronous.in>> wrote: On Thu, Sep 19, 2019, at 11:15 AM, Enrique Terrazas wrote: I am having a very similar issue. Here is what I have found: There are basically three archive settings we can select via the postorious web front end for archives. These can be found in: Settings Archiving and they are: Public archives Private archives Do not archive this list This is interface of Mailman to set the archives. In the Django administrative interface we can find those same(?/similar?) settings here: Main Page > Hyperkitty > Mailing lists Mailing List object(x) > Archive policy: never private public This is basically a hotline to the database. You can change these values, but they would be overriden with the values that are in Mailman Core on the daily cron job run. I would suggest not to tinker with values there since you could leave database in a corrupted state. Since there is an ORM layer there, chances are less but still a possibility :) I’m not sure which of the two takes precedence. My guess is postorius since that is a list owner accessible setting and the Django administrative interface would typically not be accessible to list owners. We have noticed the following odd behavior, not sure if it is a bug. For existing lists with private archives, when switching to “Do not archive this list” in postorious, the desired effect of no longer archiving the list is instantaneous. However, after the daily cron job that syncs with Mailman Core happens, the existing archives now become publicly accessible. Is this behavior based on the assumption that the list will no longer be archived and will therefore be purged? Source of truth is Mailman Core's database. Postorius is a front-end to change that and owners have permissions to do that. Hyperkitty only syncs back that information daily. I have a fix in the master which makes such that this information is synced synchronously and is available immediately to Hyperkitty. For now, you could either run the "python manage.py runjobs --daily" or wait for a day if that is possible. Enrique On Sep 19, 2019, at 1:08 PM, Abhilash Raj <maxking(a)asynchronous.in<mailto:maxking@asynchronous.in>> wrote: On Thu, Sep 19, 2019, at 3:31 AM, Paul Arenson wrote: Can anyone help with this? I set my list to private archives today. Up until then, it was pubic. And yet, if you go to the list page, you will see that if you click archives (top left), you can see them. (Filled with a bunch of tests posts for now) This change takes a bit of time to sync up Hyperkitty. THere is a daily cron job which syncs this information from Mailman Core. I have made a change which should fix this problem and the process would become synchronous. You can run `python manage.py runjobs --daily` command to force sync that information. https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flist.toky… Am I misunderstanding what a private archive is? Not really, your expectation is right. Is something wrong with my setup (which is hosted)? Thank you. _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… -- thanks, Abhilash Raj (maxking) _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… -- thanks, Abhilash Raj (maxking) _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

6 years, 4 months

Re: Subscription issue with ghost confirmations

by Brian Carpenter

On 10/29/20 12:21 PM, Mark Sapiro wrote: > On 10/29/20 8:51 AM, Brian Carpenter wrote: >> On 10/29/20 11:33 AM, Mark Sapiro wrote: >>> The real question is if a user has a subscription waiting confirmation >>> and the policy is changed to moderate, is a second request rejected >>> because of the request waiting confirmation. If so, I think this is a >>> bug which should be fixed. >>> >> Do you think this is a bug with Mailman core or my system? > > If the current policy is moderate and the user has a prior request > waiting confirmation and a new request is rejected because of the prior > request waiting confirmation, I think that is a bug in core, but I don't > know if that is the case or not. I think it is a bug in Mailman 3 core. I am seeing the same behavior on my Postorius server. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 2 months

Re: Where does sender postorius@ come from?

by Jens Günther

Thanks for the hint. Unfortunately it's not working as expected. I'm using the docker-setup and tried it in 2 different locations, but neither got the expected effect: - I put the variable in the mm-web-container-environment: mm-web: environment: - EMAIL_CONFIRMATION_FROM=myaddress(a)something.org - Then I tried settings_local.py with: EMAIL_CONFIRMATION_FROM = 'myaddress(a)something.org' What am I missing, where do I have to set this value correctly? Thanks for the help! Jens. Am 08.06.23 um 01:57 schrieb Mark Sapiro: > On 6/7/23 14:13, Jens Günther wrote: >> >> The more important question would be, where :-) since I already >> checked if I can set it to something alse, I might need a hint where >> exactly I can find it. In the SERVE_FROM_DOMAIN/admin I did not >> stumble upon it. If you don't know it, no problem, let's just wait for >> somebody who does, thanks. > > > It's the EMAIL_CONFIRMATION_FROM setting in your Django settings. >

2 years, 7 months

Re: New year releases!

by Torge Riedel

Dears, I like to know and discuss ideas to get the update process more stable! Today I updated core and web of mailman3 and ran into all the issues you can have: - Dependencies are not updated properly - In case you use "--force-reinstall" Django gets also updated in web and you need to update the urls.py file accordingly - Enhancement of settings file required (DEFAULT_AUTO_FIELD = ...) Finally I got it working, but there is always the fear for breaking something on update. I know it is open source and no one gets paid for the work. But I think there is space for improvement here. Kind regards Torge Am 04.01.23 um 10:59 schrieb Abhilash Raj: > Hello Everyone, > > Happy new year! > > I am pleased to announce several new releases for GNU Mailman project. > > 1. Mailman Core 3.3.8 [1] > 2. Postorius 1.3.8 [2] > 3. Hyperkitty 1.3.7 [3] > 4. Mailmanclient 3.3.5 [4] > 5. Django-mailman3 1.3.9 [5] > 6. Mailman-hyperkitty 1.2.1 [6] > > All the releases are published to PyPI and you can find links to all the PyPI projects: > > https://docs.mailman3.org/en/latest/ > > A full list of change logs are available below: > > [1]: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… > [2]: https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-8 > [3]: https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-7 > [4]: https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… > [5]: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst > [6]: https://gitlab.com/mailman/mailman-hyperkitty/-/blob/master/README.rst > > Finally, the minimum Python version required is 3.7, and all the components now support Python 3.7 to 3.11. > > Thanks to all the contributors for making this release possible! > > If you find any issues, you can report them at the respective bug tracker for the projects. The links to issue trackers are available > here: https://docs.mailman3.org/en/latest/ > > Installation documentation is available at > > https://docs.mailman3.org/en/latest/install/install.html > > and if you are upgrading an existing virtualenv install you can refer > > https://docs.mailman3.org/en/latest/upgrade-3.2.html > > > > _______________________________________________ > 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 torgeriedel(a)gmx.de

2 years, 11 months

Re: New year releases!

by Jeff

I finally got around to doing this upgrade. I followed the instructions at: https://docs.mailman3.org/en/latest/upgrade-3.2.html Everything seemed to go fine but, mailman3 failed to start because “_BindParamClause” could not be found in sqlalchemy.sql.expression. It looks like alembic-1.6.2 is not completely compatible with SQLAlchemy-2.0.6. I fixed the problem by hacking sqla_compat.py in alembic-1.6.2, but should Mailman start requiring a newer version of alembic? > On Jan 4, 2023, at 4:59 AM, Abhilash Raj <maxking(a)asynchronous.in> wrote: > > Hello Everyone, > > Happy new year! > > I am pleased to announce several new releases for GNU Mailman project. > > 1. Mailman Core 3.3.8 [1] > 2. Postorius 1.3.8 [2] > 3. Hyperkitty 1.3.7 [3] > 4. Mailmanclient 3.3.5 [4] > 5. Django-mailman3 1.3.9 [5] > 6. Mailman-hyperkitty 1.2.1 [6] > > All the releases are published to PyPI and you can find links to all the PyPI projects: > > https://docs.mailman3.org/en/latest/ > > A full list of change logs are available below: > > [1]: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… > [2]: https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-8 > [3]: https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-7 > [4]: https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… > [5]: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst > [6]: https://gitlab.com/mailman/mailman-hyperkitty/-/blob/master/README.rst > > Finally, the minimum Python version required is 3.7, and all the components now support Python 3.7 to 3.11. > > Thanks to all the contributors for making this release possible! > > If you find any issues, you can report them at the respective bug tracker for the projects. The links to issue trackers are available > here: https://docs.mailman3.org/en/latest/ > > Installation documentation is available at > > https://docs.mailman3.org/en/latest/install/install.html > > and if you are upgrading an existing virtualenv install you can refer > > https://docs.mailman3.org/en/latest/upgrade-3.2.html > > > -- > thanks, > Abhilash Raj (maxking) > _______________________________________________ > 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 mm3(a)steele.com ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/vnd.microsoft.icon Name: favicon.ico Replaced multipart/alternative part with first alternative.

2 years, 10 months

Re: New platform administrators

by Abhilash Raj

On Tue, Sep 18, 2018, at 1:14 PM, Simon Hanna wrote: > On 9/18/18 5:42 PM, Hellen Cubero wrote: > > Hello! > > I would like to know how to add a new site administrator to the mailman 3.2 > > platform. Can you help me please? > > You are probably referring to Postorius the webui? > > If yes, you just add another superuser. If the admin is enabled, you can > just visit https://you-url/admin sign in, and create a new user with > staff and superuser permissions. > > You can also do that on the cli using ./manage.py createsuperuser A better way would be to ask them to sign-up as a regular user and then you can go into the Admin Console (/admin) and add flags for Superuser for the user you want to promote. Create Superuser and Django's create user interfaces don't tie up with all-auth, which creates problems because their EmailAddress records aren't created, like they should be. -- thanks, Abhilash Raj (maxking)

7 years, 4 months

Mailman-users search results for query "Postorius"