Search results for "Postorius" - Mailman-users

Re: Default moderation for new members

by Seth Seeger

On Thu, Nov 14, 2019, at 9:33 PM, Mark Sapiro wrote: > > > I’d like to have new members who join my lists have their posting ability set to moderated. (After their first legitimate post, they would set to be unmoderated.) I haven’t been able to find this, though I’m suspecting the language has changed. > > > In Postorius set Settings -> Message Acceptance -> "Default action to > take when a member posts to the list" to Hold for moderation. > > This is the action which will be taken for a post from a member whose > individual Moderation is List Default as it is for all new members. > > Then when a post from that member is held, if you click the subject in > the held messages view, a dialog opens showing the message content with > Accept, Reject and Discard buttons and a dropdown list you can use to > set that member's Moderation to Default processing. > > Default processing is generally what you want as it bypasses the > moderation hold but still applies other tests such as header filters, > administrivia, implicit-dest, max-recipients, max-size, etc. So I've set my "Default action to take when a member posts to the list" to "hold". I'm just unclear on what I want to set each member's moderation action to... defer or accept? (I've been reading the docs, but I'm not clear on the difference.) Thanks, Seth

5 years, 6 months

Re: Moving existing lists to a new domain

by Mark Sapiro

On 9/18/24 10:13, Jeremy Stanley wrote: > > Since all the lists for the given domain will be moving to the same > unused new domain on the existing server, and can move at the same > time, I suppose this could be done through (offline if necessary) > backend database update queries. Yes. For the mailing list, the only changes needed are to the mailinglist table; A query like ``` UPDATE mailinglist SET mail_host = 'new.domain' WHERE mail_host = 'old_domain'; ``` would do, but this leaves the question of list_id. According to RFC 2919, section 4, the list_id should not change, but this is problematic in that if it isn't changed, a Postorius URL like https://example.com/mailman3/lists/list_name@new.domain will retrieve the list, but https://example.com/mailman3/lists/list_name.new.domain will not work. It would need to be https://example.com/mailman3/lists/list_name.old.domain so to reduce confusion, it may be better to update the list_id values A query like the following after the above should do it ``` UPDATE mailinglist SET list_id = CONCAT(list_name, '.', mail_host) WHERE mail_host = 'new_domain'; ``` For HyperKitty, similar changes need to be made to the hyperkitty_mailinglist table. The `name` column entries need to be changed from `listname(a)old.domain` to `listname(a)new.domain` and the `list_id` column entries need to be changed from `listname.old.domain` to `listname.new.domain` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months

Re: Issues with @gmail.com addresses

by Mohsen Masoudfar

I created a new list with this setting. This new created list can send to Gmail addresses, this is very strange, because I have changed the problem list (The list that cannot send to @gmail addresses) settings to match the new one, but still the issue is there. The only difference is that the problem list has been imported from mailman2. Question: is there a command line that displays all the settings of a list? I think it might be some hidden settings that are not visible in the UI? Thanks Mohsen ________________________________ From: Mohsen Masoudfar <mmasoudf(a)aaas.org> Sent: Wednesday, September 6, 2023 1:32 PM To: Mark Sapiro <mark(a)msapiro.net>; mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: Re: [MM3-users] Re: Issues with @gmail.com addresses Thank you Mark for your response as always! I checked the lists having the issue of sending emails to @gmail.com subscribers. They had already these settings (so no changes): DMARC Mitigate unconditionally : yes DMARC mitigation action: Replace From: with list address DMARC rejection notice: empty DMARC wrapped message text: empty I wonder three points: * What would be the next action to fix the issue? * This issue started around the beginning of August. Could it be due to some changes google made recently? * Give the number of Gmail users, this should annoy a bigger community, are you seeing that many upset people? Thanks, Mohsen ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, September 5, 2023 4:17 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Issues with @gmail.com addresses [EXTERNAL EMAIL] 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>, 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> 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 To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to mmasoudf(a)aaas.org

1 year, 9 months

Re: List Migration from MM2.1 -> MM3

by Odhiambo Washington

On Mon, Aug 15, 2022 at 1:31 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 8/14/22 11:04, Odhiambo Washington wrote: > > So I thought I have everything running. Fresh install of MM3 on > > Ubuntu-22.04. > > > > I have created a list in postorius - it has the same name as my old list > in > > MM2. > > > > [image: MM3.png] > > Your image didn't make it through content filtering. > The image only showed a listing of the MLs that I created via postorius. > > What is the fully qualified name of the list > skunkworks(a)lists.my.co.ke > > mailman@lists:~$ /opt/mailman/mm/venv/bin/mailman import21 > skunkworks(a)lists.my.co.ke /var/list/lists/skunkworks/config.pck > > Usage: mailman import21 [OPTIONS] LISTSPEC PICKLE_FILE > > Try 'mailman import21 -h' for help. > > > > Error: No such list: skunkworks(a)lists.my.co.ke > > Apparently the list you created is not named skunkworks(a)lists.my.co.ke Apparently so, because: mailman@lists:~$ /opt/mailman/mm/venv/bin/mailman lists No matching mailing lists found mailman@lists:~$ Which is surprising, given this: https://imgur.com/a/LPrh42K > > What am I missing? > > The Mailman 3 list skunkworks(a)lists.my.co.ke including that exact domain > must exist in order to import to it. Try > > /opt/mailman/mm/venv/bin/mailman create skunkworks(a)lists.my.co.ke root@lists:/home/wash# su - mailman mailman@lists:~$ /opt/mailman/mm/venv/bin/mailman create skunkworks(a)lists.my.co.ke sh: 1: /usr/sbin/postmap: not found sh: 1: /usr/sbin/postmap: not found Traceback (most recent call last): File "/opt/mailman/mm/venv/bin/mailman", line 8, in <module> sys.exit(main()) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/click/core.py", line 1130, in __call__ return self.main(*args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/click/core.py", line 1055, in main rv = self.invoke(ctx) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/mailman/bin/mailman.py", line 69, in invoke return super().invoke(ctx) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/click/core.py", line 1657, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/click/core.py", line 1404, in invoke return ctx.invoke(self.callback, **ctx.params) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/click/core.py", line 760, in invoke return __callback(*args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/click/decorators.py", line 26, in new_func return f(get_current_context(), *args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/mailman/commands/cli_lists.py", line 184, in create mlist = create_list(fqdn_listname, owners) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/mailman/app/lifecycle.py", line 100, in create_list call_name(config.mta.incoming).create(mlist) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/mailman/mta/postfix.py", line 93, in create self.regenerate() File "/opt/mailman/mm/venv/lib/python3.10/site-packages/mailman/mta/postfix.py", line 133, in regenerate raise RuntimeError(NL.join(errors)) RuntimeError: command failure: /usr/sbin/postmap /opt/mailman/var/data/postfix_lmtp, 127, Key has expired command failure: /usr/sbin/postmap /opt/mailman/var/data/postfix_domains, 127, Key has expired Now that wants Postfix, while I don't use Postfix, but Exim as the MTA. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 10 months

Re: Is it possible to add non-members in regex format in Mailman 3 ?

by Abhilash Raj

On Tue, Jun 16, 2020, at 7:09 AM, Shashikanth Komandoor wrote: > Hi Team, > > In mailman 2, I was able to add the non-members in the > respective privileged box even using the regex also which will be used to > add the domains instead of a single mail id. > > But in mailman 3, I am not allowed to add the non members in > the regex format. Of course it is allowing me to add individual mail ids > and give permissions. But I want to add a non-member which may be something > like the entire cisco.com domain on which I want to set the rule. > You can do that with Postorius 1.3.3 (which was released recently) and Mailman Core 3.3.1. > Please help me out by suggesting over this or if mailman 3 is > not providing then please hint me out with a work around at least. > > -- > Thanks & Regards, > Shashi Kanth.K > 9052671936 > > > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> > Virus-free. > www.avast.com > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > _______________________________________________ > 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

mailman3-web MailingList matching query does not exist.

by Loïc Dachary

Hi, The logs of mailman3-web are flooded with the following error. I suspect this is because I removed some mailing lists (using the hyperkitty web interface and the delete button) and the cache still references them. Is there a job supposed to fix this at some point ? Thanks in advance for any tip you can share :-) ii python3-django-hyperkitty 1.3.2-1.1 all Web user interface to access GNU Mailman3 archives ii python3-mailman-hyperkitty 1.1.0-9 all Mailman3 plugin to archive emails with HyperKitty ii mailman3 3.2.1-1 all Mailing list management system ii mailman3-web 0+20180916-10 all Django project integrating Mailman3 Postorius and HyperKitty ii python3-django-mailman3 1.2.0-3 all Django library to help interaction with Mailman3 (Python 3 version) ii python3-mailman-hyperkitty 1.1.0-9 all Mailman3 plugin to archive emails with HyperKitty ii python3-mailmanclient 3.2.2-1 all Python bindings for Mailman3 REST API (Python 3 version) Cheers 15:53:45 [Q] INFO Process-1:8 processing [rebuild_mailinglist_cache_for_month] 15:53:45 [Q] ERROR Failed [rebuild_mailinglist_cache_for_month] - MailingList matching query does not exist. : Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django_q/cluster.py", line 377, in worker res = f(*task['args'], **task['kwargs']) File "/usr/lib/python3/dist-packages/hyperkitty/tasks.py", line 79, in _rebuild_mailinglist_cache_for_month mlist = MailingList.objects.get(name=mlist_name) File "/usr/lib/python3/dist-packages/django/db/models/manager.py", line 85, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 380, in get self.model._meta.object_name hyperkitty.models.mailinglist.DoesNotExist: MailingList matching query does not exist. -- Loïc Dachary, Artisan Logiciel Libre

4 years, 8 months

Re: message awaits moderator approval

by Eggert Ehmke

I think I solved that. The background might be of interest for other admins, and for the developers. I had set up some new mailing lists on that server. I also had deleted an old mailing list for a domain that is no longer hosted on that server. To delete the old mailing list, I used the methods provided by postorius. Now it turned out that there were several relicts of the old list in the database, in particular in the template table. I removed them using direct SQL commands. Now my new mailing lists work as expected. Is this a bug in postorius? I think when I delete a mailing list, all relicts should be deleted from the database. Am Mittwoch, 21. Dezember 2022, 14:46:56 CET schrieb Eggert Ehmke via Mailman- users: > When I send a mail to a list that exceeds the max size, I get the above > answer. However, the moderator of that list does not get a message, and > there is no entry in the list of hold back messages. > > This should be a configuration problem, on another list on the same server > this works fine. I cannot find any differences in the settings. > > > > _______________________________________________ > 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 > /AIYSQM3XBDBQOJTOJQVXRT5PGOVUIJ73/ > > This message sent to eggert(a)eehmke.de

2 years, 5 months

Re: Pck files stuck in out queue

by Lieuallen, Thomas Otis

I ended up emailing the list. That email got stuck as well. So, I removed their template – and the message went through. So, that appears to have been the problem. But, not sure why. Thank you Tom Lieuallen From: Lieuallen, Thomas Otis via Mailman-users <mailman-users(a)mailman3.org> Date: Thursday, February 6, 2025 at 3:25 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Pck files stuck in out queue [This email originated from outside of OSU. Use caution with links and attachments.] Mark, There were no apparent permissions problems on templates. I was getting the ‘Cannot connect to SMTP server’ message in mailman.log. I did end up applying the patch to decorate.py and messages went through. I’ve since removed the patch, as I’m still looking for an answer and might as well let it queue up again. The only thing that is making me ponder at the moment is that the list owners setup a template for list:member:regular:footer in postorius. It appears that each list has a copy of that file. The modifications I see in postorius are not in their …/templates/list/<listname>/en/list:member:regular:footer.txt file. Are their modifications stored somewhere else and causing the problem? Thx Tom Lieuallen From: Mark Sapiro <mark(a)msapiro.net> Date: Thursday, February 6, 2025 at 2:22 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Pck files stuck in out queue [This email originated from outside of OSU. Use caution with links and attachments.] On 2/6/25 12:42, Lieuallen, Thomas Otis via Mailman-users wrote: > Running Mailman 3.3.10 > > I have 11x pck files stuck in my out queue. There tends to always be a .bak file as well. If I run ‘ls -l’, the files are continually updated and rotated through, just as fast as I can look. Are old ones being delivered and new ones added or the same ones just being renamed? I suspect the latter and I suspect the issue in that case is probably due to the OUT runner trying to access a template file like list:member:{regular|generic}:{header|footer}.txt and not having permission. See the last two posts in the thread at https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…><https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> > I believe they’re all for one list. When I use ‘strings’ on one to get a hint of what’s inside, I see the list members at the bottom (recipients). One of them consistently has ‘!’ before their email address. Not sure if that’s a clue. Just no other reason to suspect that, though. The files are python pickles and `strings` shows lots of stuff. The ! may be something in the pickle that's not part of the email address. The way to examine these files is with the `mailman qfile` command. -- 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 To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…><https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…><https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to lieualth(a)oregonstate.edu _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to lieualth(a)oregonstate.edu

4 months, 1 week

Container Images for Mailman 3.2 release

by Abhilash Raj

Hi All, I have updated and pushed releases for Container Images with 3.2 release of the suite. They are available at: docker.io/maxking/mailman-web:0.2 docker.io/maxking/mailman-core:0.2 A similar copy of both is also available at quay: quay.io/maxking/mailman-web:0.2 quay.io/maxking/mailman-core:0.2 The releases contain the following versions of components: mailman-core: - Mailman Core 3.2.0 - Mailman-hyperkitty 1.1.0 mailman-web: - Postorius 1.2.1 - Hyperkitty 1.2.0 - Django-mailman3 1.2.0 - MailmanClient 3.2.0 The upgrade process from 0.1 release should be relative painless, except for the full-text index, which needs to be rebuilt due to the migration from Python 2 to 3 of the full-text indexing library whoosh. You can run the following commands to do so, after the upgrade: $ docker exec -it mailman-web bash bash # python manage.py rebuild_index If you are not using the default docker-compose.yaml file provided in the repo, you need to add an extra environment variable for mailman-web container, POSTORIUS_TEMPLATE_BASE_URL, which defaults to `http://mailman-web:8000`. It should be the URL where your mailman-web container is listening on with HTTP (port 8000 by default). The rolling releases are not being rolled out right everyday now, because of broken build scripts. I'd recommend everyone use the new stable releases that I mentioned above. Going forward, I'll try to release stable versions more often, so that there isn't any need for rolling version, but fixing the rolling releases is on my TODO. Documentation for these images is available at: https://github.com/maxking/docker-mailman -- thanks, Abhilash Raj (maxking)

6 years, 10 months

Re: after last upgrade I've got a CSRF failed verification

by Mark Sapiro

On 10/26/22 04:33, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > I did it via pip and all seems to be working, but when I try to discard > or accept any message via postorius it shows a Forbidden 403 error CSRF > verification failed. > > In my settings.py I have commented out these variables: > > # Other security settings > # SECURE_SSL_REDIRECT = True > # If you set SECURE_SSL_REDIRECT to True, make sure the > SECURE_REDIRECT_EXEMPT > # contains at least this line: > # SECURE_REDIRECT_EXEMPT = [ > # "archives/api/mailman/.*", # Request from Mailman. > # ] > # SESSION_COOKIE_SECURE = True > # SECURE_CONTENT_TYPE_NOSNIFF = True > # SECURE_BROWSER_XSS_FILTER = True > # CSRF_COOKIE_SECURE = True > # CSRF_COOKIE_HTTPONLY = True > # X_FRAME_OPTIONS = 'DENY' > > I've been messing with them whith no results. It's like it lacked some > value in some template... It's not an issue with the code per se or the templates. These updates are all installed on mail.python.org and lists.mailman3.org and are working fine. After upgrading did you run django-admin collectstatic --clear django-admin compress django admin migrate If you have and it doesn't help, you probably need to add CSRF_TRUSTED_ORIGINS to your settings.py. See https://docs.djangoproject.com/en/4.1/ref/settings/#csrf-trusted-origins and note the differences between Django <4.0 and >=4.0. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 7 months

Mailman-users search results for query "Postorius"