Search results for "sapiro" - lists.mailman3.org

[MM3-users] Re: Mailman REST API not available. Please start Mailman core.

by Christian

I followed instructions provided here. Well, I rebooted the server and I'm getting the same error again at the web page of "Mailman REST API not available. Please start Mailman core." I again found locks in /opt/mailman/mm/var/locks . Once I removed them I could start mailman. Perhaps I made a boo boo. I want mailman to start without locks upon reboot. Help! (thanks) -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, February 12, 2025 1:12 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Mailman REST API not available. Please start Mailman core. On 2/12/25 12:05, Christian via Mailman-users wrote: > That worked. > > Now on > https://docs.mailman3.org/en/latest/install/virtualenv.html#starting-m > ailman > -automatically it says > > "Pay attention to the config file output above and make sure that you > see /etc/mailman3/mailman.cfg there. If the config path is different, > you should make sure to create a new config file at > /etc/mailman3/mailman.cfg and re-run the command." > > Well...mailman info yields > > GNU Mailman 3.3.5 (Tom Sawyer) > Python 3.7.3 (default, Mar 23 2024, 16:12:05) [GCC 8.3.0] config file: > /opt/mailman/mm/mailman.cfg db url: > postgres://mailman:5DqTHnv8hUQSdd@localhost/mailman > devmode: DISABLED > REST root url: http://localhost:8001/3.1/ REST credentials: > restadmin:restpass > > Should I create a new config file at /etc/mailman3/mailman.cfg ? You can, but the easiest thing is just replace the line Environment="MAILMAN_CONFIG_FILE=/etc/mailman3/mailman.cfg" in /etc/systemd/system/mailman3.service with Environment="MAILMAN_CONFIG_FILE=/opt/mailman/mm/mailman.cfg" -- 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/ NYAIOPZ3PLQCPT3QPLLRKMOUY52UORBM/ This message sent to csa(a)web-analysts.net

2 months, 1 week

[MM3-users] Re: Congrats on the instructions for installation on ubuntu, what about migration?

by Bill Oliver

Thanks. I'll think on that. My tables have a different prefix, so I'll have to remember where to change those config files... billo On Wed, 2024-10-09 at 13:18 -0700, Mark Sapiro wrote: > On 10/8/24 5:45 PM, Bill Oliver wrote: > > > > Is there a tutorial/instructions on migrating data from an old > > system > > to a new one? It's actually not the end of the world if I don't > > get > > all the old emails transferred, but I'd like to get the email > > addresses > > of the participants moved over easily... I believe that I set it > > up > > in 2020, but did not do any version upgrades since then... > > > There's no explicit doc, but there are some posts in the archives of > this list, e.g. > < > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/me > ssage/FTIC47FPQER5FLR4IW4CGI7JB6ALKIX4/>. > > The easiest scenario is if you want to migrate everything. You just > dump > the database on the old server and load it on the new one using the > database manager's tools. > > If you only want to move some, but not all lists, it's more > complicated, > but possibly the easiest thing is to migrate everything and then > delete > the unwanted lists and their archives from Postorius and HyperKitty. > > > -- > 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://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 billo(a)billoblog.com

6 months, 2 weeks

[MM3-users] Re: Performance issues with Mailman 3

by Wong, Wesley

I can confirm the settings on the old Mailman 2.1 setup had "VERP_DELIVERY_INTERVAL=0" set. In Mailman 3, I had copied the configuration from an example with the following defined for the mta: verp_confirmations: yes verp_personalized_deliveries: yes verp_delivery_interval: 1 I'll disable it and see how things go on it. -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, October 7, 2022 5:19 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Performance issues with Mailman 3 On 10/6/22 15:08, Wong, Wesley wrote: > Hi, I am having some performance problems with Mailman 3 (version 3.3.5) when it sends out a lot of messages to people. We recently migrated from our old Mailman 2.1.x system to Mailman 3.x about 3 months ago. We host about 350 lists with membership counts varying between 10 to 1500 members on some of the lists. I noticed that outbound messages from Mailman to our outbound SMTP are getting delayed up to an hour when Mailman is processing a lot of messages going to lists. I suspect the difference is your Mailman 3 instance has full VERP enabled and your Mailman 2.1 instance did not. I.e., In MM 2.1, you did not override the default `VERP_DELIVERY_INTERVAL = 0` in mm_cfg.py, but in MM 3 you have `verp_delivery_interval: 1` in the `mta` section of mailman.cfg. > I was wondering if there are good performance tuning tips to be considered for Mailman 3 (i.e. OS, database and/os Mailman Core). I am running the setup on a VM. Here is my configuration for VM and OS: Search the Titles for `performance` at https://wiki.list.org/. The articles you find are all written for MM 2.1, but you're really dealing with the MTA and the issues are the same for MM 3. -- 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

2 years, 6 months

[MM3-users] Re: Welcome message issue

by Mohsen Masoudfar

Thank you Mark! You are helpful as always. I am running: Postorius Version 1.1.2 That explains the issue. Mohsen ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, October 22, 2024 5:38 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Welcome message issue [EXTERNAL EMAIL] On 10/22/24 13:34, Mohsen Masoudfar wrote: > Good afternoon > I have an issue with welcome message. > > A list owner is requesting to update the welcome message for only one of their lists. They are requesting to change the default text and insert additional URLs pointing to sites related to their list. > I know there is a URI field that you may include a web page. But this doesn't work and gets ignored. If you are referring to the `uri` field in the template table this should work if the `name` is `list:user:notice:welcome` and the `context` is the list_id of the target list. > - is there a mailman cli option to update the default template for a single list? There is no specific cli option. A site admin can address this by creating a custom template at Mailman's var/templates/lists/LIST_ID/LC/list:user:notice:welcome.txt where LIST_ID is the desired lists ID and LC is the preferred language. The list owner can create a custom list:user:notice:welcome template via Postorius. > > I couldn't find it in WUI. Do you mean GUI? If so, since at least Postorius 1.2.0 there has been a `Templates` choice in the second level nav in the lists view. > I reviewed all parameters and variables of the list and couldn't find one that might be related to it. > > We are running an old version of Mailman 3. -- 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

5 months, 3 weeks

[MM3-users] Re: Different Mail Domain Cause Key Error

by Mark Sapiro

On 4/21/20 1:10 PM, Brian Carpenter wrote: > > Ok. The first thing however is did I miss a step? Not really. The problem is FILTER_VHOST = True doesn't work for web hosts that aren't email hosts. > Here is the complete error that is sent to me via email as superuser: > > > Internal Server Error:/mailman3/lists/ > > KeyError at/mailman3/lists/ > 'file' > > Traceback: > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/handlers/exception.py" > in inner > 34. response = get_response(request) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/handlers/base.py" > in _get_response > 115. response = > self.process_exception_by_middleware(e, request) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/handlers/base.py" > in _get_response > 113. response = wrapped_callback(request, > *callback_args, **callback_kwargs) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/postorius/views/list.py" > in list_index > 755. paginator_class=MailmanPaginator) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django_mailman3/lib/paginator.py" > in paginate > 71. objects = paginator.page(page_num) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django_mailman3/lib/paginator.py" > in page > 46. number = self.validate_number(number) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/paginator.py" > in validate_number > 48. if number > self.num_pages: > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/utils/functional.py" > in __get__ > 80. res = instance.__dict__[self.name] = self.func(instance) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/paginator.py" > in num_pages > 97. if self.count == 0 and not self.allow_empty_first_page: > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/utils/functional.py" > in __get__ > 80. res = instance.__dict__[self.name] = self.func(instance) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django_mailman3/lib/paginator.py" > in count > 56. return self.function(count=0, page=1).total_size > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/postorius/views/list.py" > in _get_list_page > 751. advertised=advertised, mail_host=mail_host, > count=count, page=page) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailmanclient/client.py" > in get_list_page > 181. return Page(self._connection, url, MailingList, count, page) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailmanclient/restbase/page.py" > in __init__ > 37. self._create_page() > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailmanclient/restbase/page.py" > in _create_page > 62. response, content = self._connection.call(self._build_url()) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailmanclient/restbase/connection.py" > in call > 112. error_msg, response, None) > > *During handling of the above exception (HTTP Error 404: {"title": "404 > Not Found"}), another exception occurred:* The above 404 is the underlying problem. In the traceback above we see that /opt/mailman/mm/venv/lib/python3.7/site-packages/postorius/views/list.py at line 751 calls client to get the view for lists for this host. The full code is def _get_list_page(count, page): client = get_mailman_client() advertised = not request.user.is_superuser mail_host = request.get_host().split(":")[0] if ( getattr(settings, 'FILTER_VHOST', False)) else None return client.get_list_page( advertised=advertised, mail_host=mail_host, count=count, page=page) The issue is the FILTER_VHOST = True setting is broken. This is <https://gitlab.com/mailman/postorius/-/issues/394> The broken code tries to get the lists for the domain in the requesting URL which here is the web_host but the web_host has no lists. This is a complicated issue. See the whole comment thread in the issue where I am trying to mentor someone to a fix, but he apparently has given up. The issue is we don't have a method for retrieving lists by web host. It is simple enough to get all the email hosts associated with a web host, but what do we do if that's more than one email host. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: Have postgresql in the mailman.cfg file but sqlite shows in the mailman info command

by Mark Sapiro

On May 29, 2024 12:50:00 PM EDT, Keith Christian <keith1christian(a)gmail.com> wrote: > >Uncommented class and url: >class: mailman.database.postgresql.PostgreSQLDatabase ><<<---------------------------------------- >url: postgresql://mailman:MYPASSWORD@localhost/mailman ><<<---------------------------------------- > > >Now I get a stack trace from "mailman info" > >(venv) [mailman3@localhost-live ~]$ mailman info >Traceback (most recent call last): > File "/opt/mailman3/venv/bin/mailman", line 33, in <module> > sys.exit(load_entry_point('mailman==3.3.9', 'console_scripts', 'mailman')()) > File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", >line 1157, in __call__ > return self.main(*args, **kwargs) > File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", >line 1077, in main > with self.make_context(prog_name, args, **extra) as ctx: > File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", >line 943, in make_context > self.parse_args(ctx, args) > File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", >line 1644, in parse_args > rest = super().parse_args(ctx, args) > File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", >line 1408, in parse_args > value, args = param.handle_parse_result(ctx, opts, args) > File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", >line 2400, in handle_parse_result > value = self.process_value(ctx, value) > File "/opt/mailman3/venv/lib64/python3.9/site-packages/click/core.py", >line 2362, in process_value > value = self.callback(ctx, self, value) > File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/bin/mailman.py", >line 95, in initialize_config > initialize(value) > File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/core/initialize.py", >line 228, in initialize > initialize_1(config_path) > File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/core/initialize.py", >line 122, in initialize_1 > mailman.config.config.load(config_path) > File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/config/config.py", >line 145, in load > self.push(filename, user_config.read()) > File "/opt/mailman3/venv/lib64/python3.9/site-packages/mailman/config/config.py", >line 150, in push > self._config.push(config_name, config_string) > File "/opt/mailman3/venv/lib64/python3.9/site-packages/lazr/config/_config.py", >line 582, in push > confs = self._getExtendedConfs(conf_name, conf_data) > File "/opt/mailman3/venv/lib64/python3.9/site-packages/lazr/config/_config.py", >line 615, in _getExtendedConfs > _parser_read_file(parser, StringIO(conf_data), conf_filename) > File "/opt/mailman3/venv/lib64/python3.9/site-packages/lazr/config/_config.py", >line 49, in _parser_read_file > parser.read_file(f, source) > File "/usr/lib64/python3.9/configparser.py", line 718, in read_file > self._read(f, source) > File "/usr/lib64/python3.9/configparser.py", line 1085, in _read > raise MissingSectionHeaderError(fpname, lineno, line) >configparser.MissingSectionHeaderError: File contains no section headers. >file: '/opt/mailman3/mailman.cfg', line: 14 ><<<---------------------------------------- >'class: mailman.database.postgresql.PostgreSQLDatabase\n' > > >Here is the complete mailman.cfg file: > > 1 # /etc/mailman3/mailman.cfg > 2 # [paths.here] > 3 # var_dir: /opt/mailman/mm/var > 4 # > 5 # [mailman] > 6 # layout: here > 7 # # This address is the "site owner" address. Certain >messages which must be > 8 # # delivered to a human, but which can't be delivered to a >list owner (e.g. a > 9 # # bounce from a list owner), will be sent to this address. >It should point to > 10 # # a human. > 11 # site_owner: user(a)example.com > 12 # > 13 # [database] > 14 # class: mailman.database.postgresql.PostgreSQLDatabase > 15 # url: postgresql://mailman:MYPASSWORD@localhost/mailman > 16 # > 17 # [archiver.prototype] > 18 # enable: yes > 19 # > 20 # # For the HyperKitty archiver. > 21 # [archiver.hyperkitty] > 22 # class: mailman_hyperkitty.Archiver > 23 # enable: yes > 24 # configuration: /etc/mailman3/mailman-hyperkitty.cfg > 25 # > 26 # [shell] > 27 # history_file: $var_dir/history.py > 28 # > 29 # [mta] > 30 # verp_confirmations: yes > 31 # verp_personalized_deliveries: yes > 32 # verp_delivery_interval: 1 > 33 # If you uncomment any of the lines in this config, you must also uncomment the preceding section header, line 13 in this case. -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

10 months, 3 weeks

[MM3-users] Re: Apple Mail encoding again

by Rainer Herbst

On Mi, 20 Apr 2022 10:01:55 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 4/20/22 07:54, Rainer Herbst wrote: >> Dear all, >> >> my first post was to optimistic - the user tested some other >>combinations and when he tries to send a signed HTML mail, the server >>again refuses to accept it with "Diagnostic-Code: smtp; 501 Message >>has defects". >> >> The user suggested that the problem is caused by a line containing >>only "-- " somewhere in the text, but I can not confirm this. >> >> Please find enclosed the refused mail (anonymized). > > That message has no defects. > ``` > >>> import email > >>> from mailman.email.message import Message > >>> txt = b""" (the testmail-abgelehnt.txt contents) """ > >>> msg = email.message_from_bytes(txt, Message) > >>> msg.defects > [] > >>> > ``` > Maybe I have deleted to much when anonymizing the message... I tested the whole message and it gave me: >>> msg.defects [InvalidMultipartContentTransferEncodingDefect()] Than I reduced the message content. The minimal message that provoked the defect is attached. When I delete line 12 ("Content-Transfer-Encoding: quoted-printable") from the message, the defect disapears. > -- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Viele Grüße Rainer Herbst Leiter IT-Service Phone: +49 331 7499-257 e-mail: rainer.herbst(a)aip.de https://www.aip.de ----------------------------------------------------------------------------------------------- Leibniz-Institut für Astrophysik Potsdam (AIP) An der Sternwarte 16, 14482 Potsdam Vorstand: Prof. Dr. Matthias Steinmetz, Wolfram Rosenbach Stiftung bürgerlichen Rechts Stiftungsverzeichnis Brandenburg: 26 742-00/7026 ----------------------------------------------------------------------------------------------- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: application/x-pkcs7-signature Name: smime.p7s

3 years

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Onyeibo Oku

On Thu Oct 13, 2022 at 6:03 AM WAT, Onyeibo Oku wrote: > On Wed, 12 Oct 2022 17:52:47 -0700 > Mark Sapiro <mark(a)msapiro.net> wrote: > > Thanks Eggert and Sapiro. > > > > > As Eggert suggests, see > > https://docs.mailman3.org/en/latest/install/virtualenv.html and > > follow that. > So far, this has been an interesting exercise. Mailman3 (core) is running but not Hyperkitty and Postorious. My setup is different though. I am running a system-wide instance of uwsgi. At the moment, uwsgi is serving a website. It is running in Emperor-tyrant mode. Hence, it can serve multiple django projects. I only need to add the relevant .ini file at /etc/uwsgi.d/ and it spawns a service for that. I have added mailman3.ini (taken from the suggested page above) into the /etc/uwsgi.d/ directory. This is what "systemctl status uwsgi" says: Oct 31 06:57:18 mail.server.tld uwsgi[20676]: [uWSGI] getting INI configuration from mailman3.ini Oct 31 06:57:18 mail.server.tld uwsgi[20676]: unable to find logger file Oct 31 06:57:18 mail.server.tld uwsgi[20261]: Mon Oct 31 06:57:18 2022 - [emperor] curse the uwsgi instance mailman3.ini (pid: 20676) Oct 31 06:57:21 mail.server.tld uwsgi[20261]: Mon Oct 31 06:57:21 2022 - [emperor] removed uwsgi instance mailman3.ini Oct 31 06:58:30 mail.server.tld uwsgi[20684]: [emperor-tyrant] dropping privileges to 973 972 for instance mailman3.ini Oct 31 06:58:30 mail.server.tld uwsgi[20684]: *** has_emperor mode detected (fd:9) *** Oct 31 06:58:30 mail.server.tld uwsgi[20684]: [uWSGI] getting INI configuration from mailman3.ini Oct 31 06:58:30 mail.server.tld uwsgi[20684]: unable to find logger file Oct 31 06:58:30 mail.server.tld uwsgi[20261]: Mon Oct 31 06:58:30 2022 - [emperor] curse the uwsgi instance mailman3.ini (pid: 20684) Oct 31 06:58:33 mail.server.tld uwsgi[20261]: Mon Oct 31 06:58:33 2022 - [emperor] removed uwsgi instance mailman3.ini It is not finding the logger file. The other django project on this machine is running fine. I can confirm that the logger plugin is installed. I must be missing something. Regards Onyeibo

2 years, 5 months

[MM3-users] Re: bounce handling in mm3 available?

by Stefan Bauer

Hi Mark, thank you. We are running 3.1.1-9. So to get you right, this version only records the bounces in database and nothing more? No disabling of users etc. Stefan Am Mo., 24. Jan. 2022 um 23:32 Uhr schrieb Mark Sapiro <mark(a)msapiro.net>: > On 1/24/22 05:20, Stefan Bauer wrote: > > Hi, > > > > what happens with bounce-mails that are processed by mailmans postfix > > instance? > > > What Mailman core version? Prior to 3.3.1, bounce events were recorded > in the bounceevent table but not otherwise processed. Subsequent to > that, they are scored if recognized and what notices are sent depends on > list settings. > > > > Jan 24 10:46:03 l01 postfix/lmtp[8432]: DF4AE600623: > > to=<company-newsletter-bounces(a)lists.company.tld>, > > relay=127.0.0.1[127.0.0.1]:8024, delay=0.03, delays=0.01/0.01/0/0.01, > > dsn=2.0.0, status=sent (250 Ok) > > > > But the list-owner does not get any notification, nor do i see any > > bounce-information in the pistorious-gui. > > What are you expecting to see in Postorius? All you can see is if a > member's delivery status is Disabled by Bounces. Things like Bounce > score are not available in Postorius. > > What notices are sent depends on the settings in the Bounce Processing > section in Postorius. For example, if your message logged by postfix was > spam to the <company-newsletter-bounces(a)lists.company.tld> address that > is not recognized as a DSN and `Forward unrecognized bounces` is > Discard, the message will be silently discarded. > > Also, if that message was a non-fatal, message-delayed type of DSN, it > will be ignored. > > -- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

3 years, 2 months

[MM3-users] Re: Disabled by bounce

by tlhackque

On 02-Feb-23 16:43, Mark Sapiro wrote: > On 2/2/23 04:54, Danil Smirnov wrote: >> Hi Mark >> >> On Wed, Feb 1, 2023 at 9:28 PM Mark Sapiro <mark(a)msapiro.net> wrote: >> >>> Yes and no. If 'Bounce info stale after' is set to 3d and no bounces >>> for >>> a user are received in a 3 day period, the user's bounce score is not >>> immediately reset, but it will be reset (to 1) the next time a >>> bounce is >>> received for the user. I.e., it is effectively the same thing unless >>> you >>> are looking at the user's bounce score which doesn't change until the >>> next bounce. >>> >> >> Isn't this a bug? We are now showing users' bounce scores on the Members >> page and this would be misleading. Is it difficult from internals >> perspective to have the bounce score reset immediately? > > > Yes, it is not difficult, but it's a lot of processing. It would > require something like a task runner task to periodically look at each > row in the member table and if the bounce score is > 0, find the > associated list's bounce_info_stale_after and if last_bounce_received > + bounce_info_stale_after < now, reset the score. > > Consider a site like mail.python.org that at this moment has 79024 > rows in the member table and 7531 of those have bounce_score > 0. > That's a lot of processing, and is it really an issue to show a > non-zero bounce score that's stale? > There's a middle ground. Seems like the sort of thing to do daily. Loose consistency would be good enough. Waiting for the next bounce - which on a low traffic list could be a long time coming - does seem difficult to explain that to users. A daily update seems easier to explain.

2 years, 2 months

[MM3-users] Re: Mails are stuck in Mailman Pipeline Queue

by Mark Sapiro

On 3/26/22 21:01, Shashikanth Komandoor wrote: > > But the below trace back is observed during mailman service stopping: This doesn't say much ... ...> Mar 27 09:01:22 2022 (5864) Uncaught runner exception: > Mar 27 09:01:22 2022 (5864) Traceback (most recent call last): > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", > line 173, in _one_iteration ... > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", > line 114, in signal_handler > raise RunnerInterrupt > mailman.interfaces.runner.RunnerInterrupt > Mar 27 09:01:22 2022 (5864) SHUNTING: 1648351882.6693938+ > c2e6ed709646a7680c73059b52d2f0451836e591 > Mar 27 09:01:22 2022 (5864) digest runner exiting. Above, digest runner was interrupted in processing and shunted the message it was working on. and below, pipeline runner was interrupted in processing and shunted the message it was working on. > Mar 27 09:01:22 2022 (5860) Uncaught runner exception: > Mar 27 09:01:22 2022 (5860) Traceback (most recent call last): > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", > line 173, in _one_iteration > self._process_one_file(msg, msgdata) > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", > line 266, in _process_one_file > keepqueued = self._dispose(mlist, msg, msgdata) > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/runners/pipeline.py", > line 37, in _dispose > process(mlist, msg, msgdata, pipeline) > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/core/pipelines.py", > line 50, in process > handler.process(mlist, msg, msgdata) > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/ > mailman/handlers/member_recipients.py", line 84, in process > for member in mlist.regular_members.members > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/ > mailman/handlers/member_recipients.py", line 83, in <genexpr> > recipients = set(member.address.email > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/model/roster.py", > line 239, in members > yield from self._get_members(DeliveryMode.regular) > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/model/roster.py", > line 226, in _get_members > if member.delivery_mode in delivery_modes: > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/model/member.py", > line 205, in delivery_mode > return self._lookup('delivery_mode') > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/model/member.py", > line 167, in _lookup > pref = getattr(self.address.preferences, preference) > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/orm/attributes.py", > line 287, in __get__ > return self.impl.get(instance_state(instance), dict_) > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/orm/attributes.py", > line 723, in get > value = self.callable_(state, passive) > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/orm/strategies.py", > line 760, in _load_for_state > session, state, primary_key_identity, passive > File "<string>", line 1, in <lambda> > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/orm/strategies.py", > line 850, in _emit_lazyload > session.query(self.mapper), primary_key_identity > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/sqlalchemy/ext/baked.py", > line 603, in _load_on_pk_identity > setup, tuple(elem is None for elem in primary_key_identity) The above says the runner was doing a database lookup. This may be a coincidence or there may be some database locking issue that underlies the issue with the pipeline runner. > File "/var/lib/mailman/venv/lib64/python3.6/site-packages/mailman/core/runner.py", > line 114, in signal_handler > raise RunnerInterrupt > mailman.interfaces.runner.RunnerInterrupt > Mar 27 09:01:22 2022 (5860) SHUNTING: 1648351882.8537986+ > 9bf59cb23a71a4bae65536bfdbec0abb261adaa0 > Mar 27 09:01:22 2022 (5860) pipeline runner exiting. I suggest doing the following assuming your Mailman database is not sqlite3 (if it is, just do step 2): 1) Stop mailman core and maybe other mailman services too. 2) Assuming the two shunted messages are still in Mailman's shunt queue, run `mailman unshunt` to unshunt them. If there are more shunted messages, inspect them with `mailman qfile` to see if you want them, They may be spam. 3) Restart your database server. 4) Start Mailman core and any other stopped services. Also, look in the database server logs for any issues. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

[MM3-users] Re: Extract posts into mbox file

by Abhilash Raj

On Sat, Apr 18, 2020, at 9:45 AM, Mark Sapiro wrote: > On 4/17/20 10:23 PM, Andrew Bernard wrote: > > Where are the posts stored in the database? What tables? How would on go about exporting them into mbox format for the complete set? > > > It depends on which archiver(s) if any are enabled for the list. > > For the prototype archiver, messages are archived in Maildir format, > <https://en.wikipedia.org/wiki/Maildir>, in the directory > var/archives/prototype/<list-address>/ > > For Hyperkitty, messages are stored in the database in the > hyperkitty_email table and non-plain text parts are in the > hyperkitty_attachment table, but you don't need to know that because in > any HyperKitty view, i.e. a message view, a thread view, a threads by > month view ot an all threads view, there is a button to download all the > messages in that view as a gzipped .mbox file. Emails from Hyperkitty are also available via a REST API endpoint. The documentation for it isn't much but you can build URL patterns by looking at: https://lists.mailman3.org/archives/api/ As Mark above mentioned, you are also able to get an mbox file downloaded via API. I wrote a small python utility to download archives from Hyperkitty to a local Maildir: https://gitlab.com/mailman/hksync But it is also possible to sync to a local mbox if need be. The tool just needs to be extended a little. Although, if the need is to *only* have a mbox or maildir, you should avoid having the complicated Hyperkitty setup and instead use the prototype archiver that Mark mentioned above. > > -- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

5 years

[MM3-users] Re: installing mailman3 core

by Abhilash Raj

On Fri, May 29, 2020, at 8:36 AM, Mark Sapiro wrote: > On 5/29/20 7:49 AM, Ralf Wiegand wrote: > > https://docs.mailman3.org/en/latest/install/install.html > > > > I was following this "official" page. There is no word on "pip install > > mailman" as an alternate choise? > > > > There is also a reference in regards to "Virtualenv Installation > > <https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst…>, > > recommended for Production" ... why is this recommended? Does the "pip > > install mailmail" install a production environment I can trust? > > > I didn't write that page, but I think it is saying that for production, > installing in a virtualenv is preferred over installing globally, and > not that it is necessarily preferred over installing a Docker container > or a distro package. Should we edit the wording to signify something else? I guess the definition of production varies a lot. While many would prefer distro packages to use in their sites, some others want the latest bug-fixed version. Debian picks up their packages from PyPI too, but they verify the signatures on packages, which `pip` doesn't. So, from a strict security point of view, Debian might be slightly better, but with the lack of a proper Web Of Trust in PyPI, the value of the signature depends on how much you trust my signing key. > > However, if you actually read the Virtualenv Installation document, you > will see under Installing Mailman Core > <https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-mail…> > it says to install Mailman core via `pip install mailman` in the > virtualenv. > > -- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

4 years, 10 months

[MM3-users] Re: Still unable to get mailman3 working on Ubuntu 20.04 LTS

by Mark Sapiro

On 1/8/22 12:31 PM, Michael Heseltine wrote: > Hi Mark, Stephen, > in fact, there isn't anything running on port 8000, even though I added the service description files under "/lib/systemd/system" as detailed in the HowTo. > > Looking at "journalctl -xe", both the "gunicorn" and the "qcluster" service run into errors i don't understand: > > (qcluster) >> Jan 08 21:22:23 lists.mydomain.com systemd[1]: qcluster.service: Start request repeated too quickly. >> Jan 08 21:22:23 lists.mydomain.com systemd[1]: qcluster.service: Failed with result 'exit-code'. >> -- Subject: Unit failed >> -- Defined-By: systemd >> -- Support: http://www.ubuntu.com/support >> -- >> -- The unit qcluster.service has entered the 'failed' state with result 'exit-code'. >> Jan 08 21:22:23 lists.mydomain.com systemd[1]: Failed to start HyperKitty async tasks runner. >> -- Subject: A start job for unit qcluster.service has failed >> -- Defined-By: systemd >> -- Support: http://www.ubuntu.com/support >> -- >> -- A start job for unit qcluster.service has finished with a failure. >> -- >> -- The job identifier is 734836 and the job result is failed. This isn't your immediate problem, but it is an issue. The above isn't too informative. What do you get if you run /opt/mailman/mm/bin/django-admin qcluster manually? > (gunicorn) >> Jan 08 21:24:58 lists.mydomain.com systemd[1]: gunicorn.service: Failed with result 'exit-code'. >> -- Subject: Unit failed >> -- Defined-By: systemd >> -- Support: http://www.ubuntu.com/support >> -- >> -- The unit gunicorn.service has entered the 'failed' state with result 'exit-code'. >> ...skipping... >> Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: File "/opt/mailman/mm/bin/gunicorn", line 14, in> >> Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: sys.exit(gunicorn.app.wsgiapp.run()) >> Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-pa> >> Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: WSGIApplication("%(prog)s [OPTIONS] [APP_MODUL> >> Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-pa> >> Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: super().run() >> Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-pa> >> Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: Arbiter(self).run() >> Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-pa> >> Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: self.halt(reason=inst.reason, exit_status=inst> >> Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-pa> >> Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: self.stop() >> Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-pa> >> Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: time.sleep(0.1) >> Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-pa> >> Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: self.reap_workers() >> Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-pa> >> Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: raise HaltServer(reason, self.WORKER_BOOT_ERRO> >> Jan 08 21:24:57 lists.mydomain.com gunicorn[3707354]: gunicorn.errors.HaltServer: <HaltServer 'Worker fa> >> Jan 08 21:24:58 lists.mydomain.com systemd[1]: gunicorn.service: Main process exited, code=exited, statu> >> -- Subject: Unit process exited >> -- Defined-By: systemd >> -- Support: http://www.ubuntu.com/support >> -- >> -- An ExecStart= process belonging to unit gunicorn.service has exited. >> -- >> -- The process' exit code is 'exited' and its exit status is 1. It would help to see the full traceback, not truncated at the right. You can scroll the display to the right with the right arrow key or just find the messages in /var/log/syslog. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: Is there a way of recording bounce messages?

by Mohsen Masoudfar

I'm dealing with the same issue. Upon reviewing the logs, I've noticed a significant number of bounced emails for a particular mailing list. Gmail users have reported not receiving emails. I haven't been able to locate the "munge from" information. My current setup is using Mailman 3.1.1. I read it has been introduced in 3.2. The Question is what to do with Mailman 3.1.1, if the upgrade is not an option. I get in the logs messages like below with several Queue-ids: Sep 25 09:03:55 localhost postfix/smtpd[26692]: 147583E927: client=a14-93.smtp-out.amazonses.com[54.240.14.93] Sep 25 09:03:55 localhost postfix/cleanup[26696]: 147583E927: message-id=<0100018acb94b326-fdf39193-144e-4fdc-8faf-0d3df54eb4ee-000000(a)email.amazonses.com> Sep 25 09:03:55 localhost postfix/qmgr[1298]: 147583E927: from=<>, size=24934, nrcpt=1 (queue active) Sep 25 09:03:55 localhost postfix/lmtp[26697]: 147583E927: to=<listname-bounces@servername>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.03, delays=0.01/0/0/0.01, dsn=2.0.0, status=sent (250 Ok) Sep 25 09:03:55 localhost postfix/qmgr[1298]: 147583E927: removed Mohsen ________________________________ From: Andrew Hodgson <andrew(a)hodgson.io> Sent: Friday, September 22, 2023 7:47 AM To: Andrew Hodgson <andrew(a)hodgson.io>; Mark Sapiro <mark(a)msapiro.net>; mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Is there a way of recording bounce messages? [EXTERNAL EMAIL] Hi. Seems other people have had this on Office365 when I searched the specific error. I have enabled VERP now on probes and all list messages so lets see if that improves things. Thanks. Andrew. -----Original Message----- From: Andrew Hodgson <andrew(a)hodgson.io> Sent: Friday, September 22, 2023 12:22 PM To: Mark Sapiro <mark(a)msapiro.net>; mailman-users(a)mailman3.org Subject: [MM3-users] Re: Is there a way of recording bounce messages? Mark Sapiro <mark(a)msapiro.net> wrote: >On 9/21/23 17:30, Thomas Ward wrote: >> >> MS365's bounce handling is weird and they do not include a delivery report in the payload, instead they take the log data and append it as a text payload portion to the message. It's annoying and problematic when debugging (and likely triggers the mailman2 equivalent of "unprocessable bounce message"). >> >> If Andrew can provide the bounce message as an example in raw form (even off list) we can dissect it - myself probably more rapidly as I am fluent in reading them at this point from weeks worth of dealing with them - and that will probably yield the info you are looking for. >It appears however that Mailman does recognize the DSN returned by MS365 as the user's delivery is being disabled by bounce. The issue is whatever DSN is returned to the list-bounces address is not attached to the notice sent to the list owner about the disable and it should be. Ok guys the plot thickens. Yesterday using the Mailman Shell I unbounced all the users on that list. We had a couple of messages yesterday and I also enabled the From munging for all messages sent to the list partway through those messages coming to the list. This morning we got all Gmail users bounced again, with no NDR attached to the message. However on one of the messages the NDR was attached, and so I'm going to send that to Mark separately. It looks like the NDR included the information for all the bouncing messages though, and that is probably because Mailman sends the messages to all users in one SMTP transaction. The message returned from Google was: user(a)gmail.com 9/22/2023 9:44:55 AM - Server at PAVPR08MB9257.eurprd08.prod.outlook.com returned '550 5.4.300 Message expired -> 421 4.4.2 Connection dropped due to SocketError' 9/22/2023 9:24:03 AM - Server at gmail-smtp-in.l.google.com (142.250.27.27) returned '421 4.4.2 Connection dropped due to SocketError' Thanks. Andrew. _______________________________________________ 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 andrew(a)hodgson.io _______________________________________________ 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, 6 months

[MM3-users] Re: mass subscribers disablement!?

by Christian Stalberg

Yes I upgraded to a version >=3.3.1 and had 70 subscribers disabled. Is there a way to see via the web GUI which subscribers were disabled? Correspondingly, can I re-enable delivery for them via the web GUI? Thank you in advance. -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, October 22, 2021 5:51 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: mass subscribers disablement!? On 10/22/21 2:07 PM, Christian Stalberg via Mailman-users wrote: > I added the additional hosts to ALLOWED HOSTS in settings_local.py and > mailman is distributing mail to subscribers again. However, I then > received many emails of valid users subscriptions being disabled. What > would cause that? Did you just upgrade Mailman core from a version <=3.3.0 to one >=3.3.1? If so, see https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/U 5ZW6X5QLQRXUOMD2DN77CYCOLKVMUXJ/ > Can subscriber management be done via command line? See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/do cs/commands.html for description of the available mailman subcommands. If you are interested in re-enabling delivery for members whose delivery is disabled by bounce, you can do this fairly easily in an interactive `mailman shell` session. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/do cs/shell.html Something like the following session: $ bin/mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> lm = getUtility(IListManager) >>> for mlist in lm.mailing_lists: ... for member in mlist.members.members: ... if member.delivery_status == DeliveryStatus.by_bounces: ... member.preferences.delivery_status = DeliveryStatus.enabled ... print('Re-enabled delivery for bouncing member {} on list {}' ... .format(member.address.email, mlist.list_name)) ... <print output here> >>> commit() >>> exit() -- 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

3 years, 5 months

[MM3-users] Re: DMARC Munging

by Allan Hansen

Mark, et al., I have entered a ticket at gitlab. Thanks. Is there a way for me to make this change to the From header munging until it is implemented in the production version? I made MM2 do the munging using such a change on your recommendation and it has worked. Our installation is from source, which might make it possible/easier? I have played a lot with the wrapping option and have come to the conclusion that it will not work. In some cases, the Apple Mail client for the desktop simply did not display the internal message, while iOS worked fine. The header munging is safer. Yours, Allan Hansen allan_hansen(a)icloud.com > On Jan 26, 2020, at 22:32 , Mark Sapiro <mark(a)msapiro.net> wrote: > > On 1/26/20 4:43 PM, Allan Hansen wrote: >> All, >> The munged From: header in MM3 still says >> 'name' via ‘listname’ <‘listaddress’> >> This caused me and my subscribers a lot of grief in MM2: >> Some mail clients use the first part up to the From for future key-ahead for new email to ’name’, hiding the address, so what they think is a personal message for ’name’, instead goes to the entire list. Red faces all around. >> Stephen Thurnbull earlier suggested further munging by replacing the list address in the From: header like this: >> 'name' via ‘listname’ <‘whoopsieaddress’> >> Which will return an automated reply explaining the issue. I like this option. How can I get that in? > > > You can file an issue at <https://gitlab.com/mailman/mailman/issues>. That will at least get it on the table, but there are no guarantees as to if/when it would be implemented. > > -- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

5 years, 2 months

[MM3-users] Re: Importing config and archives only partially succeeded?

by Eric Broens

I just notice in the webserver logfile, the same request for the same mlist, msgid and key several times per second for about 3 hours now: "GET /archives/api/mailman/urls?mlist=....&msgid=...&key=... HTTP/1.1" 200 105 "-" "python-requests/2.25.0" The request seems to originate from the server where the mailman suite is installed Best Regards,Eric On Sunday, December 13, 2020, 01:54:54 AM GMT+1, Eric Broens via Mailman-users <mailman-users(a)mailman3.org> wrote: The settings - Archiving, are not different from the ones that do show the messages:"Private Archives" selected, and Active archivers "hyperkitty" also selected. I was trying to find out how the hyperkitty page gets the mails from the database, and if I can start from there.Or maybe something is not completely correct in the database tables. Best Regards,Eric On Sunday, December 13, 2020, 01:27:53 AM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote: On 12/12/20 3:56 PM, Eric Broens via Mailman-users wrote: > After everything was imported, and I noticed that the mails were not shown in the archives for half of the mailinglists, I ran "manage.py update_index" to index the mails for all mailinglists.This command is still running for hours.Since it builds the search index, I don't expect that this would make the mails available on the webpage. I agree, that won't make the mails available on the webpage. If you're using the default Whoosh search engine, "hours" is not unexpected. Elasticsearch is much faster and Xapian faster still. What do you see in Postorius - Settings -> Archiving for the lists whose messages don't show? -- 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ _______________________________________________ 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/

4 years, 4 months

[MM3-users] Re: How to fix: [Django] ERROR (EXTERNAL IP)

by Jigme Datse

On Fri, 1 Nov 2024 12:29:56 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/31/24 21:18, Jigme Datse wrote: > > On Thu, 31 Oct 2024 20:07:00 -0700 > > Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> What's in Django's logs? > >> > > > > Attached logs (I hope that works). A couple are currently empty? > > > I suspect the django_q error is because you need to run `django-admin > migrate`[1], but it isn't responsible for your inability to get list > pages. > > Again, what's in Django's logs? These are not the uwsgi logs. If you > don't know where they are, look in your Django settings in the > LOGGING definition for the filename setting for the file handler. > > [1] The actual name of the Django admin command may be > `django-admin`, `python manage.py` or something else depending on how > Mailman web is installed. > Thank you, A couple of things, running django-admin complains about: Note that only Django core commands are listed as settings are not properly configured (error: Requested setting INSTALLED_APPS, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings.). which *that* error gets replaced by: django.core.exceptions.ImproperlyConfigured: settings.DATABASES is improperly configured. Please supply the ENGINE value. Check settings documentation for more details. with the command: python venv/lib/python3.12/site-packages/mailman_web/manage.py migrate which *might* be the wrong manage.py but other than the change with the migrate command, without it looks to throw the same output. The Django log was at that time empty it's now attached (larger than I'd like). It does seem like some configuration isn't quite working. Maybe *badly* not working with some change that happened. It's not a huge deal, this is more a "fun project" for me. This part of it isn't so much fun.

5 months, 3 weeks

[MM3-users] Re: Upgrade

by Darren Smith

Nice...spoke too soon. Mailman info works, but when attempting to start mailman I'm now getting this: Traceback (most recent call last): File "/opt/mailman3/conda/bin/mailman", line 11, in <module> sys.exit(main()) File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", line 722, in __call__ return self.main(*args, **kwargs) File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", line 676, in main _verify_python3_env() File "/opt/mailman3/conda/lib/python3.6/site-packages/click/_unicodefun.py", line 118, in _verify_python3_env 'for mitigation steps.' + extra) RuntimeError: Click will abort further execution because Python 3 was configured to use ASCII as encoding for the environment. Consult http://click.pocoo.org/python3/for mitigation steps. This system lists a couple of UTF-8 supporting locales that you can pick from. The following suitable locales where discovered: aa_DJ.utf8, aa_ER.utf8, aa_ET.utf8, (followed by a bijillion others) -Darren On Mon, Apr 16, 2018 at 11:25 AM, Darren Smith <silas.crutherton(a)gmail.com> wrote: > Boy howdy did that work... > > Thanks! > > > On Mon, Apr 16, 2018 at 11:22 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 04/16/2018 10:12 AM, Darren Smith wrote: >> >> > "/opt/mailman3/conda/lib/python3.6/site-packages/sqlalchemy/ >> engine/strategies.py", >> > line 160, in create >> > engineclass.__name__)) >> > TypeError: Invalid argument(s) 'pool_pre_ping' sent to create_engine(), >> > using configuration PGDialect_psycopg2/QueuePool/Engine. Please check >> that >> > the keyword arguments are appropriate for this combination of >> components." >> > >> > Anyone able to point me where to go to look for a solution for this? >> >> >> You need to update SQLAlchemy to >= 1.2 for this, but there is another >> issue that requires at least 1.2.3 (current is 1.2.6) >> >> >> -- >> 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/ >> > >

7 years

[MM3-users] Re: Messages attached to probe messages

by Mark Sapiro

On 7/12/22 12:36 AM, Bjoern Franke via Mailman-users wrote: > Hi, > > some time ago I started a discussion where I wrongly assumed that probe > messages were sent accidentally from example.com > > Some digging showed now that the sender of the probe messages are > correct, but the attached messages seem to be wrong. > > An attached example for bouncing messages was: > > From: Mailman <mailman(a)example.com> > To: Mailman Bounces <mailman-bounces(a)example.com> > Subject: SMTP Delivery Failure > Message-ID: <165577237837.35.8042057157021349872@mailman-core> > Date: Tue, 21 Jun 2022 00:46:18 +0000 > Message-ID-Hash: TOJ7WDT3TXWOEHZB4USRUOPZUW7BEATI > X-Message-ID-Hash: TOJ7WDT3TXWOEHZB4USRUOPZUW7BEATI > > Mail to bjo(a)schafweide.org failed at outgoing SMTP > > Error code: 554 > Error message: b'5.7.1 Spam message rejected' That's a fake DSN created by Mailman's outgoing runner. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/outgoi…. There will be nothing in Mailman's smtp.log regarding receipt of this message because this message is not received via SMTP, but see below. It is created when the outgoing runner gets a 5xx refusal and the runner calls the bounce processor directly with this fake DSN to process this refusal as a bounce. > I took a look into the logs and found no example.com, but: > > Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) handling connection > Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) >> b'LHLO mail.ffnw.de' > Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) >> b'MAIL > FROM:<yzvotmm(a)forestanes.mom> SIZE=293338' > Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) sender: > yzvotmm(a)forestanes.mom > Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) >> b'RCPT > TO:<vorstand(a)lists.ffnw.de>' > Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) recip: > vorstand(a)lists.ffnw.de > Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) >> b'DATA' > Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) >> b'QUIT' > Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) connection lost > Jun 21 00:46:14 2022 (33) ('172.20.199.1', 52074) Connection lost during > _handle_client() The above is the receipt of the post whose delivery to some recipients failed. > Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> > response exception: (554, b'5.7.1 Spam message rejected') > Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> > response exception: (554, b'5.7.1 Spam message rejected') > Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> smtp to > vorstand(a)lists.ffnw.de for 6 recips, completed in 0.7157599925994873 > seconds > Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> post to > vorstand(a)lists.ffnw.de from vorstand(a)lists.ffnw.de, 294362 bytes, 6 > failures > Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> > delivery to foo(a)stadel.info failed with code 554, b'5.7.1 Spam message > rejected' > Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> > delivery to abc(a)ffnw.de failed with code 554, b'5.7.1 Spam message > rejected' > Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> > delivery to def(a)ffnw.de failed with code 554, b'5.7.1 Spam message > rejected' > Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> > delivery to xyz(a)ffnw.de failed with code 554, b'5.7.1 Spam message > rejected' > Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> > delivery to bjo(a)schafweide.org failed with code 554, b'5.7.1 Spam > message rejected' > Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> > delivery to blabla(a)osnabrueck.freifunk.net failed with code 554, b'5.7.1 > Spam message rejected' > Jun 21 00:46:49 2022 (35) > <165577240769.30.3077851374384466408@mailman-core> smtp to > vorstand(a)lists.ffnw.de for 1 recips, completed in 0.5507137775421143 > seconds The various messages like > Jun 21 00:46:18 2022 (35) <H44657323H70760722Q60416802U@yzvotmm> > delivery to bjo(a)schafweide.org failed with code 554, b'5.7.1 Spam > message rejected' are logged by the outgoing runner when it receives a 5xx reject and creates a bounce with a fake DSN. -- 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

[MM3-users] Re: To what extent can mailman 3 handle images and html?

by Mark Sapiro

On 10/20/19 2:11 AM, Paul Arenson wrote: > Hi > > The other day I attempted to send a message from my mail client (Apple computer, Mail program, html--well, what they call Rich Text). While a user was able to send a message previously that contained an image, I was unsuccessful. It should be the same as Mailman 2.1. What are your settings for content filtering. In Postorius the only thing exposed are Settings -> Alter Messages -> Filter content, Collapse alternatives and Convert html to plaintext. If this Filter content Yes, content is filtered according to the other two settings and MIME parts may be removed according to the list settings filter_types, pass_types, filter_extensions and pass_extensions. These settings exist in core, but aren't exposed in Postorius. For a new MM3 list these settings are empty, but for a list imported from Mailman 2.1, they are set according to the corresponding MM 2.1 settings. I suspect in your case the issue is Filter content and Collapse alternatives are both Yes. Or perhaps the issue is HyperKitty's rendering of the message > As well, links were weird. > > LINKS > ===== > Because My wordpress often has a Japanese URL and they can become very long, I tried both the URL as is and embedded (made a clickable html link). > > URL > === > So while I typed > https://www.tokyoprogressive.org/journalist-ito-shiori-sues-alleged-rapis.... > > It came out double as > > https://www.tokyoprogressive.org/journalist-ito-shiori-sues-alleged-rapis... > <https://www.tokyoprogressive.org/journalist-ito-shiori-sues-alleged-rapis... > (The full link was truncated with ... at the end, and the link appeared twice with the second instance preceded by "">") I think the doubling is due to your MUA. The truncation of the displayed link in HyperKitty is expected, but the link itself should reference the full URL. > The embedded one did not come out embedded buy showed the text like this: > Alternate link: 多摩川河川敷に男性の遺体、増水した川に流されたか > <https://www.tokyoprogressive.org/%e5%a4%9a%e6%91%a9%e5%b7%9d%e6%b2%b3%e5%... What do these look like in the message received from thge list as opposed to HyperKitty? > QUESTION 1: Is there a preferred way to write links, or will there always be problems with the mail clients? > (Even the web archive shows this problem though): > > https://list.tokyoprogressive.org/hyperkitty/list/discuss@list.tokyoprogres… See what this looks like at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> > See the top item Homeless man drowns in river during Typhoon and what I mean. The first of those 3 links actually works. The other two don't work because the Japanese characters have been encoded as hex values by your MUA (which may be HyperKitty if you are posting via HyperKitty. To answer your question, you can just type the URL as you did above in your thread link, or you can surround it with angle brackets as I did in my message link. If you don't use angle brackets, it should be surrounded by whitespace to avoid ambiguity. See <https://www.rfc-editor.org/rfc/rfc3986#appendix-C> > IMAGE > No image appears though one was added inline. > > And, as I said, a user was previously able to add one. I do not know how she did it. I also posted it to my web site instead of the newsletter for unrelated reasons. But there was an image (Originally got a warning the message was held because the attachment or something). > > So are there guidelines one whether/how to attach an image so that it makes it? Are you posting via email or HyperKitty? If by email, I suspect the issue is Filter content and Collapse alternatives are both Yes. If by HyperKitty you can only post plain text. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

DEBUG var True: [02/Aug/2017 16:43:42] "GET /postorius/lists/ HTTP/1.1" 200 3645 [02/Aug/2017 16:43:48] "GET /accounts/login/?next=/postorius/lists/ HTTP/1.1" 200 10950 [02/Aug/2017 16:43:49] "GET /static/CACHE/css/hyperkitty.2f591b4e31fe.css HTTP/1.1" 200 156657 DEBUG var False: [02/Aug/2017 16:46:46] "GET /accounts/login/?next=/postorius/lists/ HTTP/1.1" 200 10001 [02/Aug/2017 16:46:46] "GET /static/CACHE/css/b3547a2ab51b.css HTTP/1.1" 404 107 [02/Aug/2017 16:46:46] "GET /static/CACHE/css/4c17bb8058aa.css HTTP/1.1" 404 107 [02/Aug/2017 16:46:46] "GET /static/CACHE/css/d6cbfc945441.css HTTP/1.1" 404 107 [02/Aug/2017 16:46:46] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" 404 105 [02/Aug/2017 16:46:46] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" 404 105 El mié., 2 ago. 2017 a las 10:56, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/02/2017 07:55 AM, Rafael Mora wrote: > > HyperKitty is looking for some files in /static/CACHE/... but it doesn't > > find them: > > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/b3547a2ab51b.css HTTP/1.1" > > 404 107 > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/4c17bb8058aa.css HTTP/1.1" > > 404 107 > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/2fa1cba00450.css HTTP/1.1" > > 404 107 > > [02/Aug/2017 14:53:38] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" > 404 > > 105 > > [02/Aug/2017 14:53:39] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" > 404 > > 105 > > > > > > Should I run any command to activate the CACHE dir? > > > You need to ensure you have a working sass compiler. As I said at > < > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > >, > See the third bullet under > <http://docs.list.org/en/latest/prodsetup.html#dependencies>. > > Then you need to run commands like > > django-admin collectstatic --clear > django-admin compress > > > -- > 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/ > -- Atentamente / Best Regards Ing. Rafael Mora

7 years, 8 months

[MM3-users] Re: Bulk delivery status change?

by Stephen Daniel

OK. Ran the script. No errors while running it, but when I look at the users through Postorius GUI, they still show as 'Disabled by Bounces' ?? On Sun, Nov 10, 2024 at 11:42 AM Stephen Daniel <swd(a)pobox.com> wrote: > Thanks all! I will use these pronto. > > On Sun, Nov 10, 2024 at 11:42 AM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 11/10/24 08:34, Odhiambo Washington via Mailman-users wrote: >> > On Sun, Nov 10, 2024 at 7:16 PM Stephen Daniel <swd(a)pobox.com> wrote: >> > >> >> Mistakes were made, and for while every single outbound email bounced. >> >> I've fixed the mistakes, but now in my largest and most active email >> list, >> >> every single user's delivery status is "Disabled by Bounces". >> >> >> >> Is there a way to bulk fix this? Or do I have to go into each user, >> one at >> >> a time, and fix them? >> > >> > Please see this thread: >> > >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >> >> The script in that post does all lists. For a single list see >> >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >> but note that the command line >> ``` >> $ shell -l list(a)example.com >> ``` >> should be >> ``` >> $ mailman shell -l list(a)example.com >> ``` >> >> -- >> 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://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 swd(a)pobox.com >> >

5 months, 1 week

[MM3-users] Re: where to configure max_days_to_hold on MM3 GUI interface?

by Shashikanth Komandoor

Hello Mark, Thanks for helping me for moving ahead in my project. Troubling you again, I would like to put another request at you. As per your suggestion, I am trying to configure my list configuration through REST API for specially the parameter like max_days_to_hold as it is not available through interface and I am following the official links of mailman 3 i.e https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/listconf.html But I am getting "name is not defined" sort of errors as below: *>>> dump_json('http://localhost:9001/3.0/lists/ <http://localhost:9001/3.0/lists/>','ant(a)example.com/config <http://ant@example.com/config>',dict(display_name='My List'),'PATCH')Traceback (most recent call last): File "<stdin>", line 1, in <module>NameError: name 'dump_json' is not defined>>>* Actually I am new to REST API but hope this is the only issue that is preventing me to go ahead. Could you please help me by saying how should I handle this so that I should be able to configure *max_days_to_hold* of a list or multiple ? On Wed, Jan 29, 2020 at 11:20 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/28/20 8:42 PM, Shashikanth Komandoor wrote: > > > > But I could see that parameter value configurable on MM2 GUI > > interface in General Options but I don't see the same on the MM3 GUI > > interface. > > > There are many core settings not (yet) exposed in Postorius. > max_days_to_hold. is one of them. It can be set via `mailman shell` or > via the REST API > < > https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/rest.html#re… > >. > > -- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

5 years, 2 months

[MM3-users] Re: Problem creating list members using REST API

by Stephen Daniel

I can give you a program written in Go. Would that be helpful? On Tue, Jan 18, 2022 at 6:49 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/18/22 2:11 PM, Stephen Daniel wrote: > > The REST API documentation is a bit informal. As someone who is not > > familiar with mailman, and who doesn't know python, they are a bit of a > > slog. > > > Agreed. I guess we sort of assume that people dealing directly with the > REST API are familiar with both. > > > > It might be worth seeing if the code can be enhanced to allow the boolean > > values to be sent in using JSON booleans as well as JSON strings. > > > I think here we only have to deal with the REST API because other uses > of as_boolean are all on strings that come from config files. We can't > modify as_boolean directly, as it is part of a third party dependency > and is intended to be used with config files, not JSON objects, but I > think something like this will do it. > ``` > --- a/src/mailman/rest/helpers.py > +++ b/src/mailman/rest/helpers.py > @@ -249,6 +249,8 @@ class GetterSetter: > """ > if self.decoder is None: > return value > + if self.decoder is as_boolean and isinstance(value, bool): > + return value > return self.decoder(value) > > > > ``` > Perhaps you could try to test that. > > I just created https://gitlab.com/mailman/mailman/-/issues/970 for this. > It would help me in fixing this if you could provide a small piece of > your code that throws the error. > > -- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

3 years, 3 months

[MM3-users] Re: Emergency Moderation

by Abhilash Raj

On Sun, May 24, 2020, at 11:34 AM, Mark Sapiro wrote: > On 5/24/20 10:59 AM, Allan Hansen wrote: > > In the MM3 settings there is an option to ‘Hold for moderation’ when members or non-members post to the list. > > I use that for the same cases where in MM2 I switched a list to ‘Emergency Moderation.’ > > > If you imported your MM 2.1 lists with `mailman import21`, `emergency` > was set appropriately for the imported list and should be working to > hold posts regardless of other settings. > > > > My own current top-of-the-list issues: > > > > A bug: Moderators can’t see/edit the list of members even when allowed to by list setting. > > The visibility issue is <https://gitlab.com/mailman/postorius/-/issues/369>. > > Editing membership beyond what could be done via the admindb interface > (i.e. clearing a moderated poster's mod flag) was never allowed for a > moderator in MM 2.1. > > In MM 3, a moderator can set a member's moderation when handling a held > post. Do you think a non-owner moderator should be able to make other > changes to a member? > > > > A feature request: Member changing email address on all lists he/she belongs to, without involving moderators. > > > This is <https://gitlab.com/mailman/postorius/-/issues/399> and we're > working on it. Another way to achieve this request, without needing the Preferred Address route is to simply Patch the Member resource with the new address, which wouldn't trigger the full subscription workflow and would have the extra advantage of having the same delivery_mode and preferences. I created: https://gitlab.com/mailman/postorius/-/issues/425 to track this issue. > > -- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

4 years, 10 months

[MM3-users] Re: installing mailman3 core

by Mark Sapiro

On 5/29/20 7:41 AM, Ralf Wiegand wrote: > Mark - What is the difference between to two install methods? What are > my pros and cons? Installing from the GitLab repository will get the latest development version, however, you can also install from this repository via pip and pick a tag or commit to install <https://pip.pypa.io/en/stable/reference/pip_install/#git> `pip install mailman3` will install the latest released version. As of this writing, that's 3.3.1, so ``` pip install mailman3 ``` and ``` pip install git+https://gitlab.com/mailman/mailman@3.3.1 ``` should give the same result although the former installs from PyPI and the latter from GitLab. The advantage to installing the latest version from GitLab is you get features and fixes that haven't been released yet. The disadvantage is you might get new bugs, although the servers that support this list and all the Mailman 3 @python.org lists are generally running the latest GitLab versions, so any serious issues will be quickly found and fixed. > I have been using this: > >>>>> > > |# Note: if we are using a dedicated postgresql database server, all > postgresql changes need to be done on the actual postgresql server.| > |>>>| > |sudo yum install postgresql-server postgresql-contrib| > |sudo postgresql-setup initdb| > |sudo systemctl start postgresql| > |sudo systemctl enable postgresql| > |sudo -u postgres psql -c ||"SELECT version();"| > |sudo useradd -c ||"Mailman User"| |-s /bin/bash -m mailman| > |sudo -u postgres create role mailman;| > |sudo -u postgres createdb -O $USER mailman| > |sudo -u postgres psql -c ||"grant all privileges on database mailman to > mailman;"| > |sudo -u postgres psql -c ||"ALTER ROLE mailman WITH PASSWORD > 'secret123';"| > |sudo -u postgres psql -c ||"ALTER ROLE "||mailman||" WITH LOGIN;"| > |sudo echo ||"listen_addresses = '*' "| |>> > /var/lib/pgsql/10/data/postgresql.conf| > |sudo echo ||"# The user mailman will be able to access all databases > from a trusted location (any) without a password"| |>> > /var/lib/pgsql/data/pg_hba.conf| > |sudo echo ||"host all mailman 0.0.0.0/0 > trust"| |>> /var/lib/pgsql/data/pg_hba.conf| > |sudo systemctl restart postgresql| > |sudo ss -nlt | grep 5432| > |<<<| > |sudo yum install python36* --skip-broken -y| > |# check make sure you have both versions| > |sudo python --version| > |Python 2.7.5| > |sudo python3 --version| > |Python 3.6.8| > |sudo pip3 install psycopg2-binary| > |sudo chown mailman.mailman /opt/mailman| > |sudo chmod 755 /opt/mailman| > |# NOTE: The first initial mailman3 core setup has to be done manually.| > |# This is a important step to ensure the user "mailman" will run the > actual mailman3 application and not root.| > |# switch to user mailman| > |mailman# cd /opt/mailman| > |mailman# git clone https:||//gitlab.com/mailman/mailman.git| This gets the head of the GitLab master branch. > |mailman# cat <<EOT >> /opt/mailman/mailman/src/mailman/config/mailman.cfg| > |[devmode]| > |enabled: yes| > |recipient: root@localhost| > |[webservice]| > |hostname: localhost| > |port: 8001| > |show_tracebacks: yes| > |use_https: yes| > |[mta]| > |incoming: mailman.mta.postfix.LMTP| > |outgoing: mailman.mta.deliver.deliver| > |lmtp_host: localhost| > |lmtp_port: 8024| > |smtp_host: localhost| > |smtp_port: 25| > |[database]| > |class||: mailman.database.postgresql.PostgreSQLDatabase| > |url: postgres:||//mailman:secret123@<IP-ADDRESS or FQDN>/mailman| > |EOT| > |mailman# python3.6 -m venv venv-3.6| > |>>| > |mailman# source venv-3.6/bin/activate| > |(venv-3.6) [mailman@empire mailman]$ cd mailman| > |(venv-3.6) [mailman@empire mailman]$ python setup.py develop| > |(venv-3.6) [mailman@empire mailman]$ mailman info| > |<<| > | > | > | > | > |So I was told I don't have to do this, I can just simple do (rhel7) > | > |yum install pyhton3| > |pip install mailman| This gets the latest release from PyPI Other than that, you still have to do the configuration and install some dependencies as in the first method. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: Log rotation

by Darren Smith

Well, that is certainly a wealth of information from you two, thanks a ton! I've got a few things to try now. I'm going to have to look up the retry runner to see if that might help when we have to shut things down. I'll let you know what I find... On Tue, Apr 10, 2018 at 5:41 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 04/10/2018 03:39 PM, Abhilash Raj wrote: > > Yes, this is a known thing and the reason for it is that the SIGTERM > isn't delivered till the process wakes up next time. We can have the > process sleep for a smaller amount of time to fix this, but then it would > mean that it will be running much more often. > > > > It is the Retry runner, which has sleep_time set to 15m. I don't know if > you want to retry very often, like 2min or 5min, but you can change it by > adding the following snippet to your mailman.cfg > > > A long time ago (in a galaxy far away) Mailman 2.1 had a global > DELIVERY_RETRY_WAIT setting. This setting had been ineffective for > years, relying instead on the retry runner's sleep time. > > In 2.1.26, for what turned out to be a probably spurious reason, I made > DELIVERY_RETRY_WAIT effective again, although the retry runner still > sleeps for 15 minutes. > > We could implement something similar in MM 3 to allow the retry runner > to have a much shorter sleep time without actually retrying the delivery > that often. The down side of that is even though we aren't retrying > delivery each time the runner wakes up, we are dequeueing and requeueing > the message each time and this would have a file system impact. > > -- > 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/ >

7 years

[MM3-users] Re: Issues with cross posted emails after upgrading to mailman 3.3.6

by Simon Coggins

On 8 Nov 2021, at 11:11 am, Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> wrote: Simon Coggins wrote: > On 7 Nov 2021, at 10:54 am, Mark Sapiro <mark(a)msapiro.netmailto<mailto:mark@msapiro.netmailto>:mark@msapiro.net<mailto:mark@msapiro.net>> wrote: > I wound up taking a different approach. I check for other references to > the message in the message store and only delete the message if there > are none. The fix is at > https://gitlab.com/mailman/mailman/-/merge_requests/932/diffshttps://gitlab…<https://gitlab.com/mailman/mailman/-/merge_requests/932/diffshttps://gitlab…> > Oh nice. That seems like a sensible solution. Thanks for tackling so quickly. I’ll do some testing today and roll it out once testing is complete. I made a small change to defend against 'impossible' situations. See https://gitlab.com/mailman/mailman/-/merge_requests/933/diffs<https://gitlab.com/mailman/mailman/-/merge_requests/933/diffs> Thanks for the heads up. I did a bunch of testing with the original patch and was happy with it so we’re running that in prod now. How far off is 3.3.6? Just working out if I apply this slight change or wait for the full release. _______________________________________________ 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> --- [https://www.cqu.edu.au/] Mr Simon Coggins Principal Systems Engineer | Digital Services Directorate CQUniversity Australia, Level 6.14, 160 Ann Street, Brisbane, QLD 4000 P +61 7 3295 1182 | X 51182 | M +61 408 115 861 | E s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au> [https://www.cqu.edu.au/social-media] I respectfully acknowledge the Traditional Owners of the land on which we work and learn, and pay respect to the First Nations Peoples and their Elders, past, present and future. This communication may contain privileged or confidential information. If you have received this in error, please return to sender and delete. CRICOS: 00219C | RTO Code 40939 ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: attachment.png Content-Type: image/png Name: attachment.png Replaced multipart/alternative part with first alternative.

3 years, 5 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Can we modify the docs? Ok, I'm going to add that config to main.cf and test Thank you El vie., 21 jul. 2017 a las 12:25, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 09:36 AM, Rafael Mora wrote: > > > > Postfix <http://www.postfix.org/>: To setup Postfix, add the following > > configuration to master.cf: > > > > # Support the default VERP delimiter.recipient_delimiter = > > +unknown_local_recipient_reject_code = 550owner_request_special = > > notransport_maps = > > hash:/path-to-mailman/var/data/postfix_lmtplocal_recipient_maps = > > hash:/path-to-mailman/var/data/postfix_lmtprelay_domains = > > hash:/path-to-mailman/var/data/postfix_domains > > > > > > I added that config at the bottom of the master.cf file and did a > 'postfix > > reload' and I got this error message: > > > > [root@localhost ~]# postfix reload > > /usr/sbin/postconf: fatal: file /etc/postfix/master.cf: line 129: bad > field > > count > > postfix/postfix-script: fatal: cannot execute /usr/sbin/postconf! > > > First of all, in a report such as this, it would really help if you > reported what is actually in master.cf in the vicinity of line 129. > > However, that said, the doc is wrong. The lines should be added to > main.cf, not master.cf. See > <https://gitlab.com/mailman/mailman-suite-doc/issues/14>. > > Also, what you post above is quite garbled. It is not clear what you > meant, but the lines to add should be > > > # Support the default VERP delimiter. > recipient_delimiter = + > unknown_local_recipient_reject_code = 550 > owner_request_special = no > transport_maps = > hash:/path-to-mailman/var/data/postfix_lmtp > local_recipient_maps = > hash:/path-to-mailman/var/data/postfix_lmtp > relay_domains = > hash:/path-to-mailman/var/data/postfix_domains > > > and should not be wrapped as in your post. > > -- > 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/ > -- Atentamente / Best Regards Ing. Rafael Mora

7 years, 9 months

[MM3-users] Re: Badsignature on uwsgi-error.log

by Helio Loureiro

Hi Mark, Thanks for your response. I found what the issue was. I actually misspelled hyperkitty as hyPperkitty on the url. So the error on mailman-hyperkitty.cfg was: base_url: http://localhost:8000/hypperkitty/ I moved to: base_url: http://localhost:8000/hyperkitty/ and it was solved. Problem was the wrong link was getting a generic page from Django instead of error. And it was failing to do the parsing probably, which was taking wrongly as key mistake. Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro On Thu, 21 Mar 2024 at 01:13, Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/20/24 14:25, Helio Loureiro wrote: > > Hi, > > > > I keep receiving a lot of errors like this: > > > > --- Logging error --- > > Traceback (most recent call last): > ... > > > "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", > > line 55, in unsign > > raise BadSignature('Signature "%s" does not match' % sig) > > django.core.signing.BadSignature: Signature "F6V0Dr_SvBsx5-cY8vcvLXrX8tA" > > does not match > ... > > > > The api_key on mailman-hypperkitty.cfg, SECRET_KEY and > MAILMAN_ARCHIVE_KEY > > on setting.py are the same. > > > Of those three, the api_key on mailman-hypperkitty.cfg and > MAILMAN_ARCHIVE_KEY must match. SECRET_KEY is different. It is a Django > thing and has nothing to do with the others. See > https://docs.djangoproject.com/en/5.0/ref/settings/#secret-key > > If you changed it, that's the issue. If you know what it was previously, > you could set the previous value in SECRET_KEY_FALLBACKS, see > https://docs.djangoproject.com/en/5.0/ref/settings/#secret-key-fallbacks > > -- > 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://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 helio(a)loureiro.eng.br >

1 year, 1 month

[MM3-users] Re: Hyperkitty issue(s)

by Mark Sapiro

On 5/27/20 2:24 PM, Bryan Loniewski wrote: > Hello -- > > I'm stuck trying to integrate Hyperkitty. I see the following errors in mailman.log and mailmansuite.log respectively: > > <snipped> > [2020-05-27 16:42:11 -0400] [5140] [ERROR] Error handling request /3.1/lists/bry_test4.lists-test.rutgers.edu/archivers > Traceback (most recent call last): > File "/opt/mailman/mm/venv/lib/python3.6/site-packages/gunicorn/workers/sync.py", line 134, in handle > self.handle_request(listener, req, client, addr) > File "/opt/mailman/mm/venv/lib/python3.6/site-packages/gunicorn/workers/sync.py", line 175, in handle_request > respiter = self.wsgi(environ, resp.start_response) > File "/opt/mailman/mm/venv/lib/python3.6/site-packages/mailman/database/transaction.py", line 50, in wrapper > rtn = function(*args, **kws) > File "/opt/mailman/mm/venv/lib/python3.6/site-packages/mailman/rest/wsgiapp.py", line 193, in __call__ > return super().__call__(environ, start_response) > File "falcon/api.py", line 274, in falcon.api.API.__call__ > File "falcon/api.py", line 269, in falcon.api.API.__call__ > File "/opt/mailman/mm/venv/lib/python3.6/site-packages/mailman/rest/lists.py", line 406, in on_get > for archiver in archiver_set.archivers > File "/opt/mailman/mm/venv/lib/python3.6/site-packages/mailman/rest/lists.py", line 407, in <dictcomp> > if archiver.system_archiver.is_enabled> File "/opt/mailman/mm/venv/lib/python3.6/site-packages/mailman/model/mailinglist.py", line 587, in system_archiver > raise AssertionError('Archiver not found: {}'.format(self.name)) > AssertionError: Archiver not found: hyperkitty I've been looking at the code, and I think this can occur if the mailing list has a configured archiver which is no longer known in mailman.config.config.archivers. I.e., the list has hyperkitty as an archiver, but hyperkitty is no longer configured as an archiver in Mailman. > and > > <snipped> > Traceback (most recent call last): ... > KeyError: 'file' This traceback is useless. All it says is a Django logging error occurred in trying to log the real exception. The interesting one is immediately before this in the log. > Note that I've kinda followed the Virtualenv route along with using Mark's helpful webpage re: his experiences. > > Some relevant? config files... > > mailman.cfg: > > <snip> > [archiver.prototype] > enable: yes > > [archiver.hyperkitty] > class: mailman_hyperkitty.Archiver > enable: yes > configuration: /opt/mailman/mm/mailman-hyperkitty.cfg > <snip> That looks good. > mailman-hyperkitty.cfg: > [general] > base_url: https://a_real_domain/mm3/hyperkitty > api_key: <movealong> > > I can provide additional conf file setups if warranted? I am curious (and perhaps this is in fact the issue) why when I run mailman conf I don't see the archiver.hyperkittty section even though its in the mailman.cfg file? I don't either and I don't know why., For example on lists.mailman3.org ``` mailman conf|grep [[]archiver [archiver.mail_archive] class: mailman.archiving.mailarchive.MailArchive [archiver.mail_archive] clobber_date: maybe [archiver.mail_archive] clobber_skew: 1d [archiver.mail_archive] configuration: python:mailman.config.mail_archive [archiver.mail_archive] enable: no [archiver.mhonarc] class: mailman.archiving.mhonarc.MHonArc [archiver.mhonarc] clobber_date: maybe [archiver.mhonarc] clobber_skew: 1d [archiver.mhonarc] configuration: python:mailman.config.mhonarc [archiver.mhonarc] enable: no [archiver.prototype] class: mailman.archiving.prototype.Prototype [archiver.prototype] clobber_date: maybe [archiver.prototype] clobber_skew: 1d [archiver.prototype] configuration: changeme [archiver.prototype] enable: yes ``` doesn't show hyperkitty and neither does ``` mailman conf -k enable [archiver.mail_archive] enable: no [archiver.mhonarc] enable: no [archiver.prototype] enable: yes ``` but ``` /mailman conf -s archiver.hyperkitty [archiver.hyperkitty] class: mailman_hyperkitty.Archiver [archiver.hyperkitty] clobber_date: maybe [archiver.hyperkitty] clobber_skew: 1d [archiver.hyperkitty] configuration: /opt/mailman/mm/deployment/mailman-hyperkitty.cfg [archiver.hyperkitty] enable: yes ``` So I don't think this per se is the issue. > Any suggestions? Try ``` mailman shell May 28 00:35:47 2020 (15162) patched 1/1 modules (sqlalchemy) Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> from mailman.config import config >>> list(config.archivers) [<mailman.archiving.mhonarc.MHonArc object at 0x7fdd9ccff6a0>, <mailman.archiving.mailarchive.MailArchive object at 0x7fdd9ccffac8>, <mailman.archiving.prototype.Prototype object at 0x7fdd9ccffb38>, <mailman_hyperkitty.Archiver object at 0x7fdd9ccffe80>] >>> ``` Does yours list hyperkitty? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: Help on removing moderators

by Mark Sapiro

On 3/4/20 6:26 AM, sean_sullivan(a)rhoworld.com wrote: > > However, if I try and bring that in as a function that can be used with mailman withlist, I am consistently getting errors, and being that I am not very experienced in python, it has me scratching my head to say the least. > > from mailmanclient import Client You do not need to use mailmanclient with shell/withlist. mailmanclient is Python bindings for REST API functions. When you are under `mailman shell` (or `mailman withlist`, a synonym for `mailman shell`) you are working within mailman core and it's just extra baggage to use mailmanclient/REST. > from mailman.interfaces.member import MemberRole, AlreadySubscribedError > from mailman.testing.helpers import subscribe Here again, mailman.testing.helpers is to provide certain functions used in doctests. You don't need that with mailman shell. > addresses = ['test1(a)example.com', 'test2(a)example.com', 'test3(a)example.com'] > > client = Client('http://localhost:8001/3.1', 'restadmin', 'restpass') > > def set_owners(mlist): > > for email_addr in addresses: > try: > member = subscribe(mlist, '', email=email_addr, role=MemberRole.owner ) See below. > print (member) > except AlreadySubscribedError as err: > print (err) > > def remove(mlist): > my_list = client.get_list(mlist) > # print(my_list.fqdn_listname) > # for email_addr in addresses: > # my_list.remove_owner(email_addr) > > The errors I am getting are: > > ./bin/mailman withlist -r set_owners.remove -l it-test-b(a)lists.rhoworld.com > Traceback (most recent call last): > File "./bin/mailman", line 8, in <module> > sys.exit(main()) > File "/opt/mailman3/lib/python3.6/site-packages/click/core.py", line 764, in __call__ > return self.main(*args, **kwargs) > File "/opt/mailman3/lib/python3.6/site-packages/click/core.py", line 717, in main > rv = self.invoke(ctx) > File "/opt/mailman3/lib/python3.6/site-packages/mailman/bin/mailman.py", line 68, in invoke > return super().invoke(ctx) > File "/opt/mailman3/lib/python3.6/site-packages/click/core.py", line 1137, in invoke > return _process_result(sub_ctx.command.invoke(sub_ctx)) > File "/opt/mailman3/lib/python3.6/site-packages/click/core.py", line 956, in invoke > return ctx.invoke(self.callback, **ctx.params) > File "/opt/mailman3/lib/python3.6/site-packages/click/core.py", line 555, in invoke > return callback(*args, **kwargs) > File "/opt/mailman3/lib/python3.6/site-packages/click/decorators.py", line 17, in new_func > return f(get_current_context(), *args, **kwargs) > File "/opt/mailman3/lib/python3.6/site-packages/mailman/commands/cli_withlist.py", line 293, in shell > r = call_name(dotted_name, m, *run_args) > File "/opt/mailman3/lib/python3.6/site-packages/mailman/utilities/modules.py", line 70, in call_name > return named_callable(*args, **kws) > File "/opt/mailman3/bin/set_owners.py", line 24, in remove > my_list = client.get_list(mlist) > File "/opt/mailman3/lib/python3.6/site-packages/mailmanclient/client.py", line 347, in get_list > 'lists/{0}'.format(fqdn_listname)) > File "/opt/mailman3/lib/python3.6/site-packages/mailmanclient/restbase/connection.py", line 112, in call > error_msg, response, None) > urllib.error.HTTPError: HTTP Error 404: 404 Not Found > > > So, I am wondering, is it possible to do something like this or am I completely misunderstanding the documentation, and why do I get a 404 here, when in the shell everything works as expected. I know I must be missing something, but cannot for the life of me figure out what that is. Any help would be greatly appreciated. Here's what you want with addresses as arguments so you can save this as set_owners.py and run things like. $ bin/mailman shell --run set_owners -l list.example.com \ test1(a)example.com test2(a)example.com test3(a)example.com' and $ bin/mailman shell --run set_owners.remove -l list.example.com \ test1(a)example.com test2(a)example.com test3(a)example.com' > from mailman.app.membership import add_member, delete_member > from mailman.interfaces.member import MemberRole, AlreadySubscribedError > from mailman.interfaces.subscriptions import RequestRecord > > def set_owners(mlist, *addresses): > for email_addr in addresses: > try: > record = RequestRecord(email_addr) > member = add_member(mlist, record, role=MemberRole.owner) > print (member) > except AlreadySubscribedError as err: > print (err) > > def remove(mlist, *addresses): > for owner in mlist.owners.members: > if owner.address.email in addresses: > owner.unsubscribe() -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

[MM3-users] Re: Debian Package Install - Ownership and Permissions

by Dave Hall

On Fri, Apr 7, 2023 at 5:47 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 4/7/23 13:43, Odhiambo Washington wrote: > > On Fri, Apr 7, 2023 at 8:09 PM Andreas Schamanek < > > as2020+github(a)fam.tuwien.ac.at> wrote: > >> > >> I am running MM2 und 3 in parallel without problems, I do have a > >> special MTA setup though (Sendmail). Can't speak for Postfix etc.. > >> > > > > Your setup can handle list1(a)domain1.name via MM2 and MM3, > simultaneously, > > right? :-) > > It is possible to have an MM2 `list1` and an MM3 `list1(a)domain1.name` > simultaneously on the same server, but what is the MTA going to do with > incoming mail to `list1(a)domain1.name`. I suppose it could deliver it to > both MM2 and MM3, but I don't see any practical use case for this. > > I run Exim4 on my servers so I can comment from this perspective. Exim had a concept of 'routers' which are stacked and processed in order of appearance. There is a router for MM2 and one for MM3 that pick off incoming mail based on whether the email address matches a list name. WIth this setup, you could have the same list name in both MM2 and MM3, but it would go to whichever router appears first and the second one would never see it. So I have the MM3 router first, and as I migrate my lists from MM3 the email for those lists no longer gets to MM2. > -- > 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://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 kdhall(a)binghamton.edu -- Dave Hall Binghamton University kdhall(a)binghamton.edu 607-760-2328 (Cell) 607-777-4641 (Office)

2 years

[MM3-users] Re: Broken web UI after upgrade

by Odhiambo Washington

On Sat, Dec 17, 2022 at 9:22 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/16/22 21:47, Odhiambo Washington wrote: > > On Fri, Dec 16, 2022 at 11:17 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> > >> I suggest you run > >> ``` > >> django-admin collectstatic --clear --noinput --verbosity 2 > >> > > > > The output is here: https://pastebin.ubuntu.com/p/qkR2bDYv3G/ > > > > > > > >> django-admin compress --verbosity 2 > >> > > > > The output of the above is here: > https://pastebin.ubuntu.com/p/T7jQPrs3JX/ > > > Those look OK. > > I suggest you look at ownership and permissions. > I doubt it's about ownership and permissions given the fact that I have even done "chown -R mailman.mailman /opt/mailman" just for the kicks. > > ``` > find /opt/mailman/mm/static/ -not -user mailman > find /opt/mailman/mm/static/ -not -perm -u+rw > find /opt/mailman/mm/static/ -type d -not -perm -u+x > ``` > and the same on > /opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/ > root@list:/home/wash# find /opt/mailman/mm/static/ -not -user mailman root@list:/home/wash# find /opt/mailman/mm/static/ -not -perm -u+rw root@list:/home/wash# find /opt/mailman/mm/static/ -type d -not -perm -u+x root@list:/home/wash# find /opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/ -not -user mailman root@list:/home/wash# find /opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/ -not -perm -u+rw root@list:/home/wash# find /opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/ -type d -not -perm -u+x root@list:/home/wash# Yielded nothing - perms and ownership are all okay. > If the above doesn't reveal anything substantial, then let me know and I > > can bump up the verbosity. > > > I don't know if --verbosity 3 will reveal anything or not. You could try. > I did check, but the output looks the same as when it's set to 2. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 4 months

[MM3-users] Re: Starting new thread in Postorius -> disappears

by Thor Atle Rustad

I go with the workaround from Cameron Smith: sudo docker-compose exec mailman-web ./manage.py runjobs yearly makes messages appear However, there was "something" else that caused my messages not only NOT to show up in Hyperkitty, but also caused them not to be sent in the first place. I believe the reason was wrong subdomain in SERVE_FROM_DOMAIN in docker-compose.yaml. 2017-11-22 0:38 GMT+01:00 Mark Sapiro <mark(a)msapiro.net>: > On 11/21/2017 01:53 AM, Thor Atle Rustad wrote: > > I have had this working before, so I guess it's a simple setup error. > > > > When I send a message from the Postorius interface, it is neither sent > out > > or stored. I briefly see this message: "Your reply has been sent and is > > being processed.", and then nothing happens. > > > I assume you mean HyperKitty. Postorius has no facility for posting > messages to a list. > > > > I have installed maxking's docker-mailman and copied my old setup with > > basic stuff like passwords and such. The only new thing is that I'm now > > running in userspace by putting in /etc/subuid and subguid: > > > When you post from HyperKitty, HyperKitty creates a > django.core.mail.EmailMessage() instance and calls it's send() method > which causes Django to send the message to the list address. It then has > to be received and processed by Mailman the same as any email post > before it will appear in the archive. > > Are you running with DEBUG = True. If so, Hyperkitty won't send the mail. > > If DEBUG = False and normal posting is working, perhaps there is some > Postfix issue in delivery of the message from Django to Mailman. > > -- > 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/ >

7 years, 5 months

[MM3-users] Re: at the finish line of mailman3 docker, but can't sign in.

by Abhilash Raj

On Fri, Jul 30, 2021, at 11:01 AM, Mark Sapiro wrote: > On 7/30/21 10:47 AM, bob B wrote: > > > > Basically once I have docker installed, and mailman3 up and no lists are available, How do I setup or/and sign in as admin? > > > I'm not sure what the actual command would be do run the django-admin > interface in the docker image, but from below, it looks like it's > `mailman-web`. Run `mailman-web createsuperuser` to create an admin ID. Container images don't support mailman-web command yet, it has to be ported to use the mailman-web command. You can run commands with `docker exec -it mailman-web ./manage.py <command>`. For creating the superuser, you can run[1] [1]: https://asynchronous.in/docker-mailman/web.html#running Although, if you have set the MAILMAN_ADMIN_EMAIL, that command should have already run in the setup process. You want to figure out the email sending process. Although, you can create a second admin and set the password for it and login using that using the command mentioned at [1]. > > > > Also In docker how can I test sending mail? the command "mailman-web sendtestemail youremailid@domain" from the mailman-web container does not work. You can run docker exec -it mailman-web ./manage.py sendtestemail youremailid@domain > > This command tries to send the mail via SMTP to localhost port 25. > > > > How can I make sure my containers can send and receive mail? > > > The MTA should be listening on port 25 and that need to be visible in > the mailman-web container. See > <https://asynchronous.in/docker-mailman/#setting-up-your-mta> > > -- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

3 years, 8 months

[MM3-users] Re: Weird response to postings after subscriptions and accounts

by Mark Sapiro

On 9/17/19 6:39 PM, paul(a)arenson.org wrote: > > A) Thoughts before summarizing tests. > 1) I had originally thought of making archives only for subscribers to give them the benefit of posting from the archives directly and being able to find stuff more like a forum (email is always hard to follow). Anyone logged in to an account can post from Hyperkitty. Their post is treated the same as if they posted by email. > 2) But in retrospect it seems people can get an idea what the list is about from free access. So that is now what I have. OK > 3) On the other hand, it is a bit confusing that a non member can post from the archives without realizing that they need to register, with my settings I can moderate and decide if I want to add him or her to the list based on whether that is spam or not. So ok. A non-member is a non-member. A post from a non-member is handled according to "Default action to take when a non-member posts to the list" unless that non-member has a Moderation action other than List Default. > B) THE TESTS > I was testing too many variables so, to simplify things, I made my settings as follows > > 1) Subscription—> Confirm > > 2) Message Acceptance—> Default processing (so only members may post) > > 3) Testing Procesure > I added people three ways—> To do that I created 3 unique addresses to see if they can send and receive by email. > > > 3a) subscribe without creating an account—from here (bottom) https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… > > 3b) Subscription / Unsubscription from same page, navigate to Login and again navigate to signup > Comment 1: Confusing because even after creating an account, they are not subscribed to the list. Maybe it makes sense if a person has many lists, but I only have this one. It does not say clearly that one has to subscribe after creating an account. I understand it's not totally explicit, but it says "To subscribe or unsubscribe from this list, please log in first. If you have not previously logged in, you may need to set up an account with the appropriate email address." To me the implication is once you have created an account, you have to come back, log in and subscribe. What do you want it to say? > Comment 2: The other thing is that it does not show my domain but that of mailman3.emwd.com <http://mailman3.emwd.com/>. Talk to Brian (emwd) > 3c) Mass Subscribe by me. Which is what I intend for my 600 users from another list company. > Comment This worked fine. > > > C) Summary > 1) I have been thinking of having an account as a good way to get users used to using the archives as a way to confirm current and past topics (as opposed to keeping track by email. But it seems I need to tell them to BOTH subscribe AND create an account. Am I thinking about it the wrong way? That's correct. They need an account and they need to subscribe that account to the list. > 2) When a person wants to unsubscribe, they go to discuss-request(a)list.tokyoprogressive.org <mailto:discuss-request@list.tokyoprogressive.org> with subject bline help. > > a) Isn’t there a better way to unsubscribe by email? email to discuss-leave(a)list.tokyoprogressive.org (or discuss-unsubscribe(a)list.tokyoprogressive.org) Or you can login, go to https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… and click the big red unsubscribe button. > b) And how about a way to remove their account itself? Log in and click the dropdown at the upper right, select Account and click the Delete Account tab or go directly to https://list.tokyoprogressive.org/user-profile/ and click the Delete Account tab or go directly to https://list.tokyoprogressive.org/user-profile/delete -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

[MM3-users] Re: How to use the "recipient_delimiter" postfix parameter with Mailman3?

by Pierre Malard

Ok, thanks for the documentation. But as Mailman uses this functionality for its own processing of emails, if I leave it to be used for another processing, Mailman will no longer work correctly... Ok, that means I'm going to forbid the use of the escape character when processing mailing lists. > Le 12 avr. 2022 à 16:37, Mark Sapiro <mark(a)msapiro.net> a écrit : > > On 4/12/22 01:56, Pierre Malard via Mailman-users wrote: >> Hi, >> We are using the « recipient_delimiter » parameter with our Postfix server as « _ ». >> Visibly, Mailman have it’s own mail configuration because it doesn’t work know. >> Is it a way to conserv this Postfix functionality? > > > Mailman by default expects the recipient delimiter to be `+`. There are various settings in the [mta] section of mailman.cfg that allow you to change this. These are documented along with default settings at lines 812 - 898 of https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.… > > -- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- Pierre Malard Responsable architectures système GeoSUD IRD - UMR Espace-Dev - UMS CPST - IR Data-Terra Maison de la Télédétection 500 rue Jean-François Breton 34093 Montpellier Cx 5 France « Les utopies ne sont souvent que des vérités prématurées » Alphonse de Lamartine |\ _,,,---,,_ /,`.-'`' -. ;-;;,_ |,4- ) )-,_. ,\ ( `'-' '---''(_/--' `-'\_) πr perl -e '$_=q#: 3|\ 5_,3-3,2_: 3/,`.'"'"'`'"'"' 5-. ;-;;,_: |,A- ) )-,_. ,\ ( `'"'"'-'"'"': '"'"'-3'"'"'2(_/--'"'"' `-'"'"'\_): 24πr::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print' - --> Ce message n’engage que son auteur <-- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

3 years

[MM3-users] Re: config incoming email in my domain cpanel

by Rafael Mora

El jue., 3 ago. 2017 a las 15:49, tlhackque via Mailman-users (< mailman-users(a)mailman3.org>) escribió: > I think you're confused. > > You already have mail.labbrands.com set up as the MX record for > labbrands.com. And it has an A record with the same address as your > webserver. > I'm working with the hostgator mailserver, we are not running a local mailserver. As suggested I added an A record like this: [image: image.png] Is it correct? is it redirecting to my Ip so I can redirect it to my postfix/mm3 server? > > So if you're getting e-mail on that domain, there's another e-mail > server running on that IP address. You can't have 2 servers on port > 25. In that case, as has been noted before, you'll need to setup a > relay in that server, not a firewall redirect. Depending on your MTA, > you would need to relay to your internal server. And make sure your > firewall setup allows your MTA to do this. > > We can see it's EXIM: > > telnet mail.labbrands.com 25 > Trying 192.185.51.89... > Connected to mail.labbrands.com (192.185.51.89). > Escape character is '^]'. > help > 220-gator4137.hostgator.com ESMTP Exim 4.87 #1 Thu, 03 Aug 2017 15:47:48 > -0500 > 220-We do not authorize the use of this system to transport unsolicited, > 220 and/or bulk e-mail. > 214-Commands supported: > 214 AUTH STARTTLS HELO EHLO MAIL RCPT DATA NOOP QUIT RSET HELP > quit > 221 gator4137.hostgator.com closing connection > Connection closed by foreign host. > > Or, consolidate all your e-mail to one server - which is a lot easier to > manage unless you have a really big operation. Postfix is probably the > right choice, but requires more setup. > > Although Mailman3 configuration is not well documented (as you've > discovered), you may want to get help from someone with more general > network and mail experience. You're now into territory that is, as > Simon indicated, not Mailman-specific. > > On 03-Aug-17 16:28, Rafael Mora wrote: > > El jue., 3 ago. 2017 a las 15:26, Mark Sapiro (<mark(a)msapiro.net>) > escribió: > > > >> On 08/03/2017 01:22 PM, Rafael Mora wrote: > >>> El jue., 3 ago. 2017 a las 15:18, Mark Sapiro (<mark(a)msapiro.net>) > >> escribió: > >>>> You need to forward port 25 for SMTP mail delivery and if you want the > >>>> web UI (Postorius and HyperKitty) accessible from the outside, port 80 > >>>> for http and/or port 443 for https > >>>> < > >>>> > >> > https://www.iana.org/assignments/service-names-port-numbers/service-names-p… > >>>>> . > >>> I mean for incoming mail redirected from my hostgator hosting, because > >> when > >>> I suscribe an email address MM3 sends a confirmation email, so I have > to > >>> reply to be suscribed to the list. > >> > >> As I said, for mail delivery you need to forward port 25 to the Mailman > >> server. > >> > > Ok so I'll redirect in my zentyal firewall the port 25 to my local > centos7 > > with postfix and MM3 with IP 192.168.1.42. Thanks Mark. > > > > > >> > >> -- > >> 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/ > >> > > -- > This communication may not represent my employer's views, > if any, on the matters discussed. > > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

7 years, 8 months

[MM3-users] Re: Mailman, etc. upgrade woes and persistent bugs

by Mark Sapiro

On 2/11/21 10:22 PM, hansen(a)rc.org wrote: > I just had my Mailman suite upgraded. When it got started, I starting receiving messages that hundreds of subscribers to the lists had been disables, including several of the list moderators. This version started supporting bounce processing, but how in the world was this upgrade allowed to act on bounces that were being collected PRIOR to enabling bounce processing?? I'm sorry about that. It's too late now, but the avoidance is discussed at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>. > I got many angry emails, messages and phone calls asking what was going on, as they were bona fide list members. I was very surprised myself. > > I then looked at several of the disabled accounts, but the subscription info page in Postorius had no information about whether an account was enabled or disabled. Why is this not displayed???. The members can't see if their account is enabled. Is this another example of the disconnect between Mailman and Postorius? If the user has a Django account, she can see all that info at (e.g. for this list) <https://lists.mailman3.org/mailman3/accounts/subscriptions/> She gets there from `Mailman settings` in the dropdown under her user name. She can also get there via the `Manage Subscription` button on the list's Info page. That takes her to `List-based preferences` for the list. Any setting not selected there is inherited from the Address-based preferences or Global Mailman preferences > Further, even after the upgrade, the moderators still cannot access the list memberships even though all the lists are set to allow that. I would have asked the moderators to do this if this access bug had been fixed, but they can't get there. You've already reported this at <https://gitlab.com/mailman/postorius/-/issues/462>, and it's been previously reported at <https://gitlab.com/mailman/postorius/-/issues/369>. > As a result of these bugs, after consulting with Brian, who helped with the upgrade, I spent many hours re-enabling the several hundred accounts that had been disabled. I had to go through each email notification to find the address of a disabled account, then find the list, then the member, in Postorius, and finally enable the account (at which time Postorius DID show the enabled status). I'm sorry you had to go through this. The potential issue and the avoidances should be better documented. Unfortunately, they aren't. > Please, can the next upgrade include these very basic fixes/enhancements, which I requested a long time ago: > > a. The ability of moderators to see the list membership (a bug). As I note above, this is a known issue. We are a small project with very feew core developers, all of whom are volunteers. There is a merge request at <https://gitlab.com/mailman/postorius/-/merge_requests/423> which purports to fix <https://gitlab.com/mailman/postorius/-/issues/369>, but as you can see from the comment thread, it is not complete and the author has apparently disappeared. If you would like to take it over and address the deficiencies, we would welcome that. > b. The ability of members to change their addresses for all lists they are subscribed to. Users can add addresses to their account and can then change their subscribed address at (again, e.g. for this list) <https://lists.mailman3.org/mailman3/accounts/list-options/mailman-users.mai…> (Get there via the `Manage Subscription` button on the list's Info page.) If one is subscribed to lists via their `primary` address, one can go to `E-mail Addresses` in their account settings and make a new address `primary` and that will change all their subscriptions. > and further, now: > > c. That when members go to look at their subscription info, they can actually see the settings. They can if they go to `Mailman settings` in the dropdown or the `Manage Subscription` button on the list's Info page and look at all the tabs. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 2 months

[MM3-users] Re: Apache Conf

by Abhilash Raj

On Fri, Oct 19, 2018, at 12:17 PM, Thomas G wrote: > Hi tried both. > > Same result. > > xxxx - - [19/Oct/2018:21:14:22 +0200] "GET /static/postorius/js/script.js > HTTP/1.1" 404 4051 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:60.0) > Gecko/20100101 Firefox/60.0" And, you have verified that the files exist at `/opt/mailman/static` on your host? > > > Le ven. 19 oct. 2018 à 18:59, Mark Sapiro <mark(a)msapiro.net> a écrit : > > > On 10/19/18 10:29 AM, Guiseppin Thomas wrote: > > > Hi, > > > Currently, I use a nginx configuration for mailman. It's work perfectly. > > > > > > I tried to do the same with Apache, but the statics files are not > > > delivered (404). > > ... > > > <VirtualHost *:80> > > > ServerName mailing.ddd.fr > > > > > > ErrorLog ${APACHE_LOG_DIR}/mailing.error.log > > > CustomLog ${APACHE_LOG_DIR}/mailing.access.log combined > > > > > > <Location /static/> > > > Alias "/opt/mailman/static/" > > > </Location> > > > > > > <Location /> > > > ProxyPass http://localhost:8000/ > > > ProxyPassReverse http://localhost:8000/ > > > ProxyPreserveHost On > > > </Location> > > > </VirtualHost>/ > > > > > > In Apache, location > > <http://httpd.apache.org/docs/2.4/mod/core.html#location> is not > > appropriate for resources in the file system. > > > > Try > > > > Alias /static/ /opt/mailman/static/ > > > > not within a location block. > > > > -- > > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > _______________________________________________ > 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)

6 years, 6 months

[MM3-users] Re: [EXTERNAL] Re: Database deadlock when trying to delete a member.

by Simon Coggins

After making that change and doing some testing. So far I’ve not had any issues and the sync are working as expected now. -Simon From: Mark Sapiro <mark(a)msapiro.net> Date: Wednesday, 24 March 2021 at 4:10 am To: "mailman-users(a)mailman3.org" <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: [EXTERNAL] Re: Database deadlock when trying to delete a member. On 3/22/21 9:53 PM, Simon Coggins wrote: > Ok after bit tracking I’ve worked out that the bouncer is dangling transactions when it’s sending warning messages. When https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py…<https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py…> is called and it get to update last_warn_sent it does the following in the DB: > > 2021-03-23 14:42:50.622 AEST [11693] LOG: statement: UPDATE member SET last_warning_sent='2021-03-23T04:42:50.622015'::timestamp, total_warnings_sent=1 WHERE member.id = 169331 > > But it never COMMITs this transaction. So all write operations are now hung waiting for the transction to be closed as the member record has been modified. As a test I added config.db.commit() after https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py…<https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py…> and restarted. And my mailman syncmembers worked perfectly and I didn’t have any hangs it correctly removed everyone it should have. In the database logs I can see the COMMIT. > > I’m pretty sure this is not the right spot for a config.db.commit() but hopefully this helps point to what might be going wrong. Thank you for all the research on this. It is extremely helpful. Instead of adding a commit after line 277 please try adding the @transactional decorator to the send_warnings_and_remove method at line 210 @transactional @dbconnection def send_warnings_and_remove(self, store): I think that is the proper fix. Let us know if that works. -- 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org>

4 years

[MM3-users] Re: Apple Mail encoding again

by Rainer Herbst

Dear all, as the original poster, I have asked the user to send a test mail through our mailman3 system (docker image maxking/mailman-core:0.4.2) and the mail passed. The user is now on Apple Mail 16, maybe that does the trick. Please find enclosed the anonymizied mail source. Best regards and thanks for caring even if the problems seems to affect only a small number of users! Rainer On Fr, 15 Apr 2022 09:03:41 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 4/14/22 21:33, Stephen J. Turnbull wrote: >> >> Whether we *want* to do that depends on how much trouble that causes >> for our main constituency (list and site admins), and whether we can >> provide discoverable documentation of the problem. My take is that >> this seems to be an extremely rare problem, and at least some MUAs >>are >> able to read the message, so we should let it through. > >First, we are not silently dropping this message. We are rejecting it >at LMTP time so the sender should be notified. > > Then the broader question is should we accept all messages with >defects, almost all of which are spam, or only certain defects and >which ones. > > I note that Apple has now released Mail 16 so maybe they've fixed >this. My macs are still on Big Sur, so I can't test this. > > > -- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Viele Grüße Rainer Herbst Leiter IT-Service Phone: +49 331 7499-257 e-mail: rainer.herbst(a)aip.de https://www.aip.de ----------------------------------------------------------------------------------------------- Leibniz-Institut für Astrophysik Potsdam (AIP) An der Sternwarte 16, 14482 Potsdam Vorstand: Prof. Dr. Matthias Steinmetz, Wolfram Rosenbach Stiftung bürgerlichen Rechts Stiftungsverzeichnis Brandenburg: 26 742-00/7026 ----------------------------------------------------------------------------------------------- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: application/x-pkcs7-signature Name: smime.p7s

3 years

[MM3-users] Re: Uncaught runner exception

by Wolfgang Bock

Hello Mark, thanks for your hint. Postfix is runnig as mta on my machine. I tested port 25 with swaks ->mail to user on server: localhost port 25 -> everything fine Mailman is configured with localhost for incoming and outgoing mails. After stopping mailman3, deleting all files in the queue directories, restart mailman3 I sent a test-mail /var/log/mailman3/mailman.log Apr 07 12:08:23 2020 (28198) Master started Apr 07 12:08:24 2020 (28206) out runner started. Apr 07 12:08:24 2020 (28202) command runner started. Apr 07 12:08:24 2020 (28203) in runner started. Apr 07 12:08:24 2020 (28200) archive runner started. Apr 07 12:08:24 2020 (28201) bounces runner started. Apr 07 12:08:24 2020 (28210) retry runner started. Apr 07 12:08:25 2020 (28208) rest runner started. Apr 07 12:08:25 2020 (28212) digest runner started. Apr 07 12:08:25 2020 (28205) nntp runner started. Apr 07 12:08:26 2020 (28211) virgin runner started. Apr 07 12:08:26 2020 (28207) pipeline runner started. Apr 07 12:08:26 2020 (28204) lmtp runner started. Apr 07 12:09:19 2020 (28203) ACCEPT: <000f01d60cc4$96c9a8d0$c45cfa70$@[domain]> Apr 07 12:09:21 2020 (28206) Cannot connect to SMTP server localhost on port 25 I have no idea what to do for solving my problems. Regards from Hamburg Wolfgang -----Ursprüngliche Nachricht----- Von: Mark Sapiro <mark(a)msapiro.net> Gesendet: Montag, 6. April 2020 23:50 An: Wolfgang Bock <mailinglisten(a)wbock.de> Betreff: Re: [MM3-users] Re: Uncaught runner exception On 4/6/20 2:44 PM, Wolfgang Bock via Mailman-users wrote: > Thank you Steven for your reply! > > I Set smtp_server to port 25 and got a "Cannot connect ro SMTP Server > on port 25", the former error message didn't show again. > > As I see port 25 is reseved for postfix. So I have to fiddle out how > mailman3 could also use this port for sending mails out. .... You need an MTA for Mailman to deliver its mail to. Normally this will be Postfix, sendmail, Exim, etc running on localhost and listening on port 25. Do you have such an MTA running on localhost? Note, Mailman does not directly send mail to end recipients. It only delivers mail to an outgoing MTA. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: Setting up on ubuntu server 22.04

by Kyriakos Terzopoulos

Thanks Mark, That seemed to work: (venv) mailman@hestia:~/venv$ mailman info GNU Mailman 3.3.8 (Tom Sawyer) Python 3.10.12 (main, Jun 11 2023, 05:26:28) [GCC 11.4.0] config file: /etc/mailman3/mailman.cfg db url: postgresql://mailman:XXXXXXXXXXXXX>@localhost/mailman devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: XXXXX:XXXXXX Now, off to handle other issues like nginx, exim4, etc. I will search or create another thread for this if I'm stuck. It would be nice to somehow update the documentation for https://docs.mailman3.org/en/latest/install/virtualenv.html. Thank you all for your efforts. *Kyriakos* On Wed, 4 Oct 2023 at 03:44, Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/3/23 06:00, Kyriakos Terzopoulos wrote: > > > > However, I cannot find the mailman/setup.py anywhere in order to patch > it, > > since the installation was done through pip from here: > > > https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… > > > > Maybe I can try upgrading python from 3.10 to 3.11 and re-install > > > Upgrading Python won't help. There is currently an incompatibility issue > when following > https://docs.mailman3.org/en/latest/install/virtualenv.html because that > doc is based on the head of the GitLab branch, but `pip install > mailman3` installs the 3.3.8 released version of core and the latest > 6.1.0 version of importlib_resources and these are incompatible. > > There are two ways to fix this. > > The easy way is to downgrade importlib_resources in your venv with > ``` > pip install importlib_resources\<6.0 > ``` > The slightly more complex way is to upgrade mailman core to 3.3.9b1 from > GitLab with > ``` > pip install -U git+https://gitlab.com/mailman/mailman.git > ``` > > -- > 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://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 kyriakos.terzopoulos(a)gmail.com >

1 year, 6 months

[MM3-users] Re: UnpicklingError on mailman lists command

by Bryan Loniewski

$ /opt/mailman/mm/bin/mailman version GNU Mailman 3.3.2 (Tom Sawyer) So, I'm running > 3.2. Any other advice on debugging the truncated data? ________________________ Bryan Loniewski Rutgers University OIT:EAS:Messaging and Collaboration Services System Administrator ________________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Monday, August 2, 2021 10:06 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: UnpicklingError on mailman lists command On 8/2/21 4:15 PM, Bryan Loniewski wrote: > Hi all -- > > $ /opt/mailman/mm/bin/mailman lists > Traceback (most recent call last): ... > File "/opt/mailman/venv/lib/python3.6/site-packages/mailman/commands/cli_lists.py", line 78, in lists > for mlist in list_manager.mailing_lists: > File "/opt/mailman/venv/lib/python3.6/site-packages/mailman/model/listmanager.py", line 100, in mailing_lists > MailingList._list_id).all() > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/query.py", line 3246, in all > return list(self) > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/loading.py", line 101, in instances > cursor.close() > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/util/langhelpers.py", line 69, in __exit__ > exc_value, with_traceback=exc_tb, > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/util/compat.py", line 178, in raise_ > raise exception > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/loading.py", line 81, in instances > rows = [proc(row) for row in fetch] > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/loading.py", line 81, in <listcomp> > rows = [proc(row) for row in fetch] > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/loading.py", line 589, in _instance > populators, > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/orm/loading.py", line 726, in _populate_full > dict_[key] = getter(row) > File "/opt/mailman/venv/lib/python3.6/site-packages/sqlalchemy/sql/sqltypes.py", line 1708, in process > return loads(value) > _pickle.UnpicklingError: pickle data was truncated This is probably https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.co… which was fixed in Mailman 3.2.0 by https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.co…. What version are you running? If your version is 3.2.0 or greater, it could be one of the other issues with MySQL/MariaDB truncating data. -- 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://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

3 years, 8 months

[MM3-users] Re: Rejecting held emails

by Darren Smith

Mark, You're quite right, I meant Discard. Thanks for the clarification. I hope to be able to pull a fix in for this in the near future. :) -Darren On Thu, Apr 26, 2018 at 10:14 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 04/26/2018 08:43 AM, Darren Smith wrote: > > > > We recently had a phishing message make it through our spam filters and > > arrive at a mailing list. The good news is that since it was not from a > > list member it was in the held message queue. > > > > I was able to find the message in the var/messages directory by searching > > for a keyword in the subject. However, after rejecting the message from > > Postorius, the message doesn't seem to be removed from the var/messages > > directory. > > > Do you mean Reject and not Discard? Phishing/Spam should never be > "rejected" for backscatter reasons. Reject should only be used for > somehow inappropriate posts from known people. > > > > Is this expected behavior? I know that infosec people won't be too happy > > about a phishing email sitting around on our disk. (Infosec guys are > > notoriously paranoid. :) ) > > > > Is there some sort of cleanup process that would remove these messages? > If > > not, does this pose an issue where over time disk usage will creep up? > This > > could be a pretty significant problem if that is the case. > > > It's not the behavior I would "expect", but it is the way it currently > works, and yes, all your concerns are valid. This is > <https://gitlab.com/mailman/mailman/issues/257> which I just edited to > note that in addition to not removing the pending db entry, the message > isn't removed either. > > -- > 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/ >

6 years, 11 months

[MM3-users] Re: Walk-thru for Ubuntu Bionic Mailman 3 Full setup

by Kelly Close

Thanks for those clarifications Mark. -- K. Kelly Close, P. E. Senior Project Manager | Water Rights Engineer | Technology Team Lead Office: 303-455-9589 Direct: 303-867-7665 Kelly.Close(a)LREwater.com LREWATER.COM 1221 Auraria Parkway Denver, CO 80204 **CONFIDENTIALITY NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. Thank you. On Tue, Jun 16, 2020, 7:51 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/16/20 5:03 PM, kelly.close(a)lrewater.com wrote: > > I resolved this myself with a search that turned up a 2018 post from > Mark that suggested typing "mailman aliases" to create the > hash/alias/lookup table/file things in /var/lib/mailman3/data (that's where > they are on Ubuntu 18.04). I looked in that folder and sure enough it was > empty so I typed "sudo mailman aliases" which did indeed create the 4 > things that needed to be there: > > postfix_domans > > postfix_domains.db > > postfix_lmtp > > postfix_lmtp.db > > > > But, they were owned by root:root and everything else under that > /ver/lib/mailman3 folder is owned by "list" so I took a guess changed the > ownership on the 4 files to list:list. > > Because that's how you ran it. Run > > sudo -u list mailman aliases. > > > > Seems to have worked! I was perplexed about why I had to do this though > because these were created automatically last time I did this, but I > figured that out too. > > > Current `mailman start` should create the aliases. > > -- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

4 years, 10 months

[MM3-users] Re: Postorius password resets

by Andrew Hodgson

Mark Sapiro wrote: >On 10/15/20 9:24 PM, Andrew Hodgson wrote: >> Mark Sapiro wrote: >> >>> On 10/14/20 11:11 AM, Andrew Hodgson wrote: >> >>>> I am having an issue with our system where password resets are giving the users an email with a http://localhost:8000 URL. I have made sure settings in settings_local.py (and even settings.py) are as follows: >>>> >>>> POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.hodgsonfamily.org' >> >>> This is not relevant. >> >> Does it need resetting back to http://localhost:8000? Not if it works. Most likely either one is OK, but localhost:8000 avoids a DNS lookup an proxying through the web server. Ok I have reset this value now. >>>> However emails are still coming through with the wrong URL. >> >>> I'm not sure offhand, but it's either domains in Postorius or sites in the django admin UI. >> >> I've checked both and cannot see any errors (I just have the one site lists.hodgsonfamily.org) and nothing is empty which seems as though it needs filling in. >What's in `sites` and what's in `Mail domains` in the django admin UI https://lists.hodgsonfamily.org/admin/django_mailman3/maildomain/: <Mailman domain lists.hodgsonfamily.org> https://lists.hodgsonfamily.org/admin/django_mailman3/maildomain/1/change/ Site: lists.hodgsonfamily.org Mail domain: lists.hodgsonfamily.org https://lists.hodgsonfamily.org/admin/sites/site/1/change/ Domain name and display name: lists.hodgsonfamily.org >and what's in Web Host in the Postorius domains view - in particular, if you have Postorius 1.3.3, what's the SITE_ID, and what's SITE_ID in settings(_local).py. https://lists.hodgsonfamily.org/postorius/domains/ Mail Host Description Alias Domain Web Host lists.hodgsonfamily.org lists.hodgsonfamily.org (lists.hodgsonfamily.org) SITE_ID = 1 Site ID is 1 in settings.py (not overridden in settings_local.py) > Also, when you go to the archive UI, whats the domain at the top left of the pages. Lists.hodgsonfamily.org I have overridden the following settings relating to this in settings_local.py: USE_X_FORWARDED_HOST = True ALLOWED_HOSTS = [ 'localhost', 'lists.hodgsonfamily.org' ] Settings.py is from the latest commit from the Mailman Suite Gitlab project. Thanks for helping me with this. Andrew.

4 years, 6 months

[MM3-users] Re: Template Ignored?

by Stephen Daniel

Fixed the POSTORIUS_TEMPLATE_BASE_URL. Doesn't fix the issue. I've been playing with wget, and no matter what I put, I keep getting a 404 error. So: this works: wget -O wget.out --user restadmin --password restpass ' http://localhost:8001/3.1/lists/list.example.com' but this does not (404 error): wget -O wget.out --user restadmin --password restpass ' http://localhost:8001/3.1/templates/list/list.example.com/list:user:notice:… ' Is there a way to list all templates? Or all templates for a list? On Thu, Feb 17, 2022 at 12:34 PM Stephen Daniel <swd(a)pobox.com> wrote: > That pulls a 404 error. Thanks for the hint. I will investigate. > > On Thu, Feb 17, 2022 at 11:49 AM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 2/17/22 08:04, Stephen Daniel wrote: >> > Mailman3 people -- >> > >> > I created a new list, and used postorius to create a template for " >> > list:user:notice:welcome". I then used the mass subscription feature to >> > add myself to the list, having checked "pre-confirmed", "pre-approved", >> and >> > "pre-verified". >> > >> > I received a welcome message that appears to be the default welcome >> > message. It certainly wasn't what I put into my template. >> > >> > Any suggestions on how I get mailman to use my template? Things I >> might be >> > doing wrong? >> >> >> What is your setting for POSTORIUS_TEMPLATE_BASE_URL? If you create a >> full URL by appending >> `/api/templates/list/list.example.com/list:user:notice:welcome` >> <http://list.example.com/list:user:notice:welcome> to that >> where `list.example.com` is the actual list_id of your list, and go to >> that URL, what do you get? >> >> -- >> 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> >

3 years, 2 months

[MM3-users] Re: hyperkitty failed to create a thread

by Abhilash Raj

On Thu, Feb 14, 2019, at 11:51 AM, Danil Smirnov wrote: > Thank you very much for the quick fix, Mark and Abhilash! > > Abhilash, could you include the fix into the "latest" version of > mailman-web container please? They are nightly builds, if the fix was merged and the CI went through, they should already be in there. > > Btw I wasn't able to find a changelog of Mailman docker images anywhere and > 'Releases' page in Github is quite outdated too... Is there any other > place I should check? I have admittedly been too busy to write release notes, but the recent releases have seen not too much changes other than version bumps for the included Mailman packages. > > Danil > > вт, 12 февр. 2019 г., 4:06 Mark Sapiro <mark(a)msapiro.net>: > > > On 2/11/19 9:47 AM, Danil Smirnov wrote: > > > > > > What could be a reason of HyperKitty failing to create a thread from > > > chained emails? > > > > > > For example, see "RECENTLY ACTIVE DISCUSSIONS" on page > > > https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org/ > > > > > > "Openvpn and Network mapping" discussion displayed as five threads > > instead > > > of only one... > > > > > > Any ideas how to improve HyperKitty ability to detect threaded messages? > > > > > > Thanks for the report. > > > > The MR at <https://gitlab.com/mailman/hyperkitty/merge_requests/125> > > will fix this. > > > > -- > > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > _______________________________________________ > 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)

6 years, 2 months

[MM3-users] Re: Notifying owners of membership changes but not moderators

by Perry Kollmorgen

Thanks Mark. So, I have python scripts which do the adding of nonmembers and moderators. For the nonmember script I needed to add something so that the nonmembers can send, i.e the moderaction_action = 'defer' This is my code for nonmembers: mailing_list.add_role('nonmember', nonmember.email, display_name=nonmember.display_name) list_member = mailing_list.get_nonmember(nonmember.email) list_member.moderation_action = 'defer' list_member.save() For the code for moderators it currently only adds them: mailing_list.add_moderator(moderator.email, display_name=moderator.display_name) Would I need to add something similar which sets a delivery_status for the moderator added ? Cheers, Perry ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, 27 November 2024 2:16 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Notifying owners of membership changes but not moderators On 11/26/24 4:54 PM, Perry Kollmorgen wrote: > > Is there any way to have these only for Owners ? No. Essentially all admin notices are sent to LISTNAME-owner@DOMAIN and that in turn resends to owners and moderators. There are no controls to restrict this to only owners and not moderators, however it doesn't send to those with delivery disabled, so you could do something like this in `mailman shell` ``` $ mailman shell -l LIST_ID Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the LIST_ID mailing list >>> for moderator in m.moderators.members: ... moderator.preferences.delivery_status = DeliveryStatus.by_moderator ... >>> commit() ``` This will not affect the delivery status of the user's role as list member. This is not available in Postorius and also, the moderator can't set the delivery_status for their moderator role either, only for their member role. -- 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://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 pcjkollmorgen(a)hotmail.com

4 months, 4 weeks

[MM3-users] Re: MM3 templates

by Odhiambo Washington

On Thu, Feb 16, 2023 at 9:32 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/15/23 23:42, Odhiambo Washington wrote: > > On Thu, Feb 16, 2023 at 10:26 AM Mark Sapiro <mark(a)msapiro.net> wrote: > > > > In my case, I had the exact same files in the two paths and the > > list:user:action:subscribe.txt was still not used in my tests. > > Why? > > > I don't know why? What's the content of the template table in the database? > ``` > SELECT * FROM template; > ``` > root@localhost [mailmansuite]> SELECT * FROM template; Empty set (0.03 sec) > I have now created the directory: > > mkdir -p /opt/mailman/mm/var/templates/domains/lists.kictanet.or.ke/en/ > > And I have placed the same files in there. Gearing up for a test to see > if > > the template will be used this time around. > > > That's just wasting space. If you're putting the exact same templates in > site/, domains/ and lists/, you might just as well delete the ones in > domains/ and lists/ and Mailman will use the ones from site/. > Well, space is cheap these days. > >> A template from import21 of the kictanet(a)lists.kictanet.or.ke list will > >> be stored in the > >> /opt/mailman/mm/var/templates/lists/kictanet.lists.kictanet.or.ke/en/ > >> directory. > >> > > > > It wasn't a template per se. It was the regular nondigest msg_footer from > > MM2. > > > import21 imports the nondigest msg_footer, makes certain adjustments for > Mailman3 compatibility and stores it as a template in the > var/templates/lists/<list-id>/<lc>/ directory, however if it was the MM > 2.1 default msg_footer, it won't be stored as a template and the MM3 > default list:member:generic:footer template will be used. > And what I am seeing is that the default list:member:generic:footer template is what is showing up in all posts. To my chagrin though. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 2 months

[MM3-users] Re: Mailman 3 Keeps Forgettings Imported Lists

by Ryan McClung

I do see the output of the script and it shows the mailing lists being created. If you put "${VARIABLE}"@domain.com it outputs correctly. Also, to that end, the output of lists changes depending on which directory I am in which makes 0 sense. On Tue, Jul 31, 2018 at 3:27 PM Ryan McClung <rmcclung(a)afilias.info> wrote: > I do see the output of the script and it shows the mailing lists being > created. If you put "${VARIABLE}"@domain.com it outputs correctly. > > On Tue, Jul 31, 2018 at 3:22 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 07/31/2018 07:04 AM, Ryan McClung wrote: >> > Scratch that. Ran with the corrected script and getting the following: >> > [root@mailman3(stg) archives]# mailman lists >> > No matching mailing lists found >> > >> > Any thoughts? >> >> This >> >> > for DIR in $DIRS; do mailman create "${DIR}"; mailman import21 "${DIR}"@ >> afilias.info "${DIR}"/config.pck; >> >> is still wrong. The list name for mailman create needs to be fully >> qualified as in >> >> > for DIR in $DIRS; do mailman create ${DIR}(a)afilias.info; mailman >> import21 ${DIR}(a)afilias.info ${DIR}/config.pck; >> >> (Do you look at the output from your script?) >> >> -- >> 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> > > > -- > > Ryan McClung > Systems Administrator @ Afilias Canada > A. 204-4141 Yonge Street, Toronto, ON, Canada, M2P 2A8 > <https://maps.google.com/?q=4141+Yonge+Street,+Toronto,+ON,+Canada,+M2P+2A8&…> > W. www.afilias.info > T. +1.416.646.3304 x4186 > -- Ryan McClung Systems Administrator @ Afilias Canada A. 204-4141 Yonge Street, Toronto, ON, Canada, M2P 2A8 <https://maps.google.com/?q=4141+Yonge+Street,+Toronto,+ON,+Canada,+M2P+2A8&…> W. www.afilias.info T. +1.416.646.3304 x4186

6 years, 8 months

[MM3-users] Re: hyperkitty won't list more than 5 posts and shows empty grey Activity Summary box

by Abhilash Raj

On Wed, 9 Aug 2017 15:45:48 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 08/09/2017 02:35 PM, Abhilash Raj wrote: > > Hi, > > > > On Wed, 9 Aug 2017 13:42:20 -0700 > > Mark Sapiro <mark(a)msapiro.net> wrote: > [...] > > > > I wasn't aware that Core needed cron jobs too, is that true for 3.1 release as > > well? > > > It's only that one and whether it's needed or not depends on list > configuration. The list has attributes digest_send_periodic and > digest_size_threshold. When a post is received it is added to the list's > digest mbox, and if that causes the size of the mbox to reach > digest_size_threshold K bytes, a digest is sent. Additionally, if > digest_send_periodic is true, a digest is sent periodically whether or > not it has reached digest_size_threshold. > > However, the sending of periodic digests depends on cron running > something periodically to actually trigger the sending. Can this be done using the REST API? If not, maybe we should do that so that Postorius can take of the periodic tasks? I am thinking mostly about the container images because the mailman-core container runs nothing else other than Core. I'd have to another cron for this which isn't a lot of overhead but since mailman-web container already has periodic tasks, it would be great if I could trigger it from there. > > Note: I've just looked at the code and there seems to be an issue with > using 'mailman digests --send' to send the periodic digests. It appears > that if a list's digest mbox has any messages, 'mailman digests --send' > will send a digest even if digest_send_periodic is false. I've just > reported <https://gitlab.com/mailman/mailman/issues/384> for this issue. Also, it seems that Postorius doesn't have any way to set `digest_send_periodic` and only has a setting to set the max_threshold for the digest. I opened another issue (https://gitlab.com/mailman/postorius/issues/211) to add this feature. -- thanks, Abhilash Raj

7 years, 8 months

[MM3-users] Re: Missing whitespace in postfix_vmap after mailman genaliases

by Wolfgang Bock

Dear Mark, I am running mailman3 (version 3.2.1) on debian buster. Created yesterday a Test mailinglist and faced the same problem in postmapping postfix_vmap again. Is the debian buster version of mailman3 not uptodate?? Regards Wolfgang -----Ursprüngliche Nachricht----- Von: Mark Sapiro <mark(a)msapiro.net> Gesendet: Sonntag, 20. September 2020 00:43 An: mailman-users(a)mailman3.org Betreff: [MM3-users] Re: Missing whitespace in postfix_vmap after mailman genaliases On 9/19/20 3:05 PM, Wolfgang Bock via Mailman-users wrote: > > after creating a new list I got the following errormessage: > > mailman aliases -> postmap: warning: > /var/lib/mailman3/data/postfix_vmap, > line 17: expected format: key whitespace value > > /var/lib/mailman3/data/postfix_vmap > # AUTOMATICALLY GENERATED BY MAILMAN ON 2020-09-19 07:44:34 .... > xxxxxxxxxxx(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-bounces(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-bounces(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-confirm(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-confirm(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-join(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-join(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-leave(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-leave(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-owner(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-owner(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-request(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-request(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-subscribe(a)lists.xxxxxxxxxxxxxxxx.de > xxxxxxxxxxx-subscribe(a)xxxxxxxxxxxxx.de > xxxxxxxxxxx-unsubscribe(a)lists.xxxxxxxxxxxxxxxx.dexxxxxxxxxxx-unsubscri > be@xxx > xxxxxxxxxx.de > > The last line in the left part contains 48 chars. It isn't clear what you really have, but I'm guessing that in each case except the last, what you show as two lines is actually a single line with whitespace between and the last line has no whitespace. This is <https://gitlab.com/mailman/mailman/-/issues/651>, fixed in Mailman 3.3.1 by <https://gitlab.com/mailman/mailman/-/merge_requests/576>. > I solved the problem by adding a whitespathe last line has no > whitespace.ce in the last line and I made a new postmap for postfix_vmap. > > But it would be better to solve the problem by changing the genaliases > process in the next update. Already fixed and released in the last update. -- 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 7 months

[MM3-users] Re: Using the API to create nonmembers with a different moderation action than the list default

by Perry Kollmorgen

Oh great, that will be very useful when it is ready. It is easy for standard users to maintain a list which can be used also for sending access to other lists, particularly when nested. This along with the extra URL variables for use in templates look handy also. I already have added some URLs to our templates manually however if we expand to other domains it would save on some updating of templates. Usually, I would look to merge in useful PRs to my own branch of the source code used in production however with the use of docker this time around it isn't quite as easy. Likely not too difficult, but it might be good to wait too. Regards, Perry ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Saturday, June 8, 2024 3:59:46 AM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Using the API to create nonmembers with a different moderation action than the list default On 6/6/24 11:36 PM, Perry Kollmorgen wrote: > Hi, > > My next challenge is to script the setup of a bunch of nonmembers who have a moderation action of accept (or maybe defer) whilst the list itself has a nonmember action of hold. > > This is due to a relatively heavy use of nested lists, and have a fair number of people who might possibly send to all lists, and are important enough they wouldn't want to be manually allowed each time even if it only once. Note that beginning with Mailman 3.3.10 (not yet released) you can put things like @list2@example.com in accept_these_nonmembers of list1(a)example.com to accept posts from non_members who are members of list2(a)example.com. See https://gitlab.com/mailman/mailman/-/merge_requests/1154 -- 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://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 pcjkollmorgen(a)hotmail.com

10 months, 2 weeks

[MM3-users] Re: sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for one_or_none()

by Shashikanth Komandoor

Thank you Mark. What you have said is right.. I found a list with two "hyperkitty" records in the listarchiver in the database. I had removed the list and recreated it and now I found it is working fine. The recreated list is having only one record. After searching the links you provided I found there is just a work around but not the precaution to be taken for not getting the duplicate record. Can you say what might be the reason for this duplication? If I need to provide any details, please let me know. On Fri, Jul 24, 2020 at 11:50 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/24/20 10:34 AM, Shashikanth Komandoor wrote: > > Hi Team, > > > > Today, I found an error message like "Multiple rows were found > > for one_or_none()" when a hold message is approved for a list. Until > > yesterday the mails were accepted and delivered fine. > > > We have seen this issue before. See > <https://gitlab.com/mailman/mailman/-/issues/657>. There are also > multiple threads on it in the archive, e.g., > < > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > >. > > We don't know how it happens, but the issue is that the `listarchiver` > table in the database has multiple `mhonarc` entries for the same > `mailing_list_id`. > > You can see the problem with the query > > select * from listarchiver where name = 'mhonarc'; > > There will be two entries with the same `mailing_list_id` and deleting > one of them will fix this and you can run `mailman unshunt` to reprocess > the shunted messages. > > The above referenced issue contains a script that can be run to remove > the extra entry. > > -- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

4 years, 8 months

[MM3-users] Re: Mailman 3, postfix domains, and postgresql cannot authenticate user

by Keith Christian

Odhiambo, Yes, trying to. Mark, I'll review your suggestions. Thanks. On Wed, Jul 3, 2024, 12:52 Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/3/24 09:22, Keith Christian via Mailman-users wrote: > > > --------------------------------------------------------------------------- > > First issue:Postfix v3.5.8 on RHEL 8. > > The below is from journalctl -xe: > > > --------------------------------------------------------------------------- > > Jul 03 08:12:04 somehost.somedomain postfix/qmgr[947499]: error: open > > database /opt/mailman3/mm/var/data/postfix_domains.db: No such file or > > directory > > Jul 03 08:12:42 somehost.somedomain postfix/smtpd[947510]: error: open > > database /opt/mailman3/mm/var/data/postfix_domains.db: No such file or > > directory > > Jul 03 08:12:42 somehost.somedomain postfix/smtpd[947510]: error: open > > database /opt/mailman3/mm/var/data/postfix_lmtp.db: No such file or > > directory > > > > I manually created the var_dir: /opt/mailman3/mm/var directory > > specified in the mailman.cfg file. > > How do I find out how to populate the postfix_domains.db files, and > > the postfix_lmtp.db file? > > > The `mailman aliases` command generates the postfix_domains and > postfix_lmtp files and calls the configured postmap_command (default > /usr/sbin/postmap) to create the .db files. `mailman start` also > generates these files by default. > > > > > --------------------------------------------------------------------------- > > Second issue: Postgresql authentication. > > PostgreSQL v10.23. > > > --------------------------------------------------------------------------- > > I have this in the active mailman3.cfg file, where xxxxxxxxxx is the > > same complex password in the mailman3 config file: > > url: postgresql://mailman3:xxxxxxxxxx@localhost/mailman3/mailman3 > > > I don't think you should have two /mailman3 at the end > > the form is `postgresql://user:password@host:port/database_name` The > default port is 5432. > > -- > 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://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 keith1christian(a)gmail.com >

9 months, 2 weeks

[MM3-users] Re: Help with fresh debian install

by Mark Sapiro

On 10/3/19 5:17 PM, Mark Dadgar wrote: > > I brought up a fresh install of Mailman3 via the current Debian package alongside my current 2.1 setup (installed and updated from source since 2002) on Ubuntu 18.04 LTS. > > Importing lists from 2.1 has been a real problem. > > I am trying to import a list with no archives to keep it simple while I prove out the process. If I run the mailman import21 comment as my user, I get the following errors: > > — > mark@mail:/tmp$ mailman import21 announce(a)pdc-racing.net ./announce-config.pck > Traceback (most recent call last): > File "/usr/bin/mailman", line 11, in <module> > load_entry_point('mailman==3.1.1', 'console_scripts', 'mailman')() > File "/usr/lib/python3/dist-packages/mailman/bin/mailman.py", line 94, in main > initialize(config_path) > File "/usr/lib/python3/dist-packages/mailman/core/initialize.py", line 189, in initialize > initialize_2(propagate_logs=propagate_logs) > File "/usr/lib/python3/dist-packages/mailman/core/initialize.py", line 152, in initialize_2 > mailman.core.logging.initialize(propagate_logs) > File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 157, in initialize > _init_logger(propagate, sub_name, log, logger_config) > File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 110, in _init_logger > handler = ReopenableFileHandler(sub_name, path_abs) > File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 50, in __init__ > self._stream = self._open() > File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 53, in _open > return codecs.open(self.filename, 'a', 'utf-8') > File "/usr/lib/python3.6/codecs.py", line 897, in open > file = builtins.open(filename, mode, buffering) > PermissionError: [Errno 13] Permission denied: '/var/log/mailman3/mailman.log' This is the issue. I don't know how the Debian packages do this, but I recommend having a 'mailman' user that owns everything and running commands as that user. > Error in atexit._run_exitfuncs: > Traceback (most recent call last): > File "/usr/lib/python3.6/logging/__init__.py", line 1945, in shutdown > h.flush() > File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 56, in flush > if self._stream: > AttributeError: 'ReopenableFileHandler' object has no attribute '_stream' This is due to the prior permissions error. > If I run it as root, it runs for a long time but spews a HUGE stream of these errors to /var/log/mailman3/mailman.log: If there are a lot of members to add, that can take a long time. The current version of import21 has a progress thermometer for this. > — > Oct 03 17:08:48 2019 (19118) Skipping and preserving unparseable message: 1570147727.3029191+80f1cc4d18f54868ad6162e8e41e52567185e983 > Oct 03 17:08:49 2019 (19118) Uncaught runner exception: [Errno 13] Permission denied: '/var/lib/mailman3/queue/virgin/1570147728.618866+174175d39c301feab4ebb2aac0a51226334fa54c.pck' > Oct 03 17:08:49 2019 (19118) Traceback (most recent call last): > File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 156, in _one_iteration > msg, msgdata = self.switchboard.dequeue(filebase) > File "/usr/lib/python3/dist-packages/mailman/core/switchboard.py", line 150, in dequeue > with open(filename, 'rb') as fp: > PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/queue/virgin/1570147728.618866+174175d39c301feab4ebb2aac0a51226334fa54c.pck' First, I don't know what these messages are. Normally import21 doesn't send any mail. I'm guessing it's trying to send 'you are subscribed' notices to the users, but it shouldn't be doing this. All these files should wind up in Mailman's var/queue/bad/ directory with a .psv extension. You should be able to examine them with the 'mailman qfile' command. Whatever they are, the error comes from virgin runner so import21 should have actually succeeded. Did it import the list? > It also dumps some mail footer templates into the template directory that are owned by root, which seems … incorrect? It makes a weak effort at converting the list's msg_footer and digest_footer into MM 3 templates in templates/list/<list-id>/<list-lang>/. These are owned by root in your case because you ran import21 as root. > Any thoughts on what’s going wrong here? It looks like this may be an issue with the Debian package, at least the sending of messages part. As for the rest, the Debian package should install stuff as a Mailman user, perhaps 'mailman' or 'list', and you should be running all commands as that user. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: Subscription request cannot be moderated: 404 Not Found

by Eric Broens

Hi Mark, I can't find any log entry which indicate a problem with this subscription request. The _request table does not contain a request for the specific mailinglist, but I am not sure if subscription requests are included in this table. The token is found in the pended table: +-----+------------------------------------------+---------------------+ | id | token | expiration_date | +-----+------------------------------------------+---------------------+ | 115 | 4d6b4b11266c7332684c5a492eb3f92c531f761b | 2031-01-04 16:17:38 | +-----+------------------------------------------+---------------------+ These are the relevant entries in the pendedkeyvalue table: +------+--------------+-------------------------------------+-----------+ | id | key | value | pended_id | +------+--------------+-------------------------------------+-----------+ | 1130 | type | subscription | 115 | | 1131 | list_id | "********************" | 115 | | 1132 | email | "***********************@*********" | 115 | | 1133 | display_name | "" | 115 | | 1134 | when | "2021-01-06T16:17:38" | 115 | | 1135 | token_owner | "moderator" | 115 | +------+--------------+-------------------------------------+-----------+ Can I workaround this problem for this specific subscriber by adding entries in the _request table, and if so what do I need to add? Thanks in advance, Eric On Friday, January 15, 2021, 11:42:47 PM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote: On 1/14/21 3:43 PM, Eric Broens via Mailman-users wrote: > Hi Mark, > The link that shows the subscription request pending approval is as follows: 'https://<host_url>/postorius/lists/<listname>.<domain>/subscription_requests' > > The link behind the accept button is as follows. 'https://<host_url>/postorius/lists/<listname>.<domain>/handle_subscription_request/4d6b4b11266c7332684c5a492eb3f92c531f761b/accept' > > I have checked if there is already a subscription with that email address, but that's not the case. I don't know why that would 404 unless the token 4d6b4b11266c7332684c5a492eb3f92c531f761b didn't exist, but since it came from a "current" view, it should be good. I have seen occasional issues where two moderators attempt to handle the same request in close succession - i.e. both get the pending request and try to handle it and the second fails because the request is gone, but that appears not to be the case here. You might check the web server logs, the Django log and Mailman's logs to see if there is any more of a clue. -- 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 3 months

[MM3-users] Re: How to identify the exact reason behind the shunting of the mails ?

by Shashikanth Komandoor

Thank you Mark for your immediate response. The below are the tracebacks I could find in the mailman log. *Jun 17 19:04:08 2021 (8642) Uncaught runner exception: sequence item 0: expected str instance, Header foundJun 17 19:04:08 2021 (8642) Traceback (most recent call last): File "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 173, in _one_iteration self._process_one_file(msg, msgdata) File "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 266, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/var/lib/mailman/mailman/src/mailman/runners/pipeline.py", line 37, in _dispose process(mlist, msg, msgdata, pipeline) File "/var/lib/mailman/mailman/src/mailman/core/pipelines.py", line 50, in process handler.process(mlist, msg, msgdata) File "/var/lib/mailman/mailman/src/mailman/handlers/avoid_duplicates.py", line 59, in process addrs = getaddresses(msg.get_all(header, [])) File "/usr/lib64/python3.6/email/utils.py", line 112, in getaddresses all = COMMASPACE.join(fieldvalues)TypeError: sequence item 0: expected str instance, Header foundJun 17 19:04:08 2021 (8642) SHUNTING: 1623936848.367641+4753f8127953071ddcabfe828ebe72fcf04d0ae2* In the shunt file, I see something like this as below in CC while To is good: *Cc: =?unknown-8bit?q?=22Support_Zimbra=22_=3Csupport-zimbra=40nic=2Ein=3E=2C?= =?unknown-8bit?b?ICLgpLbgpLDgpKYg4KSu4KS+4KSl4KWB4KSwIC0gU2hhcmFkIE1hdGh1ciIgPHN1cHBvcnQtdmFqcmFAc3VwcG9ydGdvdi5pbj4s?= =?unknown-8bit?b?ICLgpLDgpL7gpJzgpYfgpLYg4KS44KS/4KSC4KS5IC0gUmFqZXNoIFNpbmdoIiA8cmFqc0BuaWMuaW4+LA==?= =?unknown-8bit?b?ICJTYWJ5YXNhY2hpIENob3VkaHVyeSIgPHNhYnlhQG5pYy5pbj4sIG1haWxhZG1pbkBuaWMuaW4s?= =?unknown-8bit?b?ICJNUklUVU5KQVkgS1VNQVIiIDxta0BuaWMuaW4+LCAiQmhyaWd1IEt1bWFyIiA8YmhyaWd1QG5pYy5pbj4s?= =?unknown-8bit?b?ICJPbSBQcmFrYXNoIiA8b3AubmhxQG5pYy5pbj4sICJIYXJpaGFyYW4gTSIgPGhhcmloYXJhbi5tQGdvdi5pbj4s?= =?unknown-8bit?b?ICJQaGlzaGluZyBQaGlzaGluZyIgPHBoaXNoaW5nQG5pYy5pbj4sICJpbmNpZGVudCIgPGluY2lkZW50QG5pYy5pbj4s?= =?unknown-8bit?b?ICJNYW5hdiBSYWtoZWphIiA8bWFuYXYucmFraGVqYUBuaWMuaW4+?=* Also, I came to know that two of the recipients in CC block have their mail ID display name in their local language. While I am not sure, I doubt if it could be the issue of getting shunted. Please confirm and suggest any solution. On Thu, Jun 17, 2021 at 8:48 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/17/21 6:56 AM, Shashikanth Komandoor wrote: > > > > Is there any chance to find out the reason for shunting of the > > mails through any means ? > > > > > Look in Mailman's var/logs/mailman.log for the tracebacks associated > with the shunted messages. > > -- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

3 years, 10 months

[MM3-users] Re: lmtp runner not starting

by Guillermo Hernandez (Oldno7)

El 1/4/23 a las 21:14, Mark Sapiro escribió: > On 4/1/23 12:00, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> >> El 1/4/23 a las 20:44, Mark Sapiro escribió: >>> ... >>> lmtp runner did not start because at some point it had died and >>> restarting Mailman won't restart a runner that died and was marked >>> to not restart. >>> >>> You need to stop Mailman and make sure when mailman is stopped that >>> there are no files in mailman's var/locks/ directory (remove any >>> that are there) and then start Mailman and lmtp runner should start. >>> >> I stopped mailman and removed all that was in there (there were many >> locked registers). Restarted mailman, and it shows the same error >> that in my previous mail. >> >> Now there is two new locked files, one (master.lck) which its content >> is the name of the other file. And the second one has the same content: >> >> master.lck|www.proteccion-civil.eu|9389|7022761192045613065 > Sorry, I sent my previous mail, and then received this > > Those are the master lock that prevents Mailman core from starting > when it is running. They should not be removed unless Mailman core is > stopped. Everytime I deleted that files I previously have stopped mailman, yes > >> will try deleting the content of var/locks and restarting the server > > If you had completely stopped Mailman core and then started it, lmtp > runner should have started. What are the complete log messages from > mailman.log following the start? > I sent them before > What does `mailman conf -s runner.lmtp` show? > Here it is: root@www:/usr/local/mailman3 # /usr/bin/su -m mailman3 -c "/usr/local/bin/mailman -C /usr/local/mailman3/var/etc/mailman.cfg conf -s runner.lmtp" [runner.lmtp] class: mailman.runners.lmtp.LMTPRunner [runner.lmtp] instances: 1 [runner.lmtp] max_restarts: 10 [runner.lmtp] path: [runner.lmtp] sleep_time: 1s [runner.lmtp] start: yes -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

2 years

[MM3-users] Re: mailman3 does not send to the members of the lists

by Mark Sapiro

On 7/12/20 4:16 PM, maszap(a)tin.it wrote: > Hi > My mail.log > > Jul 13 01:15:12 gamelia postfix/smtpd[1973]: connect from localhost[127.0.0.1] > Jul 13 01:15:12 gamelia postfix/trivial-rewrite[1974]: warning: do not list domain pratico.work in BOTH virtual_mailbox_domains and relay_domains > Jul 13 01:15:12 gamelia postfix/trivial-rewrite[1974]: warning: do not list domain pratico.work in BOTH virtual_mailbox_domains and relay_domains > Jul 13 01:15:12 gamelia postfix/smtpd[1973]: 276C0C202B7: client=localhost[127.0.0.1] > Jul 13 01:15:12 gamelia postfix/cleanup[1975]: 276C0C202B7: message-id=<20200712231512.1546.30031(a)mail.pratico.work> > Jul 13 01:15:12 gamelia opendkim[726]: 276C0C202B7: DKIM-Signature field added (s=mail2020, d=pratico.work) > Jul 13 01:15:12 gamelia postfix/qmgr[1533]: 276C0C202B7: from=<admin(a)pratico.work>, size=586, nrcpt=2 (queue active) > Jul 13 01:15:12 gamelia postfix/smtpd[1973]: disconnect from localhost[127.0.0.1] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 > Jul 13 01:15:12 gamelia postfix/smtpd[1978]: connect from localhost[127.0.0.1] > Jul 13 01:15:12 gamelia postfix/trivial-rewrite[1974]: warning: do not list domain pratico.work in BOTH virtual_mailbox_domains and relay_domains > Jul 13 01:15:12 gamelia postfix/trivial-rewrite[1974]: warning: do not list domain pratico.work in BOTH virtual_mailbox_domains and relay_domains > Jul 13 01:15:12 gamelia postfix/smtpd[1978]: C3A57C20D52: client=localhost[127.0.0.1] > Jul 13 01:15:12 gamelia postfix/trivial-rewrite[1974]: warning: do not list domain pratico.work in BOTH virtual_mailbox_domains and relay_domains > Jul 13 01:15:12 gamelia postfix/cleanup[1975]: C3A57C20D52: message-id=<20200712231512.1546.30031(a)mail.pratico.work> > Jul 13 01:15:12 gamelia opendkim[726]: C3A57C20D52: DKIM-Signature field added (s=mail2020, d=pratico.work) > Jul 13 01:15:12 gamelia postfix/qmgr[1533]: C3A57C20D52: from=<admin(a)pratico.work>, size=1610, nrcpt=2 (queue active) > Jul 13 01:15:12 gamelia postfix/smtpd[1978]: disconnect from localhost[127.0.0.1] ehlo=1 mail=1 rcpt=2 data=1 quit=1 commands=6 > Jul 13 01:15:12 gamelia postfix/trivial-rewrite[1974]: warning: do not list domain pratico.work in BOTH virtual_mailbox_domains and relay_domains > Jul 13 01:15:12 gamelia postfix/trivial-rewrite[1974]: warning: do not list domain pratico.work in BOTH virtual_mailbox_domains and relay_domains > Jul 13 01:15:12 gamelia amavis[1566]: (01566-01) Passed CLEAN {RelayedInbound}, [127.0.0.1]:36322 <admin(a)pratico.work> -> <admin(a)pratico.work>,<info@pratico$ > Jul 13 01:15:12 gamelia postfix/smtp[1976]: 276C0C202B7: to=<admin(a)pratico.work>, orig_to=<max(a)pratico.work>, relay=127.0.0.1[127.0.0.1]:10024, delay=0.76, $ > Jul 13 01:15:12 gamelia postfix/smtp[1976]: 276C0C202B7: to=<info(a)pratico.work>, orig_to=<max(a)pratico.work>, relay=127.0.0.1[127.0.0.1]:10024, delay=0.76, d$ > Jul 13 01:15:12 gamelia postfix/qmgr[1533]: 276C0C202B7: removed > Jul 13 01:15:12 gamelia dovecot: lmtp(1980): Connect from local > Jul 13 01:15:12 gamelia dovecot: lmtp(admin(a)pratico.work)<1980><wZyjNoCZC1+8BwAA0Fextg>: sieve: msgid=<20200712231512.1546.30031(a)mail.pratico.work>: stored $ > Jul 13 01:15:12 gamelia dovecot: lmtp(info(a)pratico.work)<1980><wZyjNoCZC1+8BwAA0Fextg:2>: sieve: msgid=<20200712231512.1546.30031(a)mail.pratico.work>: stored$ > Jul 13 01:15:12 gamelia postfix/lmtp[1979]: C3A57C20D52: to=<admin(a)pratico.work>, relay=mail.pratico.work[private/dovecot-lmtp], delay=0.13, delays=0.09/0.0$ > Jul 13 01:15:12 gamelia postfix/lmtp[1979]: C3A57C20D52: to=<info(a)pratico.work>, relay=mail.pratico.work[private/dovecot-lmtp], delay=0.13, delays=0.09/0.01$ > Jul 13 01:15:12 gamelia postfix/qmgr[1533]: C3A57C20D52: removed > Jul 13 01:15:12 gamelia dovecot: lmtp(1980): Disconnect from local: Client has quit the connection (state=READY) > Jul 13 01:15:16 gamelia dovecot: imap-login: Login: user=<admin(a)pratico.work>, method=PLAIN, rip=173.249.18.220, lip=173.249.18.220, mpid=1983, TLS, session$ > Jul 13 01:15:16 gamelia dovecot: imap(admin(a)pratico.work)<1983><IiFCv0aqJoyt+RLc>: Logged out in=297 out=5915 deleted=0 expunged=0 trashed=0 hdr_count=11 hd$ The issue here is the message is being delivered to Dovecot via LMTP rather than to Mailman via LMTP. See this thread <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>. > sudo mailman conf -s logging.smtp > > [logging.smtp] datefmt: %b %d %H:%M:%S %Y > [logging.smtp] every: $msgid smtp to $listname for $recip recips, completed in $time seconds > [logging.smtp] failure: $msgid delivery to $recip failed with code $smtpcode, $smtpmsg > [logging.smtp] format: %(asctime)s (%(process)d) %(message)s > [logging.smtp] level: info > [logging.smtp] path: smtp.log > [logging.smtp] propagate: no > [logging.smtp] refused: $msgid post to $listname from $sender, $size bytes, $refused failures > [logging.smtp] success: $msgid post to $listname from $sender, $size bytes With these settings, posts should be logged. They aren't because no mail is delivered to Mailman at all. The Mail that local users receive doesn't come from the list. It comes from Dovecot. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 9 months

[MM3-users] Re: Single-Sign-out for List member

by Abhilash Raj

On Thu, Aug 13, 2020, at 10:04 AM, Mark Sapiro wrote: > On 8/13/20 6:21 AM, w.schoener(a)alp.dillingen.de wrote: > > > > So I would like to ad a link in the footer of every message, with which every receiver/member can sign out of the newsletter with one click. > > It does not seam to be possible, to put this into effect with mailman 3. > > Does anybody have any hints, how to create a link, and when this link is called, the user is signed out of the newsletter. > > > You can set the list's unsubscription_policy to open and set the link as > a mailto: to the list-leave address, but that still requires a second > click to send the mail. > > The solution is to create a web based CGI script which is called with a > URL like > <https://example.com/unsub_script/list.example.com/user@example.net> and > have that script invoke the appropriate `mailman` command to remove the > member from the list. Beginning with Mailman 3.3.2, this would be If this is one-click, can't this URL be hit by anyone trying to remove the user from any MailingList without any auth or anything? > > mailman delmembers -l list.example.com -m user(a)example.net -g > > to remove the member and send a goodbye message. In older Mailman, it > would be something like > > echo user(a)example.net | mailman members -x - list.example.com > > I understand you may have a legal requirement do do this, but these > "one-click - no user confirmation" links are a bad idea because usera > will reply to a list post or forward it and not remove the link and > userb will receive usera's reply and click usera's unsubscribe link > either maliciously or thinking it will unsubscribe userb. > > -- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

4 years, 8 months

[MM3-users] Re: Edit archived email? Is it possible?

by Prasanth Nair

Hi Mark, Thank you for your help. Let me try this. Kind regards, Prasanth On Tue, 28 Sept 2021 at 18:03, Mark Sapiro <mark(a)msapiro.net> wrote: > On 9/28/21 6:02 AM, Prasanth Nair wrote: > > Hello, > > > > Does anyone know how to edit an archived email in Mailman3? It is > possible > > in Mailman2 ( > > > https://wiki.list.org/DOC/How%20do%20I%20edit%20the%20archives%20of%20a%20M… > ). > > Is there any option similar to this in Mailman3? > > > In some sense the process is the same but possibly even simpler in > Mailman 3. You need to modify the underlying data which requires > appropriate access to the server. > > In Mailman 3, the data are in the hyperkitty_email table in Mailman's > database. You can get the Message-ID hash from the URL to the archived > message, e.g. for the message to which I'm replying, the URL is > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > and the hash is 7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA. Then if you have > access, you can do database queries like > ``` > SELECT subject, content FROM hyperkitty_email WHERE message_id_hash = > '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; > ``` > and > ``` > UPDATE hyperkitty_email SET content = '<new content>' WHERE > message_id_hash = '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; > UPDATE hyperkitty_email SET subject = '<new subject>' WHERE > message_id_hash = '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; > ``` > If the message has attachments, they are in the hyperkitty_attachment > table and can be referenced by `email_id` which is the corresponding > `id` from the hyperkitty_email entry. > > You can also do similar things via `django-admin shell`. E.g. > ``` > $ django-admin shell > Python ... > (InteractiveConsole) > >>> from hyperkitty.models.email import Email > >>> x = > Email.objects.filter(message_id_hash='7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA') > >>> print(x[0].content) > ``` > but this requires some knowledge of HyperKitty's models and Django's ORM. > > -- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

3 years, 6 months

[MM3-users] Re: What to backup?

by Alain Kohli

Thank you, that's perfect! For anyone that might stumble upon this, I had to make two minor adjustments to automate it. import os msg_ids = {} lm = getUtility(IListManager) ms = getUtility(IMessageStore) for mlistin lm.mailing_lists: requestdb = IListRequests(mlist) for rqin requestdb.held_requests: key, msgdata = requestdb.get_request(rq.id) if msgdata['_request_type'] !='held_message': continue msg = ms.get_message_by_id(key) msg_ids[(msg['Message-ID-Hash'])] =True for root, dirs, filesin os.walk('/docker/var/messages'): for filein files: if not msg_ids.get(file, False): msg = ms.get_message_by_hash(file) # It happened to me that msg was 'None' if msg: ms.delete_message(msg['Message-ID']) # I couldn't run it with '--run' and if you pipe it into 'mailman shell' # I needed this or the loop above wouldn't execute. pass On 5/27/19 6:22 AM, Mark Sapiro wrote: > On 5/26/19 3:07 PM, Mark Sapiro wrote: >> You could modify the above to write the list to a file and then wrap the >> whole thing in a shell script which would make the list and then do >> something like >> >> for f in `find var/messages -type f`;do >> n=`cut -d / -f5 <<<$f` >> for keep in `cat list` ;do >> k=0 >> if [ $n == $keep ] ;then >> k=1 >> break >> fi >> done >> if [ $k -eq 0 ]; then >> rm $f >> fi >> done > Actually, I thought about it a bit more, and I decided that arcane shell > script was a bit obscure and it would be easier to just do it in Python. > Plus, you can properly delete the message that way. > > A complete script for `mailman shell` is like > > import os > msg_ids = {} > lm = getUtility(IListManager) > ms = getUtility(IMessageStore) > for mlist in lm.mailing_lists: > requestdb = IListRequests(mlist) > for rq in requestdb.held_requests: > key, msgdata = requestdb.get_request(rq.id) > if msgdata['_request_type'] != 'held_message': > continue > msg = ms.get_message_by_id(key) > msg_ids[(msg['Message-ID-Hash'])] = True > > for root, dirs, files in os.walk('path/to/var/messages'): > for file in files: > if not msg_ids.get(file, False): > msg = ms.get_message_by_hash(file) > ms.delete_message(msg['Message-ID']) > >

5 years, 10 months

[MM3-users] Re: [EXTERNAL] Re: Database deadlock when trying to delete a member.

by Simon Coggins

Thanks I’ll give that a try. Also in my tracing of the code I noticed https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/interfaces/dat… it starts with a single quote and ends with triple quotes so the single quote is never terminated. -Simon From: Mark Sapiro <mark(a)msapiro.net> Date: Wednesday, 24 March 2021 at 4:10 am To: "mailman-users(a)mailman3.org" <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: [EXTERNAL] Re: Database deadlock when trying to delete a member. On 3/22/21 9:53 PM, Simon Coggins wrote: > Ok after bit tracking I’ve worked out that the bouncer is dangling transactions when it’s sending warning messages. When https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py…<https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py…> is called and it get to update last_warn_sent it does the following in the DB: > > 2021-03-23 14:42:50.622 AEST [11693] LOG: statement: UPDATE member SET last_warning_sent='2021-03-23T04:42:50.622015'::timestamp, total_warnings_sent=1 WHERE member.id = 169331 > > But it never COMMITs this transaction. So all write operations are now hung waiting for the transction to be closed as the member record has been modified. As a test I added config.db.commit() after https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py…<https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py…> and restarted. And my mailman syncmembers worked perfectly and I didn’t have any hangs it correctly removed everyone it should have. In the database logs I can see the COMMIT. > > I’m pretty sure this is not the right spot for a config.db.commit() but hopefully this helps point to what might be going wrong. Thank you for all the research on this. It is extremely helpful. Instead of adding a commit after line 277 please try adding the @transactional decorator to the send_warnings_and_remove method at line 210 @transactional @dbconnection def send_warnings_and_remove(self, store): I think that is the proper fix. Let us know if that works. -- 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org>

4 years, 1 month

[MM3-users] Re: (Custom) Plugins: Proper file path(s) for adding a handler?

by Thomas Ward

I was able to instantiate the class AND get the expected three objects from it - pre_hook, post_hook, and resource. >>> from mailman_customizations.hooks import MailmanCustomizations >>> instance = MailmanCustomizations() >>> dir(instance) ['__class__', '__delattr__', '__dict__', '__dir__', '__doc__', '__eq__', '__format__', '__ge__', '__getattribute__', '__gt__', '__hash__', '__implemented__', '__init__', '__init_subclass__', '__le__', '__lt__', '__module__', '__ne__', '__new__', '__providedBy__', '__provides__', '__reduce__', '__reduce_ex__', '__repr__', '__setattr__', '__sizeof__', '__str__', '__subclasshook__', '__weakref__', 'post_hook', 'pre_hook', 'resource'] I know Abhilash Raj is probably well versed in this from statements made elsewhere, so I've added them in the CC field. Abhilash Raj, any ideas? Thomas -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, October 24, 2023 10:36 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: (Custom) Plugins: Proper file path(s) for adding a handler? On 10/24/23 3:56 PM, Thomas Ward via Mailman-users wrote: > > When I DO NOT have the module loaded in the configuration, `mailman > shell` works. Since that was functional, I went into the shell and > executed this: > > > from mailman_customizations.hooks import MailmanCustomizations > > This worked fine, but obviously importing the class doesn't > necessarily > *activate* the class. So something is up with how I'm *supposed* to > activate the plugin in the config, and we know that it's visible to > Mailman in its shell, but it can't autoload it. I'm past the limit of my knowledge here and only stabbing in the dark, but what happens after you import it. Can you instantiate it, e.g. ``` instance = MailmanCustomizations() dir(instance) ``` I'm not saying this should succeed, just that it may possibly provide useful information. -- 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://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 teward(a)thomas-ward.net

1 year, 5 months

[MM3-users] Re: digests are created but not sent out

by "Jörg M. Schulz"

when I use the lines below, the templates are looked for in //var. When I comment them out, the location is correct: /var/lib/mailman3/ (debian buster standard) . The user list has full access. The folder is empty. See mailman.cfg: [mailman] # This address is the "site owner" address. Certain messages which must be # delivered to a human, but which can't be delivered to a list owner (e.g. a # bounce from a list owner), will be sent to this address. It should point to # a human. site_owner: help(a)elternserver.de # This is the local-part of an email address used in the From field whenever a # message comes from some entity to which there is no natural reply recipient. # Mailman will append '@' and the host name of the list involved. This # address must not bounce and it must not point to a Mailman process. noreply_address: noreply # The default language for this server. default_language: en [language.en] charset: utf-8 enabled: yes [language.de] description: German charset: iso-8859-1 enabled: yes > Am 09.01.2019 um 21:12 schrieb Mark Sapiro <mark(a)msapiro.net>: > > On 1/9/19 12:02 PM, "Jörg M. Schulz" wrote: >> start fails when I use >> >> >> # The default language for this server. >> default_language: en >> [language.en] >> charset: utf-8 >> enabled: yes >> >> when I comment out the lines above, mailman starts. > > > And in what section is this put? I.e. if the last preceding section > header is not [mailman], the default_language: en is in a section where > it doesn't belong. > > Or are you saying that you had set the server default_language to > something other than 'en' and the above is intended to change it to > 'en'. In that case, look at var/templates/en and ensure it and > subordinates are user:group list:list > > -- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

6 years, 3 months

[MM3-users] Re: Disabled by bounce

by Allan Hansen

Mark, I can see your argument here, but if a 'Disabled by bounce' subscription is enabled, it would require just looking at that particular subscription and set the bounce count to 0, so that the next bounce (before staleness) does not disable it again. __ Yours, Allan On 2/2/23, 13:44, "Mark Sapiro" <mark(a)msapiro.net> wrote: On 2/2/23 04:54, Danil Smirnov wrote: > Hi Mark > > On Wed, Feb 1, 2023 at 9:28 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> Yes and no. If 'Bounce info stale after' is set to 3d and no bounces for >> a user are received in a 3 day period, the user's bounce score is not >> immediately reset, but it will be reset (to 1) the next time a bounce is >> received for the user. I.e., it is effectively the same thing unless you >> are looking at the user's bounce score which doesn't change until the >> next bounce. >> > > Isn't this a bug? We are now showing users' bounce scores on the Members > page and this would be misleading. Is it difficult from internals > perspective to have the bounce score reset immediately? Yes, it is not difficult, but it's a lot of processing. It would require something like a task runner task to periodically look at each row in the member table and if the bounce score is > 0, find the associated list's bounce_info_stale_after and if last_bounce_received + bounce_info_stale_after < now, reset the score. Consider a site like mail.python.org that at this moment has 79024 rows in the member table and 7531 of those have bounce_score > 0. That's a lot of processing, and is it really an issue to show a non-zero bounce score that's stale? -- 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: mailman-users(a)mailman3.org <https://lists.mailman3.org/archives/list/<a href=>/message/ERW6LLR3VIJHUS5ECDA7A2P53WD7ZZEB/">https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to hansen(a)rc.org

2 years, 2 months

[MM3-users] Re: digests are created but not sent out

by "Jörg M. Schulz"

When I remove the offending special character from the footer, digests are sent out perfectly. So, for international use, we have to wait for the language template system to be ready … By the way: Thank you for your continuing work with this marvellous piece of software. > Am 09.01.2019 um 19:16 schrieb Mark Sapiro <mark(a)msapiro.net>: > > On 1/9/19 9:33 AM, "Jörg M. Schulz" wrote: >> But, also in mailman log. >> Uncaught runner exception: 'ascii' codec can't encode character '\xdf' in position 157: ordinal not in range(128) >> Jan 09 12:24:06 2019 (17491) Traceback (most recent call last): >> File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 173, in _one_iteration >> self._process_one_file(msg, msgdata) >> File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 266, in _process_one_file >> keepqueued = self._dispose(mlist, msg, msgdata) >> File "/usr/lib/python3/dist-packages/mailman/runners/digest.py", line 324, in _dispose >> mime = mime_digest.finish() >> File "/usr/lib/python3/dist-packages/mailman/runners/digest.py", line 185, in finish >> footer = MIMEText(footer_text.encode(self._charset), >> so the footers may not contain special characters. >> Will review this one. > > > in the above, self._charset is the character set of the lists > preferred_language. The footer can't contain characters not in the > character set of the list's preferred_language. For English (en) this is > us-ascii. For German (de) it is iso-8859-1. These are artifacts from > Mailman 2.1 > > You can change this for English by putting > > [language.en] > charset: utf-8 > > in your mailman.cfg. This works because us-ascii is a proper subset of > utf-8. > > For other languages, a change like this might require recoding of > templates and/or a message catalog, but since we don't currently ship > any non-English templates or message catalogs, that is moot at the moment. > > -- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

6 years, 3 months

[MM3-users] Re: Hyperkitty on Debian 12

by Markus Grandpré

Dear Mr Sapiro, thank you very much for your help. The required command is: # mailman-web hyperkitty_import \ -l mailman21-migration-test-04(a)mailman.uni-konstanz.de \ /var/mailman21/testlist.mbox Due to the following warnings, I still have to customize Hyperkitty: django_mailman3.MailDomain: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the DjangoMailman3Config.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. ... Can you give me another hint? As Linux admin I installed the packages mailman and mailman-web that were offered to me under Debian 12. Although during the installation of the packages user "list" was created, I cannot use it: # su - list This account is currently not available As with Mailman 2.1, I will probably have to continue working with Mailman3 as root. Too bad that there is no documentation for Debian admins like me, who don't want to dive too deep into the python framework. Or have I overlooked something? Best regards, Markus Am 25.03.24 um 18:56 schrieb Mark Sapiro: > On 3/25/24 07:58, Markus Grandpre wrote: >> Dear list members, >> >> when following the instructions to migrate list archives from >> Mailman21 to Mailman3 (see [1]), I face the following problem: >> >> # python3 manage.py hyperkitty_import -l mailman21-migration-test-04 >> /var/mailman21/testlist.mbox >> python3: can't open file '/var/mailman21/manage.py': [Errno 2] No such >> file or directory >> >> and have no clue, where to find the right <manage.py> file. The command > > > This depends on how you installed Mailman 3. You may or may not want > `python3 manage.py` at all. The required command could be something like > `django-admin` or `mailman-web`. > > Also the `#` prompt indicates you may be running as root. Mailman > related commands should be run as the Mailman user (could be `mailman` > or `list` or ... depending again on how you installed Mailman). Running > as root can create files owned by root that later can't be read by the > Mailman user. > -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342

1 year

[MM3-users] Re: config incoming email in my domain cpanel

by Rafael Mora

Hello Mark, Ok I Will ask hostgator if they provide mailman. Thank you very much for all your help! On Thu, Aug 3, 2017, 18:12 Mark Sapiro <mark(a)msapiro.net> wrote: > On 08/03/2017 02:14 PM, Rafael Mora wrote: > > El jue., 3 ago. 2017 a las 16:07, tlhackque via Mailman-users (< > > mailman-users(a)mailman3.org>) escribió: > > > >> You've said you're working with labbrands.com. > >> > >> labbrands.com has address 192.185.51.89 > >> mail.labbrands.com has address 192.185.51.89 > >> www.labbrands.com is an alias for labbrands.com. > >> > >> telnet proves that Exim is running on that IP address. Either you're > >> running it, or hostgator is redirecting the SMTP ports. > >> > >> You added: > >> lists.labbrands.com has address 190.145.27.66 > >> > >> Presumably that's a different machine. > >> > >> So that now needs an MX record, and a firewall routing. > > > > > > I added the MX record on our hostgator hosting like this: > > [image: image.png] > > > > Is it correct??? > > > Your screen shot, along with the excessive quoting, only caused your > post to be "too big". > > All the screen shot says is you have two MX records. The higher > priority, 0, is mail.labbrands.com and the lower priority , 1, is > lists.labbrands.com. > > What this means is mail to the domain will be delivered to > mail.labbrands.com unless that server is somehow unreachable in which > case lists.labbrands.com will be tried. > > This is probably not what you want. > > I hate to say this at this point, but you are on a cPanel host. cPanel > provides a functional Mailman 2.1 service. You might save yourself a lot > of grief by just using that. > > -- > 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/ > -- Atentamente / Best Regards Ing. Rafael Mora

7 years, 8 months

[MM3-users] Re: Please help - Held message is crashing mailman.

by Mark Sapiro

On 4/5/19 10:27 PM, Alex King via Mailman-users wrote: > Hi, > > I've used mailman a lot in the past, and decided to install mailman3 in > a recent install. I'm unimpressed so far, it seems buggy. > > Running on Ubuntu 18.04.2 LTS from packages, mailman3 3.1.1-9, > mailman3-web 0+20170523-14, python-django-postorius 1.1.2-3. > > After a few messages, I now can't go to the "Held Messages" in > postorius, I get a 500 error. > > I tried to interact on the command line, but could not work out how. > Reading > https://mailman.readthedocs.io/en/latest/src/mailman/docs/install.html > and > https://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/shell.ht…, > I tried: > > # mailman shell > Welcome to the GNU Mailman shell > >>>> command = cli('mailman.commands.cli_withlist.shell') > Traceback (most recent call last): > File "/usr/lib/python3.6/code.py", line 91, in runcode > exec(code, self.locals) > File "<console>", line 1, in <module> > NameError: name 'cli' is not defined > > I did a lot of reading of the manual and googled, but I have no idea > where the cli object is supposed to come from.....? The documentation > is confusing. The line command = cli('mailman.commands.cli_withlist.shell') in <https://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/shell.ht…> is dependent upon some behind the scenes setup to make the doctests work. Granted this is confusing, but basically all that does is set things up for the doctests to run the 'mailman shell' command. It is not intended to be run from within 'mailman shell'. > Anyway, after some trial and error, i found: > > # mailman shell > Welcome to the GNU Mailman shell >>>> list_manager = getUtility(IListManager) >>>> m=list_manager.get("committee(a)[redacted].org") >>>> from mailman.interfaces.requests import IListRequests >>>> requests = IListRequests(m) >>>> [x for x in requests.held_requests][0].id > 8 >>>> requests.get_request(8) > Traceback (most recent call last): > File "/usr/lib/python3.6/code.py", line 91, in runcode > exec(code, self.locals) > File "<console>", line 1, in <module> > File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", > line 85, in wrapper > return function(args[0], config.db.store, *args[1:], **kws) > File "/usr/lib/python3/dist-packages/mailman/model/requests.py", line > 120, in get_request > result.data_hash, expunge=False) > File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", > line 85, in wrapper > return function(args[0], config.db.store, *args[1:], **kws) > File "/usr/lib/python3/dist-packages/mailman/model/pending.py", line > 138, in confirm > value = json.loads(keyvalue.value) > File "/usr/lib/python3.6/json/__init__.py", line 354, in loads > return _default_decoder.decode(s) > File "/usr/lib/python3.6/json/decoder.py", line 339, in decode > obj, end = self.raw_decode(s, idx=_w(s, 0).end()) > File "/usr/lib/python3.6/json/decoder.py", line 355, in raw_decode > obj, end = self.scan_once(s, idx) > json.decoder.JSONDecodeError: Unterminated string starting at: line 1 > column 1 (char 0) > > It seems something was written out to disk that can't be read in for > some reason (assuming a json object on disk?) This is <https://gitlab.com/mailman/mailman/issues/385> which should be fixed by <https://gitlab.com/mailman/mailman/merge_requests/333>. The fix in in Mailman core version 3.2.0 > How do I debug this further? How do I find the json being decoded? Any > help would be appreciated. (I found mailman2 just worked, I was happy > with that.) The issue is in storing a pickled representation of the json encoding of 'rule_misses'. This gets very long if you have lots of header filters, and with at least the mysql backend gets truncated in the database which causes the Unterminated string error. I'm not sure what your options are for upgrading. The current Debian packages are all >= 3.2.0 [1], but Ubuntu doesn't get 3.2.0 until cosmic (18.10) [2]. [1] https://packages.debian.org/search?keywords=mailman3 [2] https://packages.ubuntu.com/search?keywords=mailman3 > (My colleague posted a bug about this I believe but I don't have the > link to that.) I haven't seen it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

[MM3-users] Re: [EXTERNAL] Re: Database deadlock when trying to delete a member.

by Simon Coggins

I’ve been running with this change as you suggested for a few weeks now in our test environment and I’ve not hit any issues. So this fixes my problem. Will this change be added to mailman core or should I look at manually patching during my upgrades? -Simon From: Mark Sapiro <mark(a)msapiro.net> Date: Wednesday, 24 March 2021 at 4:10 am To: "mailman-users(a)mailman3.org" <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: [EXTERNAL] Re: Database deadlock when trying to delete a member. On 3/22/21 9:53 PM, Simon Coggins wrote: > Ok after bit tracking I’ve worked out that the bouncer is dangling transactions when it’s sending warning messages. When https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py…<https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py…> is called and it get to update last_warn_sent it does the following in the DB: > > 2021-03-23 14:42:50.622 AEST [11693] LOG: statement: UPDATE member SET last_warning_sent='2021-03-23T04:42:50.622015'::timestamp, total_warnings_sent=1 WHERE member.id = 169331 > > But it never COMMITs this transaction. So all write operations are now hung waiting for the transction to be closed as the member record has been modified. As a test I added config.db.commit() after https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py…<https://gitlab.com/mailman/mailman/-/blob/3.3.4/src/mailman/model/bounce.py…> and restarted. And my mailman syncmembers worked perfectly and I didn’t have any hangs it correctly removed everyone it should have. In the database logs I can see the COMMIT. > > I’m pretty sure this is not the right spot for a config.db.commit() but hopefully this helps point to what might be going wrong. Thank you for all the research on this. It is extremely helpful. Instead of adding a commit after line 277 please try adding the @transactional decorator to the send_warnings_and_remove method at line 210 @transactional @dbconnection def send_warnings_and_remove(self, store): I think that is the proper fix. Let us know if that works. -- 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org>

4 years

[MM3-users] Re: Single-Sign-out for List member

by Abhilash Raj

On Thu, Aug 13, 2020, at 10:04 AM, Mark Sapiro wrote: > On 8/13/20 6:21 AM, w.schoener(a)alp.dillingen.de wrote: > > > > So I would like to ad a link in the footer of every message, with which every receiver/member can sign out of the newsletter with one click. > > It does not seam to be possible, to put this into effect with mailman 3. > > Does anybody have any hints, how to create a link, and when this link is called, the user is signed out of the newsletter. > > > You can set the list's unsubscription_policy to open and set the link as > a mailto: to the list-leave address, but that still requires a second > click to send the mail. > > The solution is to create a web based CGI script which is called with a > URL like > <https://example.com/unsub_script/list.example.com/user@example.net> and > have that script invoke the appropriate `mailman` command to remove the > member from the list. Beginning with Mailman 3.3.2, this would be > > mailman delmembers -l list.example.com -m user(a)example.net -g > > to remove the member and send a goodbye message. In older Mailman, it > would be something like > > echo user(a)example.net | mailman members -x - list.example.com > > I understand you may have a legal requirement do do this, but these > "one-click - no user confirmation" links are a bad idea because usera > will reply to a list post or forward it and not remove the link and > userb will receive usera's reply and click usera's unsubscribe link > either maliciously or thinking it will unsubscribe userb. There is also the issue that these days some Mail clients will try to create a preview of all the URLs if they can and it would inadvertently GET the URL resulting in the un-subscription. > > -- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

4 years, 8 months

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Onyeibo Oku

On Wed, 12 Oct 2022 17:52:47 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: Thanks Eggert and Sapiro. > > As Eggert suggests, see > https://docs.mailman3.org/en/latest/install/virtualenv.html and > follow that. I already started out on the above route. Its an adaptation because I am running Fedora. I had no problem with system-wide installations via dnf package management. However, some parts of the documentation does not add up. > You don't need to download the source from GitLab. > Following that doc will get the latest releases from PyPI via pip. > Those are still somewhat out of date - we really should make new > releases - so if you want the latest from GitLab, there are a couple > of ways to do it. Perhaps the easiest is to just run the various `pip > install` commands as documented and then upgrade Mailman core in your > venv with ``` > pip install --upgrade git+https://gitlab.com/mailman/mailman@master > ``` > and update the various mailman web packages with > ``` > pip install --upgrade git+https://gitlab.com/mailman/xxx@master > ``` > where xxx is mailman-web, mailman-hyperkitty, django-mailman3, > postorius, hyperkitty. I.e., run it 5 times, once for each value of > xxx. > I will come to this eventually (assuming that does not break things later). I aim to get it all working with regular pip packages first. I have installed mailman core already. Fedora expects mailman files to reside at /usr/lib/mailman. It appears to ship with a mailman unix user. I adapted to those system defaults. Now I observe that "su - mailman" gives me the proper prompt but .bashrc doesn't kick in. I still have to manually change to the virtual environment despite setting the automatic change in .bashrc. However, "su mailman" runs .bashrc but the prompt says "bash X.XX $". Is this normal? Subsequent parts of the doc show the path "/opt/mailman/mm/var/*" which should correspond to "/usr/lib/mailman/mm/var/*" on my instance. However, I don't see any instructions on how to get the "/mm" folder and the associated sub-folders. I just have "/usr/lib/mailman" I am lost "pip list" within the venv environment confirms that I have "mailman 3.3.5". What am I missing? Regards Onyeibo

2 years, 6 months

[MM3-users] Re: How to fix lists with characters errors?

by Helio Loureiro

Hi, it is python 3.10. Problem is... some mailing lists were created long ago, with python2 something. Most probably 2.5. And the tables on mysql were set to latin1. That I know. Question now is how to fix this. Any suggestion? What is the table? I probably can run some script for these specific lists that have the failure, import data as latim-1, and update back to the table as utf-8. Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro On Fri, 22 Mar 2024 at 20:53, Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/22/24 05:37, Helio Loureiro wrote: > > Hi, > > > > I just found several lists have the issue like this regarding charset: > > > > (venv) mailman@new-mailman3 ~ (v3.1.1)> mailman members > ... > > Traceback (most recent call last): > ... > > line 109, in display_members > > print(f'{address.display_name} <{address.original_email}>', > > UnicodeEncodeError: 'latin-1' codec can't encode character '\u0142' in > > position 9: ordinal not in range(256) > > > There is something in your python that has set the encoding for stdout > to latin1 instead of the default utf-8. E.g. > ``` > $ python3.10 > Python 3.10.9 (main, Dec 11 2022, 12:59:24) [GCC 9.4.0] on linux > Type "help", "copyright", "credits" or "license" for more information. > >>> name = 'abc\u0142def' > >>> print (f'{name}') > abcłdef > >>> import sys > >>> sys.stdout.reconfigure(encoding='latin1') > >>> print (f'{name}') > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > UnicodeEncodeError: 'latin-1' codec can't encode character '\u0142' in > position 3: ordinal not in range(256) > >>> > ``` > > -- > 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://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 helio(a)loureiro.eng.br >

1 year, 1 month

[MM3-users] Re: Speed/progress of update_index_one_list?

by Philip Colmer

We've now completed the indexing of our lists, some of which are quite large (100K+ messages per list). I wanted to share our findings of using Xapian to do this. Firstly, using "-v 2", e.g. "mailman-web update_index_one_list -v 2 <email address>", causes the command to print out the progress being made in batches of 1,000 messages. Secondly, Xapian is single-threaded. It only allows one writer at a time. Therefore, we focussed on speed of the hard drives and, on the advice received from the Xapian list, memory. Since we were using AWS EC2 with EBS storage, I elected to move the EBS storage from gp2 to gp3 - which has a higher base I/O figure - and I selected a r6i.8xlarge as this guaranteed 10Gb throughput to the EBS storage. It also delivered 32 vCPU and 256GB RAM. It was possibly overkill but it did the job (see below) and we've now switched back to a t3a.xlarge. Speed-wise, with the above configuration, the system indexed a list of nearly 85K messages in 46 minutes. I hope that is helpful information to anyone else who finds themselves migrating large Mailman 2 archives. Regards Philip On Fri, 14 Jan 2022 at 17:33, Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/14/22 12:38 AM, Philip Colmer wrote: > > I have now switched to Xapian but, in a way, my original questions still > > stand. Is there a way of monitoring the progress of > > "update_index_one_list"? What can I do to the specification of the server > > to make that process go (much) faster? > > > > HyperKitty does the indexing by calling the Haystack update_index > command. See > > https://django-haystack.readthedocs.io/en/master/management_commands.html#u… > > This command has options such as --verbosity and --workers. I think > verbosity is set from the option provided to update_index_one_list and > if set to 2 will give some progress info. > > workers could increase parallelism but is unconditionally passed by > hyperkitty as 0 > > > -- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

3 years, 3 months

[MM3-users] Re: Another interesting error...

by Darren Smith

OK chalk another one up to a python newbie... commit() was the magic sauce that we needed. The error 500 is no longer happening on that mailing list. We have three different lists so far that have gotten into this state, and we are going to work on the other two to make sure that this all works. FYI if this is fixed somehow in a later release (later than 3.1.0) we are working on migrating to the latest mailman code. -Darren On Mon, Apr 23, 2018 at 4:20 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 04/23/2018 02:59 PM, Darren Smith wrote: > > Well, using the mailman shell we were able to find the request that was > > causing the problem - it was apparently a spam message that had some > > chinese characters in it. > > > I am trying to duplicate this issue in a test environment. I can create > a message with an invalid RFC 2047 encoded subject, i.e., > > Subject: =?gb2312?Q?=ff=fe=de=21=a2?= > > and send it to a list where it gets held, but I don't get a 500 in > postorius and I see the held message with a raw (not decoded) header. > > I think there were some recent changes that affect this. I'll look some > more. > > > > We used the shell to delete the held request... > > > > And postorius is still giving me an error 500. > > > > If I'm not mistaken the held messages are kept in .pck files - do you > know > > if when postorius asks for held messages through the API, does mailman go > > to the database or to the .pck? I would actually suspect the latter, or > > removing the request should have fixed the problem. > > > They were held in .pck files in Mailman 2.1, but not in Mailman 3. They > should just be in the database and deleting them via mailman shell > should delete them as long as you quit the shell or commit(). > > -- > 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/ >

7 years

[MM3-users] Re: hyperkitty.lib.utils Failed to update the fulltext index

by Abhilash Raj

On Wed, Apr 17, 2019, at 8:18 AM, Mark Sapiro wrote: > On 4/17/19 8:10 AM, Abhilash Raj wrote: > > On Wed, Apr 17, 2019, at 8:06 AM, Ben Harris wrote: > >> April 17, 2019 11:03 AM, "Abhilash Raj" <maxking(a)asynchronous.in> wrote: > >>> > >>> Which version of Hyperkitty are you using? > >>> > >>> Did you upgrade the version of Hyperkitty when you migrated to the > >>> new host? > >> > >> I'm using the mailman3-full package in ubuntu (i'm aware it's behind a couple > >> releases), so it's hyperkitty 1.1.4. > >> > >> I didn't upgrade anything with the move. > > > > I am not sure where does Debian packaged version store it's fulltext index, but > > I am assuming the move somehow makes Hyperkitty not be able to read the > > index. > > > I think this is a known incompatibility between the Python 2.7 and > Python 3 versions of Whoosh. I *think* 1.1.x releases were based on Python 2.7, so that part looks right to me. > > From the tracebacks, the current HyperKitty is running under Python 2.7. > If the prior server was running HyperKitty with Python 3, that would > explain this. Given that 1.1.x supports only 2.7 and Ubuntu doesn't have 1.2 release, it is unlikely Python 3 was used. > > > Can you try removing and re-building the entire index? I don't know again > > the right command for Django there, but the hyperkitty command you want > > to run is called `rebuild_index`. For source package, something like: > > > > $ python manage.py rebuild_index > > > > Do note that this will take a lot of time if you have a big archive. > > > If this is the incompatibility, rebuilding the index will fix it. > > -- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

6 years

[MM3-users] Re: including a template failed

by Wolfgang Bock

Dear Mark, Q: Can you get https://webmail.domain-02.de/mailman3/postorius/api/templates/list/mylist.li sts.domain-03.de/list:member:regular:footer on the Mailman machine? A: No Q: What is your setting for POSTORIUS_TEMPLATE_BASE_URL? A: was: POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost/mailman3/' Changed it to: POSTORIUS_TEMPLATE_BASE_URL = 'https://localhost/mailman3/' Now another problem occurs: Sep 23 22:51:34 2020 (13492) Cannot connect to SMTP server localhost on port 25 HTTPSConnectionPool ... 'localhost' doesn't match either of 'blog.domain-04.de', 'lists.domain-04.de', 'mail.domain-04.de', 'domain-04.de', 'www.domain-04.de'"))) Port 25 entry results from the manual regarding the postfix configuration: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.ht ml e.g.: [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: mail.example.com lmtp_port: 8024 smtp_host: mail.example.com smtp_port: 25 Regards Wolfgang -----Ursprüngliche Nachricht----- Von: Mark Sapiro <mark(a)msapiro.net> Gesendet: Sonntag, 20. September 2020 01:05 An: mailman-users(a)mailman3.org Betreff: [MM3-users] Re: including a template failed On 9/19/20 2:47 PM, Wolfgang Bock via Mailman-users wrote: > Hi, > > I created a new mailinglist and got during the test-process the > following errormessage in my mailman.log after: > ... > Sep 19 22:55:08 2020 (1433) ACCEPT: > <000001d68ec7$2553e6e0$6ffbb4a0$(a)domain-01.de> > > Errors: > > Sep 19 22:55:09 2020 (1436) Cannot connect to SMTP server localhost on > port > 25 > HTTPSConnectionPool(host='webmail.domain-02.de', port=443): Max > retries exceeded with url: > /mailman3/postorius/api/templates/list/mylist.lists.domain-03.de/list: > member :regular:footer (Caused by NewConnectionError('<urllib3.connec > tion.VerifiedHTTPSConnection object at 0x7fc8380f1748>: Failed to > establish a new connection: [Errno -2] Name or service not known')) > ... This is wierd. It looks like we are trying to establish a connection to host='webmail.domain-02.de', port=443 in order to GET /mailman3/postorius/api/templates/list/mylist.lists.domain-03.de/list:member :regular:footer, but the error says "Cannot connect to SMTP server localhost on port 25". I have no idea how port 25 is coming into it. Can you get https://webmail.domain-02.de/mailman3/postorius/api/templates/list/mylist.li sts.domain-03.de/list:member:regular:footer on the Mailman machine? What is your setting for POSTORIUS_TEMPLATE_BASE_URL? -- 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 7 months

[MM3-users] Re: can't get mail into mailman3 in docker

by matthew＠alberti.us

I use the docker-mailman setup. Below is the partial contents of my mailman-extra.cfg. I think by default, you would use the Docker assigned private network IP addresses for communicating with the containers. In my setup, 172.19.199.1 is the host (where postfix is) and 172.19.199.2 is mailman-core... # EMAIL SERVER / MTA CONFIGURATION [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: 172.19.199.2 lmtp_port: 8024 smtp_host: 172.19.199.1 smtp_port: 25 configuration: /etc/postfix-mailman.cfg This is all really going to depend on your particular setup. I'm late to the thread; but let me know if that improves the situation. - Matt Alberti -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Saturday, August 7, 2021 2:04 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: can't get mail into mailman3 in docker On 8/6/21 11:28 AM, bob B wrote: > I see nothing for today when the error happens in > /opt/mailman/var/logs/smtp.log > > But the log has a bunch of these, but these stopped around the 4th > > Aug 04 19:46:04 2021 (28) Available AUTH mechanisms: LOGIN(builtin) > PLAIN(builtin) Aug 04 19:46:04 2021 (28) Peer: ('127.0.0.1', 33912) > Aug 04 19:46:04 2021 (28) ('127.0.0.1', 33912) handling connection Aug > 04 19:46:04 2021 (28) ('127.0.0.1', 33912) EOF received Aug 04 > 19:46:04 2021 (28) ('127.0.0.1', 33912) Connection lost during > _handle_client() Aug 04 19:46:04 2021 (28) ('127.0.0.1', 33912) > connection lost These are normal messages from the startup of Mailman's lmtp runner. If you correlate these with mailman.log, you'll probably see the server starting at these times. The fact that there is nothing in this log correlating with the Postfix message 2021-08-06T09:08:41.974225-04:00 dockerhost postfix/lmtp[109783]: D630B3083ED0: to=<test(a)mailman-docker.###.####>, relay=localhost[127.0.0.1]:8024, delay=0.11, delays=0.05/0.02/0.04/0, dsn=4.4.2, status=deferred (lost connection with localhost[127.0.0.1] while receiving the initial server greeting) seems to say that Postfix isn't really connecting to Mailman's lmtp and this is consistent with netstat -l not showing something listening on port 8024. I note you have lmtp_host: localhost in the [mta] section in mailman-extra.cfg. Try changing that to lmtp_host: 127.0.0.1 -- 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

3 years, 8 months

[MM3-users] Re: update_index

by Darren Smith

OK - next issue...here's the warning that I'm receiving when I run that: /__init__.py:1451: RuntimeWarning: DateTimeField Email.archived_date received a naive datetime (2018-04-03 07:51:25) while time zone support is active. RuntimeWarning) I'm not sure that anything else occurred. The indexing took 2 seconds, and there have been tens of thousands of emails imported since the last index. Thoughts? -Darren On Tue, Apr 3, 2018 at 10:55 AM, Darren Smith <silas.crutherton(a)gmail.com> wrote: > Holy cow I think that's exactly what the problem is. I will give that a > try and let you know what happens! > > On Tue, Apr 3, 2018 at 10:50 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 04/03/2018 09:02 AM, Darren Smith wrote: >> > Hello, >> > >> > If I'm reading the docs correctly, when we run manage.py update_index, >> it >> > should be an incremental index of new emails that have been added since >> the >> > last time update_index was run - can anyone confirm that this is the >> > expected behavior? Or is there another command line option that I am >> > missing? >> >> >> There are two ways to run update_index. >> >> Hyperkitty's update_index is incremental and is run by >> >> manage.py runjob update_index >> >> Running >> >> manage.py update_index >> >> runs haystack's update_index which with no options does a full update. Run >> >> manage.py update_index --help >> >> to see the options. The incremental 'manage.py runjob update_index' >> should be run every minute by 'manage.py runjobs minutely' assuming cron >> is running the periodic Django jobs, so running either update_index job >> manually shouldn't be necessary >> >> >> ... >> > So...can anyone help with how to get the update_index to do only emails >> > added since the last time the update_index was run? >> >> >> manage.py runjob update_index >> >> -- >> 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/ >> > >

7 years

[MM3-users] Re: Emergency Moderation

by Allan Hansen

> On May 24, 2020, at 11:34 , Mark Sapiro <mark(a)msapiro.net> wrote: > > On 5/24/20 10:59 AM, Allan Hansen wrote: >> In the MM3 settings there is an option to ‘Hold for moderation’ when members or non-members post to the list. >> I use that for the same cases where in MM2 I switched a list to ‘Emergency Moderation.’ > > > If you imported your MM 2.1 lists with `mailman import21`, `emergency` > was set appropriately for the imported list and should be working to > hold posts regardless of other settings. Not sure what is the difference between ‘emergency moderation’ and ‘Hold for moderation.’ It appears redundant. > > >> My own current top-of-the-list issues: >> >> A bug: Moderators can’t see/edit the list of members even when allowed to by list setting. > > The visibility issue is <https://gitlab.com/mailman/postorius/-/issues/369>. > > Editing membership beyond what could be done via the admindb interface > (i.e. clearing a moderated poster's mod flag) was never allowed for a > moderator in MM 2.1. > > In MM 3, a moderator can set a member's moderation when handling a held > post. Do you think a non-owner moderator should be able to make other > changes to a member? I can only speak for my own application of MM3: Desiring consistency between the lists, I don’t want to turn all the moderators into owners who can change list settings. Many of my moderators keep asking me to see the list of members and to subscribe and remove members. I end up servicing those requests. So... a. Moderators should be able to unsubscribe and subscribe members. b. Moderators should be able to set the member’s moderation status. c. Moderators should not be able to see/modify any other member settings. > > >> A feature request: Member changing email address on all lists he/she belongs to, without involving moderators. > > > This is <https://gitlab.com/mailman/postorius/-/issues/399> and we're > working on it. Awesome!!!! Thank you, Allan > > -- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 10 months

[MM3-users] Re: Apple Mail encoding again

by David Newman

On 4/14/22 9:50 AM, Mark Sapiro wrote: > On 4/14/22 08:21, Stephen J. Turnbull wrote: >> Mark Sapiro writes: >> >> > That combination at least produces multipart/signed messages with >> > multipart/* parts containing a Content-Transfer-Encoding: header. >> > >> > The Python 3 email library considers this to be a >> > InvalidMultipartContentTransferEncodingDefect() message defect. >> >> Merely containing C-T-E is not an error per RFC 2045, although it >> seems to consider it a stupid thing to do. If present, it may be >> "binary", "7-bit", or "8-bit" (below summarized as "cleartext"). >> >> Did Apple Mail apply a non-cleartext C-T-E? Or has an RFC tightening >> that restriction been published since? (I don't know why it would, >> though.) > > > Yes. The C-T-E on all the multipart parts was quoted-printable, not > allowed under RFC 2045. > > >> Even with a non-cleartext C-T-E, it seems reasonable for Mailman to >> treat it as application/octet-stream and pass it through, unless the >> list is configured to do something like strip application/octet-stream >> or that requires decoding like spam-filtering (Postel principle, >> although one could argue it shouldn't be sent on on the same principle >> -- ah, the joys of being an e-mail Mediator). That would be >> especially true it if were quoted-printable, since any relevant MIME >> headers would (presumably) be pure ASCII and therefore unencoded. > > > The Python email library says the message is defective. Mailman's lmtp > runner in turn rejects the defective message with a 501 status > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/lmtp.p… > Yes. To be clear, this is an Apple Mail issue. Mailman 3 accepted PGP-signed messages from Apple Mail on versions prior to 15.0 running on MacOS 12.0.1. Something changed on Apple's part. > > It could accept a defective message or one with specific defects, but > this is problematic for further processing. For example, at least one > MUA, Thunderbird, renders such a message with an empty body. That's not my experience. Mailman 3 accepted without complaint a PGP-signed message I sent from Thunderbird 91.8.0 and forwarded it to list subscribers with the message body intact. dn

3 years

[MM3-users] Re: Mails sent by mailman-web runjobs hourly

by Abhilash Raj

On Fri, Jun 17, 2022, at 2:38 AM, Mark Sapiro wrote: > On 6/16/22 03:44, Eggert Ehmke wrote: >> I get lots of mails originating from the mailman-web runjobs hourly. They are >> sent to mailman@<mytld>. The content looks like >> >> 07:00:03 [Q] INFO Enqueued 12571 >> 07:00:03 [Q] INFO Enqueued 12572 >> 07:00:03 [Q] INFO Enqueued 12573 >> >> How can I disable these emails? > > These message come from Django Q, https://django-q.readthedocs.io/en/latest/ > > I don't think there is a way to disable those specific messages which > occur at times when tasks are queued instead of started immediately. > They are sent to `mailman` because `mailman` owns the crontab and the > crontab has no MAILTO=. You can't stop those specific messages, but you can set up the log level of django-q to WARNING from INFO so that it doesn't send out these logs. You want to add something like this in your settings.py in LOGGING config: https://github.com/Koed00/django-q/blob/15155c7a99ea85a092b1d11da730ba0c4fa… "loggers": { "django_q": { "handlers": ["file"], "level": "WARNING", }, }, Please make sure to *add* "django_q" settings as there might be other existing loggers defined there. Also, I used "file" as the handler for example, so it won't even write to stdout for warning and/or send emails. Make sure that you change that to your liking to include "console" if you want emails for warning logs. > > You can redirect these and all other messages from hourly jobs by > surrounding the hourly jobs command in the crontab with MAILTO= as in > ``` > MAILTO=other(a)example.com > @hourly /opt/mailman/mm/bin/django-admin runjobs hourly > MAILTO=mailman > ``` > or possibly discard them with something like > ``` > @hourly /opt/mailman/mm/bin/django-admin runjobs hourly > /dev/null > ``` > but either of these could redirect or discard other messages from hourly > jobs which you might want. > > -- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- thanks, Abhilash Raj (maxking)

2 years, 10 months

[MM3-users] Re: Odd behavior: "Invalid" list destinations result in mail routing loop w/ SMTP relay in line

by Thomas Ward

Yeah I'll set up some advanced debugging in Postfix on the relays to see whats' coming in and out. Will take time though 'cause we have a TON of messaging going through that smtpproxy out to the 'net so it'll take a bit for me to dissect the message logs. Give me a bit since it's EOD for me now. Thomas On 12/6/23 15:44, Mark Sapiro wrote: > On 12/6/23 11:11, Thomas Ward via Mailman-users wrote: >> See, that's the oddness. There appears to be SOME weird mail loop >> here where $ORIGIN (MS365/Exchange) hands it once, then there's >> back-and-forth between SMTPPROXY and Mailman. IT's really odd how it >> behaves, and I have no explanation for it. >> >> Right now I'm away from the office where this happens, but when I'm >> back there I'll grab logs from both sides. >> >> >> Thomas >> >> On 12/5/23 17:54, Mark Sapiro wrote: >>> On 12/5/23 10:08, Thomas Ward via Mailman-users wrote: >>>> We use a multi-hop SMTP system to go from the inside of our network >>>> out to the Internet at the domain test.lists.example.com. >>>> >>>> The setup is this way for ingress: >>>> >>>> {EXTERNAL} -> MS365 (relay/antispam) -> MS On-Prem (via 365 >>>> Connector) -> Mailman for delivery to listserv > > > Presumably the EXTERNAL to MS365 SMTP transaction includes > > MAIL FROM: <user(a)example.com> > RCPT TO: <invalid(a)test.lists.example.com> > > It seems that somewhere in the path to Mailman this is getting changed to > > MAIL FROM: <invalid(a)test.lists.example.com> > > so the outbound DSN is sent to invalid(a)test.lists.example.com instead > of user(a)example.com. The question is which one of the MTAs in the path > is doing this and why. > > But even more mysterious is the fact that the DSN from Mailman should > be sent with > > MAIL FROM: <> > > so when it's undeliverable, no further DSN is sent. >

1 year, 4 months

[MM3-users] Re: Issues installing postorius and hyperkitty

by Mark Sapiro

On 10/23/19 6:43 AM, thushantha.lakmal(a)arm.com wrote: > Hi All. > > Im trying to install the mailmain suite with the postorius and hyperkitty . Mailman installation completed successfully but for postorius and hyperkitty Im getting the following errors .. > > Please can someone help me .. > > > > For postorius (Using pip3 install postorius ) > > ERROR: django-mailman3 1.3.0 has requirement Django<2.2,>=1.11, but you'll have django 2.2.6 which is incompatible. How is Django 2.2.6 installed? If you are only using Django for Mailman (Postorius and HyperKitty), just do pip3 install Django<2.2 > For hyperkitty (Using pip3 install hyperkitty ) All of the below is saying that the install of hyperkitty is trying to install rcssmin, that in turn requires building '_rcssmin' extension which requires gcc. Do you have some other C compiler not named gcc? If so, you might be able to work around this by creating a symlink to your C compiler from /usr/bin/gcc, but it would be better to install gcc using apt, rpm, or whatever your package manager is. > > de41118f448bcb3b8df405c5228e1 > Stored in directory: /root/.cache/pip/wheels/79/50/a5/9410f4b2e62e35c285de46ffa88c2562403cb576e1e7859d68 > Building wheel for rcssmin (setup.py) ... error > ERROR: Command errored out with exit status 1: > command: /usr/bin/python3 -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-563o314q/rcssmin/setup.py'"'"'; __file__='"'"'/tmp/pip-install-563o314q/rcssmin/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' bdist_wheel -d /tmp/pip-wheel-491rzr5s --python-tag cp36 > cwd: /tmp/pip-install-563o314q/rcssmin/ > Complete output (12 lines): > running bdist_wheel > running build > running build_py > creating build > creating build/lib.linux-x86_64-3.6 > copying ./rcssmin.py -> build/lib.linux-x86_64-3.6 > running build_ext > building '_rcssmin' extension > creating build/temp.linux-x86_64-3.6 > gcc -pthread -Wno-unused-result -Wsign-compare -DDYNAMIC_ANNOTATIONS_ENABLED=1 -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC -DEXT_MODULE=_rcssmin -UEXT_PACKAGE -I_setup/include -I/usr/include/python3.6m -c rcssmin.c -o build/temp.linux-x86_64-3.6/rcssmin.o > unable to execute 'gcc': No such file or directory > error: command 'gcc' failed with exit status 1 > ---------------------------------------- > ERROR: Failed building wheel for rcssmin > Running setup.py clean for rcssmin > Successfully built robot-detection django-haystack > Failed to build rcssmin > Installing collected packages: rjsmin, django-appconf, rcssmin, django-compressor, robot-detection, django-haystack, djangorestframework, decorator, networkx, django-extensions, wcwidth, blessed, arrow, django-picklefield, django-q, hyperkitty > Running setup.py install for rcssmin ... error > ERROR: Command errored out with exit status 1: > command: /usr/bin/python3 -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-563o314q/rcssmin/setup.py'"'"'; __file__='"'"'/tmp/pip-install-563o314q/rcssmin/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-6g8g9aoj/install-record.txt --single-version-externally-managed --compile > cwd: /tmp/pip-install-563o314q/rcssmin/ > Complete output (12 lines): > running install > running build > running build_py > creating build > creating build/lib.linux-x86_64-3.6 > copying ./rcssmin.py -> build/lib.linux-x86_64-3.6 > running build_ext > building '_rcssmin' extension > creating build/temp.linux-x86_64-3.6 > gcc -pthread -Wno-unused-result -Wsign-compare -DDYNAMIC_ANNOTATIONS_ENABLED=1 -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC -DEXT_MODULE=_rcssmin -UEXT_PACKAGE -I_setup/include -I/usr/include/python3.6m -c rcssmin.c -o build/temp.linux-x86_64-3.6/rcssmin.o > unable to execute 'gcc': No such file or directory > error: command 'gcc' failed with exit status 1 > ---------------------------------------- > ERROR: Command errored out with exit status 1: /usr/bin/python3 -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-563o314q/rcssmin/setup.py'"'"'; __file__='"'"'/tmp/pip-install-563o314q/rcssmin/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-6g8g9aoj/install-record.txt --single-version-externally-managed --compile Check the logs for full command output. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: spanish localization

by Guillermo Hernandez (Oldno7)

On 13/2/21 23:53, Mark Sapiro wrote: > On 2/13/21 11:52 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> On 13/2/21 20:00, Mark Sapiro wrote: >>> If there are issues in this mailman.po, they exist in weblate too and >>> need to be fixed there. >> That clarifies all. Thanks. As I said in my previous message, I'll wait >> for the next upgrade and hopingly the translations done after 7h of >> november (by others and me) will be there. > > What translations are those? Please give specific examples. What I am > saying is Mailman core 3.3.3 is currently up to date with weblate. There > are no Spanish translations for core done after 7 November in weblate > and weblate shows 100% completion for Spanish for Mailman core. > Well.. It surely is in the case of mailman core, but not in postorius, hyperkitty and django_mailman3. And these are what are serving the translated terms what the users see. I did some exploration this morning (Spain time) in the weblate statistics and archives and I found that the changes done from Victoriano and me were recorded. I did a screencopy of all that if someone has any doubt about it. I downloaded this files: -rw-r--r-- 1 1002 wheel 11037 Feb 14 10:57 gnu-mailman-django-mailman3-es.po -rw-r--r-- 1 1002 wheel 34511 Feb 14 10:54 gnu-mailman-hyperkitty-es.po -rw-r--r-- 1 1002 wheel 143758 Feb 14 10:51 gnu-mailman-mailman-es.po -rw-r--r-- 1 1002 wheel 104997 Feb 14 10:49 gnu-mailman-postorius-es.po The thing is that they differ from the .po installed via pip upgrade. Mostly, as said, postorius, hyperkitty and django_mailman3. I saved a backup copy of the "django.po" that lies in the packages path for the es language. In my case /usr/local/lib/python3.7/site-packages/[package]/locale/es/LC_MESSAGES and replaced by the downladed file, changing the name (as all of them was named django.po in destination). Then I did, as you pointed in a message and Victoriano found the right way in our systems, a django-admin compilemessages for each package. And now I have all the postiorius web interface correctly translated (at least almost all of it). Now I can make a tutorial for my moderators and users without them complaining about the mixing language terms. I have also a screencopy of before-after If someone wants to see the changes. Thanks all for your support.

4 years, 2 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

Hello guys, This is what I've got on ../var/data: [root@localhost data]# pwd /var/lib/mailman/var/data [root@localhost data]# ls -l total 76 -rw-rw---- 1 mailman mailman 74752 Jul 16 16:44 mailman.db What should I do in order to let mailman install the DB files? Thanks El dom., 23 jul. 2017 a las 11:19, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/23/2017 08:16 AM, Rafael Mora wrote: > > This is the content of my /var/log: > > > > > > [root@localhost log]# pwd > > /var/log > > [root@localhost log]# ls > > anaconda grubby messages-20170716 spooler-20170710 > > audit grubby_prune_debug messages-20170723 spooler-20170716 > > boot.log httpd mysqld.log spooler-20170723 > > btmp lastlog php-fpm tallylog > > btmp-20170701 letsencrypt ppp tuned > > chrony maillog rhsm wtmp > > cron maillog-20170702 samba xferlog > > cron-20170702 maillog-20170710 secure xferlog-20170702 > > cron-20170710 maillog-20170716 secure-20170702 xferlog-20170710 > > cron-20170716 maillog-20170723 secure-20170710 xferlog-20170716 > > cron-20170723 mailman secure-20170716 xferlog-20170723 > > dmesg messages secure-20170723 yum.log > > dmesg.old messages-20170702 spooler > > firewalld messages-20170710 spooler-20170702 > > > Your current postfix log is /var/log/maillog. The files like > /var/log/maillog-20170702, etc are older versions rotated by logrotate. > > On 07/23/2017 08:14 AM, Rafael Mora wrote: > > content of the file maillog-20170723 (I didn't find mail.log in > /var/log): > > > > [root@localhost log]# cat maillog-20170723 > > You want to be looking at /var/log/maillog for current messages. > > > ... > > Jul 21 16:10:47 localhost postfix/qmgr[2116]: error: open database > > /var/lib/mailman/var/data/postfix_domains.db: No such file or directory > > > Is this where these files are? You should have at least postfix_domains, > postfix_domains.db, postfix_lmtp and postfix_lmtp.db in the > /var/lib/mailman/var/data/ directory. It this the case? > > > output command 'postconf -n': > > > ... > > transport_maps = hash:/var/libmailman/var/data/postfix_lmtp > > > This is missing a / > > > transport_maps = hash:/var/lib/mailman/var/data/postfix_lmtp > > > -- > 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/ > -- Atentamente / Best Regards Ing. Rafael Mora

7 years, 9 months

[MM3-users] Re: logrotate

by Christian

Thank you! Would I run your script weekly in cron or ? -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, May 2, 2023 4:37 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: logrotate Please don't hijack threads. Post a new topic as an original post, not as a reply to an old thread. On 5/2/23 15:45, Christian via Mailman-users wrote: > I noticed that my mailman logfiles are not being rotated. I followed > the instructions in > https://mail.python.org/archives/list/mailman-developers@python.org/me > ssage/ > FM3TSMQ63JR2KROJGOSPENODOOQVRYCL/ Those instructions are for Mailman 2.1. > Now when I try and run logrotate I get the following error > > root@zarathustra:/opt/mailman/mm/logs# logrotate /etc/logrotate.conf > error: stat of /opt/mailman/mm/logs/bounce.log failed: No such file > or directory > error: stat of /opt/mailman/mm/error.log failed: No such file or > directory > error: stat of /opt/mailman/mm/mailman.log failed: No such file or > directory > error: stat of /opt/mailman/mm/mailmansuite.log failed: No such file > or directory > error: stat of /opt/mailman/mm/smtp.log failed: No such file or > directory > root@zarathustra: > > What am I doing wrong please? Here's a logrotate script I use: ``` /opt/mailman/mm/var/logs/*.log { missingok sharedscripts su mailman mailman postrotate sudo -u mailman /opt/mailman/mm/bin/mailman reopen &>/dev/null || true if [ -r /opt/mailman/mm/var/gunicorn.pid ]; then PID=`cat /opt/mailman/mm/var/gunicorn.pid` kill -s USR1 $PID fi endscript } ``` A couple of caveats. The first line of the postrotate script may be wrapped. `sudo ... true` is all one line. That line could also be ``` /opt/mailman/mm/bin/mailman --run-as-root reopen &>/dev/null || true ``` I.e., it either has to run as the mailman user or specify the --run-as-root option. Also, if logs aren't in /opt/mailman/mm/var/logs/ or gunicorn.pid isn't in /opt/mailman/mm/var/ those paths need adjusting. Finally, there may be an issue with `mailman reopen` in the postrotate scrupt. See https://gitlab.com/mailman/mailman/-/issues/1078 -- 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/ JTUKYJDD5Y5JIAVK3OOFNVCK4CVDGK6O/ This message sent to csa(a)web-analysts.net

1 year, 11 months

[MM3-users] Re: Hipperkitty failing to archive messages in a list

by Mark Sapiro

On 1/5/22 4:01 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > pip install --upgrade --force-reinstall --no-deps --no-cache-dir > django-mailman3 mailman mailman-hyperkitty mailmanclient postorius > django hyperkitty > > su -m mailman3 -c "python3 manage.py collectstatic" > su -m mailman3 -c "python3 manage.py migrate" > > In this last point I've received some warnings of this kind: > > *-*-*-*-*-*-* > > WARNINGS: > account.EmailAddress: (models.W042) Auto-created primary key used when > not defining a primary key type, by default 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > AccountConfig.default_auto_field attribute to point to a subclass of > AutoField, e.g. 'django.db.models.BigAutoField'. > account.EmailConfirmation: (models.W042) Auto-created primary key used > when not defining a primary key type, by default > 'django.db.models.AutoField'. > > ... > > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > SocialAccountConfig.default_auto_field attribute to point to a subclass > of AutoField, e.g. 'django.db.models.BigAutoField'. This is from Django >=3.2 can be fixed by adding DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' to your settings. This has been done in HyperKitty's example_project/settings.py for the not yet released 1.3.6 version. These warnings are only warnings, they aren't fatal. ... > Running a 'su -m mailman3 -c "python3 manage.py makemigrations" shows > the same warning listed before and some new errors: > > *-*-*-*-*-*-* > > Migrations for 'postorius': > /usr/local/lib/python3.7/site-packages/postorius/migrations/0017_alter_emailtemplate_name.py > > - Alter field name on emailtemplate > Traceback (most recent call last): > File "manage.py", line 10, in <module> > execute_from_command_line(sys.argv) > File > "/usr/local/lib/python3.7/site-packages/django/core/management/__init__.py", > line 419, in execute_from_command_line > utility.execute() > File > "/usr/local/lib/python3.7/site-packages/django/core/management/__init__.py", > line 413, in execute > self.fetch_command(subcommand).run_from_argv(self.argv) > File > "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", > line 354, in run_from_argv > self.execute(*args, **cmd_options) > File > "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", > line 398, in execute > output = self.handle(*args, **options) > File > "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", > line 89, in wrapped > res = handle_func(*args, **kwargs) > File > "/usr/local/lib/python3.7/site-packages/django/core/management/commands/makemigrations.py", > line 190, in handle > self.write_migration_files(changes) > File > "/usr/local/lib/python3.7/site-packages/django/core/management/commands/makemigrations.py", > line 228, in write_migration_files > with open(writer.path, "w", encoding='utf-8') as fh: > PermissionError: [Errno 13] Permission denied: > '/usr/local/lib/python3.7/site-packages/postorius/migrations/0017_alter_emailtemplate_name.py' > > > *-*-*-*-*-*-* > > The file > '/usr/local/lib/python3.7/site-packages/postorius/migrations/0017_alter_emailtemplate_name.py' > does not exist at all makemigrations is trying to create that migration and you don't have permission to create the file. I don't know why it's trying to do that. Postorius 1.3.6 has migrations through 0016_auto_20210810_2157.py and shouldn't need more. To you have modificationd to Postorius? > Despite the error, I did a 'su -m mailman3 -c "python3 manage.py > compress"' and the subsequent "django-admin compilemessages" in > > /usr/local/lib/python3.7/site-packages/postorius, ../hyperkitty and > ../django_mailman3 > > And the log continues showing the same error when trying archive a new > message. > > ERROR 2022-01-05 12:27:31,406 6988 hyperkitty.views.mailman The > MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. > ERROR 2022-01-05 12:27:31,418 6988 hyperkitty.views.mailman The > MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. > ERROR 2022-01-05 12:27:31,685 6988 hyperkitty.views.mailman The > MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. > ERROR 2022-01-05 12:27:32,045 6988 hyperkitty.views.mailman The > MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. > ERROR 2022-01-05 12:27:32,070 6988 hyperkitty.views.mailman The > MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. > ERROR 2022-01-05 12:27:32,093 6988 hyperkitty.views.mailman The > MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. These messages come from some HyperKitty version between commit b415d29d6cc59b3270c35b03ba3313dd03450271 Mon Jun 21 00:11:48 2021 -0700 and commit c6272f3ef8375865382d0741d3d371a0dc41508a Fri Oct 8 06:32:06 2021 +0000 They do not come from HyperKitty 1.3.5 but from something later than 1.3.4 which makes be think your mailman-hyperkitty version is not 1.2.0 either. I suggest you do pip install --upgrade hyperkitty mailman-hyperkitty and ensure it installs hyperkitty 1.3.5 and mailman-hyperkitty 1.2.0 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: Issues with @gmail.com addresses

by Mohsen Masoudfar

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

[MM3-users] Re: Mailman Core 3.3.2 is now out

by Abhilash Raj

On Wed, Nov 25, 2020, at 9:24 AM, Mark Sapiro wrote: > On 11/24/20 7:22 PM, Abhilash Raj wrote: > > > > I think I should keep in mind next time to use the #<heading-name> like `#3.3.2` pointed out by Torge, instead of `#id` (which is what I see when I hover over the Link in browser so I copied ;). > > > It's more complicated than that. Sometimes the fragment name is the > heading and sometimes it is `#idn`. At the moment, neither #3.3.2 nor > #3.3.3 work at all as these are #id2 and #id1 respectively. Currently > the fragment for 3.3.3 Bugs is #bugs and the fragment for 3.3.2 Bugs is > #id3, but presumably prior to the addition of 3.3.3, #bugs was Bugs > under 3.3.2, Just as now, #command-line is Command line under 3.3.2, but > when a Command line section is added under 3.3.3, that will probably get > the command-line id. > > Thus, the note "Permalink to this headline" es misleading at best > because it isn't very permanent fo an evolving document. Yeah, I was thinking about internal references, `:ref:` which accepts heading names, but anchors aren't added you are right. > > > > You can specify explicit anchor name in .rst too, I think just adding a `.. _news-3.3.2` just above the heading will generate an anchor on the page with #news-3.3.2 (I haven't verified this but I think it will!) which links to the heading. > > > I too think this is correct. I suppose it might be worth doing for > NEWS.rst in particular since Sphinx doesn't seem to like fragments like > n.n.n. Another way to deal with this would be to always use code names. > It seems like a heading `n.n.n` will always get a `#idn` id, but, e.g. > `3.3.0 – “Tom Sawyer”` gets `#tom-sawyer` Yep, I created news-3.3.3 for 3.3.3 and we can keep the convention going. I tested it out and it worked for me. https://gitlab.com/mailman/mailman/-/merge_requests/736 > -- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

4 years, 4 months

[MM3-users] Re: Weird behavior with Outlook and any MM3 List

by Thomas Ward

Ye it gets a little tricky when we have custom thread IDs being added. I could do some postprocessing on a reply and see what the "In-Reply-To" header says if I can figure out how to fetch the previous message subject line for the custom need for my workplace with a thread/post ID in the subject line. I'm going to experiment with alternative brackets and see if it still does it. While also opening a support ticket with Microsoft to give me a chance to rage at them. I'll report back if I find a solution/alternative. Thomas -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, November 1, 2023 2:36 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Weird behavior with Outlook and any MM3 List On 11/1/23 09:42, Thomas Ward via Mailman-users wrote: > I'm seeing some *really* odd behavior with Mailman 3 and Microsoft Outlook clients (even Outlook Web Access). > > When messages come in with a subject prefix, of any way shape or form, Microsoft Outlook seems to *completely strip* the prefixes from any "reply" sent, which could be problematic. > > While the "In-Reply-To" header is still intact and such, Microsoft just seems to 'strip' prefixes from subject lines and that causes a problem in some cases. > > Has anyone observed this behavior before? If so, have you found any workarounds? This is a Microsoft/Outlook issue. As you note at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… this is just the way Outlook displays the message subject. I know of now way around this, but I don't use Microsoft MUAs. Does Outlook also strip the prefix from replies? This probably wouldn't matter for replies to the list as the list will add it back, but might be an issue for other direct recipients. Presumably, Outlook is looking at the [] around the prefix. You might try either dropping the brackets or using something else such as _My-List_ instead of [MyList]. -- 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://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 teward(a)thomas-ward.net

1 year, 5 months

[MM3-users] Re: digests are created but not sent out

by "Jörg M. Schulz"

To make it work, I have to comment out like this: Also only commenting out the .de section doesn’t help # The default language for this server. default_language: en # [language.en] # charset: utf-8 # enabled: yes # [language.de] # description: German # charset: iso-8859-1 # enabled: yes > Am 09.01.2019 um 21:50 schrieb Mark Sapiro <mark(a)msapiro.net>: > > On 1/9/19 12:20 PM, "Jörg M. Schulz" wrote: >> when I use the lines below, the templates are looked for in //var. >> When I comment them out, the location is correct: /var/lib/mailman3/ (debian buster standard) . The user list has full access. The folder is empty. > > > //var refers to the directory defined in mailman.cfg (or the default in > mailman/config/schema.cfg) as > > [paths.master] > var_dir: > > > Exactly which of the following lines did you add and then comment out? > Just the three lines > >> [language.en] >> charset: utf-8 >> enabled: yes > > > or something more? > > >> mailman.cfg: >> >> [mailman] >> # This address is the "site owner" address. Certain messages which must be >> # delivered to a human, but which can't be delivered to a list owner (e.g. a >> # bounce from a list owner), will be sent to this address. It should point to >> # a human. >> site_owner: help(a)elternserver.de >> >> # This is the local-part of an email address used in the From field whenever a >> # message comes from some entity to which there is no natural reply recipient. >> # Mailman will append '@' and the host name of the list involved. This >> # address must not bounce and it must not point to a Mailman process. >> noreply_address: noreply >> >> # The default language for this server. >> default_language: en >> [language.en] >> charset: utf-8 >> enabled: yes >> >> [language.de] >> description: German >> charset: iso-8859-1 >> enabled: yes > > > -- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

6 years, 3 months

[MM3-users] Re: Hyperkitty: AttributeError: 'NoneType' object has no attribute 'subject'

by Mark Sapiro

On 01/13/2018 09:46 AM, Alex McLean wrote: > I'm getting a 500 server error with some threads in hyperkitty, e.g. this one: > https://we.lurk.org/hyperkitty/list/tidal@we.lurk.org/thread/3IN5NFFFPVAQSR… > > The following appears in the log, any pointers much appreciated! > > ERROR 2018-01-13 12:29:53,855 6056 django.request Internal Server Error: /hyperkitty/list/tidal(a)we.lurk.org/thread/4ECEUJRXMJ2U7EPKRMU6V6A3FVL523BC/ > Traceback (most recent call last): > File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/exception.py", line 41, in inner > response = get_response(request) > File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line 249, in _legacy_get_response > response = self._get_response(request) > File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line 187, in _get_response > response = self.process_exception_by_middleware(e, request) > File "/usr/local/lib/python2.7/dist-packages/django/core/handlers/base.py", line 185, in _get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File "/usr/local/lib/python2.7/dist-packages/hyperkitty/lib/view_helpers.py", line 136, in inner > return func(request, *args, **kwargs) > File "/usr/local/lib/python2.7/dist-packages/hyperkitty/views/thread.py", line 193, in thread_index > return render(request, "hyperkitty/thread.html", context) > File "/usr/local/lib/python2.7/dist-packages/django/shortcuts.py", line 30, in render > content = loader.render_to_string(template_name, context, request, using=using) > File "/usr/local/lib/python2.7/dist-packages/django/template/loader.py", line 68, in render_to_string > return template.render(context, request) > File "/usr/local/lib/python2.7/dist-packages/django/template/backends/django.py", line 66, in render > return self.template.render(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 207, in render > return self._render(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 199, in _render > return self.nodelist.render(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 990, in render > bit = node.render_annotated(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 957, in render_annotated > return self.render(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/loader_tags.py", line 177, in render > return compiled_parent._render(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 199, in _render > return self.nodelist.render(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 990, in render > bit = node.render_annotated(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 957, in render_annotated > return self.render(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/loader_tags.py", line 72, in render > result = block.nodelist.render(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 990, in render > bit = node.render_annotated(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 957, in render_annotated > return self.render(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/defaulttags.py", line 529, in render > return self.nodelist.render(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 990, in render > bit = node.render_annotated(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 957, in render_annotated > return self.render(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/defaulttags.py", line 322, in render > return nodelist.render(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 990, in render > bit = node.render_annotated(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 957, in render_annotated > return self.render(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 1040, in render > output = self.filter_expression.resolve(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 708, in resolve > obj = self.var.resolve(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 849, in resolve > value = self._resolve_lookup(context) > File "/usr/local/lib/python2.7/dist-packages/django/template/base.py", line 890, in _resolve_lookup > current = getattr(current, bit) > File "/usr/local/lib/python2.7/dist-packages/hyperkitty/models/thread.py", line 108, in subject > return self.cached_values["subject"]() > File "/usr/local/lib/python2.7/dist-packages/hyperkitty/models/common.py", line 61, in __call__ > return self.get_or_set(*args, **kwargs) > File "/usr/local/lib/python2.7/dist-packages/hyperkitty/models/common.py", line 57, in get_or_set > value = self.rebuild(*args, **kwargs) > File "/usr/local/lib/python2.7/dist-packages/hyperkitty/models/common.py", line 49, in rebuild > value = self.get_value(*args, **kwargs) > File "/usr/local/lib/python2.7/dist-packages/hyperkitty/models/thread.py", line 223, in get_value > return self.instance.starting_email.subject > AttributeError: 'NoneType' object has no attribute 'subject' This may be related to our not clearing cache when deleting messages/threads. See <https://gitlab.com/mailman/hyperkitty/issues/160>. If so, restarting your web server may help. -- 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

[MM3-users] Re: Mailman 3 Keeps Forgettings Imported Lists

by Ryan McClung

Hey there, Im going to breakdown my response into sections: 1) Yes, there is only one install of mailman on the box. 2) I created the list using the script below 3) My method of importing it is by copying the lists to /opt/mailman/old/lists and running these commands (within lists) MYDIR="/opt/mailman/old/lists" DIRS=`ls -l $MYDIR | egrep '^d' | awk '{print $9}'` for DIR in $DIRS; do mailman import21 "${DIR}"@afilias.info "${DIR}"/config.pck; done However, if you look at the above you can see where I am going wrong. What it should actually be doing is: MYDIR="/opt/mailman/old/lists" DIRS=`ls -l $MYDIR | egrep '^d' | awk '{print $9}'` for DIR in $DIRS; do mailman create "${DIR}"; mailman import21 "${DIR}"@ afilias.info "${DIR}"/config.pck; done Sorry for wasting your time on this one. Coffee is on me. On Mon, Jul 30, 2018 at 6:05 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 07/30/2018 07:37 AM, Ryan McClung wrote: > > GNU Mailman 3.2.0 (La Villa Strangiato) > > Python 3.6.5 (default, Apr 10 2018, 17:08:37) > > [GCC 4.8.5 20150623 (Red Hat 4.8.5-16)] > > config file: /opt/mailman/var/etc/mailman.cfg > > db url: sqlite:////opt/mailman/var/data/mailman.db > > devmode: DISABLED > > REST root url: http://localhost:8001/3.1/ > > > > Shortly after I run an import on a bunch of lists they all disappear. > > [root@mailman3(stg) mailman]# mailman lists > > No matching mailing lists found > > > > I have 30+ lists. > > > Does the 'mailman lists' command invoke the identical 'mailman' file as > the 'mailman import21' command that did the imports. And how did you > create the lists before importing them? > > We have done several imports of 2.1 lists to > <https://mail.python.org/mm3/mailman3/> and have never seen an issue > like this. > > -- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Ryan McClung Systems Administrator @ Afilias Canada A. 204-4141 Yonge Street, Toronto, ON, Canada, M2P 2A8 <https://maps.google.com/?q=4141+Yonge+Street,+Toronto,+ON,+Canada,+M2P+2A8&…> W. www.afilias.info T. +1.416.646.3304 x4186

6 years, 8 months

[MM3-users] Re: sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for one_or_none()

by Shashikanth Komandoor

Thank you Mark for your response. But I am having a final query over this issue. Out of the two hyperkitty records I observed in the database, I am confused which record do I need to remove directly from the database? Because I doubt still there is one more list with the same style i.e. with two hyperkitty records. Please advise. On Mon, Jul 27, 2020 at 4:40 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/26/20 10:45 AM, Shashikanth Komandoor wrote: > > Thank you Mark. > > > > What you have said is right.. > > > > I found a list with two "hyperkitty" records in the listarchiver in the > > database. I had removed the list and recreated it and now I found it is > > working fine. The recreated list is having only one record. > > > OK, but that's not a reasonable way to fix this in general. You can just > remove the `extra` record using a direct database query which is > probably the least disruptive way to fix this. > > > > After searching the links you provided I found there is just a work > around > > but not the precaution to be taken for not getting the duplicate record. > > > > Can you say what might be the reason for this duplication? If I need to > > provide any details, please let me know. > > > As noted in the threads I referenced, we don't know the cause. Yours is > the first report of this issue with the `hyperkitty` archiver. In all > the other reports, the duplicate archiver has been `mhonarc`. > > If it happens again and you know the exact sequence of events that led > to it, i.e. what was done with the list between the last time it worked > and when it stopped working, that might give us clues, but currently we > are at a total loss to understand how this happens. > > -- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

4 years, 8 months

[MM3-users] Re: Pck files stuck in out queue

by Lieuallen, Thomas Otis

Mark, I checked the database; nothing there. Note that there are only 3x entries and only one is list:member:regular:header (my test), so just nothing of interest. The URL works and produces the proper template information. I finally did a find/grep in the mailman tree and found a match for this errant string. It is under the cache folder. This corresponds to the cache_dir value. I could wipe the file out, but what is the proper way of doing so and should they be cleaned out via a schedule? These don’t appear to be web related, as far as I can tell. Thank you Tom Lieuallen From: Mark Sapiro <mark(a)msapiro.net> Date: Friday, February 7, 2025 at 10:37 AM 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/7/25 10:08, Lieuallen, Thomas Otis via Mailman-users wrote: > > I have a remaining issue that baffles me. With my test list, I created a template for ‘list:member:regular:header’. It just has text in it, keeping it simple. I create it and see the entries in the database tables and they are correct. However, when I send a test email, my template text is not inserted, but instead another simple text: “testing hello”. I do the same with list:member:regular:footer, and it works just fine. It is just the header that is working incorrectly. When I remove that postorius header template for the list, that ‘testing hello’ goes away. So, it’s only appearing when I have a postorius template setup for that list. What do you get from the following database queries? SELECT * FROM template WHERE name = 'list:member:regular:header'; SELECT * FROM postorius_emailtemplate WHERE name = 'list:member:regular:header'; Depending on your installation, these tables may be in separate databases, i.e., template table in mailman db and postorius_emailtemplate in mailmanweb db. And what do you get if you go to the uri in the result(s) from the first query? The context in the first results and maybe the second results should also be a clue. -- 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://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

2 months, 2 weeks

[MM3-users] Re: List description as sender

by Henrik Rasmussen

It is the description in the Settings -> List Identity -> Description that is used in the list overview https://list.example.com/postorius/lists/ and also as the "From:" in the mails sent to the subscribers. I try to keep the descriptions as short as possible, and I don't consider "Newsletter to the members of the Anthropology Society" a long message, when displayed in https://list.example.com/postorius/lists/, but when the description is displayed as From: in mails, I agree it is a long description. On lists.mailman3.org, the description "General list for Mailman 3 users and others interested in Mailman 3" is also short, but when used as From: it is fairly long. -----Oprindelig meddelelse----- From: Mailman-users is an infrequent newsletter sent to list administrators <mailman-users(a)lists.example.com> Sent: 14. september 2018 13:20 To: mailman-users(a)lists.example.com Subject: Test 201809141319 [cid:image001.png@01D44E6C.A57045A0] -- Henrik Rasmussen <her(a)adm.ku.dk<mailto:her@adm.ku.dk>> University of Copenhagen, Danmark -----Oprindelig meddelelse----- Fra: Mark Sapiro <mark(a)msapiro.net> Sendt: 14. september 2018 17:36 Til: mailman-users(a)mailman3.org Emne: [MM3-users] Re: List description as sender On 09/14/2018 05:35 AM, Henrik Rasmussen wrote: > When receiving a mail from Mailman 3, the From: User name is the description of the list, like From: Long desription of the list for all members of certain project <project(a)lists.example.com<mailto:project@lists.example.com>>. > > Starting to get old, I recall something about a discussion we once had on http://mail.python.org/pipermail/mailman-users/, but I don't recall the reason for this and I can't find the discussion, so it might be something I dreamed. Specifically what messages are you talking about? The only case I see offhand where the From: is as you describe is in posts from an anonymous list. In any case, the list description is described in Postorius as "This description is used when the mailing list is listed with other mailing lists, or in headers, and so forth. It should be as succinct as you can get it, while still identifying what the list is." I.e., it shouldn't be a long description. -- 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/

6 years, 7 months

[MM3-users] Re: Mailman3 without Hyperkitty in docker

by Abhilash Raj

On Thu, Feb 28, 2019, at 5:19 PM, Abhilash Raj wrote: > On February 27, 2019 11:53:34 PM PST, Danil Smirnov <danil(a)smirnov.la> wrote: > >Hi Mark, > > > >Actually all this stuff happens inside the container after it's started > >and > >initialized without errors. I didn't amend the image anyhow. > > > >Also I have the configuration based on docker-compose.yaml provided in > >the > >repository which works just fine for mailman-web image. > > > >The very same config with postorius image (+ UWSGI_STATIC_MAP param) > >fails > >with 500 error... > > > >Now answering your questions: > > > >ср, 27 февр. 2019 г., 22:56 Mark Sapiro <mark(a)msapiro.net>: > > > >> do you have django-q in INSTALLED_APPS in your Django settings and > >what > >> is set for Q_CLUSTER? > >> > > > >I've checked settings.py inside the container and I haven't found any > >of > >the mentioned configurations there. > > > >Does the manage.py that's being run here point to the right > >settings.py? > >> > > > >No clue. > > > >Also I wonder why we have some Hyperkitty-related cronjobs in non-HK > >configured image? > > > >https://github.com/maxking/docker-mailman/blob/master/postorius/mailman-web… > > Because I am a dum dum ;-) > > Will work on removing those crons and stuff. Would be nice if you > opened an issue on Github so that I don't forget. Should now be fixed in the latest image. > > >Danil > > > > > > > >> -- > >> 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > >> > >_______________________________________________ > >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/ > > > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. -- thanks, Abhilash Raj (maxking)

6 years, 1 month

[MM3-users] Re: Pck files stuck in out queue

by Lieuallen, Thomas Otis

Mark, Actually, this is saying cache_life under mailman: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/config/doc… There is a cache_lifetime under ‘dmarc’. I used your clue about the database to concoct my own solution… 😊. I edited the ‘expires_on’ values in the file_cache table in the database so the files were expired. It looks like the times in that table are UTC. I’m going to ratchet down my cache_life so anyone that is playing with templates doesn’t go bonkers (like me) with why their changes aren’t honored. I have a small site, so not much performance impact. Thank you for your help. Tom Lieuallen From: Mark Sapiro <mark(a)msapiro.net> Date: Monday, February 10, 2025 at 12:46 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/10/25 12:09, Lieuallen, Thomas Otis via Mailman-users wrote: > > I haven’t figured out how to work with these cache files. I found some mention that a runner would clean up cache files after a week (default) and that one could use ‘cache_life’ to change that default. So, I set the following and restarted mailman. The cache files hadn’t been removed after > 4 hours, so I unset it and restarted again. > > Cache_life: 1d The setting is actually `cache_lifetime` in the `[mailman]` section of mailman.cfg, however when a file is cached, it's lifetime is saved in the database and won't be changed by changing that setting. > Without further information or direction, I’m tempted to just remove those cache files and move on with life. Removing them is OK, but a database entry will still exist pointing to them and attempt to retrieve them will return `Cache content lost`. The way to properly remove them is in Mailman shell ``` $ mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> cm = getUtility(ICacheManager) >>> cm.clear() >>> commit() >>> ``` -- 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://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

2 months, 1 week

[MM3-users] Re: statistics monitoring for Mailman3

by Mohsen Masoudfar

Hi Mark, Thanks again for the nice Python script. There is an issue with outlook.com. They add a '^M' (carriage Return) before msgid!! Here is part of the log that shows that. This is not in every log, though. I updated the get_log_data function (please see below), I believe it is not the smartest solution, but it seems to be working for me. Mar 14 12:53:19 2021 (11696) ('127.0.0.1', 55180) Data: b'QUIT' Mar 14 12:53:19 2021 (11696) ('127.0.0.1', 55180) connection lost Mar 14 12:53:19 2021 (11696) Connection lost during _handle_client() Mar 14 12:53:21 2021 (11701) <MN2PR20MB324587763E970CC56351F8C5B66D9(a)MN2PR20MB3245.namprd20.prod.outlook.com> smtp to testlist3(a)newlistserv.aaas.org for 1 recips, completed in 0.013000726699829102 seconds Mar 14 12:53:21 2021 (11701) <MN2PR20MB324587763E970CC56351F8C5B66D9(a)MN2PR20MB3245.namprd20.prod.outlook.com> post to testlist3(a)newlistserv.aaas.org from testlist3(a)newlistserv.aaas.org, 7940 bytes LOGRETS = ('^(?P<time_stamp>[^(]*) $\d+$ (?:\n|\r\n)') LOGREMI = (' (?P<msgid><[^>]*>) smtp to (?P<listname>[^ ]*) for (?P<count>\d+) recips, completed ') def get_log_data(log): data = [] with open(log) as fp: for line in fp.readlines(): mo = re.match(LOGRE, line) if not mo: mts = re.match(LOGRETS, line) if mts: dt = datetime.datetime.strptime(mts.group('time_stamp'), '%b %d %H:%M:%S %Y') if not mts: mmi = re.match(LOGREMI, line) if mmi: mid = mmi.group('msgid') lname = mmi.group('listname') count = int(mmi.group('count')) data.append([dt, mid, lname, count]) continue continue dt = datetime.datetime.strptime(mo.group('time_stamp'), '%b %d %H:%M:%S %Y') mid = mo.group('msgid') lname = mo.group('listname') count = int(mo.group('count')) data.append([dt, mid, lname, count]) return data Thanks Mohsen -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, March 12, 2021 2:42 PM To: MM3 Users <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: statistics monitoring for Mailman3 [EXTERNAL EMAIL] On 3/12/21 11:22 AM, Mohsen Masoudfar wrote: > I was checking on log rotating on smtp.log. On my server it does not rotate. I could use log-rotator to rotate that, but could not find any information how to inform the mailman process of the rotation, e.g. which signal to send him? The `mailman reopen` command is the recommended way, or you can send the `master` a SIGUSR1. The master's PID is in the file var/master.pid or /var/run/mailman/master.pid if you've configured `layout: fhs`. -- 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…

4 years, 1 month

[MM3-users] Re: Mailman3 stopped sending out mail

by Mark Sapiro

On 12/31/18 2:14 AM, Abhijith PA via Mailman-users wrote: > > Recently my mailman3 instance stopped distributing mail. But mailman's > own mail (notification, digest etc) and archiving are working OK. I > couldn't figure what is going wrong > >>From mail.log > > --- > Dec 31 10:03:20 lists postfix/smtpd[10900]: Anonymous TLS connection > established from mail.xxxx.xx[5.79.72.163]: TLSv1.2 with cipher > ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits) > Dec 31 10:03:20 lists postfix/smtpd[10900]: Anonymous TLS connection > established from mail.xxxx.xx[5.79.72.163]: TLSv1.2 with cipher > ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits) > Dec 31 10:03:20 lists policyd-spf[10907]: prepend Received-SPF: Pass > (mailfrom) identity=mailfrom; client-ip=5.79.72.163; helo=mail.xxxx.xx; > envelope-from=abhijith(a)xxxx.xx; receiver=<UNKNOWN> > Dec 31 10:03:20 lists policyd-spf[10907]: prepend Received-SPF: Pass > (mailfrom) identity=mailfrom; client-ip=5.79.72.163; helo=mail.xxxx.xx; > envelope-from=abhijith(a)xxxx.xx; receiver=<UNKNOWN> > Dec 31 10:03:21 lists postfix/smtpd[10900]: 04C2412038F: > client=mail.xxxx.xx[5.79.72.163] > Dec 31 10:03:21 lists postfix/smtpd[10900]: 04C2412038F: > client=mail.xxxx.xx[5.79.72.163] > Dec 31 10:03:21 lists postfix/cleanup[10912]: 04C2412038F: > message-id=<f875c144-a23c-baa2-7de2-1b102d3e7494(a)xxxx.xx> > Dec 31 10:03:21 lists postfix/cleanup[10912]: 04C2412038F: > message-id=<f875c144-a23c-baa2-7de2-1b102d3e7494(a)xxxx.xx> > Dec 31 10:03:21 lists opendkim[450]: 04C2412038F: s=_teknikKey d=xxxx.xx > SSL > Dec 31 10:03:21 lists opendkim[450]: 04C2412038F: s=_teknikKey d=xxxx.xx > SSL > Dec 31 10:03:21 lists postfix/smtpd[10900]: disconnect from > mail.xxxx.xx[5.79.72.163] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 > commands=7 > Dec 31 10:03:21 lists postfix/smtpd[10900]: disconnect from > mail.xxxx.xx[5.79.72.163] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 > commands=7 > Dec 31 10:03:21 lists postfix/qmgr[13211]: 04C2412038F: > from=<abhijith(a)xxxx.xx>, size=1699, nrcpt=1 (queue active) > Dec 31 10:03:21 lists postfix/qmgr[13211]: 04C2412038F: > from=<abhijith(a)xxxx.xx>, size=1699, nrcpt=1 (queue active) > Dec 31 10:03:21 lists postfix/lmtp[10915]: 04C2412038F: > to=<test3(a)lists.yyyy.yy>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.87, > delays=0.62/0.02/0.04/0.2, dsn=2.0.0, status=sent (250 Ok) > Dec 31 10:03:21 lists postfix/lmtp[10915]: 04C2412038F: > to=<test3(a)lists.yyyy.yy>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.87, > delays=0.62/0.02/0.04/0.2, dsn=2.0.0, status=sent (250 Ok) > Dec 31 10:03:21 lists postfix/qmgr[13211]: 04C2412038F: removed > Dec 31 10:03:21 lists postfix/qmgr[13211]: 04C2412038F: removed Aside from the fact that every log message seems to appear twice, this is a normal interaction for an incoming message to test3(a)lists.yyyy.yy and delivered via lmtp to Mailman. Is there anything later in the Postfix log for an outgoing message? > I am not sure why 'postfix/qmgr[13211]: 04C2412038F: removed' is happening. Because Postfix has finished processing the message, has delivered it and has now removed it from the Postfix queue. > from /var/log/mailman3/smtp.log: > > Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) handling connection > Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) Data: b'LHLO lists.xxxx.xx' > Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) Data: b'MAIL > FROM:<abhijith(a)xxxx.xx>' > Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) sender: abhijith(a)xxxx.xx > Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) Data: b'RCPT > TO:<test3(a)xxxx.xx>' > Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) recip: test3(a)xxxx.xx > Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) Data: b'DATA' > Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) Data: b'QUIT' > Dec 31 10:03:21 2018 (6323) ('127.0.0.1', 48720) connection lost > Dec 31 10:03:21 2018 (6323) Connection lost during _handle_client() This again looks normal other than the fact that the recipient in the Postfix log is test3(a)lists.yyyy.yy and the recipient here is test3(a)xxxx.xx. Presumably this is just because you chose to mung the address differently in the two cases. > Here again I am doubtful about 'Connection lost during _handle_client()'. That's a red herring. Postfix has sent QUIT and one side or the other has disconnected before the response to QUIT was delivered. That's not a problem. This 'Connection lost during _handle_client()' message is a normal occurrence. It appears that Mailman has received the post. You say above "...archiving are working OK". Does this mean the received post was archived? If so, and it wasn't delivered, either there were no eligible recipients or something went wrong in the pipeline between to-archive and to-outgoing. Are there messages like Dec 31 10:03:xx 2018 (6323) <message-id> smtp to test3(a)xxxx.xx for n recips, completed in n.nn seconds Dec 31 10:03:xx 2018 (6323) <message-id> post to test3(a)xxxx.xx from test3-bounces(a)xxxx.xx, nnn bytes in /var/log/mailman3/smtp.log What's in /var/log/mailman3/mailman.log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 3 months

[MM3-users] Re: Can login at /admin, but cannot login at the account/login page.

by Abhilash Raj

> On Aug 15, 2021, at 11:33 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 8/14/21 9:34 PM, Stephen J. Turnbull wrote: >> I'm sorry, I'm in a "second vaccination" fog at the moment (mending >> but concentration lasts only about 10 minutes), so I'll answer what I >> know offhand since Abhilash is busy and Mark is probably offline for >> vacation by now. > > > Not quite, but very soon. > > >> pabsta(a)gmail.com writes: >> > However, if logout and attempt to login from the postorius website, >> > I get a « 502 bad gateway » error after roughly 30 seconds. The >> > logs in Systemctl for gunicorn register a "DIGEST-MD5 common mech >> > free" error message > > >> I would guess this is also just a connection drop because it doesn't >> receive the expected response within timeout. > > > I'm sure that's right. > > >> > and the nginx error logs just show a connection drop: >> > >> > 2021/08/12 18:11:09 [error] 26026#26026: *31 upstream prematurely closed connbection while reading response header from upstream, client: [ip redacted], server: >> > [domain redacted], request: "POST /accounts/login/ HTTP/2.0", upstream: "http://127.0.0.1:8006/accounts/login/", host: "[domain redacted]", referrer: "https://[domain redacted]/accounts/login/?next=/mailman3/lists/" >> a > > > I see in the above `upstream: "http://127.0.0.1:8006/accounts/login/",` but in your settings > > ACCOUNT_DEFAULT_HTTP_PROTOCOL = "https" > > > I suspect you may be getting a redirect from http to https which is losing POST data and you need to change > > proxy_pass http://127.0.0.1:8006; > > in your nginx configuration to > > proxy_pass https://127.0.0.1:8006; > > or set > > ACCOUNT_DEFAULT_HTTP_PROTOCOL = "http" > This configuration actually doesn’t really dictate connection related configs, but mostly, the protocol to use in the emails generated by django-allauth to verify email and such. It shouldn’t have affect on the problem IMO. > -- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- thanks, Abhilash Raj (maxking)

3 years, 8 months

[MM3-users] Re: Mailman3 on AlmaLinux 9 - Python3.9 errors

by Willie Castillo

I saw them. OK, I must be missing several steps. I'll have to start from scratch. Let me carefully follow the link you send me, it should work for Almalinux 9.4 right? We recommend installing Pypi packages in a virtualenv. Doc is at https://urldefense.us/v3/__https://docs.mailman3.org/en/latest/install/virt… [cid:92ffd146-5b65-4e46-a2f8-021ea40371e9] Willie Castillo Linux Systems Administrator, IT Department - Defense & Security CAE USA T. +1-813-885-7481 E. Willie.Castillo(a)caemilusa.com A. 4908 Tampa West Blvd, Tampa, Fl. 33634 cae.com CONFIDENTIALITY NOTICE This e-mail message is intended only for the above named recipient(s) and may contain information that is confidential. If you have received this message in error or are not the named recipient(s), please immediately notify the sender, delete this e-mail message without making a copy and do not disclose or relay this e-mail message to anyone. ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Thursday, July 18, 2024 2:55 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [NON-INTERNAL] [MM3-users] Re: Mailman3 on AlmaLinux 9 - Python3.9 errors [You don't often get email from mark(a)msapiro.net. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. On 7/18/24 11:12 AM, willie.castillo(a)caemilusa.com wrote: > Mark first let me thank you for your assistance with this. I don't believe I mentioned that this is a fresh/new installation I'm performing on an AlmaLinux 9.4 VM. I have searched everywhere for a solid Mailman installation on AlmaLinux document/process but, I haven't had any luck. I tried following documentation on this site and I only found this https://urldefense.us/v3/__https://docs.mailman3.org/en/latest/install/dist… . Did you see my post at https://urldefense.us/v3/__https://lists.mailman3.org/archives/list/mailman… We recommend installing Pypi packages in a virtualenv. Doc is at https://urldefense.us/v3/__https://docs.mailman3.org/en/latest/install/virt… -- 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://urldefense.us/v3/__https://lists.mailman3.org/mailman3/lists/mailma… Archived at: https://urldefense.us/v3/__https://lists.mailman3.org/archives/list/mailman… This message sent to willie.castillo(a)caemilusa.com ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: Outlook-2rvyqd2h.png Replaced multipart/alternative part with first alternative.

9 months

[MM3-users] Re: Mailman web Stopped working after upgrade

by David Krantz

Hi, I tried psycopg2-binary and a few other rehashes of that. Now I got it working by downloading the source for psycopg2 manually and building it myself, then I installed it into my venv like any other self-built package. https://pypi.org/project/psycopg2/#files I run mod_wsgi in Apache so I thought it should be enough to restart Apache. I am quite convinced that I did that (and for that matter restart the machine at a few points). But I might have been sloppy and reversed the order in the end when I got it running, this process is a bit to manual. I will use another solution when I rebuild the server one day. The problem with rebuilding the server is that I'd have to install a MTA with all its modules, milters, setups and what not, and mailman. To just reinstall on a fresh machine would be easy, the trick is that I want to rebuild some things in a better way which will take me some time. E.g. using a separate wsgi service and a more modern spam filter than Spamassassin. Otherwise it is easy. But my situation now is a bit short on time so if I can postpone that a bit I will. Thanks. // David // David On Tue, Mar 3, 2020 at 10:02 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > On 3/3/20 12:33 PM, David Krantz wrote: > > > > I think that this might be due to some kind of python misfeature where > > compiled code behaves slightly differently to interpreted code, that > > might explain the delay in it working initially before breaking. I > > have no idea of how to solve this. I have tried to uninstall and > > reinstlall psycopg2 in different versions without any luck. > > You need to activate your virtualenv and do > > pip install psycopg2-binary > > it must be psycopg2-binary, not just psycopg2. It's probably best to do > > pip uninstall psycopg2 > > first. > > As far as it working for a while, did you restart your wsgi service > (gunicorn, uwsgi, ??) after upgrading? > > -- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

5 years, 1 month

[MM3-users] Re: How to fix lists with characters errors?

by Helio Loureiro

Hi, Thanks a lot! Nice catch. It was indeed loading as latin-1. Not sure why, but that's a matter to discuss on the Ubuntu mailing list. Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro On Sun, 24 Mar 2024 at 01:07, Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/23/24 11:56, Helio Loureiro wrote: > > Hi, > > it is python 3.10. Problem is... some mailing lists were created long > ago, > > with python2 something. Most probably 2.5. And the tables on mysql were > > set to latin1. > > > This has nothing to do with the data or the charsets/collation in the > database. The issue is the locale setting in your python is causing > stdout output from the `mailman members` command to be encoded as > `latin1` and at least some user's display name contains a `\u0142` (i.e. > `ł` character. > > > > That I know. Question now is how to fix this. Any suggestion? What is > > the table? I probably can run some script for these specific lists that > > have the failure, import data as latim-1, and update back to the table as > > utf-8. > > That's not the issue. The issue is the Python in your venv has > sys.stdout.encoding set to latin1, probably for locale reasons. You ca > apply this patch > ``` > --- a/src/mailman/commands/cli_members.py > +++ b/src/mailman/commands/cli_members.py > @@ -17,6 +17,7 @@ > > """The 'members' subcommand.""" > > +import sys > import click > > from mailman.core.i18n import _ > @@ -30,6 +31,9 @@ from zope.component import getUtility > from zope.interface import implementer > > > +sys.stdout.reconfigure(encoding='utf-8') > + > + > def display_members(ctx, mlist, role, regular, digest, > nomail, outfp, email_only, count_only): > # Which type of digest recipients should we display? > ``` > to mailman/commands/cli_members.py to fix the issue. > > -- > 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://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 helio(a)loureiro.eng.br >

1 year

[MM3-users] Request Entity Too Large

by Christian Stalberg

Now mail sent to mm3 for distribution is not going out, for two different lists. The mailman.log shows this error: Oct 17 21:50:00 2021 (491) ACCEPT: <030601d7c3a0$ee342f20$ca9c8d60$(a)somedomain.com> Oct 17 21:50:04 2021 (488) HyperKitty failure on https://somedomain.net/archives/api/mailman/archive: <html> <head><title>413 Request Entity Too Large</title></head> <body bgcolor="white"> <center><h1>413 Request Entity Too Large</h1></center> <hr><center>nginx/1.14.2</center> </body> </html> (413) Oct 17 21:50:04 2021 (488) Exception in the HyperKitty archiver: <html> <head><title>413 Request Entity Too Large</title></head> <body bgcolor="white"> <center><h1>413 Request Entity Too Large</h1></center> <hr><center>nginx/1.14.2</center> </body> </html> Oct 17 21:50:04 2021 (488) Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman_hyperkitty/__init_ _.py", line 154, in _archive_message url = self._send_message(mlist, msg) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman_hyperkitty/__init_ _.py", line 210, in _send_message raise ValueError(result.text) ValueError: <html> <head><title>413 Request Entity Too Large</title></head> <body bgcolor="white"> <center><h1>413 Request Entity Too Large</h1></center> <hr><center>nginx/1.14.2</center> </body> </html> Please advise. TY. -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Saturday, October 16, 2021 11:21 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: FW: [Django] ERROR (EXTERNAL IP): Internal Server Error: /user-profile/ On 10/16/21 9:52 AM, Christian Stalberg via Mailman-users wrote: > When I go to https://.../admin/ I get a Django Administration screen > and in the upper right hand corner I see > > WELCOME, <username>. VIEW SITE / CHANGE PASSWORD / LOG OUT And my point was if you go to Users under Authentication and Authorization you should find that alekos.pantazis is a user. If you go to your own https://www.grizz.org/user-profile/ page, do you see a gravatar to the right of the Username, First name, Last name boxes, and does going there produce the same error in the logs. If that's all OK, then I don't know what produced the original error, but I think you can ignore it. If that produces the same error in the logs, then something is wrong with your django-mailman3 installation, but I don't know what. -- 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

3 years, 6 months

[MM3-users] Re: MM attaches mime-attachments to mail as text file since update to 3.3.8

by Stefan Bauer

Dear Mark, thank you for your time. Here are the lists settings and an example mail attached. Filter content: NO Filter types: EMPTY Pass types: EMPTY Pass extensions: EMPTY Collapse alterantives: YES Convert html to plaintext: NO Thunderbird is showing the mail "correct". Outlook does show the attachments as attachments. Thank you. Stefan Am Mi., 18. Jan. 2023 um 18:02 Uhr schrieb Mark Sapiro <mark(a)msapiro.net>: > On 1/17/23 23:45, Stefan Bauer wrote: > > Dear Users & Developers, > > > > we're running MM3 on Ubuntu 22 and used the venv-installation method. > > Last week we updated via¹ to > > > > Mailman Core-Version GNU Mailman 3.3.8 (Tom Sawyer) > > Mailman Core API-Version 3.1 > > Mailman Core Python-Version 3.10.6 (main, Nov 14 2022, 16:10:14) [GCC > > 11.3.0] > > > > and now mailman attaches mime-attachments to email as text-files. That > > breaks many mails in our environment. > > > > For example: Now we have attachments like > > > > smime.p7s + ATT000001.txt as well as what looks like MM footers > > "mailing list --- test@domain ... To unsubscripbe send an email to ..." > > > > How can we get the "old" processing back? > > I doubt this has anything to do with the upgrade per se. It has to do > with MIME multipart (in this case, signed) messages and how MM > headers/footers are added. The MM 2.1 FAQ article at > <https://wiki.list.org/x/4030707> has some info on this. > > In order to say more, I would need to see the list's settings for > Filter types, Filter extensions, Pass types, Pass extensions, Collapse > alternatives and Convert html to plaintext and the complete MIME > structure of the incoming message. > > -- > 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://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 cubewerk(a)gmail.com > ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

2 years, 3 months

[MM3-users] Re: nginx configuration on a multitasking server

by David Newman

On 12/10/21 4:48 PM, Mark Sapiro wrote: > On 12/10/21 3:22 PM, David Newman wrote: >> On 12/10/21 12:57 PM, Mark Sapiro wrote: >>> >>> Are you using uwsgi or some other wsgi server. >> >> uwsgi, per the venv and PDF docs. Thanks for the fix. >> >> Regarding the uwsgi_pass docs, would 'uwsgi_pass_header' directives >> replace the 'proxy_set_header' ones in the venv doc? >> >> Looking at the uwsgi doc, it seems they might do different things. > > > If you are using uwsgi and proxy_pass http://127.0.0.1:8000 is working > for you, then I'm satisfied that the docs are OK now and we don't need > to say anything about uwsgi_pass. > > > >> It's not the situation I have to deal with, though. Short of changing >> a long-standing URL, what I'm looking to do is have "/" continue to >> default to roundcubemail, and have users type in longer URLs for MM3 >> and other services. > > > I think you can set the document root to the roundcubemail root and then > set locations for the Mailman destinations as, e.g. > > location /mailman3/ { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > } > location /archives/ { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > } > location /accounts/ { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > } > location /admin/ { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > } > location /user-profile/ { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > } > > I haven't tried anything like this, so I'm not sure it will work, but I > think so. Update: The above worked fine until MM3 informed a list owner of pending subscription requests, with a URL like this: https://lists.example.com/mailman/admindb/listname and that URL returned a 404 error. Adding a stanza for 'location /mailman/' to the nginx config above clears the 404 error, but Postorius returns "Page not found" with no entry in the web or MM3 logs, and a 200 OK in the Nginx logs. I think the URL is supposed to go to the list page in Postorius. How to configure this so that list owners and moderators get a valid URL for list management? Thanks! dn

3 years, 4 months

[MM3-users] Re: Pck files stuck in out queue

by Lieuallen, Thomas Otis

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://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://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

2 months, 2 weeks

[MM3-users] Re: {Spam?} Server name in new account confirmation email

by Meehan, John

Thanks for your replies. From Mark's reply, and looking at django_allauth, the Subject of the confirmation email uses the site name from the django_site db table in brackets, but the URL in the message body comes from the HTTP header. Adding proxy_set_header Host $http_host before the proxy_pass line on the SSL proxy server solved the problem. ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Thursday, December 3, 2020 10:25 AM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: {Spam?} Server name in new account confirmation email On 12/3/20 9:26 AM, Meehan, John wrote: > Hi, when someone creates a new account (Sign Up), an email is sent to them to confirm their email address. It has the form below. Does anyone know how I can Caution (External, mark(a)msapiro.net<mailto:mark@msapiro.net>) Sensitive Content, First-Time Sender Details<https://shared.outlook.inky.com/details?id=Y29tbXNjb3BlL2pvaG4ubWVlaGFuQGNv…> Report This Email<https://shared.outlook.inky.com/report?id=Y29tbXNjb3BlL2pvaG4ubWVlaGFuQGNvb…> FAQ<https://www.inky.com/banner-faq/> Protection by INKY<https://www.inky.com> On 12/3/20 9:26 AM, Meehan, John wrote: > Hi, when someone creates a new account (Sign Up), an email is sent to them to confirm their email address. It has the form below. Does anyone know how I can change the server name in the URL (From server.example.com to something else)? I have an SSL proxy server that I want to direct users through. Thanks. - John This message comes from django_allauth. The domains come from the django_site database table. If you have Postorius >= 1.3.3 The Domains view will show you the SITE_ID for the domain and has an `Edit` link the the Django admin UI entry for that site. Otherwise, you can go to the Django admin `Sites` view and see the DOMAIN NAME and DISPLAY NAME for each defined site, and you can edit the domain name. You may also need to adjust the SITE_ID setting in your Django settings to match the site you want. The trick here is the SITE_IDs aren't displayed in the Django admin UI or in Postorius < 1.3.3, and they may not be sequential or start at 1. If you query the database with `SELECT * FROM django_site;` you'll see entries with columns id, domain and name which will tell you the SITE_ID. -- 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://secure-web.cisco.com/1FBkrl8Fna83jeBpMzhcS-TGdx6ALOyBwi0uCPsqGDtm9J…

4 years, 4 months

[MM3-users] Re: content filtering in version 3.1

by Simon Handfield

Thanks for your quick reply, Mark. I see, I've retried without the -l switch and the shell returns without error. The --help switch returns: # mailman shell --help usage: mailman shell [-h] [-i] [-r RUN] [--details] [LISTNAME] positional arguments: LISTNAME The 'fully qualified list name', i.e. the posting address of the mailing list to inject the message into. This can be a Python regular expression, in which case all mailing lists whose posting address matches will be processed. To use a regular expression, LISTNAME must start with a ^ (and the matching is done with re.match(). LISTNAME cannot be a regular expression unless --run is given. Thanks once again, Simon. ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, 12 May 2021 14:22 To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: content filtering in version 3.1 On 5/11/21 8:45 PM, Simon Handfield via Mailman-users wrote: > Hi everyone, > > I'm sorry to resurrect this thread from so long ago but it appeared to provide exactly the answer I was looking for, trying to manage pass_types in 3.1.1 on Ubuntu 18.04. > > GNU Mailman 3.1.1 (Between The Wheels) > > Unfortunately when I run: > > ./bin/mailman shell -l [list address] > > I receive: > > usage: mailman [-h] [-v] [-C CONFIG] > {help,aliases,conf,create,digests,import21,info,inject,lists,members,qfile,remove,reopen,restart,shell,start,status,stop,unshunt,version,withlist} > ... > mailman: error: unrecognized arguments: -l > > Can anyone advise how I can use the -l switch to manage this setting for a list? Older versions of Mailman core did not support the -l/--listspec option for mailman shell. They expected the listname as an argument as in ``` mailman shell list(a)example.com ``` What does ``` mailman shell --help ``` show in your case? -- 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://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… _ [State Library of NSW]<https://www.sl.nsw.gov.au/> Simon Handfield Desktop and Infrastructure Leader simon.handfield(a)sl.nsw.gov.au<mailto:simon.handfield@sl.nsw.gov.au> +61 2 9273 1535 Macquarie Street, Sydney NSW 2000, Australia www.sl.nsw.gov.au<https://www.sl.nsw.gov.au/> This message is intended for the addressee named and may contain confidential information. If you are not the intended recipient, please delete it and notify the sender. Views expressed in this message are those of the individual sender, and are not necessarily the views of their organisation.

3 years, 11 months

[MM3-users] Re: Multi-domain oddities in Hyperkitty and Postorius

by Mark Sapiro

On 2/15/23 07:52, Jeremy Stanley wrote: > > Thanks, I'm still doing my best to wrap my brain around how Django > uses database migrations to create sites (seems like a very strange > use of a migration, I'm only accustomed to seeing them applied for > database schema updates). I don't think it does. There are a couple of migrations at django/contrib/sites/migrations, but these are only the initial creation of the model and an update to make the domain field unique. Why do you think it creates sites in this way. > Once I work out how to script site > creation, I'm still not completely finding the explanations I need > for how to map them to domains in Mailman though. > > The Mailman documentation about domains says "Domains are how > Mailman interacts with email host names and web host names" but > doesn't actually go on to say (that I can find anywhere) how it > actually associates them. Mailman core doesn't associate domains with Django sites. Mailman core knows nothing about a web UI. The association between Mailman core domains and Django sites is via Postorius. It doesn't exist in Mailman core. When Postorius sees a new domain from core, it assigns it a web_host based on the current web host accessing Postorius. > I can see in the API docs that a POST to > the domains endpoint will create a new domain with a specific > mail_host FQDN, but there's some association somewhere of that to a > web host (Django site), right? No. The only association is if Postorius is creating the domain in core, vs something else creating it via the REST API, Postorius will assign it a web_host in it's own Domain model, and that web host must be an existing Django site, which is only created via Django. > How is that set or manipulated > through the API? Or is that something which has to be set directly > in Django's data structures instead? Yes, A new site has to be created in Django. Even Postorius doesn't do that. > To recap, on creation of a mailing list server I want to populate it > automatically with multiple lists on different domains and have > dynamic SITE_ID=0 domain guessing performed so that the correct site > name and list filtering is performed depending on which domain name > is used in a URL the client requests. I believe I need to have the > automation perform the following steps: > > 1. Instantiate the Mailman installation and run initial migrations > with SITE_ID=1 in order to avoid the problem mentioned in the docs > about not using SITE_ID=0 until the tables have been populated, then > switch the settings.py to use SITE_ID=0 once done. > > 2. Create the individual sites I need in Django (Mailman web hosts) > by creating and applying database migrations. No. You create the sites via Django, but not by creating and applying database migrations. > 3. Create the individual domains I need in Mailman (Mailman mail > hosts) through its REST API. > > 4. "Somehow" tell Mailman (or Django?) which mail hosts correspond > to what web hosts. Neither Mailman nor Django. It's Postorius which maintains the relationship between Django sites which it calls web_hosts and domains. > As I said, I'm still trying to understand how to make step 2 happen > (Django has a steep learning curve for me), but beyond that I'm > unsure how to do step 4 at all. I can do all of this through the > WebUI of course, and have confirmed that it works as expected when I > do, I'm just trying to work out the automation so that our other > sysadmins don't have to perform these steps by hand the next time we > need to rebuild the server. Step 2. $ django_admin shell ``` >>> from django.contrib.sites.models import Site >>> new_site = Site(id=5, domain='5.example.com', name='display_name') >>> new_site.save() ``` Of course the values are up to you and you can omit the id= to have Django assign the first available.. Once you've done step 2, you need to create a domain in Postorius. Look at the code behind Postorius add new domain. Or you can create the domain in core via REST, but you then have to modify it in Postorius to associate the correct site. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: Bulk delivery status change?

by Stephen Daniel

If I run >>> for mlist in getUtility(IListManager): ... print(mlist) ... <mailing list "testlist1(a)chapelwoodhoadev.org" at 0x7f83f593fba8> I get only one list. Permissions? Where are the other lists? On Sun, Nov 10, 2024 at 11:52 AM Stephen Daniel <swd(a)pobox.com> wrote: > OK. Ran the script. No errors while running it, but when I look at the > users through Postorius GUI, they still show as 'Disabled by Bounces' > > ?? > > On Sun, Nov 10, 2024 at 11:42 AM Stephen Daniel <swd(a)pobox.com> wrote: > >> Thanks all! I will use these pronto. >> >> On Sun, Nov 10, 2024 at 11:42 AM Mark Sapiro <mark(a)msapiro.net> wrote: >> >>> On 11/10/24 08:34, Odhiambo Washington via Mailman-users wrote: >>> > On Sun, Nov 10, 2024 at 7:16 PM Stephen Daniel <swd(a)pobox.com> wrote: >>> > >>> >> Mistakes were made, and for while every single outbound email bounced. >>> >> I've fixed the mistakes, but now in my largest and most active email >>> list, >>> >> every single user's delivery status is "Disabled by Bounces". >>> >> >>> >> Is there a way to bulk fix this? Or do I have to go into each user, >>> one at >>> >> a time, and fix them? >>> > >>> > Please see this thread: >>> > >>> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >>> >>> The script in that post does all lists. For a single list see >>> >>> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >>> but note that the command line >>> ``` >>> $ shell -l list(a)example.com >>> ``` >>> should be >>> ``` >>> $ mailman shell -l list(a)example.com >>> ``` >>> >>> -- >>> 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://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 swd(a)pobox.com >>> >>

5 months, 1 week

[MM3-users] Re: Running mailman3 on AWS and dealing with SES email verification

by Mohsen Masoudfar

Thank you Mark, this is really very helpful. I am going to work on the details. It would be breat, if there were a way to set some of this options as default, like DMARC mitigation is default to no, I changed it to unconditionally and replace From to with list address and got good results, but the default is no. How may I changed the default, do that the list owner/creator does not need to update these fields. Thanks Mohsen -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Thursday, April 30, 2020 1:15 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Running mailman3 on AWS and dealing with SES email verification [EXTERNAL EMAIL] On 4/30/20 9:25 AM, Mohsen Masoudfar wrote: > Hi, > > This seems to be a very basic question and/or issue, but I could not find a reliable for it: > > Assume a list member with the email address like (just as an example) > joe.student(a)university.edu sends an email to a list, Mailman gets the > email, processes it and would try to send that email to all members > with a sender field as: 'joe.student(a)university.edu'. plus > listname(a)listserver.TLD Are you referring to the envelope sender or to the From: header? The envelope sender will be listname-bounces(a)listserver.TLD or if VERP is enabled, listname-bounces+recipient=recipient.domain(a)listserver.TLD. The From: header will be unchanged from the incoming message. If yo want the From: to be the list, you can apply DMARC "Replace From with list address" unconditionally and the From: will look like From: joe.student via listname <listname(a)listserver.TLD> ... > I found some solution: > > > * Asking the members to add their email to the signature > * manipulating the from field and add the name of the sender as a comment, not that easy, needs some Python code > * manipulating the from files and replacing the @ with something else, not that easy, needs some Python code > * . . . The DMARC mitigations will do these thing for you. > More important: None of these would allow a simple click on the reply bottom to send the email to the original sender. And they will add the poster's original From: address to Reply-To: -- 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…

4 years, 11 months

[MM3-users] Re: MTA setup

by Arte Chambers

I'm not sure how to check mailmans shunt queue. I'm not seeing any errors in mailman logs There are several .pck files in Mailman's var/archives/hyperkitty/spool/ I can send email from the server using mail utilities as long as the "from email address" contains the server's domain name. I also notice that in this MM3-Users list the "from" email shows senders(a)emailaddress.com VIA mailman3.org. I'm wondering if I've missed something that would allow my server to behave this way. Thank you, Paul 'Arte Chambers' Robey 502-408-6922 On Sun, Nov 17, 2024 at 11:31 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 11/17/24 19:32, Arte Chambers via Mailman-users wrote: > > > > Mailman is successfully sending invite emails however user messages sent > to > > the list are not being sent to subscribers. Also in Hyperkitty none of my > > test messages to the list are showing up in the archive. > > > Are there messages in Mailman's shunt queue? Check for errors in > mailman.log. Are there messages for hyperkitty queued in Mailman's > var/archives/hyperkitty/spool/ directory? > > > I am using Postfix with an SMTP relay hosted at Brevo.com (formally > > sendinblue). Brevo's logs show the message getting rejected > > > > > > Log from brevo.com (SMPT Relay) > > Sent on 17-11-2024 21:49:16 > >>From listmember(a)gmail.com > > To listmember(a)gmail.com > > Message ID<CAPesOD1y0fEaG=GFodz=Lgs1m_hqRErPnQcpXCNtKsBbJ= > > BJ7Q(a)mail.gmail.com> > > > > 17-11-2024 21:49:16 > > Sending has been rejected because the sender you used > listmember(a)gmail.com > > is not valid. Validate your sender or authenticate your domain > > > This appears to be something you need to do for the MTA at > smtp-relay.sendinblue.com, or possibly something more is needed in > /etc/postfix/sasl_passwd. > > > #SMPT Relay Brevo > > relayhost = [smtp-relay.sendinblue.com]:587 > > smtp_sasl_auth_enable = yes > > smtp_sasl_security_options = noanonymous > > smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd > > > -- > 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://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 paul.m.robey(a)gmail.com >

4 months

[MM3-users] Re: Mailman REST API not available. Please start Mailman core.

by Christian

That worked. Now on https://docs.mailman3.org/en/latest/install/virtualenv.html#starting-mailman -automatically it says "Pay attention to the config file output above and make sure that you see /etc/mailman3/mailman.cfg there. If the config path is different, you should make sure to create a new config file at /etc/mailman3/mailman.cfg and re-run the command." Well...mailman info yields GNU Mailman 3.3.5 (Tom Sawyer) Python 3.7.3 (default, Mar 23 2024, 16:12:05) [GCC 8.3.0] config file: /opt/mailman/mm/mailman.cfg db url: postgres://mailman:5DqTHnv8hUQSdd@localhost/mailman devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:restpass Should I create a new config file at /etc/mailman3/mailman.cfg ? Lastly, when I ran this command it says "loaded failed failed" (venv) mailman@lists:/opt/mailman/mm$ systemctl list-units | grep -i mailman gunicorn.service loaded active running GNU Mailman web interfaces ● mailman.service loaded failed failed GNU Mailing List Manager Please advise. Thank you. -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, February 12, 2025 10:33 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Mailman REST API not available. Please start Mailman core. On 2/12/25 09:24, Christian via Mailman-users wrote: > Running Debian 4.19.316-1 > Python 3.7.3 > > I am unable to start mailman core > > > mailman@lists:~$ /opt/mailman/mm/bin/mailman start > Usage: mailman start [OPTIONS] > Try 'mailman start -h' for help. > > Error: A previous run of GNU Mailman did not exit cleanly > (stale_lock). Try using --force mailman@lists:~$ > > > I try using --force and it did not work. So how do I start it? In Mailman's var/locks directory (maybe /opt/mailman/mm/var/locks/) you will see at least two files. The ones of interest are: ``` master.lck master.lck|<host_name>|<pid>|<random_integer> ``` First verify that pid is not running or if it is, that it's not Mailman's `master` process. Then remove all the files from the var/locks/ directory and Mailman should start. > Bottom line: I would like for Mailman core to start when I reboot the > server. How can this be achieved please? See https://docs.mailman3.org/en/latest/install/virtualenv.html#starting-mailman -automatically -- 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/ LV5WTFTNRZ455KPDESRQHFV67SJ5VOFH/ This message sent to csa(a)web-analysts.net

2 months, 1 week

[MM3-users] Re: I have issue where it does not send emails on to people in the list I create.

by Mark Sapiro

On 4/30/20 8:30 AM, john_warland(a)hotmail.com wrote: > Hello, > > I am quite new to Mailman3 and have been trying to get a working local test setup on a single VM (Centos07) > > I have issue where if I send an email to the list. it does not send emails on to the people subscribed to that list. > > Note the steps below were put together from memory after a few days of repeatably trying different things so there will be some inaccuracies > > > I have mailman running on same local box as postfix, postorius and hyperkitty. > > I have root as the superuser in Postorius and have tried the following: > > In unix shell created new user 'developer' > In unix shell created new user 'tester' > > In shell send an email from developer user to tester: > echo 'Hello' | mailx -s 'Hello Subject line' tester(a)sandbox.mytest.com > > Confirmed user tester received email in cat /home/tester/Maildir/new/ folder: > > Return-Path: <developer(a)cloud7.sandbox.mytest.com> > X-Original-To: tester(a)cloud7.sandbox.mytest.com > Delivered-To: tester(a)cloud7.sandbox.mytest.com > Received: by cloud7.sandbox.mytest.com (Postfix, from userid 1000) > > In Postorius web frontend: > > Signed up as root > Received confirmation email in /root/Maildir/new/ folder so cut and pasted the Url in the email to activate account. > Created new list called testlist(a)sandbox.mytest.com > Logged out > > Signed up as tester > Received confirmation email in /home/tester/Maildir/new/ folder so cut and pasted the Url to activate account. > Subscribed tester to the testlist. > > Next in unix shell su as developer and send an email to testlist(a)sandbox.mytest.com > > The root user gets the following email > > Content-Transfer-Encoding: 7bit > Subject: Your message to testlist(a)cloud7.sandbox.mytest.com awaits moderator approval > From: testlist-bounces(a)cloud7.sandbox.mytest.com > To: developer(a)cloud7.sandbox.mytest.com > Message-ID: <158824480291.3035.17408340520496115243(a)localhost.localdomain> > Date: Thu, 30 Apr 2020 11:06:42 +0000 > Precedence: bulk > X-Mailman-Version: 3.3.0 > > Your mail to 'testlist(a)cloud7.sandbox.mytest.com' with the subject > > hello there 2 > > Is being held until the list moderator can review it for approval. > > The message is being held because: > > The message is not from a list member > > Either the message will get posted to the list, or you will receive notification of the moderator's decision. > > Once I have gone back into Postorius as root and approved the message, root user gets a second email: > > Return-Path: <testlist-bounces(a)cloud7.sandbox.mytest.com> > X-Original-To: root(a)cloud7.sandbox.mytest.com > Delivered-To: root(a)cloud7.sandbox.mytest.com > Received: from localhost.localdomain (localhost [IPv6:::1]) > by cloud7.sandbox.mytest.com (Postfix) with ESMTP id E056A84CE4 > for <root(a)cloud7.sandbox.mytest.com>; Thu, 30 Apr 2020 11:09:10 +0000 (UTC) > Received: by cloud7.sandbox.mytest.com (Postfix, from userid 1000) > id 8F1B684CE4; Thu, 30 Apr 2020 11:06:41 +0000 (UTC) > Date: Thu, 30 Apr 2020 11:06:41 +0000 > To: testlist(a)cloud7.sandbox.mytest.com > User-Agent: Heirloom mailx 12.5 7/5/10 > MIME-Version: 1.0 > Message-Id: <20200430110641.8F1B684CE4(a)sandbox.mytest.com> > From: developer(a)cloud7.sandbox.mytest.com > X-MailFrom: developer(a)cloud7.sandbox.mytest.com > X-Mailman-Rule-Hits: nonmember-moderation > X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation > Message-ID-Hash: FAPTJKJRZG2ELSOSBRBIDOBWXP3Y5QAY > X-Message-ID-Hash: FAPTJKJRZG2ELSOSBRBIDOBWXP3Y5QAY > X-Mailman-Approved-At: Thu, 30 Apr 2020 11:09:10 +0000 > X-Mailman-Version: 3.3.0 > Precedence: list > > Subject: [Testlist] hello there 2 > > List-Id: A test list <testlist.sandbox.mytest.com> > List-Help: <mailto:testlist-request@sandbox.mytest.com?subject=help> > List-Post: <mailto:testlist@sandbox.mytest.com> > List-Subscribe: <mailto:testlist-join@sandbox.mytest.com> > List-Unsubscribe: <mailto:testlist-leave@sandbox.mytest.com> > Content-Type: text/plain; charset="us-ascii" > Content-Transfer-Encoding: 7bit > > A test email 2 > _______________________________________________ > Testlist mailing list -- testlist(a)sandbox.mytest.com > To unsubscribe send an email to testlist-leave(a)sandbox.mytest.com > > > At no point does the email appear in the tester(a)sandbox.mytest.com Maildir Why does root get the list post? Is root also a member of the list. What's in logs? Mailman's logs and the MTA logs > > Configs as follows.. tl;dr and mostly irrelevant. What do the following shell commands show mailman members testlist.sandbox.mytest.com mailman members -r testlist.sandbox.mytest.com mailman members -n any testlist.sandbox.mytest.com -- 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

[MM3-users] Re: unrequested unsubscription

by Mike Wertheim

Thanks. Here are the log lines that correspond to the emails to the "-leave" address in /var/log/mailman3/smtp.log... Jun 14 10:10:29 2023 (199628) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Jun 14 10:10:29 2023 (199628) Peer: ('127.0.0.1', 35610) Jun 14 10:10:29 2023 (199628) ('127.0.0.1', 35610) handling connection Jun 14 10:10:29 2023 (199628) ('127.0.0.1', 35610) Data: b'LHLO mydomain.com ' Jun 14 10:10:29 2023 (199628) ('127.0.0.1', 35610) Data: b'MAIL FROM:< someone-i-know(a)gmail.com>' Jun 14 10:10:29 2023 (199628) ('127.0.0.1', 35610) sender: someone-i-know(a)gmail.com Jun 14 10:10:29 2023 (199628) ('127.0.0.1', 35610) Data: b'RCPT TO:< mylist-leave(a)mydomain.com>' Jun 14 10:10:29 2023 (199628) ('127.0.0.1', 35610) recip: mylist-leave(a)mydomain.com Jun 14 10:10:29 2023 (199628) ('127.0.0.1', 35610) Data: b'DATA' Jun 14 10:10:29 2023 (199628) ('127.0.0.1', 35610) Data: b'QUIT' Jun 14 10:10:29 2023 (199628) ('127.0.0.1', 35610) connection lost The IP address is 127.0.0.1. Would that imply that the messages were really sent from the localhost, or could that mean that the real sender IP address just wasn't captured for some reason? On Wed, Jun 14, 2023 at 8:29 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/14/23 19:40, Mike Wertheim wrote: > > I have a Mailman 3 email list, running on Mailman 3.3.3 on Debian 11. > > > > A few of the list members are reporting that they received Email Address > > Unsubscription Confirmation emails, but claim that they never requested > to > > be unsubscribed. (All are Gmail users. but they might be coincidental, > > since most list members are Gmail users.) > > > > Has anyone seen this behavior before? Any ideas on what might be > happening? > > > Yes. This is someone sending an email `leave` or `unsubscribe` command > for the user in question. This may be malicious, i.e. someone doesn't > like a user's posts and tries to unsubscribe them, or it may be just > spam of some sort. > > the user should just ignore the email. Beyond that, there's not much you > can do unless you can identify from mail logs the source of the requests. > > -- > 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://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 mike.wertheim(a)gmail.com >

1 year, 10 months

[MM3-users] Re: Splitting hosts: mta&core vs postorius

by Mark Sapiro

On 6/22/20 12:23 PM, Ruth Ivimey-Cook wrote: > >> I agree with this, we need a setting for which interface for Gunicorn >> to listen on, and what Mailman Core sends out in the self_link >> attribute when responding to REST requests. >> > Exactly! :-) Except if there were a `bind_host` setting to specify the host to bind the REST API to and you set that to `0.0.0.0` you would have exactly what leads to the situation below, so we need to understand what's happening there (although I think I do - see below). On 6/22/20 12:21 PM, Ruth Ivimey-Cook wrote: > > I did try with the gunicorn patch Mark mentioned (host = "0.0.0.0") and > changing the cfg file hostname back to the full name of the host, and > that now works!! -- in that the problem I showed earlier is gone. > > > However I then get another issue. From the mailman.log file I now see in > the last few lines. For clarity I've numbered them like this "{1}": > > {1} [22/Jun/2020:00:58:24 +0000] "GET /3.1/domains HTTP/1.1" 200 320 "-" > "GNU Mailman REST client v3.3.1" > {2} [22/Jun/2020:00:58:24 +0000] "GET /3.1/domains/ch-bc.org.uk > HTTP/1.1" 200 215 "-" "GNU Mailman REST client v3.3.1" > {3} [22/Jun/2020:00:58:24 +0000] "GET > /3.1/domains/greyarea-web1.cam.ivimey.org/lists?advertised=true&count=0&page=1 > HTTP/1.1" 404 26 "-" "GNU Mailman REST client v3.3.1" > > At this point the browser screen reports "Something went wrong" and the > message "HTTP Error 404: {"title": "404 Not Found"}" Tracebacks would really help. You should be able to find them in the log configured as LOGGING['handlers']['file']['filename'] in your Django settings. > Previously, the process stopped at line {1}. Now that and line {2} is > executed (AFAIK) correctly, but then line {3} is isssued. I have no idea > why something is looking for "domains/greyarea-web1": > > - Only the "ch-bc.org.uk" domain is listed in the reply to line {1}, as > expected; Go to your Django admin web UI and look at your Django Mailman 3 Mail domains. This will be at a URL like https://greyarea-web1.cam.ivimey.org/admin/django_mailman3/maildomain/ Do you see this domain there? If so, delete it. > - "greyarea-web1" doesn't appear in any lists I can show with the > "mailman" cli command (and I think I tried them all); But that's looking at Mailman core which is not where Postorius is getting this list. > - "greyarea-web1" doesn't appear anywhere in the source or config other > than as the name of the host its running on or as an ALLOWED_HOST; > > - I tried using "curl -X DELETE" (from the api docs) to delete a domain > called that and it says no such list exists. Again, you're talking to core, not Django. > My only possible clue is that I think, at some point in the journey of > configuring mailman, I might have created a list called that on the > host. However since then I have wiped the install files and reinstalled. > I cannot make sense of this being the answer given the checks just listed. Did you wipe the database on greyarea-web1? > I went looking through the python source and can see that the get() > function does indeed throw a 404 exception if the domain isn't found, > but I cannot see which code is parsing the reply from the first line > > So I have two questions: > > 1) How can I fix this problem? See above. > 2) why does getting an 404 reply here cause the postorius web page to > produce a "something went wrong" /404 and nothing else, when it could > have simply reported that something had gone wrong with one specific > domain; Because the code isn't robust enough :( ... > Ideally, and this is icing on the cake, a listen address specification > should allow multiple IPs to be passed in, in which case the server > listens on all of them. I expect the python libraries already support this. We could implement a bind_address setting that would pass to gunicorns --bind parameter anything acceptable to gunicorn, although multiple values are tricky as they apparently require multiple -b/--bind options and a single -b/--bind doesn't support a list of values. But, I'm not convinced that this is something anyone needs. I'm still waiting for a response to <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

[MM3-users] Re: Handling of SPAM mails in mailman3 - Check for X-Spam Header

by Torge Riedel

Am 18.01.20 um 19:38 schrieb Mark Sapiro: > On 1/18/20 6:58 AM, Torge Riedel wrote: >> Am 16.01.20 um 21:43 schrieb Mark Sapiro: >>> This won't work for posts from members because the header checks are >>> done between member moderation checks and non-member moderation checks, >>> but if you create a Header Filter for header 'x-spam' and pattern 'yes' >>> with action hold, a message from a non-member which has an X-Spam: Yes >>> header should be held for that reason. >>> >>> >> Hi Mark, >> >> thank you for your answer. Just to understand that right: In case a >> posting with an "X-Spam: Yes" header comes from a member, it will not be >> held? It will be directly forwarded to the list? > No. I apologize for being unclear. > > A post from a member will first be handled according to that member's > moderation action which may be the list's default action for posts from > members or a specific action for that member. > > If that moderation action is reject, discard or hold, the post will be > rejected, discarded or held as a moderated member post regardless of any > header filters. > > If the action is accept, the post will be accepted without any further > checks including the header checks. > > If the action is defer (default processing) the message will be held for > matching the X-Spam: Yes header. > > What I meant was if the member's (or default) action was hold, the post > would be held, but the reason would be moderated member, not header match. > > The bottom line here is the moderation action of accept should only be > used in cases of a highly trusted member (such as a list owner) because > it bypasses other checks, but the address is still subject to spoofing. > In the normal case where a moderation hold is not desired, use the defer > (default processing) action. > Hi Mark, thanks for clarification. I will add a header filter. One final question: When adding a new header filter I can select between different actions. And there is one named "Default Anti-Spam action" (roughly translated from German). I cannot find anything else about this somewhere else in the settings (Postorius). So what it is the "Default Anti-Spam action"? Best regards Torge

5 years, 3 months

[MM3-users] Re: How to delete non-users

by Mark Sapiro

On 9/16/22 16:40, Allan Hansen wrote: > Hi Mark, > > Thank you for looking into it. > > We are very strict about memberships, which we are because of spam, bots and malicious contributors and because we don't want anyone to think that our lists are used for spam: > > When a user applies, the server sends a message to the moderator. > The moderator communicates with the potential member and accepts or does not accept the application. So Subscription policy is Moderate or Confirm, then moderate. > At this point, if the user has not been accepted, but tried to send a message to the list, a non-member membership is created. Yes. This is expected. > When he/she logs in to list his/her account, the list to which he/she holds non-memberships will be listed and the user will think that he/she has been properly subscribed (why else are the lists listed). I'm guessing you are talking about the https://www.example.com/mailman3/accounts/subscriptions/ page. On that page, all membership roles (owner, moderator, member, nonmember) are listed. Note that if the user goes instead to info page for the list, appropriate pronoun will be presented with a subscribe form. > Noone notices the column that shows the role as 'nonmember.' So he/she thinks that the subscription request has been accepted, but nothing is working. That's why the 'non-member' record is an issue. I also don't see why non-members are automatically added, filling up the database with junk (at least from our point of view, with all respect). That's the way Mailman 3 is designed. Changing it would be a major undertaking. Consider the case where default nonmember action is hold rather than discard. Then when handling a nonmember post, the moderator can set the nonmember's moderation to default processing to essentially accept future posts from that nonmember if the nonmember has a legitimate reason to post, or to discard if the nonmember is a spammer. If you think it would help, you might consider colorizing the roles on that page so perhaps nonmember could be in red. This should be a simple patch to Postorius. > But our lists don't accept messages from non-members. Such messages are quietly discarded, as most are spam, as mentioned above. > So now the user is neither getting emails from the lists nor is unable to send messages to the list. > The next step for the user is to complain to me. ☹ Why didn't you (or the moderator) accept the held subscription at the beginning? > I have looked for a template that could be used to warn someone when he/she is added as a non-member, but did not find one. It's also not clear that I'd want one, as most of these non-subscriptions are by spammers and I prefer not to reply to spammers. __ > > I tried your suggestion below, Mark. > Here's my transcript: > > ********** > Welcome to the GNU Mailman shell > Use commit() to commit changes. > Use abort() to discard changes since the last commit. > Exit with ctrl+D does an implicit commit() but exit() does not. > >>>> lm = getUtility(IListManager) >>>> for l in lm: > ... for nm in l.nonmembers.members: > ... nm.unsubscribe() > ... >>>> > ********** > I did this twice, once with commit() and once typing ctrl/d (ctrl/D) just gave me a beep. > Calling commit() did not return to the ... as in your example, but showed the >>> prompt, so I tried ctrl/D (beep) and then ctrl/d (exit). My example did not show a `...` in response to commit(). Commit() was followed by three backticks which is markup for the end if the literal text. The >>> following commit() is expected. Either calling commit() explicitly or exiting with ctrl-D should commit the changes. > I then went to the Postorius page for one of the lists and found that all the non-members were still present. I don't know why this would be. I tested that script and it worked for me. My original point is the presence of a nonmember role should not prevent the user from subscribing. If there is an issue with subscribing it is probably because of the outstanding subscription request waiting moderator approval. I understand that you would like the nonmember role to disappear, but that isn't going to happen in the distribution, and I can't undertake the extensive effort required to figure out how you can do it for your site. -- 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

[MM3-users] Re: Intermittent: pymysql.err.InternalError: Packet sequence number wrong - got 102 expected 77

by Mark Sapiro

For anyone who's interested, here's a reformatted version of the traceback. ``` > Full log follows: > [2021-05-23 07:31:45 +0200] [8244] [ERROR] Error handling request /3.1/lists?advertised=true&count=10&page=1 > Traceback (most recent call last): > File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1284, in _execute_context > cursor, statement, parameters, context > File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/default.py", line 590, in do_execute > cursor.execute(statement, parameters) > File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/cursors.py", line 170, in execute > result = self._query(query) > File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/cursors.py", line 328, in _query > conn.query(q) > File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 517, in query > self._affected_rows = self._read_query_result(unbuffered=unbuffered) > File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 732, in _read_query_result > result.read() > File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 1082, in read > self._read_result_packet(first_packet) > File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 1151, in _read_result_packet > self._get_descriptions() > File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 1222, in _get_descriptions > field = self.connection._read_packet(FieldDescriptorPacket) > File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 671, in _read_packet > % (packet_number, self._next_seq_id)) > pymysql.err.InternalError: Packet sequence number wrong - got 102 expected 77 > > The above exception was the direct cause of the following exception: > > Traceback (most recent call last): > File "/opt/mailman/core/venv/lib/python3.6/site-packages/mailman/database/transaction.py", line 50, in wrapper > rtn = function(*args, **kws) > File "/opt/mailman/core/venv/lib/python3.6/site-packages/mailman/rest/wsgiapp.py", line 193, in __call__ > return super().__call__(environ, start_response) > File "falcon/api.py", line 274, in falcon.api.API.__call__ > File "falcon/api.py", line 269, in falcon.api.API.__call__ > File "/opt/mailman/core/venv/lib/python3.6/site-packages/mailman/rest/lists.py", line 322, in on_get > resource = self._make_collection(request) > File "/opt/mailman/core/venv/lib/python3.6/site-packages/mailman/rest/helpers.py", line 172, in _make_collection > request, self._get_collection(request)) > File "/opt/mailman/core/venv/lib/python3.6/site-packages/mailman/rest/helpers.py", line 167, in _paginate > return list_start, total_size, collection[list_start:list_end] > File "/opt/mailman/core/venv/lib/python3.6/site-packages/mailman/utilities/queries.py", line 42, in __getitem__ > return self._query[index] > File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/orm/query.py", line 3149, in __getitem__ > return list(res) > File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/orm/query.py", line 3481, in __iter__ > return self._execute_and_instances(context) > File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/orm/query.py", line 3506, in _execute_and_instances > result = conn.execute(querycontext.statement, self._params) > File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1020, in execute > return meth(self, multiparams, params) > File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/sql/elements.py", line 298, in _execute_on_connection > return connection._execute_clauseelement(self, multiparams, params) > File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1139, in _execute_clauseelement > distilled_params, > File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1324, in _execute_context > e, statement, parameters, cursor, context > File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1518, in _handle_dbapi_exception > sqlalchemy_exception, with_traceback=exc_info[2], from_=e > File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/util/compat.py", line 178, in raise_ > raise exception > File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/base.py", line 1284, in _execute_context > cursor, statement, parameters, context > File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/default.py", line 590, in do_execute > cursor.execute(statement, parameters) > File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/cursors.py", line 170, in execute > result = self._query(query) > File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/cursors.py", line 328, in _query > conn.query(q) > File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 517, in query > self._affected_rows = self._read_query_result(unbuffered=unbuffered) > File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 732, in _read_query_result > result.read() > File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 1082, in read > self._read_result_packet(first_packet) > File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 1151, in _read_result_packet > self._get_descriptions() > File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 1222, in _get_descriptions > field = self.connection._read_packet(FieldDescriptorPacket) > File "/opt/mailman/core/venv/lib/python3.6/site-packages/pymysql/connections.py", line 671, in _read_packet > % (packet_number, self._next_seq_id)) > sqlalchemy.exc.InternalError: (pymysql.err.InternalError) Packet sequence number wrong - got 102 expected 77 [SQL: SELECT mailinglist.list_id AS mailinglist_list_id, mailinglist.preferred_language AS mailinglist_preferred_language, mailingli$ FROM mailinglist WHERE mailinglist.advertised = true ORDER BY mailinglist.list_id LIMIT %(param_1)s] [parameters: {'param_1': 10}] > (Background on this error at: http://sqlalche.me/e/2j85) ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

[MM3-users] Re: Recipient address rejected: User unknown in local recipient table

by Mohsen Masoudfar

Thanks you so much Mark, I appreciate your help! Yes, I did: [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: newlistserv.aaas.org lmtp_port: 8024 smtp_host: newlistserv.aaas.org smtp_port: 25 configuration: python:mailman.config.postfix # postconf recipient_delimiter recipient_delimiter = + # postconf owner_request_special owner_request_special = no in main.cf: local_recipient_maps = hash:/opt/mailman/var/data/postfix_lmtp transport_maps = hash:/opt/mailman/var/data/postfix_lmtp virtual_alias_maps = hash:/opt/mailman/var/data/postfix_vmap Bur for some reason the postfix_lmtp.db is older than postfix_lmtp, which means it does not get updated automated, I guess. I restarted the whole stack and added a new list. In postfix logs I see: Apr 17 18:20:28 mailmandev01 postfix/smtpd[31399]: error: open database /opt/mailman/var/data/postfix_domains.db: No such file or directory Apr 17 18:20:28 mailmandev01 postfix/smtpd[31399]: error: open database /opt/mailman/var/data/postfix_vmap.db: No such file or directory I touched the /opt/mailman/var/data/postfix_vmap, but it did not help neither. In addition, I found out this : On my old mailman2 I have a setting in postfix main.cf: alias_maps = dbm:/usr/local/mailman/data/aliases the file /usr/local/mailman/data/aliases says in its first line: # This file is generated by Mailman, and is kept in sync with the # binary hash file aliases.db. YOU SHOULD NOT MANUALLY EDIT THIS FILE This makes a lot of sense to me. The point is I am missing any similar settings on postfix on mailman3. Maybe local_recipient_maps do that, but as I mentioned the DB file is older than the text file. The result is that the list (which is actually a postfix user) is unknown to postfix completely. Now what is missing here? It appears that postorius can talk to postfix to send welcome messages out, but Postfix is not aware about the User that Postorius has created and exists in SQLite DB. So rejects any email addressed to that one. Thanks Mohsen -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, April 15, 2020 10:09 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Recipient address rejected: User unknown in local recipient table [EXTERNAL EMAIL] On 4/15/20 3:47 PM, Mohsen Masoudfar wrote: > I am new to mailman3, my understanding was, maybe wrong, that when I create a list, mailman3 adds that to the local list of users. I think , I am missing something . . . > Or probably this is related to a postfix setting? Have you configured Mailman core and Postfix per <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailman.r…>? -- 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…

5 years

[MM3-users] Re: "held for moderation" - alias domain details sought

by Greg Newby

Thanks for this. After adding to "acceptable aliases," I also needed to add an entry in /etc/aliases, and then the moderation didn't happen. That's great! If I use an alias domain, will that replace the need for entries in /etc/aliases? I'm hesitant to explore since this is my production mail server. ~ Greg On Fri, Nov 1, 2024 at 1:51 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 11/1/24 11:14, Jeremy Stanley wrote: > > On 2024-11-01 11:04:07 -0700 (-0700), Greg Newby via Mailman-users wrote: > >> Hi friends. I've viewed this old thread: > >> > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > >> and documentation here: > >> > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… > >> (and the Postfix docs it links to). Those documents don't seem to guide > my > >> situation, or maybe I just need a more specific example. > > > The alias domain discussed at > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… > has nothing to do with what you are doing. > > > >> The problem is that when messages are delivered to the alias domain, > they > >> are held for moderation. I.e., mail to the alias domain like > >> testlist(a)domain.tld is held for moderation, but mail from the same > >> subscribed, non-moderated user to testlist(a)lists.domain.tld is posted > >> immediately without moderation. > > [...] > > > > I manage a similar setup (though with Exim instead of Postfix), and > > when migrating from Mailman v2 to v3 kept the same basic settings > > which seemed to work: notably, under Message Acceptance I set the > > alias addresses for the list in the Acceptable aliases field. If > > memory serves, not doing that caused messages addressed to those > > aliases to be unconditionally held for moderation. > > > This is the correct solution. Just add `testlist(a)domain.tld` to the > acceptable aliases setting of the `testlist(a)lists.domain.tld` list. > > -- > 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://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 gbnewby(a)petascale.org >

5 months, 2 weeks

[MM3-users] Re: Upgrade

by Darren Smith

By the way, in reading the URL in the error, I attempted to set the LANG and LC_ALL to en_US.utf8 (as was found in the error) but it still does not work. On Mon, Apr 16, 2018 at 11:26 AM, Darren Smith <silas.crutherton(a)gmail.com> wrote: > Nice...spoke too soon. > > Mailman info works, but when attempting to start mailman I'm now getting > this: > > Traceback (most recent call last): > File "/opt/mailman3/conda/bin/mailman", line 11, in <module> > sys.exit(main()) > File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", > line 722, in __call__ > return self.main(*args, **kwargs) > File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", > line 676, in main > _verify_python3_env() > File "/opt/mailman3/conda/lib/python3.6/site-packages/click/_unicodefun.py", > line 118, in _verify_python3_env > 'for mitigation steps.' + extra) > RuntimeError: Click will abort further execution because Python 3 was > configured to use ASCII as encoding for the environment. Consult > http://click.pocoo.org/python3/for mitigation steps. > > This system lists a couple of UTF-8 supporting locales that > you can pick from. The following suitable locales where > discovered: aa_DJ.utf8, aa_ER.utf8, aa_ET.utf8, (followed by a bijillion > others) > > -Darren > > On Mon, Apr 16, 2018 at 11:25 AM, Darren Smith <silas.crutherton(a)gmail.com > > wrote: > >> Boy howdy did that work... >> >> Thanks! >> >> >> On Mon, Apr 16, 2018 at 11:22 AM, Mark Sapiro <mark(a)msapiro.net> wrote: >> >>> On 04/16/2018 10:12 AM, Darren Smith wrote: >>> >>> > "/opt/mailman3/conda/lib/python3.6/site-packages/sqlalchemy/ >>> engine/strategies.py", >>> > line 160, in create >>> > engineclass.__name__)) >>> > TypeError: Invalid argument(s) 'pool_pre_ping' sent to create_engine(), >>> > using configuration PGDialect_psycopg2/QueuePool/Engine. Please >>> check that >>> > the keyword arguments are appropriate for this combination of >>> components." >>> > >>> > Anyone able to point me where to go to look for a solution for this? >>> >>> >>> You need to update SQLAlchemy to >= 1.2 for this, but there is another >>> issue that requires at least 1.2.3 (current is 1.2.6) >>> >>> >>> -- >>> 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/ >>> >> >> >

7 years

[MM3-users] Re: using SSH/TLS with external MTA

by Roland Giesler

On 2024/07/28 17:06, Mark Sapiro wrote: > On 7/28/24 06:26, Roland Giesler via Mailman-users wrote: >> On 2024/07/28 00:39, Mark Sapiro wrote: >> A mail was sent to root on the localhost with the following content: >> >> Return-Path: <root(a)giesler.za.net> >> X-Original-To: root@localhost >> Delivered-To: root@localhost >> Received: from mailman.fast.za.net (localhost [IPv6:::1]) >> by mailman.localdomain (Postfix) with ESMTP id 2174A120A5B >> for <root@localhost>; Sun, 28 Jul 2024 13:11:03 +0000 (UTC) >> Content-Type: text/plain; charset="utf-8" >> MIME-Version: 1.0 >> Content-Transfer-Encoding: quoted-printable >> Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: >> /accounts/login/ >> From: root(a)giesler.za.net >> To: root@localhost >> Date: Sun, 28 Jul 2024 13:11:03 -0000 >> Message-ID: <172217226313.2150.10895652368679013629(a)mailman.fast.za.net> >> >> Internal Server Error: /accounts/login/ >> >> SMTPRecipientsRefused at /accounts/login/ >> {'roland(a)giesler.za.net': (454, b'4.7.1 <roland(a)giesler.za.net>: >> Relay acce= >> ss denied')} > > This is mail from django-allauth, not from Mailman. Your settings in > mailman.cfg do not affect how this mail is sent. See > https://docs.djangoproject.com/en/5.0/topics/email/#smtp-backend for > the Django settings for this. These settings from the Django docs look like the ones in mailman.cfg. Do I have to set them somewhere else too? SMTP backend¶ <https://docs.djangoproject.com/en/5.0/topics/email/#smtp-backend> /class/|backends.smtp.||EmailBackend|(/host=None/,/port=None/,/username=None/,/password=None/,/use_tls=None/,/fail_silently=False/,/use_ssl=None/,/timeout=None/,/ssl_keyfile=None/,/ssl_certfile=None/,/**kwargs/)¶ <https://docs.djangoproject.com/en/5.0/topics/email/#django.core.mail.backen…> This is the default backend. Email will be sent through a SMTP server. The value for each argument is retrieved from the matching setting if the argument is|None|: * |host|:|EMAIL_HOST| <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_HOST> * |port|:|EMAIL_PORT| <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_PORT> * |username|:|EMAIL_HOST_USER| <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_HOST_…> * |password|:|EMAIL_HOST_PASSWORD| <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_HOST_…> * |use_tls|:|EMAIL_USE_TLS| <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_USE_T…> * |use_ssl|:|EMAIL_USE_SSL| <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_USE_S…> * |timeout|:|EMAIL_TIMEOUT| <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_TIMEO…> * |ssl_keyfile|:|EMAIL_SSL_KEYFILE| <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_SSL_K…> * |ssl_certfile|:|EMAIL_SSL_CERTFILE| <https://docs.djangoproject.com/en/5.0/ref/settings/#std-setting-EMAIL_SSL_C…> The SMTP backend is the default configuration inherited by Django. If you want to specify it explicitly, put the following in your settings: EMAIL_BACKEND = "django.core.mail.backends.smtp.EmailBackend" If unspecified, the default|timeout|will be the one provided by|socket.getdefaulttimeout()| <https://docs.python.org/3/library/socket.html#socket.getdefaulttimeout>, which defaults to|None|(no timeout).

8 months, 3 weeks

[MM3-users] Re: CSS Hyperkitty ERROR

by Johan Alsina

Stephen J. Turnbull wrote: > Johan Alsina via Mailman-users writes: > > Hi, i installed mailman3 with virtualenv, all is working fine, the > > admin site works fine, the mailman(postorious) site works fine, but > > when im in hyperkitty the site shows without the css style.. in my > > web browser dev tool it shows like they loaded ok.. > > I think you need to figure out why the dev tool can see the CSS files > but other environments can't. It sounds exactly like all the other > problems I couldn't diagnose. :-/ > > Any ideas? :/ > > My static files are loading from > > /static/CACHE/css/output.a0f71925131b.css and > > /static/hyperkitty/libs/fonts/font-awesome/css/font-awesome.min.css > > I've run into the "no styles" issue on a number of new hosts where the > problem was that somewhere on the path to the CSS files was a > directory, typically owned by root, without "x" permissions for > "other" users. That difference across trees is weakly consistent with > a "somewhere in between" permissions problem. > Steve Hi Steve, thanks for answer, i tried all about permissions and paths and i thins all its ok.. here you can see my paths/permissions.. General: https://freeimage.host/i/3ok1LDN Django project: https://freeimage.host/i/3ok1ZxI Mark Sapiro wrote: > On 3/17/25 6:46 PM, Johan Alsina via Mailman-users wrote: > > Hi, i installed mailman3 with virtualenv, all is working fine, the admin site works fine, the mailman(postorious) site works fine, but when im in hyperkitty the site shows without the css style.. in my web browser dev tool it shows like they loaded ok.. > > Have you run mailman-web collectstatic and mailman-web compress? See > https://docs.mailman3.org/en/latest/install/virtualenv.html#collect-static-f... > If you have, try running them again as mailman-web collectstatic --clear and mailman-web compress. > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan Hi Mark, thanks for the answer. Yes, i tried all variations about collectstatic, clear_cache, etc.. comands with no difference. I dont get any error and the files are collected ok.. Like i said before, i think the problem comes with the css files in /static/CACHE.. because the ones that are in /static/hyperkitty are loading ok.. css files in /static/CACHE not loading: https://freeimage.host/i/3okk6CJ img files in /static/hyperkitty loading: https://freeimage.host/i/3okkPEv I tried to move /static/CACHE inside of /static/hyperkitty but when i run collectstatic the files goes again to the default path.. Thanks in advance..

1 month

[MM3-users] Re: Problem creating list members using REST API

by Stephen Daniel

The REST API documentation is a bit informal. As someone who is not familiar with mailman, and who doesn't know python, they are a bit of a slog. One day it would be nice to augment the documentation with a formal and complete reference document. Something like this one <https://infosight.hpe.com/InfoSight/media/cms/active/public/pubs_REST_API_R…>. A formal reference manual needs a complete listing of every type of object, all possible operations on each object, and all required and optional parameters. Since creating a formal document like that is probably out of scope, at a minimum it would be good to specify that boolean values are passed as JSON strings, not JSON booleans. It might be worth seeing if the code can be enhanced to allow the boolean values to be sent in using JSON booleans as well as JSON strings. Thanks again for the prompt response! -- Stephen On Tue, Jan 18, 2022 at 4:25 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/18/22 10:53 AM, Stephen Daniel wrote: > > 2nd follow-up. Apologies for spamming this list. > > > > I went wandering through the code as suggested by the traceback. I > > discovered that thee "as_boolean" routine is expecting a string argument > > but getting a boolean argument. > > > > So, If I send the booleans as strings, with values "true" or "false", all > > is well. > > This is not what the API documentation suggests I should do. Can someone > > either fix the documentation or the code? > > > Those snippets in the documentation are doctests. That code is actually > executed by unit testing and passes. In all those snippets, dump_json is > passing the second argument as `data` to > mailman.testing.documentation.dump_json() which in turn calls > mailman.testing.documentation.call_http() which calls > mailman.testing.helpers.call_api() which ultimately calls > requests.request() with the same `data` argument. > > So basically, the issue is the difference between how requests.request() > handles that `data` dictionary in creating the POST data and whatever > you are doing. > > Possibly we could add some caveat to > < > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/docum…> > > or possibly elsewhere. Do you have a suggestion as to what? > > > -- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

3 years, 3 months

[MM3-users] Re: digest summary heavily cluttered with hrml code

by Mohsen Masoudfar

Hi Mark, Thanks again for your help! Yes, I meant "Today's Topic". I checked the link you sent, but could not see the solution to the issue. You mentioned: " They are in order of priority, list based, address based and global" Is this in descending or ascending priority? If I set it at list level, does it overwrite the member setting (address based?? )? I set them along with "Delivery mode" at the member level and saved it, but when I get back to it, it still shows "Regular" and other fields like: acknowledge_posts, delivery_status, hide_address, receive_list_copy, receive_own_postings are empty, even though I set them and saved. Thanks Mohsen -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, October 14, 2020 12:21 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: digest summary heavily cluttered with hrml code [EXTERNAL EMAIL] On 10/14/20 8:46 AM, Mohsen Masoudfar wrote: > Hi, > > I am running Mailman 3.1.1 on Ubuntu 18.04. > > The user complains that the digest summary is cluttered with HTML code. What does 'summary' mean in this context? Are you referring to the 'Today's Topics:' list or the messages themselves? Is this perhaps <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.co…>? > I thought, I may fix it by: > Members > {user} > Member options > Delivery mode set to [Plain Text Digest]. After setting the value and clicking [save changes], I tried to check the value by getting back to Members setting for the user, it shows the value as "Regular", which was the value before I tried to update it. There are actually 3 sets of user preferences. They are in order of priority, list based, address based and global. You can see these if you are logged in to the web UI as the user and go to 'Mailman settings' in the pull down at the top right. There are issues in Postorius if a user is a member of a list with more than one role - see <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.co…>. > Question 1: How may I be sure that the value is set, if it is set? Examine the settings with `mailman shell` > Question 2: How may set it for all members of the list? Create a `mailman shell` script. > Question 3: Is there a CLI way to do this? I tried "mailman members " command. But it seems not supporting this option. Again, `mailman shell`, but this is low level and requires some knowledge of Mailman internals. -- 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…

4 years, 6 months

[MM3-users] Re: Getting rid of held messages from the command line

by Mark Sapiro

On 03/14/2018 03:04 AM, Aymeric Mansoux wrote: > > So far so good, however, for some reasons, a couple of our lists have started to accumulate held messages that cannot be manipulated via the REST API. Regardless if we use the web interface or mailmanclient, it ends up with: > > Mar 14 10:58:32 2018 (24287) REST request handler error: > Traceback (most recent call last): > File "/usr/lib/python3.5/wsgiref/handlers.py", line 137, in run > self.result = application(self.environ, self.start_response) > File "/usr/local/lib/python3.5/dist-packages/mailman/database/transaction.py", line 50, in wrapper > rtn = function(*args, **kws) > File "/usr/local/lib/python3.5/dist-packages/mailman/rest/wsgiapp.py", line 214, in __call__ > return super().__call__(environ, start_response) > File "/usr/local/lib/python3.5/dist-packages/falcon/api.py", line 244, in __call__ > responder(req, resp, **params) > File "/usr/local/lib/python3.5/dist-packages/mailman/rest/post_moderation.py", line 167, in on_get > resource = self._make_collection(request) > File "/usr/local/lib/python3.5/dist-packages/mailman/rest/helpers.py", line 159, in _make_collection > for resource in collection] > File "/usr/local/lib/python3.5/dist-packages/mailman/rest/helpers.py", line 159, in <listcomp> > for resource in collection] > File "/usr/local/lib/python3.5/dist-packages/mailman/rest/post_moderation.py", line 157, in _resource_as_dict > resource = self._make_resource(request.id) > File "/usr/local/lib/python3.5/dist-packages/mailman/rest/post_moderation.py", line 70, in _make_resource > resource = super()._make_resource(request_id) > File "/usr/local/lib/python3.5/dist-packages/mailman/rest/post_moderation.py", line 39, in _make_resource > results = requests.get_request(request_id) > File "/usr/local/lib/python3.5/dist-packages/mailman/database/transaction.py", line 85, in wrapper > return function(args[0], config.db.store, *args[1:], **kws) > File "/usr/local/lib/python3.5/dist-packages/mailman/model/requests.py", line 120, in get_request > result.data_hash, expunge=False) > File "/usr/local/lib/python3.5/dist-packages/mailman/database/transaction.py", line 85, in wrapper > return function(args[0], config.db.store, *args[1:], **kws) > File "/usr/local/lib/python3.5/dist-packages/mailman/model/pending.py", line 138, in confirm > value = json.loads(keyvalue.value) > File "/usr/lib/python3.5/json/__init__.py", line 319, in loads > return _default_decoder.decode(s) > File "/usr/lib/python3.5/json/decoder.py", line 339, in decode > obj, end = self.raw_decode(s, idx=_w(s, 0).end()) > File "/usr/lib/python3.5/json/decoder.py", line 355, in raw_decode > obj, end = self.scan_once(s, idx) > json.decoder.JSONDecodeError: Unterminated string starting at: line 1 column 1 (char 0) > Mar 14 10:58:32 2018 (24287) 127.0.0.1 - - "GET /3.1/lists/xx(a)xx.xx/held HTTP/1.1" 500 59 > > Is there a way to manipulate/see/remove these mails differently? Right now this prevent moderation of any held messages (note: some lists do not suffer from this and the held panel or mailmanclient works perfectly fine). We've seen this issue before with a different underlying cause. See <https://gitlab.com/mailman/mailman/issues/256>. There are a couple of problems here. The serious problem is if there is a held message which somehow throws an exception in processing in mailman/rest/post_moderation.py, that totally breaks the Postorius held messages view for that list. We need to fix that. Also it would be good to see the problem message. Here are some things you can do in 'mailman shell' (aka mailman withlist). It is not clear what might not work, but you can try mailman shell -l list@domain which will respond Welcome to the GNU Mailman shell The variable 'm' is the list@domain mailing list >>> Then you should be able to do at the >>> prompts: >>> req_db = IListRequests(m) >>> reqs = list(req_db.held_requests) reqs is now a list of the held requests and you can do something like >>> for req in reqs: ... print('{}: {}'.format(req.id, req.request_type)) ... or since req_db.held_requests is a generator >>> for req in rdb.held_requests: ... print('{}: {}'.format(req.id, req.request_type)) ... either of which will produce a list like 1: RequestType.held_message with the IDs and types of each request. You can handle these requests with something like >>> from mailman.app.moderator import handle_message >>> handle_message(m, 1, Action.defer) where the second argument is the ID of the message and the action is one of Action.defer, Action.hold, Action.discard, Action.reject or Action.accept, the first two of which do nothing, but the others will do the indicated action. You can see the actual messages like this >>> msg_db = getUtility(IMessageStore) then >>> key = req[0].key >>> msg_db.get_message_by_id(key) which will return the actual held message that is in this case index 0 in the list of held_requests. You may have to do >>> commit() when done, although if you don't do abort(), just exiting with control-D should do a commit(). I hope you find this helpful, and if you do determine the content of the offending message(s), it will be helpful if you post that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 1 month

[MM3-users] Re: Mailman 3, postfix domains, and postgresql cannot authenticate user

by Keith Christian

Mark, RE: The `mailman aliases` command generates the postfix_domains and postfix_lmtp files and calls the configured postmap_command (default /usr/sbin/postmap) to create the .db files. `mailman start` also generates these files by default. I ran mailman aliases and the first try got can't read main.cf. I granted read-only access to other on the file, the next mailman aliases command ran without errors, but I don't know if it did anything or not, e.g. nothing in postfix_domains or the lmtp files. How can I verify that "mailman aliases" worked? Thanks, ---------- Keith On Wed, Jul 3, 2024 at 2:52 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > On 7/3/24 09:22, Keith Christian via Mailman-users wrote: > > --------------------------------------------------------------------------- > > First issue:Postfix v3.5.8 on RHEL 8. > > The below is from journalctl -xe: > > --------------------------------------------------------------------------- > > Jul 03 08:12:04 somehost.somedomain postfix/qmgr[947499]: error: open > > database /opt/mailman3/mm/var/data/postfix_domains.db: No such file or > > directory > > Jul 03 08:12:42 somehost.somedomain postfix/smtpd[947510]: error: open > > database /opt/mailman3/mm/var/data/postfix_domains.db: No such file or > > directory > > Jul 03 08:12:42 somehost.somedomain postfix/smtpd[947510]: error: open > > database /opt/mailman3/mm/var/data/postfix_lmtp.db: No such file or > > directory > > > > I manually created the var_dir: /opt/mailman3/mm/var directory > > specified in the mailman.cfg file. > > How do I find out how to populate the postfix_domains.db files, and > > the postfix_lmtp.db file? > > > The `mailman aliases` command generates the postfix_domains and > postfix_lmtp files and calls the configured postmap_command (default > /usr/sbin/postmap) to create the .db files. `mailman start` also > generates these files by default. > > > > --------------------------------------------------------------------------- > > Second issue: Postgresql authentication. > > PostgreSQL v10.23. > > --------------------------------------------------------------------------- > > I have this in the active mailman3.cfg file, where xxxxxxxxxx is the > > same complex password in the mailman3 config file: > > url: postgresql://mailman3:xxxxxxxxxx@localhost/mailman3/mailman3 > > > I don't think you should have two /mailman3 at the end > > the form is `postgresql://user:password@host:port/database_name` The > default port is 5432. > > -- > 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://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 keith1christian(a)gmail.com

9 months, 2 weeks

[MM3-users] Re: Mailman REST API not available. Please start Mailman Core.

by Shashikanth Komandoor

Thank you Mark for your response. I understood that gunicorn is a front end that is used like web server like nginx. But I don't think I am using it instead I am using the httpd to redirect requests to postorius. And I am starting the mailman-suite with the command "python manage.py runserver 0.0.0.0:8000 --insecure &". Hope this does not use gunicorn (which of course I don't know what it is until now). Please correct me if any point I am mentioning is wrong. So, in this case, do you think configuring gunicorn as below would work: *calling gunicorn.cfg in mailman.cfg as below * *[webservice]* *configuration: /var/lib/mailman/mailman/src/mailman/config/gunicorn.cfg* *and content of gunicorn.cfg as below* *(venv3) [root@lsmgr mailman]# cat /var/lib/mailman/mailman/src/mailman/config/gunicorn.cfg[gunicorn]# All the options that can be put here are available at# http://docs.gunicorn.org/en/stable/settings.html#settings <http://docs.gunicorn.org/en/stable/settings.html#settings># No of seconds to wait before killing the worker processes.* *workers = 4graceful_timeout = 90* Also what is the difference between timeout and graceful_timeout ? Please help me if I can increase the management better. Any guide is also helpful for me. <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> On Thu, Jul 23, 2020 at 4:10 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/22/20 9:21 AM, Shashikanth Komandoor wrote: > > Hi Mark, > > > > Never mind please I am sending to you only instead of group as I am > > sending you the production content along with the mail. > > > See my other reply. > > > > I have configured the workers count as 4 and timeout as 900 in > > mailman.cfg under [webservice]. This is FYI. > > You can't configure Mailman's REST gunicorn workers directly in the > [webservice] section of mailman.cfg. The only thing you can configure > there is: > > configuration: /path/to/gunicorn.cfg > > That file, which is separate from your web server gunicorn.cfg, is where > you put things like > > [gunicorn] > timeout = 900 > > It also will not work to put a gunicorn section in mailman.cfg. It must > be in a separate file pointed to by webservice.configuration. > > Increasing the number of workers won't help this issue. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > -- Thanks & Regards, Shashi Kanth.K 9052671936

4 years, 9 months

[MM3-users] Re: Mailman 3 Privacy Policies, GDPR, etc and social logins

by Jered Floyd

This was what I was using as well, but it failed to meet their requirements for some ineffable reason. I had a few back-and-forths with someone for whom English was not their first language, and got them to accept a slightly modified version that I posted at https://www.convivian.com/mailman-privacy.html Now, the latest is that I have a new message noting that apps requesting user data (e.g. email address) must be linked to Business Profiles (text below). Django-allauth is cool, but I think it's not going to be long for this world and we'll just have to do internal auth. Disappointing from a workflow perspective, but I'm happy to dissuade subscribers to not use Facebook. Regards, --Jered P.S. The fresh hell from Facebook: You are receiving this message because Mailman List Manager is not connected to a verified Meta Business Account. On Feb 1, 2023 Meta began requiring business verification for apps that request access to data from users (for some apps this is called advanced access). Learn more about this requirement. [https://developers.facebook.com/blog/post/2023/02/01/developer-platform-req…] Here’s what a person with full control of your Business Account needs to do by Feb 2, 2024 to maintain access: Connect the app to a Business Account, if you haven't already. Complete business verification for the Business Account. Business Accounts connect your Facebook Pages, Instagram accounts and the people who work on them, so you can manage them all in one place. ----- On Sep 19, 2023, at 5:00 PM, Mark Sapiro mark(a)msapiro.net wrote: > On 9/19/23 6:22 AM, Jered Floyd wrote: >> >> This is a bit of a headache. Do we have a draft of a community Privacy Policy >> for a vanilla Mailman 3 install that meets Facebook's requirements? Is this >> going to be a constantly unraveling thread of future GDPR and Right to Be >> Forgotten troubles, since there doesn't seem to be an easy way to scrub a >> subscriber from Hyperkitty archives if they request so? How have others >> addressed this situation? > > > I use https://www.list.org/privacy.html which appears to satisfy Facebook. > > -- > 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://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 jered(a)convivian.com

1 year, 6 months

[MM3-users] Re: Missing Base64 encoding from control message reply

by Jana Berger

On 24.09.2023 16:52, Mark Sapiro wrote: > On 9/24/23 07:20, Stephen J. Turnbull wrote: >> >> The only thing I can think of at the moment that might move the >> discussion forward is if Mark knows how to run his test in your Docker >> environment to see if it also produces >> Content-Type: text/plain; charset="US-ASCII" >> Content-Transfer-Encoding: 7bit > > Assuming there is not something like > ``` > [language.en] > charset: utf-8 > ``` > in your mailman.cfg overriding the default us-ascii charset for > English, if you send a message From: yourself to > list-confirm-xxxxxxx(a)example.com with Subject: Re: Your confirmation > is needed to join the list(a)example.com mailing list (replacing list > and example.com with the actual list and domain), you should receive a > response like (some headers removed) > ``` > Subject: The results of your email commands > From: list-bounces(a)example.com > To: mark(a)example.com > MIME-Version: 1.0 > Content-Type: text/plain; charset="us-ascii" > Content-Transfer-Encoding: 7bit > Message-ID: <169556563227.2592.7908020161516725770(a)example.com> > Date: Sun, 24 Sep 2023 07:27:12 -0700 > Precedence: bulk > X-Mailman-Version: 3.3.9b1 > List-Id: A test list <list.example.com> > List-Help: <mailto:list-request@example.com?subject=help> > List-Owner: <mailto:list-owner@example.com> > List-Subscribe: <mailto:list-join@example.com> > List-Unsubscribe: <mailto:list-leave@example.com> > > The results of your email command are provided below. > > - Original message details: > From: Mark Sapiro <mark(a)example.com> > Subject: Re: Your confirmation is needed to join the > list.example.com mailing list. > Date: Sun, 24 Sep 2023 07:27:10 -0700 > Message-ID: <20230924142710.GA23819(a)example.com> > > - Results: > Confirmation token did not match > > - Done. > > ``` > What do you get? > Well, that confirms it. I send the mail from an account at GMX and received the Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 with a properly (!) base64-encoded message body. I then send the mail both from my own mail system (which is also the one being used by Mailman) and got Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" with no encoding on the message. Lastly, I send the same mail from a GoogleMail account, which also received Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" with no encoding. ... which means this is almost surely a bug in the MTA of GMX, which will be much, much more difficult and unlikely to be fixed - that is why I had hoped for this to be an issue in/with Mailman ;) Thank you for the pointers and help!

1 year, 6 months

[MM3-users] Re: The message is larger than the 40 KB maximum size

by Mohsen Masoudfar

Hi Mark, Thank you Mark and Phil for your help. It seems I got stuck! 1- I tried to set up the max_message_size in WUI under: listname > settings > Message Acceptance > Maximum message size to 0. After hitting save button, I got the error message: " An error occured: Unknown attribute: max_message_size" 2- I checked the python files and found this file, where, it seems, the default value is defined: /usr/lib/python3/dist-packages/mailman/styles/base.py : mlist.max_message_size = 40 I changed this value to 0, saved the file, restarted the mailman and postgresql (not sure if needed) and sent an email with a large attachment to my test list with just two members. I got the response email: The message is being held because: The message is larger than the 40 KB maximum size 3- I totally agree that the most important issue is the fact that the message vanished with the production list. I repeated the same with a (test) list which has two members, I got the email mentioning the 40 KB limit and I could release it. This is how I am running my tests now. I repeated it with the original list (with 197 members) the message disappeared again. I can send an email to the list with 197 members, without this attachment and it works. 4- I checked the folders, under /var/lib/mailman3/queue/, all folders are empty: archive/ bad/ bounces/ command/ digest/ in/ nntp/ out/ pipeline/ retry/ shunt/ virgin/ Thanks Mohsen -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, September 18, 2020 4:00 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: The message is larger than the 40 KB maximum size [EXTERNAL EMAIL] On 9/18/20 12:48 PM, Phil Stracchino wrote: > On 2020-09-18 15:32, Mohsen Masoudfar wrote: >> Hi, >> >> I am trying to find how I may change this. I have an attachment of 800 KB, and when I post it to the list, I do not get any response and nothing is hold. It looks like the message is just dropped. > > > Assuming that this works roughly the same in mm3 as it does in mm2, > you can set max_message_size in your list configuration. It defaults > to 40; units are KB. Yes, and you can set it to zero for "unlimited", but even if that is a satisfactory workaround, the much more interesting question, at least to me, is why does the message "disappear". -- 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…

4 years, 7 months

[MM3-users] Re: converting bulk accept_these_nonmembers in migration from mailman 2 to 3

by Mark Sapiro

On 2/12/22 08:19, Lucio Chiappetti wrote: > Dear Mark, thanks for your interest. > > On Fri, 11 Feb 2022, Mark Sapiro wrote: > >> This may actually be a bug. I'll have to think about that. I've filed >> https://gitlab.com/mailman/mailman/-/issues/978 on this. > >> This is https://gitlab.com/mailman/mailman/-/issues/794 (still open) > > Given the time needed to solve the issues (I will anyhow notify the site > administrators, hopting they would update mailman when/if resolved), > this means we have to find a workaround. https://gitlab.com/mailman/mailman/-/issues/978 has been fixed. You can apply the fix to mailman/rules/moderation.py from https://gitlab.com/mailman/mailman/-/merge_requests/961/diffs > not sure what you mean by "defer". The non-member options I see are called > > List default -- follow the list's default member action. > Hold -- This holds the message for approval by the list moderators. > Reject -- this automatically rejects the message by sending a bounce > notice to the post's author. The text of the bounce notice can be > configured by you. > Discard -- this simply discards the message, with no notice sent to the > post's author. > Accept -- accepts any postings without any further checks. > Default Processing -- run additional checks and accept the message. `defer` is what's called `Default Processing` in the above list. > But if hold_these_nonmembers takes priority this will be uselesws in the > current setting. True, but if you apply the fix for https://gitlab.com/mailman/mailman/-/issues/978, hold_these_nonmembers won't take priority. > I go to the non-member list, select non-member options and at the bottom > see an item Administration options Moderation. The possible values are > those I pasted above. > > The actual value for most of the imported non-members is "Default > processing" while it is "List default" for thoase automatically added > afresh, It is "Discard" for a number of imported non-members with > spam-looking addresses (I guess they were in some other *_not_members > part of the standard 2.1 antispam ... I can't recall me doing something > on those) That all seems exactly what it should be. > Side question: is there a way to operate IN BULK on non-members ? Like > it is for members (I exported them to CSV). No. Postorius doesn't currently support a CSV export for nonmembers as it does for members, but you could do the equivalent in `mailman shell` ``` $ mailman shell -l list.example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list.example.com mailing list >>> for nonmemb in m.nonmembers.members: ... print(nonmemb.address.email) ... ``` > I am not so concerned of these 189 (or better of the 189 minus the > discard ones which should stay) ... anyhow moving them back will be > uncomfortable if there is not a bulk operation tool. > > I am more concerned of the new cases automatically added. Apply the patch. ... > (*) by the way do you confirm that if one is subscribed to a list with > an address (be it bulk subscription, import or new fast subscription), > this person CANNOT change their settings (or address) unless one does a > "sign in" to a (Postorius) account ? That is correct. User's can add multiple addresses to their identity, change addresses and change other settings, but currently that has to be done via Postorius or another web UI that communicates with Mailman Core's REST API. ...>> Addresses still work, and accept_these_nonmembers takes precedence >> over hold_these_nonmembers just as in MM 2.1. > > This was not my impression when I ran a thorough test of 12 cases. > Except the obvious case of the subscriber posting from the subscription > address, all messages went on hold. If a nonmember address is in accept_these_nonmembers, a post from that address should be accepted regardless of hold_these_nonmembers. > Whatever the non-member moderation would be (even if set to reject ! ... > but that makes sense if *_these_nonmembers prevail on non-member > options), and even if the address was set explicitly in > accept_these_nonmembers (should I delete it from the non-member list ?) You can leave it as a nonmember. > What is the actual order (or flow chart) of choices ? Without the fix for https://gitlab.com/mailman/mailman/-/issues/978 the order is - Is the sender a member? If so, apply the member's moderation action or list default. - The sender is a nonmember, if the address matches one of (accept|hold|reject|discard)_these_nonmembers (checked in that order), apply that action. - If no match above, apply the nonmember's moderation action - will be `List Default` for new nonmembers. With the fix for https://gitlab.com/mailman/mailman/-/issues/978 the order is - Is the sender a member? If so, apply the member's moderation action or list default. - The sender is a nonmember, if the nonmember's moderation action is other than List Default, apply that action. - If not, if the address matches one of (accept|hold|reject|discard)_these_nonmembers (checked in that order), apply that action. - If none of the above, apply the list's default nonmember action. > *_these_nonmembers in the order listed in the page (within each in the > order of occurrence of regexp's) then non-member options ? That's the way it works without the fix except the order of regexps/addresses in a *_these_nonmembers list is immaterial. if the address matches any one of them, that action applies. > If I have Name.Surname(a)inaf.it in accept_these_nonmembers, then > hold_these_nonmembers set to > > ^.+@.+\.it > ^.+@.+\.tng\.iac\.es > > what do you foresee ? Assuming Name.Surname(a)inaf.it is not a member, a post from Name.Surname(a)inaf.it will not be held for nonmember moderation. > And for different regexps, will processing terminate at the first > non-matching one, will they be ANDed or ORed, or what ? They will all be checked until one matches or none do., I.e., effectively ORed. > I am reluctant to accept inconditionally ^.+\..+(a)inaf\.it (they may be > falsified, only the check on their presence in the other list (issue 794) > > I guess I should remove the ^.+@.+\.it regexp AND AT THE SAME TIME > change the Default action to take when a non-member posts to the list to > Hold instead of Discard. > > This way we'll have to check spam (instead of having it auto-discarded), > but if people with alternate addresses post, once they are entered in > the Non-member list they can be authorized to pass for the future ... > > .. would it work ? I think that would work, but if you just apply the patch from https://gitlab.com/mailman/mailman/-/merge_requests/961/diffs, it will work the way it did in MM 2.1 honoring a nonmember's explicit moderation action before checking *_these_nonmembers. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

[MM3-users] Re: Is there a way of recording bounce messages?

by Andrew Hodgson

Hi. Seems other people have had this on Office365 when I searched the specific error. I have enabled VERP now on probes and all list messages so lets see if that improves things. Thanks. Andrew. -----Original Message----- From: Andrew Hodgson <andrew(a)hodgson.io> Sent: Friday, September 22, 2023 12:22 PM To: Mark Sapiro <mark(a)msapiro.net>; mailman-users(a)mailman3.org Subject: [MM3-users] Re: Is there a way of recording bounce messages? Mark Sapiro <mark(a)msapiro.net> wrote: >On 9/21/23 17:30, Thomas Ward wrote: >> >> MS365's bounce handling is weird and they do not include a delivery report in the payload, instead they take the log data and append it as a text payload portion to the message. It's annoying and problematic when debugging (and likely triggers the mailman2 equivalent of "unprocessable bounce message"). >> >> If Andrew can provide the bounce message as an example in raw form (even off list) we can dissect it - myself probably more rapidly as I am fluent in reading them at this point from weeks worth of dealing with them - and that will probably yield the info you are looking for. >It appears however that Mailman does recognize the DSN returned by MS365 as the user's delivery is being disabled by bounce. The issue is whatever DSN is returned to the list-bounces address is not attached to the notice sent to the list owner about the disable and it should be. Ok guys the plot thickens. Yesterday using the Mailman Shell I unbounced all the users on that list. We had a couple of messages yesterday and I also enabled the From munging for all messages sent to the list partway through those messages coming to the list. This morning we got all Gmail users bounced again, with no NDR attached to the message. However on one of the messages the NDR was attached, and so I'm going to send that to Mark separately. It looks like the NDR included the information for all the bouncing messages though, and that is probably because Mailman sends the messages to all users in one SMTP transaction. The message returned from Google was: user(a)gmail.com 9/22/2023 9:44:55 AM - Server at PAVPR08MB9257.eurprd08.prod.outlook.com returned '550 5.4.300 Message expired -> 421 4.4.2 Connection dropped due to SocketError' 9/22/2023 9:24:03 AM - Server at gmail-smtp-in.l.google.com (142.250.27.27) returned '421 4.4.2 Connection dropped due to SocketError' Thanks. Andrew. _______________________________________________ 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 andrew(a)hodgson.io

1 year, 7 months

[MM3-users] Re: MM3 Docker

by Odhiambo Washington

On Tue, 8 Jan 2019 at 03:29, Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/7/19 1:18 AM, Odhiambo Washington wrote: > > On Sun, 6 Jan 2019 at 23:39, Mark Sapiro <mark(a)msapiro.net> wrote: > >> > >> Please help me understand what steps are missing and I will try to > >> provide the information. > > > > > > Okay. > > > > At the installation stage, you say the following: > > "I already had some things set up in /opt/mailman including a git > > subdirectory containing clones of the GitLab mailman, mailmanclient, > > mailman-hyperkitty, hyperkitty, django-mailman3 and > > postorius projects. On the third server I have added mailman-suite > > because I use the settings.py from that project as the basis for mine." > > > > Please assume that the reader is a newbie to python3 virtualenv and give > the > > details of the commands they need to execute to (a) clone all the > projects > > needed > > and (b) create the virtualenv. > > > > The next steps are: > > mkdir /opt/mailman/mm > > > > Then you say "I then created a /opt/mailman/mm directory and within that > a > > Python 3.6 virtualenv" > > What happens here is something that needs clarification, because you are > > specific about "python3.6". > > I have googled and realized that one has to be specific about the python > > version they want to use in their virtualenv > > as shown here -> > > > https://stackoverflow.com/questions/45293436/how-to-specify-python-version-… > > > > exact command to execute to create the /opt/mailman/mm/venv > > exact command to execute to activate virtualenv > > > I have added a comment to the page which I hope gives you what you want. > > I also added a section on templates instead of referring to a prior > version of the page. > That makes it better. However, as a newbie, something is not yet clear: "When active in a particular shell, it can be deactivated with the command deactivate or by exiting that shell." HI am trying to understand the effect of detaching from a venv. I am assuming that a virtualenv is a container that is supposed to be always active for the services within to be accessible. Is that right? So, how do I ensure it's always running/up, or that does not matter as the scripts which run the services will always refer to the files? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

6 years, 3 months

[MM3-users] Re: no bounce-processing with verp_probes: yes

by Stefan Bauer

Thank you Mark. The problem was, that the bounce-process was dying as we had nearly 200.000 unprocessed bounce messages in database. After setting UPDATE bounceevent SET processed = 1; the bounce-process keeps running and bounce.log is going wild and logs Member ... already scored a bounce on list list.domain.tld today. I see now the bounce-queue is quickly decreasing. Am Mi., 6. Dez. 2023 um 22:22 Uhr schrieb Mark Sapiro <mark(a)msapiro.net>: > On 12/6/23 06:26, Stefan Bauer wrote: > > Dear Users, > > > > during one of our upgrades to 3.3.x we set verp_probes: yes according to > > upgrade notes[1]. > > > > However it looks like this disabled bounce handling completely. > > > > Howto verify (MM 3.3.9): > > > > Set > > verp_probes: yes > > verp_delivery_interval: 1 > > restart mailman3 > > create test-list > > add an undeliverable recipient to the list that is known to bounce. > > send 6 mails to list. > > Bounce score is only incremented on the first bounce for that day. > > > see, that all the bounce-messages are received by mailman according to > > postfix log[2] > > So they are delivered. At this point, having set `verp_probes: yes` has > no effect on the processing. It only comes in to play when the > threshhold is reached. > > > check bounce.log - no entry. > > get bounce_score from API[3] - shows bounce_score 0. > > > This says bounces are not being processed. Is the bounces runner > running? If it is there should be entries like > > Member undeliverable-recipient(a)realdomain.tld on list > v-test.lists.lists.tld, bounce score = 1. > > and > > Member undeliverable-recipient(a)realdomain.tld already scored a bounce on > list v-test.lists.lists.tld today. > > in bounce.log. and bounce score should be 1. This is independent of > `verp_probes: yes`. > > If the bounce runner is not running, stop and start Mailman core. You > must stop and then start, not restart. > > Also check mailman.log for a reason why bounces runner is not running. > > If bounces runner is running, check mailman.log for possible errors > relating to bounce processing. > > -- > 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://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 cubewerk(a)gmail.com >

1 year, 4 months

[MM3-users] Re: Long-shot cry for help

by Mark Sapiro

On 6/3/21 6:34 AM, David Partain via Mailman-users wrote: > Hi, > > I'm having severe operational issues with my mailman3 site. My site is built on standard Ubuntu packages (18.04), and they're ancient. I'm having two big issues... > > 1. I have the old smiley problem that I've had from the very beginning and never solved. I have added 'charset': 'utf8mb4' to the relevant config file (/etc/mailman3/mailman-web.py), but that hasn't "taken", in the sense that the calls to mysql do not include the charset stuff. You may need to set the character set and collation for the DB or the server to utf8mb4. See https://dev.mysql.com/doc/refman/5.7/en/charset-applications.html for MySQL (I don't know about MariaDB. > /usr/share/mailman3-web/settings_local.py links to /etc/mailman3/mailman-web.py and there is no file /usr/share/mailman3-web/settings_local.pyc. I moved it out of the way hoping it'd get re-built, but it has not been in the months since. Python3 does not create .pyc files in the same directory as the .py. They are created in a __pycache__ sub-directory. See https://www.python.org/dev/peps/pep-3147/ for details. However, you seem to be still running a Python 2.7 version of Django et al. In this case, if it's not creating a .pyc, it is likely because it doesn't have permission. That is not a problem. If there's no .pyc, it just runs the .py. > The result of this that I get hundreds of mail messages to root (thousands, really), rapidly filling / with mail in /var/mail/root and logging in /var/log/mail.log. The mail has something like "Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive" and "DataError at /hyperkitty/api/mailman/archive (1366, u"Incorrect string value: '\\xF0\\x9F\\x98\\x8A\\x0D\\x0A...' for column 'content' at row 1")" Tell your users that smiley faces and other non-base-plane unicode emojis in email subjects add no value ;) > I have tried to trace to figure out what file is _actually_ controlling the calls to mysql. There's a file called /var/lib/ucf/cache/:etc:mailman3:mailman-web.py as well, but I have no idea what that is or if it might be used. I don't know what that is either. The underlying database access is via Django. See, e.g., https://docs.djangoproject.com/en/3.2/ref/databases/ However, it is not the MySQL queries that are the issue. > Is there something like 'mailman info' for mailman-web so I can see what files are being used? I'd love to fix this... > > 2. There's this one curious cron job... > > * * * * * www-data [ -f /usr/bin/django-admin ] && python2.7 /usr/bin/django-admin runjobs minutely --pythonpath /usr/share/mailman3-web --settings settings > > (yes, I know python2.7 is a problem... see the last paragraph below). > > These jobs start piling up. They run & run & run, and eventually the machine screeches to halt when it runs out of memory and goes belly up. This is a relatively recent development. After a while, I'll have 5 or 6 or more of these all running, looking something like this: > > www-data 6366 6364 99 15:00 ? 00:12:27 python2.7 /usr/bin/django-admin runjobs minutely --pythonpath /usr/share/mailman3-web --settings settings > > What this means in practice right now is that I'm forced to go in and kill these on a regular basis or the machine _will_ die and people _will_ shout at me. > > Does anyone have any idea why these might not be finishing? Can I comment this out completely & live happier? Any help whatsoever? You don't NEED to run this job. In the latest releases there are no minutely jobs anyway. Prior to HyperKitty 1.3.0 the update_index job was run minutely to update the search indexes with new posts, but now it's hourly. You probably have a huge backlog of unindexed posts causing this job to run for a long time (Whoosh is particularly slow at indexing, Xapian is much better). I suggest for now, you quit running the minutely jobs and just try manually running ``` python2.7 /usr/bin/django-admin runjob update_index --pythonpath /usr/share/mailman3-web --settings settings ``` which will probably run for hours if not days. Then after it completes, you can add that to cron to run hourly. > Finally, I should add that I know my current installation is fundamentally flawed because I chose to go with distro packages. I simply cannot fix it. My strong recommendation to others who follow me is that they do NOT do this. Bite the bullet and install via pip... I'm now in the process of setting up a new server that is completely based on the latest via pip installation. I have to get away from what I have or lose my sanity. Good plan. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 10 months

[MM3-users] Re: Issue with Held Messages

by Jean-Luc Wasmer

On 2016-08-20 02:08, Mark Sapiro wrote: > On 08/19/2016 10:39 PM, Jean-Luc Wasmer wrote: >> On 2016-08-19 17:58, Mark Sapiro wrote: >>> On 08/17/2016 09:17 PM, Jean-Luc Wasmer wrote: >>>> >>>> No matter what action I set for member posts (Hold for moderator, >>>> Reject) they are always delivered. >>> >>> >>> I don't know why this would be. Perhaps the member's moderation is >>> set >>> to Accept immediately - you can see this on ther member's options >>> page >>> in Postorius when logged in as a list owner. >> >> Apart from "Mode of Delivery" that is set to "Regular" for the user, >> none of the following attributes are set: >> >> Mail Delivery >> Receive own posts to the list >> Receive acknowledgement mails >> Conceal address from the subscriber list >> Avoid duplicate copies of messages > > > If you look at the user's options when logged in as a list owner, you > should see an additional "Administration options" section below those > with a "Moderation" setting. What is that set to? I log in as the admin user created with "mailman-web-django-admin createsuperuser", I created the list logged in as this admin user and its email address is displayed in the "Owners" sections of the "Members" tab. I only have that 1 other member and when I check it settings, the last section is "Avoid duplicate copies of messages?" and then there's the "Save" button. >> By the way, I didn't mention before but in Settings | Message >> Acceptance, the "Acceptable aliases:" box contains "[]". When I try to >> Save changes after modifying something, I gut "An error occured: []" >> in >> the yellow banner (instead of "The settings have been updated."). > > > What happens if you clear the Acceptable aliases box before saving? Then I get "The settings have been updated." after pressing "Save changes". But if I navigate elsewhere and come back, the brackets are back in the form. > You may find <https://wiki.list.org/x/17891998> of interest. Indeed, I actually stumbled upon it yesterday. It would have helped me, specially setting up Apache's vhost (the example provided in the bundler only helped getting half of it working). One of the issues was the permissions to the run/wsgi path. Also, as I run on FreeBSD I had to create an rc script... I don't mind sharing it, it's not super advanced but it does the job.

8 years, 8 months

[MM3-users] Re: Apache+mod_wsgi issue

by Guillermo Hernandez (Oldno7)

El 26/12/22 a las 19:19, Mark Sapiro escribió: > On 12/26/22 07:42, Odhiambo Washington wrote: > >> Hi @Guillermo Hernandez (Oldno7) <guillermo(a)querysoft.es> >> >> Does your https://site.name/user-profile/ work? > > Again, Guillermo is using uWSGI, not Apache mod_wsgi Well... now I am not sure, you know I've been confused before about that. In my httpd.conf I have: ############## LoadModule wsgi_module "/usr/local/lib/python3.9/site-packages/mod_wsgi/server/mod_wsgi-py39.cpython-39.so" WSGIPythonHome "/usr/local" WSGIDaemonProcess hyperkitty threads=25 python-path=/usr/local/mailman3 user=mailman3 group=mailman WSGIProcessGroup hyperkitty ############### And in then end of my vhost definition file there is this line: Include "/usr/local/mailman3/apache24.uwsgi.conf" In that file I have: ######### begin of apache24.uwsgi.conf Alias /favicon.ico /usr/local/mailman3/static/hyperkitty/favicon.ico Alias /static /usr/local/mailman3/static ######### # for hyperkitty Alias /static/admin /usr/local/mailman3/static/admin Alias /static/CACHE /usr/local/mailman3/static/CACHE Alias /static/django_extensions /usr/local/mailman3/static/django_extensions Alias /static/hyperkitty /usr/local/mailman3/static/hyperkitty Alias /static/mailman3 /usr/local/mailman3/static/hyperkitty Alias /static/django-mailman3 /usr/local/mailman3/static/django-mailman3 Alias /static/rest_framework /usr/local/mailman3/static/rest_framework # for postorius Alias /static/postorius /usr/local/mailman3/static/postorius Alias /static/archives /usr/local/mailman3/static/postorius ##### ###ErrorLog /var/log/httpd/hyperkitty_error.log ###CustomLog /var/log/httpd/hyperkitty_access.log combined <Directory "/usr/local/mailman3/static"> Require all granted </Directory> #### esto va en el httpd.conf ##WSGIDaemonProcess hyperkitty threads=25 python-path=/usr/local/mailman3 user=mailman group=mailman ## esta es la de Sapiro #WSGIDaemonProcess mailman-web display-name=mailman-web maximum-requests=1000 umask=0002 ####user=mailman group=mailman ####python-path=/opt/mailman/mm/venv/lib/python3.6/site-packages:/opt/mailman/mm/venv/lib/python3.6 ####python-home=/opt/mailman/mm/venv home=/opt/mailman/mm/var #### agregado el 08/07/22 WSGIPassAuthorization On #### WSGIScriptAlias /mailman3 /usr/local/mailman3/wsgi.py process-group=hyperkitty WSGIScriptAlias /hyperkitty /usr/local/mailman3/wsgi.py process-group=hyperkitty WSGIScriptAlias /postorius /usr/local/mailman3/wsgi.py process-group=hyperkitty WSGIScriptAlias /archives /usr/local/mailman3/wsgi.py process-group=hyperkitty <Directory "/usr/local/mailman3"> <Files wsgi.py> Require all granted </Files> WSGIProcessGroup hyperkitty </Directory> ####################### end of apache24.uwsgi.conf And the related wsgi.py is as follows: """ WSGI config for HyperKitty project. It exposes the WSGI callable as a module-level variable named ``application``. For more information on this file, see https://docs.djangoproject.com/en/{{ docs_version }}/howto/deployment/wsgi/ """ import os from django.core.wsgi import get_wsgi_application #### os.environ.setdefault("DJANGO_SETTINGS_MODULE", "settings") ##os.environ["DJANGO_SETTINGS_MODULE"] = "{{ project_name }}.settings" application = get_wsgi_application() ################ I don't want to put more noise in the list. But I'm confused because I always updated via pip the apache mod_wsgi thinking is was needed for my configuration. If it is not, I will stop updating it. -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

2 years, 3 months

[MM3-users] Re: {Spam?} Re: Installation Wooes

by Samir Faci

The only way I've gotten it to work so far is by using the FQN. I can switch back to 127.0.0.1 but that wasn't working. Here's the configuration I have. incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver smtp_host: 127.0.0.1 smtp_port: 25 smtp_user: smtp_pass: lmtp_host: 127.0.0.1 lmtp_port: 8024 and the end result: https://gist.github.com/safaci2000/b1c91f936df1c0d5668250cf1d503494 I tried setting the smtp_host to 127.0.0.1 and list.domain.org both result in the same issue. ie: Here's the combinations I've tried: smtp_host: 127.0.0.1 lmtp_host: 127.0.0.1 #fail smtp_host: lists.domain.org lmtp_host: 127.0.0.1 #fail Finally I even tried the exact copy from the documentation: incoming: mailman.mta.postfix.LMTPoutgoing: mailman.mta.deliver.deliverlmtp_host: 127.0.0.1lmtp_port: 8024smtp_host: localhostsmtp_port: 25configuration: python:mailman.config.postfix ## Fail. smtp_host: lists.domain.org lmtp_host: lists.domain.org # success. The error I get if I don't open port 8024 is below and in the gist i linked earlier. May 4 17:50:09 lists postfix/lmtp[2600677]: D98A21473D5: to=< testing(a)lists.domain.org>, relay=none, delay=0.05, delays=0.03/0.01/0/0, dsn=4.4.1, status=deferred (connect to lists.domain.org[198.199.98.177]:8024: Connection refused) The only way I've gotten it to work so far is by binding both the smtp_host and lmtp_host to be lists.domain.org and opening up port 8024. I'd rather not have that port open but I'm open to suggestions on what else to try. Locally on the server: PING lists.domain.org (198.199.98.177) 56(84) bytes of data. 64 bytes from 198.199.98.177 (198.199.98.177): icmp_seq=1 ttl=64 time=0.071 ms 64 bytes from 198.199.98.177 (198.199.98.177): icmp_seq=2 ttl=64 time=0.048 ms 64 bytes from 198.199.98.177 (198.199.98.177): icmp_seq=3 ttl=64 time=0.069 ms -- Samir Faci On Mon, May 4, 2020 at 9:45 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/3/20 10:04 PM, Samir Faci wrote: > > > > # Where the LMTP server listens for connections. Use 127.0.0.1 instead > of > > # localhost for Postfix integration, because Postfix only consults DNS > > # (e.g. not /etc/hosts). > > lmtp_host: lists.domain.org > > lmtp_port: 8024 > > Why, in spite of the comment, do you have > > lmtp_host: lists.domain.org > > and not > > lmtp_host: 127.0.0.1 > > Note that > > lmtp_host: 127.0.0.1 > lmtp_port: 8024 > > are the defaults. > > > > So, now it's finally working but here's a question. Does 8024 need to be > > publically accessible from the outside? > > > No. Port 8024 is only for LMTP delivery from Postfix to Mailman. > > -- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Thank you Samir Faci https://keybase.io/csgeek

4 years, 11 months

[MM3-users] Re: Edit archived email? Is it possible?

by Prasanth Nair

Hi Mark, Many thanks for your help. I have managed to modify some of the messages after following your instructions. Kind regards, Prasanth On Wed, 29 Sept 2021 at 08:08, Prasanth Nair <prasanth.nair(a)linaro.org> wrote: > Hi Mark, > > Thank you for your help. Let me try this. > > Kind regards, > Prasanth > > On Tue, 28 Sept 2021 at 18:03, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 9/28/21 6:02 AM, Prasanth Nair wrote: >> > Hello, >> > >> > Does anyone know how to edit an archived email in Mailman3? It is >> possible >> > in Mailman2 ( >> > >> https://wiki.list.org/DOC/How%20do%20I%20edit%20the%20archives%20of%20a%20M… >> ). >> > Is there any option similar to this in Mailman3? >> >> >> In some sense the process is the same but possibly even simpler in >> Mailman 3. You need to modify the underlying data which requires >> appropriate access to the server. >> >> In Mailman 3, the data are in the hyperkitty_email table in Mailman's >> database. You can get the Message-ID hash from the URL to the archived >> message, e.g. for the message to which I'm replying, the URL is >> >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >> and the hash is 7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA. Then if you have >> access, you can do database queries like >> ``` >> SELECT subject, content FROM hyperkitty_email WHERE message_id_hash = >> '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; >> ``` >> and >> ``` >> UPDATE hyperkitty_email SET content = '<new content>' WHERE >> message_id_hash = '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; >> UPDATE hyperkitty_email SET subject = '<new subject>' WHERE >> message_id_hash = '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; >> ``` >> If the message has attachments, they are in the hyperkitty_attachment >> table and can be referenced by `email_id` which is the corresponding >> `id` from the hyperkitty_email entry. >> >> You can also do similar things via `django-admin shell`. E.g. >> ``` >> $ django-admin shell >> Python ... >> (InteractiveConsole) >> >>> from hyperkitty.models.email import Email >> >>> x = >> Email.objects.filter(message_id_hash='7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA') >> >>> print(x[0].content) >> ``` >> but this requires some knowledge of HyperKitty's models and Django's ORM. >> >> -- >> 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> >

3 years, 6 months

[MM3-users] Re: Badsignature on uwsgi-error.log

by Helio Loureiro

Hi, I was wrong. It keeps happening. So the base_url didn't fix the issue. And the keys are the same in all configurations. Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro On Fri, 22 Mar 2024 at 09:37, Helio Loureiro <helio(a)loureiro.eng.br> wrote: > Hi Mark, > > Thanks for your response. I found what the issue was. > > I actually misspelled hyperkitty as hyPperkitty on the url. > > So the error on mailman-hyperkitty.cfg was: > > base_url: http://localhost:8000/hypperkitty/ > > I moved to: > > base_url: http://localhost:8000/hyperkitty/ > > and it was solved. > > Problem was the wrong link was getting a generic page from Django instead > of error. And it was failing to do the parsing probably, which was taking > wrongly as key mistake. > Best Regards, > Helio Loureiro > https://helio.loureiro.eng.br > https://github.com/helioloureiro > https://mastodon.social/@helioloureiro > > > On Thu, 21 Mar 2024 at 01:13, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 3/20/24 14:25, Helio Loureiro wrote: >> > Hi, >> > >> > I keep receiving a lot of errors like this: >> > >> > --- Logging error --- >> > Traceback (most recent call last): >> ... >> > >> "/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py", >> > line 55, in unsign >> > raise BadSignature('Signature "%s" does not match' % sig) >> > django.core.signing.BadSignature: Signature >> "F6V0Dr_SvBsx5-cY8vcvLXrX8tA" >> > does not match >> ... >> > >> > The api_key on mailman-hypperkitty.cfg, SECRET_KEY and >> MAILMAN_ARCHIVE_KEY >> > on setting.py are the same. >> >> >> Of those three, the api_key on mailman-hypperkitty.cfg and >> MAILMAN_ARCHIVE_KEY must match. SECRET_KEY is different. It is a Django >> thing and has nothing to do with the others. See >> https://docs.djangoproject.com/en/5.0/ref/settings/#secret-key >> >> If you changed it, that's the issue. If you know what it was previously, >> you could set the previous value in SECRET_KEY_FALLBACKS, see >> https://docs.djangoproject.com/en/5.0/ref/settings/#secret-key-fallbacks >> >> -- >> 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://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 helio(a)loureiro.eng.br >> >

1 year, 1 month

[MM3-users] Re: users, users and users (was Re: Re: Cannot request password reset: "The e-mail address is not assigned to any user account")

by Mark Sapiro

On 1/28/22 00:41, IOhannes m zmölnig wrote: > > i'm afraid i still do not fully understand which types of "users" there > are. > > > afaics, there are three different types: > - django users > this is what get's listed under > <https://lists.mailman3.org/admin/auth/user/> Correct. > - mailman accounts > this is what is created when you visit > <https://lists.mailman3.org/accounts/signup/> No. That creates a Django user, not a Mailman user. What you think of as a Mailman account is actually a Django account. > - email addresses > this is what is created when i subscribe to a list *without* having > an account. > e.g. via the "Subscribe" button on > <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Mailman core has users and addresses. A user has one or more associated addresses. When you subscribe to a list without having an account in that way, or via email to list-join or list-subscribe or by being mass subscribed by the list admin or by being imported by `mailman import21`, assuming you are previously unknown, this creates a Mailman user with an associated address and subscribes the user or address. Each user has a primary address and zero or more additional linked addresses. The user can be subscribed to a list as a user in which case, delivery if any is to the user's primary address, or can be subscribed as an address. > afaiu, (multiple) "email addresses" can be associated with a single > "mailman account" (but this is strictly optional). Yes, see above. > if an "email address" is first used to subscribe to a list without a > mailman account, and later a mailman account is created with that very > email address, they get automatically associated. > a single "email address" cannot be associated with more than one > "mailman accounts". Based on the above, your "mailman accounts" are actually Django accounts. With that in mind, the above is correct, but there is no real link between Mailman users and Django users. When you are logged in to the web UI you are logged in as a Django user, and Postorius and HyperKitty know that user's email address and can therefore know if it is a list member and know what address to subscribe or unsubscribe as requested. > i think i got this one right (as it seems pretty straightforward). > > what i don't fully grasp yet is the relation between "django users" and > "mailman accounts". As I have said, what you are calling a mailman account is a Django user and not a Mailman user. > intuitively, i would have thought that they are identical. They are, but they are not Mailman core users. > now mark wrote: > > a Django user, which is distinct from a Mailman user. The users you > > added via the web API are Mailman users, but in order to access their > > lists via the web UI they have to `sign up` to create a Django > > account. > > that seems to indicate, that a "django user" is a (strict) superset of a > "mailman account". No. A Django user is the same thing as what you call a mailman account. A Mailman core user is a separate thing entirely. > you (as admin) can create "mailman accounts" via the web API¹, but they > are only expanded to "mailman accounts" if you (as user) go through the > "Sign Up" process. No. An admin can create Mailman users via the Postorius UI. A Django superuser can also create Django users through the Django admin UI. > otoh, if you create an initial "django user" by signing up, you > automatically create a "mailman account". Because they are the same thing. When you go to the Sign-up link on a Postorius or Hyperkitty page you go to https://example.com/accounts/signup/, and that's Django, not Mailman. > so are the two distinct concepts that are just associated via some > common property (e.g. the email address), or is there some intrinsic > relationship between the two (e.g. parent-child inheritance relationship)? They are distinct. Django users have email addresses and Mailman users have email addresses and they can be associated in that way. There is no other link. > so my recent experiment (comparing the output of > <https://lists.example.com/admin/auth/user/> with that of `[u for u in > getUtility(IUserManager).users]`) indicates that they are indeed > distinct objects that *can* be associated with each other. > > could you please clarify this? I hope I have. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

[MM3-users] Re: mailman3-web and the django middleware problem

by Thomas Stein

Am 2024-04-26 00:52, schrieb Mark Sapiro: > On 4/25/24 14:01, Thomas Stein wrote: >> Am 2024-04-25 22:03, schrieb Mark Sapiro: >>> >>> I don't know how things are arranged in the Debian/Ubuntu package, >>> but you may have a settings.py which at the end does something like >>> ``` >>> try: >>> from settings_local import * >>> except ImportError: >>> pass >>> ``` >>> If that is the case, adding the above snippet to the end of >>> settings_local.py should work. >> >> Yes, that's the case. I added the snippet in question to >> settings_local.py but this leads to another error: >> >> File "/usr/share/mailman3-web/settings.py", line 503, in <module> >> from settings_local import * >> File "/usr/share/mailman3-web/settings_local.py", line 194, in >> <module> >> x = list(MIDDLEWARE) >> ^^^^^^^^^^ >> NameError: name 'MIDDLEWARE' is not defined >> dpkg: error processing package mailman3-web (--configure): > > Yes. I understand. In your case, MIDDLEWARE is only defined in > settings.py and not in settings_local.py. As I understand it originally > you added > ``` > x = list(MIDDLEWARE) > x.insert(0, 'allauth.account.middleware.AccountMiddleware') > MIDDLEWARE = x > ``` > to settings.py and you say it didn't help. I don't know why that > wouldn't work as long as there is no setting for MIDDLEWARE in > settings_local.py and you added that after the MIDDLEWARE setting in > settings.py. > When you say it didn't help, do you mean you still get the > > django.core.exceptions.ImproperlyConfigured: > allauth.account.middleware.AccountMiddleware must be added to > settings.MIDDLEWARE > > message or something else? I note that the original post in this thread > refers to /etc/mailman3/mailman-web.py which is presumably where the > package ultimately puts the Django settings, and I don't know what > `dpkg --configure` is doing. > > One thing you could try is in settings_local.py, put > ``` > from settings import MIDDLEWARE > x = list(MIDDLEWARE) > x.insert(0, 'allauth.account.middleware.AccountMiddleware') > MIDDLEWARE = x > ``` > to work around the NameError. After that I get: File "/usr/share/mailman3-web/urls.py", line 20, in <module> from django.conf.urls import include, url ImportError: cannot import name 'url' from 'django.conf.urls' (/usr/lib/python3/dist-packages/django/conf/urls/__init__.py) dpkg: error processing package mailman3-web (--configure): installed mailman3-web package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: I guess I'll wait for the new package for now. thanks again! t.

11 months, 4 weeks

[MM3-users] Re: MM2.1 -> MM3.3 migration. To hold or not hold

by Gerald Vogt

Hi, are you sure you are both talking about the same setting? You wrote initially: "The list settings have automatically (and appropriately) been set to hold mails when I go to Settings -> Message Acceptance -> "Default action to take when a *non-member* posts to the list" -- it says Hold for moderation" That's for non-members, not for members. That does not apply to users which you have mass subscribed. For those there is the "Default action to take when a member posts to the list". That's the one Mark Sapiro mentioned. Regards, Gerald On 18.11.24 10:59, mark(a)suburbia.org.au wrote: > Hi Mark, > > Thanks for taking the time to reply. > > Mark Sapiro wrote: >> On 11/16/24 21:41, mark(a)suburbia.org.au wrote: > >>> However, I've just done a test of a newly added user (a test email account for me), seen that the Moderation Action is None, but when I posted to the list from the address, it was not held for moderation, and went through. >>> Am I missing something with the expected functionality? >>> A member's moderation action of None means use the Default action to take when a member posts to the list. Is that set to Hold for moderation? >> Actually, it is good practice to set that to Hold for moderation for >> all lists or at least all those that don't require moderator approval >> for subscription to prevent a spammer from subscribing and spamming the >> list. Then, upon approving a member's post you can also set the member's >> moderation action to default processing and upon discarding a spammers >> post, you can also set the spammer's moderation action to Discard. > > I agree. My point was that the list is set as default to hold for moderation. But, a new user who sends an email to the list, whose Moderation Action is set to "none", was able to email the list without the email being held for moderation. I would have expected based on the threads I quoted, that a user who is added to the list via Mass subscribe, would not be able to send to the list without it being held. > > I'm happy to do more testing, provide other information/logs as desired if that would help? > > cheers, > Mark > _______________________________________________ > 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 vogt(a)spamcop.net

5 months

[MM3-users] Re: config.pck from mailman2 has characters that won't import with import21

by Mark Sapiro

On 7/20/24 10:19 PM, Greg Newby wrote: > Hi. I've set up MM3 in a venv successfully and am importing my legacy lists. > > I no longer have a running instance of mailman2, so don't know how I can > change the offending list settings (i.e., in config.pck). > > The problem seems to be a digest footer from the previous incarnation of > the list (list name is edited below, to protect the innocent): That's not the issue. > (venv) mailman@mail:~$ mailman import21 abc(a)lists.abcabcabc.org > /var/lib/mailman/lists/abc/config.pck > Unable to convert mailing list attribute: msg_footer with value > "_______________________________________________ > ${display_name} mailing list -- ${listname} > To unsubscribe send an email to ${short_listname}-leave@${domain} > %(web_page_url)slistinfo/%(_internal_name)s" > Unable to convert mailing list attribute: digest_footer with value > "_______________________________________________ > ${display_name} mailing list -- ${listname} > To unsubscribe send an email to ${short_listname}-leave@${domain} > %(web_page_url)slistinfo/%(_internal_name)s" The above are non-fatal. The importer just won't make list specific templates for those. If you need the footers to be different from the defaults, you will need to create them manually. > Importing members [------------------------------------] 0% > Traceback (most recent call last): > File "/opt/mailman/venv/bin/mailman", line 8, in <module> > sys.exit(main()) > ^^^^^^ > File "/opt/mailman/venv/lib/python3.12/site-packages/click/core.py", line > 1157, in __call__ > return self.main(*args, **kwargs) > ^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman/venv/lib/python3.12/site-packages/click/core.py", line > 1078, in main > rv = self.invoke(ctx) > ^^^^^^^^^^^^^^^^ > File > "/opt/mailman/venv/lib/python3.12/site-packages/mailman/bin/mailman.py", > line 69, in invoke > return super().invoke(ctx) > ^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman/venv/lib/python3.12/site-packages/click/core.py", line > 1688, in invoke > return _process_result(sub_ctx.command.invoke(sub_ctx)) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman/venv/lib/python3.12/site-packages/click/core.py", line > 1434, in invoke > return ctx.invoke(self.callback, **ctx.params) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/opt/mailman/venv/lib/python3.12/site-packages/click/core.py", line > 783, in invoke > return __callback(*args, **kwargs) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File > "/opt/mailman/venv/lib/python3.12/site-packages/click/decorators.py", line > 33, in new_func > return f(get_current_context(), *args, **kwargs) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File > "/opt/mailman/venv/lib/python3.12/site-packages/mailman/commands/cli_import.py", > line 89, in import21 > import_config_pck(mlist, config_dict) > File > "/opt/mailman/venv/lib/python3.12/site-packages/mailman/utilities/importer.py", > line 578, in import_config_pck > import_roster(mlist, config_dict, members, MemberRole.member) > File > "/opt/mailman/venv/lib/python3.12/site-packages/mailman/utilities/importer.py", > line 625, in import_roster > _import_roster(mlist, config_dict, iterator, role, action=action) > File > "/opt/mailman/venv/lib/python3.12/site-packages/mailman/utilities/importer.py", > line 645, in _import_roster > if IBanManager(mlist).is_banned(email): > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File > "/opt/mailman/venv/lib/python3.12/site-packages/mailman/database/transaction.py", > line 106, in wrapper > return function(args[0], config.db.store, *args[1:], **kws) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File > "/opt/mailman/venv/lib/python3.12/site-packages/mailman/model/bans.py", > line 103, in is_banned > re.match(ban.email, email, re.IGNORECASE) is not None): > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3.12/re/__init__.py", line 167, in match > return _compile(pattern, flags).match(string) > ^^^^^^^^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3.12/re/__init__.py", line 307, in _compile > p = _compiler.compile(pattern, flags) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3.12/re/_compiler.py", line 745, in compile > p = _parser.parse(p, flags) > ^^^^^^^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3.12/re/_parser.py", line 979, in parse > p = _parse_sub(source, state, flags & SRE_FLAG_VERBOSE, 0) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3.12/re/_parser.py", line 460, in _parse_sub > itemsappend(_parse(source, state, verbose, nested + 1, > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3.12/re/_parser.py", line 690, in _parse > raise source.error("multiple repeat", > re.error: multiple repeat at position 11 The list's ban_list has an invalid regexp. Do the following in Mailman 3's `mailman shell` ``` bin/mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. >>> import pickle >>> from contextlib import ExitStack >>> from mailman.commands.cli_import import _Mailman, _Bouncer >>> from mailman.utilities.modules import hacked_sys_modules >>> with ExitStack() as resources: ... resources.enter_context(hacked_sys_modules('Mailman', _Mailman)) ... resources.enter_context( ... hacked_sys_modules('Mailman.Bouncer', _Bouncer)) ... with open('/path/to/config.pck', 'rb+') as fp: ... data = pickle.load(fp) ... print(data['ban_list']) ... data['ban_list'] = [] ... fp.seek(0) ... pickle.dump(data, fp) ... >>> ``` This will print the ban_list so you can see it and then save the config.pck with an empty ban_list. That config.pck will no longer be usable in Mailman 2.1 because the pickle protocol is too high and the bounce_info items if any will be corrupted, but it should work with import21. Note that all the ExitStack and hacked_sys_modules stuff is only needed if there is bounce_info in the config.pck, but it doesn't hurt in any case. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months

[MM3-users] Re: config incoming email in my domain cpanel

by tlhackque

You've said you're working with labbrands.com. labbrands.com has address 192.185.51.89 mail.labbrands.com has address 192.185.51.89 www.labbrands.com is an alias for labbrands.com. telnet proves that Exim is running on that IP address. Either you're running it, or hostgator is redirecting the SMTP ports. You added: lists.labbrands.com has address 190.145.27.66 Presumably that's a different machine. So that now needs an MX record, and a firewall routing. And the SPF records ... and spam and virus filters, and all the other stuff you need to setup an independent, public-facing smtp server. But at least you won't have to relay. Good luck. On 03-Aug-17 16:55, Rafael Mora wrote: > El jue., 3 ago. 2017 a las 15:49, tlhackque via Mailman-users (< > mailman-users(a)mailman3.org>) escribió: > >> I think you're confused. >> >> You already have mail.labbrands.com set up as the MX record for >> labbrands.com. And it has an A record with the same address as your >> webserver. >> > I'm working with the hostgator mailserver, we are not running a local > mailserver. > > As suggested I added an A record like this: > [image: image.png] > > Is it correct? is it redirecting to my Ip so I can redirect it to my > postfix/mm3 server? > > >> So if you're getting e-mail on that domain, there's another e-mail >> server running on that IP address. You can't have 2 servers on port >> 25. In that case, as has been noted before, you'll need to setup a >> relay in that server, not a firewall redirect. Depending on your MTA, >> you would need to relay to your internal server. And make sure your >> firewall setup allows your MTA to do this. >> >> We can see it's EXIM: >> >> telnet mail.labbrands.com 25 >> Trying 192.185.51.89... >> Connected to mail.labbrands.com (192.185.51.89). >> Escape character is '^]'. >> help >> 220-gator4137.hostgator.com ESMTP Exim 4.87 #1 Thu, 03 Aug 2017 15:47:48 >> -0500 >> 220-We do not authorize the use of this system to transport unsolicited, >> 220 and/or bulk e-mail. >> 214-Commands supported: >> 214 AUTH STARTTLS HELO EHLO MAIL RCPT DATA NOOP QUIT RSET HELP >> quit >> 221 gator4137.hostgator.com closing connection >> Connection closed by foreign host. >> >> Or, consolidate all your e-mail to one server - which is a lot easier to >> manage unless you have a really big operation. Postfix is probably the >> right choice, but requires more setup. >> >> Although Mailman3 configuration is not well documented (as you've >> discovered), you may want to get help from someone with more general >> network and mail experience. You're now into territory that is, as >> Simon indicated, not Mailman-specific. >> >> On 03-Aug-17 16:28, Rafael Mora wrote: >>> El jue., 3 ago. 2017 a las 15:26, Mark Sapiro (<mark(a)msapiro.net>) >> escribió: >>>> On 08/03/2017 01:22 PM, Rafael Mora wrote: >>>>> El jue., 3 ago. 2017 a las 15:18, Mark Sapiro (<mark(a)msapiro.net>) >>>> escribió: >>>>>> You need to forward port 25 for SMTP mail delivery and if you want the >>>>>> web UI (Postorius and HyperKitty) accessible from the outside, port 80 >>>>>> for http and/or port 443 for https >>>>>> < >>>>>> >> https://www.iana.org/assignments/service-names-port-numbers/service-names-p… >>>>>>> . >>>>> I mean for incoming mail redirected from my hostgator hosting, because >>>> when >>>>> I suscribe an email address MM3 sends a confirmation email, so I have >> to >>>>> reply to be suscribed to the list. >>>> As I said, for mail delivery you need to forward port 25 to the Mailman >>>> server. >>>> >>> Ok so I'll redirect in my zentyal firewall the port 25 to my local >> centos7 >>> with postfix and MM3 with IP 192.168.1.42. Thanks Mark. >>> >>> >>>> -- >>>> 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/ >>>> >> -- >> This communication may not represent my employer's views, >> if any, on the matters discussed. >> >> _______________________________________________ >> Mailman-users mailing list >> mailman-users(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> -- This communication may not represent my employer's views, if any, on the matters discussed.

7 years, 8 months

[MM3-users] Re: The message is larger than the 40 KB maximum size

by Mohsen Masoudfar

It seems something is fundamentally wrong with Hyperkitty: From /var/log/mailman3/mailman.log --- 49 Sep 21 21:49:25 2020 (24925) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/urls: <html><title>Auth required</title><body> 50 <h1>Authorization Required</h1></body></html> (401) 51 Sep 21 21:49:25 2020 (24925) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/urls: <html><title>Auth required</title><body> 52 <h1>Authorization Required</h1></body></html> (401) 53 Sep 21 21:49:25 2020 (24925) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/urls: <html><title>Auth required</title><body> 54 <h1>Authorization Required</h1></body></html> (401) 55 Sep 21 21:49:26 2020 (24918) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/archive: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2. 0//EN"> 56 <html><head> 57 <title>503 Service Unavailable</title> 58 </head><body> 59 <h1>Service Unavailable</h1> 60 <p>The server is temporarily unable to service your 61 request due to maintenance downtime or capacity 62 problems. Please try again later.</p> 63 <hr> 64 <address>Apache/2.4.29 (Ubuntu) Server at localhost Port 80</address> 65 </body></html> 66 (503) 67 Sep 21 21:49:26 2020 (24918) Exception in the HyperKitty archiver: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> 68 <html><head> 69 <title>503 Service Unavailable</title> 70 </head><body> 71 <h1>Service Unavailable</h1> 72 <p>The server is temporarily unable to service your 73 request due to maintenance downtime or capacity 74 problems. Please try again later.</p> 75 <hr> 76 <address>Apache/2.4.29 (Ubuntu) Server at localhost Port 80</address> 77 </body></html> 78 Sep 21 21:49:26 2020 (24918) Traceback (most recent call last): 79 File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message 80 url = self._send_message(mlist, msg) 81 File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 210, in _send_message 82 raise ValueError(result.text) 83 ValueError: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> 84 <html><head> 85 <title>503 Service Unavailable</title> 86 </head><body> 87 <h1>Service Unavailable</h1> 88 <p>The server is temporarily unable to service your 89 request due to maintenance downtime or capacity 90 problems. Please try again later.</p> --- Thanks Mohsen -----Original Message----- From: Mohsen Masoudfar <mmasoudf(a)aaas.org> Sent: Monday, September 21, 2020 12:24 PM To: Mark Sapiro <mark(a)msapiro.net>; mailman-users(a)mailman3.org Subject: [MM3-users] Re: The message is larger than the 40 KB maximum size [EXTERNAL EMAIL] Hi Mark, Thank you Mark and Phil for your help. It seems I got stuck! 1- I tried to set up the max_message_size in WUI under: listname > settings > Message Acceptance > Maximum message size to 0. After hitting save button, I got the error message: " An error occured: Unknown attribute: max_message_size" 2- I checked the python files and found this file, where, it seems, the default value is defined: /usr/lib/python3/dist-packages/mailman/styles/base.py : mlist.max_message_size = 40 I changed this value to 0, saved the file, restarted the mailman and postgresql (not sure if needed) and sent an email with a large attachment to my test list with just two members. I got the response email: The message is being held because: The message is larger than the 40 KB maximum size 3- I totally agree that the most important issue is the fact that the message vanished with the production list. I repeated the same with a (test) list which has two members, I got the email mentioning the 40 KB limit and I could release it. This is how I am running my tests now. I repeated it with the original list (with 197 members) the message disappeared again. I can send an email to the list with 197 members, without this attachment and it works. 4- I checked the folders, under /var/lib/mailman3/queue/, all folders are empty: archive/ bad/ bounces/ command/ digest/ in/ nntp/ out/ pipeline/ retry/ shunt/ virgin/ Thanks Mohsen -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, September 18, 2020 4:00 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: The message is larger than the 40 KB maximum size [EXTERNAL EMAIL] On 9/18/20 12:48 PM, Phil Stracchino wrote: > On 2020-09-18 15:32, Mohsen Masoudfar wrote: >> Hi, >> >> I am trying to find how I may change this. I have an attachment of 800 KB, and when I post it to the list, I do not get any response and nothing is hold. It looks like the message is just dropped. > > > Assuming that this works roughly the same in mm3 as it does in mm2, > you can set max_message_size in your list configuration. It defaults > to 40; units are KB. Yes, and you can set it to zero for "unlimited", but even if that is a satisfactory workaround, the much more interesting question, at least to me, is why does the message "disappear". -- 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… _______________________________________________ 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…

4 years, 7 months

[MM3-users] django-allauth 0.59.0 (was: django-allauth failures, but only for some users)

by Jered Floyd

FYI, django-allauth 0.59.0 was released on December 12 and incorporates the patches to work properly with Mailman again. The only other issue is formatting of the login page. As I noted previously, this can be fixed by copying site-packages/allauth/templates/socialaccount/login.html to site-packages/django_mailman3/templates/socialaccount/login.html and changing the first line from: {% extends "socialaccount/base_entrance.html" %} to {% extends "django_mailman3/profile/base.html" %} --Jered ----- On Dec 7, 2023, at 9:57 PM, Jered Floyd jered(a)convivian.com wrote: > You're welcome. Thank you for all your hard work making Mailman 3 happen at all! > > I think django_allauth integration is again stable, but for now I'm pinning > 0.58.2 + this patch. I'll test again once there is another release > notification, but since I rebuild by container image every 2-3 weeks I am > getting exhausted by surprises... > > --Jered > > ----- On Dec 7, 2023, at 7:44 PM, Mark Sapiro mark(a)msapiro.net wrote: > >> On 12/7/23 14:33, Jered Floyd wrote: >>> >>> FYI, The django-allauth author has proposed fixing both of these with an even >>> simpler change, which is now upstream and queued for a future release. >>> >>> --Jered >> >> >> Thank you again for your work on this. I can confirm that the patch >> below fixes my issue with >> https://msapiro.net/accounts/social/connections/ and SITE_ID = 0. >> >> >>> --- a/allauth/socialaccount/adapter.py >>> +++ b/allauth/socialaccount/adapter.py >>> @@ -228,7 +228,10 @@ class DefaultSocialAccountAdapter(object): >>> provider_to_apps = {} >>> >>> # First, populate it with the DB backed apps. >>> - db_apps = SocialApp.objects.on_site(request) >>> + if request: >>> + db_apps = SocialApp.objects.on_site(request) >>> + else: >>> + db_apps = SocialApp.objects.all() >>> if provider: >>> db_apps = db_apps.filter(Q(provider=provider) | Q(provider_id=provider)) >>> if client_id: >> >> -- >> 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://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 jered(a)convivian.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 jered(a)convivian.com

1 year, 4 months

[MM3-users] Re: Scheduled tasks

by Darren Smith

I will take up any problems with the installation with the creator. However, I was able to find and run some of the scripts this afternoon, and I'm running some of the longer-running ones tonight while the usage is lower. As for bogging down - I mean attempting to click on an email can take a LONG time to render, and we frequently get 504 gateway timeouts (the calls to hyperkitty are timing out). I am trying hard to figure out why this is happening and to try to tune the system. I still suspect that there are some inefficiencies with how the database is being used, or how the database is doing things. I will take a look at qcluster, that was interesting info and hopefully it can help me out. Thanks for your response, -Darren On Thu, Jun 7, 2018 at 4:16 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/7/18 9:59 AM, Darren Smith wrote: > > All, > > > > I am looking more through the documentation of the Mailman Suite here: > > > > https://media.readthedocs.org/pdf/gnu-mailman/latest/gnu-mailman.pdf > > > > In section 3.2.5 it talks about the scheduled tasks that need to be run > to > > do "specific routine functions" in hyperkitty. > > > > I installed through the easy install script found here: > > > > https://github.com/iomarmochtar/mailman3_ei/ > > > > However, I can't find anything in THAT documentation that talks about > these > > cron jobs, and in fact the Mailman Suite isn't installed through that > > script. > > > That is a third party project. If you have issues with it, you should > take them up with @iomarmochtar. > > > > Can someone point me to any other documentation about the tasks that need > > to be run on a continual basis? > > > The section 3.2.5 you refer to tells you what needs to be set up in > cron. For a list of the jobs tat are run, use > > django-admin runjobs --list > > > . Our hyperkitty installation seems to be > > bogging down more and more, and I am hoping that it will be as simple as > > just running some jobs that haven't been on our radar. > > > what do you mean by 'bogging down'? If you aren't doing so, setting up > qcluster as in section 3.2.3 may help. > > -- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

6 years, 10 months

[MM3-users] Re: Installing mailman 3

by Abhilash Raj

Hi, On Tue, Aug 1, 2017, at 02:11 PM, Rafael Mora wrote: > It's ok now, but still I can't make it send the confirmation email > > This is from mailman.log: > > > [mailman@localhost logs]$ tail -f mailman.log > Aug 01 15:59:18 2017 (2327) lmtp runner started. > Aug 01 15:59:18 2017 (2333) virgin runner started. > Aug 01 15:59:18 2017 (2332) retry runner started. > Aug 01 15:59:18 2017 (2330) pipeline runner started. > Aug 01 15:59:18 2017 (2325) command runner started. > Aug 01 15:59:19 2017 (2328) nntp runner started. > Aug 01 15:59:19 2017 (2326) in runner started. > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET > /3.0/lists?count=0&page=1&advertised=true HTTP/1.1" 200 90 > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET > /3.0/lists?count=10&page=1&advertised=true HTTP/1.1" 200 90 > Aug 01 16:01:38 2017 (2331) 127.0.0.1 - - "GET /3.0/domains HTTP/1.1" 200 > 90 > > > > > What should I do? If you are talking about Account confirmation emails, they usually are sent out from Django and not Mailman Core itself. To configure Django you need to edit the `settings.py` file, wherever that is one your installation. If you are following the guide mentioned at http://docs.mailman3.org/en/latest/prodsetup.html, it should be at `mailman-suite/mailman-suite_project/settings.py`. To configure your Django to send emails, have a look at http://docs.mailman3.org/en/latest/config-web.html#setting-up-email-required. That documentation page has pretty much everything you need in order to have a running Web Frontend, please go through it and make sure you have everything configured. Finally, the actual emails from Mailing lists are supposed to be handled by Core. You need to configure Postorius & Mailman both to communicate. The settings are mentioned http://docs.mailman3.org/en/latest/config-core.html#configuring-mta here. Hope that helps! > > > > > > > El mar., 1 ago. 2017 a las 15:36, Mark Sapiro (<mark(a)msapiro.net>) > escribió: > > > On 8/1/17 1:14 PM, Rafael Mora wrote: > > > > > > Why does it say Address already in use? > > > > > > Because you are starting lm tp runner and it's already running. > > > > Do 'mailman stop'. Then ensure no Mailman processes are running. kill > > any if necessary. Then do 'mailman start'. > > > > -- > > 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/ > > > -- > > Atentamente / Best Regards > > Ing. Rafael Mora > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- thanks, Abhilash Raj

7 years, 8 months

[MM3-users] Re: Request for help debugging a hyperkitty connection issue

by Stephen Daniel

Got it in one! I had put "www.LISTDOMAIN.org/archive" in as the base URL in mailman-hyperkitty.cfg. No such host exists. Replaced with "LISTDOMAIN.org/archive" and all is well! Thanks!!! To the contributing community: would there be a way to enhance the logging of this error to include the resource that failed to connect? Thanks. -- Stephen Daniel On Thu, Jan 6, 2022 at 5:15 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/6/22 12:12 PM, Stephen Daniel wrote: > > > > I have two problems. One is with getting list mail out of GCP. I am > > working on that. The issue I don't know how to address is a problem with > > hyperkitty. Nothing is being archived. When I send an email through my > > test list, this message shows up in the mailman log: > > > > Jan 04 11:57:26 2022 (806) Exception in "hyperkitty" archiver > > > > Traceback (most recent call last): > > > > File > > "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connection.py", > > line 175, in _new_conn > > > > (self._dns_host, self.port), self.timeout, **extra_kw > > > > File > > > "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/util/connection.py", > > line 73, in create_connection > > > > for res in socket.getaddrinfo(host, port, family, > socket.SOCK_STREAM): > > > > File "/usr/lib/python3.7/socket.py", line 748, in getaddrinfo > > > > for res in _socket.getaddrinfo(host, port, family, type, proto, > flags): > > > > socket.gaierror: [Errno -2] Name or service not known > > > > > > This triggers a bunch more tracebacks. > > > > Then I get this: > > > > Jan 04 11:57:27 2022 (797) Connection to HyperKitty failed: > > HTTPSConnectionPool(host='www.XXXXX.dev <http://www.xxxxx.dev/>', > > port=443): Max retries exceeded with url: /archives/api/mailman/archive > > (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object > > at 0x7f2114e14e10>: Failed to establish a new connection: [Errno -2] Name > > or service not known')) > > > What is your setting for base_url: in mailman-hyperkitty.cfg?. Can you get > > wget -O- xxx > > where xxx is base_url with `api/` appended. This should return an html > page of API documentation. > > If your base_url: seems good and its scheme is `https`, try changing it > to `http`. > > > -- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

3 years, 3 months

[MM3-users] Re: new list not working

by Christian

When I ran mailman members -r -n enabled redlatinleg(a)lists.ccalternatives.org I did receive a list of subscribers for the new list I created, not just the owner or moderator. Upon closer examination, another of my longtime working lists is also not working. Similar behavior as the new list I created in that I see the message has been archived, but not distributed to the subscribers. -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Thursday, March 9, 2023 1:44 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: new list not working On 3/9/23 13:26, Christian via Mailman-users wrote: > I am only having issues with the new list. > > > > Below are logfile entries > > > > Smtp.log > > ++++++ > > Mar 09 20:57:09 2023 (9401) Available AUTH mechanisms: LOGIN(builtin) > PLAIN(builtin) > > Mar 09 20:57:09 2023 (9401) Peer: ('127.0.0.1', 35982) > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) handling connection > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'LHLO zarathustra.ccalternatives.org' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'MAIL FROM:<christian(a)naturalintelligence.us> SIZE=3653' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) sender: > christian(a)naturalintelligence.us > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'RCPT TO:<redlatinleg(a)lists.ccalternatives.org>' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) recip: > redlatinleg(a)lists.ccalternatives.org > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'DATA' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'QUIT' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) connection lost > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) Connection lost > during _handle_client() This is the post being delivered to mailman and is expected. > > > Access.log Irrelevant. > Mailman.log > > ++++++++ > > Mar 09 20:57:09 2023 (9400) ACCEPT: > <032101d952c9$caf09990$60d1ccb0$(a)naturalintelligence.us> > > Mar 09 13:03:42 2023 (9397) HyperKitty archived message > <032101d952c9$caf09990$60d1ccb0$(a)naturalintelligence.us> to > https://lists.ccalternatives.org/archives/list/redlatinleg@lists.ccalt > ernatives.org/message/PAJ5GDGGK74LWHQINB32BDV22BMR6LRQ/ These are the expected messages (there seems to be a time zone difference) and in the absence of any other error type messages say the message should have been delivered to the eligible recipients. Are there any? See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/ CTAF4RDJ2CTNCGI7MXFYL3Q5HTGYMZH6/ or the results from ``` mailman members -r -n enabled redlatinleg(a)lists.ccalternatives.org ``` > mailmansuite.log not relevant. -- 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/ ZVY3EFBA5WQKYS6E7AS475TNY6C4NJQU/ This message sent to csa(a)web-analysts.net

2 years, 1 month

[MM3-users] Re: SMTPSenderRefused - howto enable STARTTLS for local mail drop

by Stefan Bauer

Unfortunately i need this, as the postfix is listening on all interfaces and we have the policy to enforce TLS only. Nothing special in the logs: Dec 07 08:14:14 2021 (12303) Using agent: <mailman.mta.bulk.BulkDelivery object at 0x7fbc29b1c4a8> Dec 07 08:14:14 2021 (12303) Connecting to localhost:25 Dec 07 08:14:14 2021 (12303) envsender: v-test-bounces@domain, recipients: ['recipient(a)own.domain'], size(msgtext): 5809 Dec 07 08:14:14 2021 (12303) <kcEE.aBI3BVc2RCi6kAxA4PJ0hg.ADrcCDrr1wE(a)mailsrv103.my.domain> smtp to v-test@domain for 1 recips, completed in 0.008081912994384766 seconds Dec 07 08:14:14 2021 (12303) <kcEE.aBI3BVc2RCi6kAxA4PJ0hg.ADrcCDrr1wE(a)mailsrv103.my.domain> post to v-test@domain from v-test@domain, 5336 bytes Dec 07 08:14:47 2021 (12297) Peer: ('127.0.0.1', 43210) Dec 07 08:14:47 2021 (12297) ('127.0.0.1', 43210) handling connection Dec 07 08:14:47 2021 (12297) b'220 ml01.my.domain GNU Mailman LMTP runner 2.0\r\n' Dec 07 08:14:47 2021 (12297) ('127.0.0.1', 43210) EOF received Dec 07 08:14:47 2021 (12297) Connection lost during _handle_client() Dec 07 08:14:47 2021 (12297) ('127.0.0.1', 43210) connection lost Dec 07 08:15:00 2021 (12297) Peer: ('127.0.0.1', 43516) Dec 07 08:15:00 2021 (12297) ('127.0.0.1', 43516) handling connection Is my mailman version maybe too old for this setting? I'm running GNU Mailman 3.1.1 (Between The Wheels) Thank you. Am Mo., 6. Dez. 2021 um 19:04 Uhr schrieb Mark Sapiro <mark(a)msapiro.net>: > On 12/6/21 2:51 AM, Stefan Bauer wrote: > > Need to bring this up again. Django now sends with STARTTLS, but mailman > > itself, does still only drop mails in cleartext. > > Dec 6 11:47:33 al01 postfix/lmtp[7598]: A6422600510: > > to=<remote-party@remote>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.01, > > delays=0.01/0/0/0.01, dsn=2.0.0, status=sent (250 Ok) > > Dec 6 11:47:33 al01 postfix/qmgr[29156]: A6422600510: removed > > Dec 6 11:47:35 al01 postfix/smtpd[8092]: disconnect from localhost[::1] > > ehlo=1 mail=2 rcpt=2 data=2 commands=7 > > > > No starttls=1 at all :( > > > > Does the above settings work for anyone? > > > > etc/mailman3/mailman.cfg > > [mta] > > incoming: mailman.mta.postfix.LMTP > > outgoing: mailman.mta.deliver.deliver > > > > smtp_host: localhost > > smtp_port: 25 > > smtp_user: > > smtp_pass: > > smtp_verify_hostname: false > > smtp_verify_cert: false > > smtp_secure_mode: starttls > > > This should work. What do you see in Mailman's smtp.log if you add > ``` > [logging.smtp] > level: debug > ``` > to mailman.cfg. > > However, do you really need this. It will only affect delivery from > Mailman to Postfix via the loopback interface on the localhost. > > -- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

3 years, 4 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

New output from command 'postconf -n ': [root@localhost ~]# postconf -n alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix data_directory = /var/lib/postfix debug_peer_level = 2 debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin ddd $daemon_directory/$process_name $process_id & sleep 5 html_directory = no inet_interfaces = localhost inet_protocols = all local_recipient_maps = hash:/var/lib/mailman/var/data/postfix_lmtp mail_owner = postfix mailq_path = /usr/bin/mailq.postfix manpage_directory = /usr/share/man mydestination = $myhostname, localhost.$mydomain, localhost newaliases_path = /usr/bin/newaliases.postfix owner_request_special = no queue_directory = /var/spool/postfix readme_directory = /usr/share/doc/postfix-2.10.1/README_FILES recipient_delimiter = + relay_domains = hash:/var/lib/mailman/var/data/postfix_domains sample_directory = /usr/share/doc/postfix-2.10.1/samples sendmail_path = /usr/sbin/sendmail.postfix setgid_group = postdrop transport_maps = hash:/var/lib/mailman/var/data/postfix_lmtp unknown_local_recipient_reject_code = 550 El dom., 23 jul. 2017 a las 11:19, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/23/2017 08:16 AM, Rafael Mora wrote: > > This is the content of my /var/log: > > > > > > [root@localhost log]# pwd > > /var/log > > [root@localhost log]# ls > > anaconda grubby messages-20170716 spooler-20170710 > > audit grubby_prune_debug messages-20170723 spooler-20170716 > > boot.log httpd mysqld.log spooler-20170723 > > btmp lastlog php-fpm tallylog > > btmp-20170701 letsencrypt ppp tuned > > chrony maillog rhsm wtmp > > cron maillog-20170702 samba xferlog > > cron-20170702 maillog-20170710 secure xferlog-20170702 > > cron-20170710 maillog-20170716 secure-20170702 xferlog-20170710 > > cron-20170716 maillog-20170723 secure-20170710 xferlog-20170716 > > cron-20170723 mailman secure-20170716 xferlog-20170723 > > dmesg messages secure-20170723 yum.log > > dmesg.old messages-20170702 spooler > > firewalld messages-20170710 spooler-20170702 > > > Your current postfix log is /var/log/maillog. The files like > /var/log/maillog-20170702, etc are older versions rotated by logrotate. > > On 07/23/2017 08:14 AM, Rafael Mora wrote: > > content of the file maillog-20170723 (I didn't find mail.log in > /var/log): > > > > [root@localhost log]# cat maillog-20170723 > > You want to be looking at /var/log/maillog for current messages. > > > ... > > Jul 21 16:10:47 localhost postfix/qmgr[2116]: error: open database > > /var/lib/mailman/var/data/postfix_domains.db: No such file or directory > > > Is this where these files are? You should have at least postfix_domains, > postfix_domains.db, postfix_lmtp and postfix_lmtp.db in the > /var/lib/mailman/var/data/ directory. It this the case? > > > output command 'postconf -n': > > > ... > > transport_maps = hash:/var/libmailman/var/data/postfix_lmtp > > > This is missing a / > > > transport_maps = hash:/var/lib/mailman/var/data/postfix_lmtp > > > -- > 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/ > -- Atentamente / Best Regards Ing. Rafael Mora

7 years, 8 months

[MM3-users] Re: templates

by Odhiambo Washington

If you don't have any templates in the file system and none in the DB table, then you must go to Jerusalem and pray, because you don't have any and nothing will work the way you want. It's either or! On Thu, May 4, 2023, 21:14 Christian via Mailman-users < mailman-users(a)mailman3.org> wrote: > In March when I started troubleshooting my lists, you stated: > > "Also, one other thing you might check. Do these non-working lists have > templates defined in postorius, in particular, one for > list:member:regular:footer, and if not, are there any in Mailman's > var/templates/lists/redlatinleg(a)lists.ccalternatives.org/ derectory that > Mailman doesn't have permission to find and read?" > > There are no other templates listed in either Postorius nor in Mailman's > var/templates (as I stated, I do not even lave a 'lists' subdirectory under > Mailman's var/templates). My subscribers are not receiving message > distributions from my lists, even while some of them are listed in the > archives. > > > > > -----Original Message----- > From: Mark Sapiro <mark(a)msapiro.net> > Sent: Thursday, May 4, 2023 10:58 AM > To: mailman-users(a)mailman3.org > Subject: [MM3-users] Re: templates > > On 5/4/23 10:33, Christian via Mailman-users wrote: > > I'm having issues with my lists. For each list I have created a > > template [ list:user:action:subscribe ]which has a prospective > > subscriber have to consent to list rules before they are subscribed. > > This template I created is listed in Postorius for each list. I have > > noticed that there are no other templates listed in Postorius. > Furthermore, there is no 'lists' > > subdirectory under Mailman's var/templates/. > > > When you set a template in Postorius it saves it in the > postorius_emailtemplate table in the database and tells Mailman core to get > the template from Postorius via a URI to a Postorius API. > > -- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at: > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/ > QIHCMEBWANR67HV3NKBK5MCQNSNZRF2A/ > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> > > This message sent to csa(a)web-analysts.net > > _______________________________________________ > 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 >

1 year, 11 months

[MM3-users] Re: mailman3 postorius cannot retrieve template at ... (<no authorization>)

by Mark Sapiro

On 10/29/21 3:41 AM, Wolfgang Bock via Mailman-users wrote: > > the question is: postgres - mailman3web-postorius_emailtemplate table vs > mailman3 - templates table > > I installed a brand new mailman3 with mailman Core 3.3.3, Api 3.1, Core > Python 3.9.2 postgres12 nginx on debian bullseye. > > I created a template via postorius -> lists -> (testliste01) -> templates > -> new template -> [list:member:regular:footer] and > [list:member:digest:footer] > > They are shown in the postgres database mailman3 table templates: > id name context uri username password > 14 list:member:digest:footer testliste01.mydomain.de > http://localhost/postorius/api/templates/list/testliste01.mydomain.de/list:m > ember:digest:footer > 15 list:member:regular:footer testliste01.mydomain.de > http://localhost/postorius/api/templates/list/testliste01.mydomain.de/list:m > ember:regular:footer > > First there where no templates in the /var/lib/mailman3/templates folder, > which was empty after installation. This is expected. That is one place where you can put custom templates. > Later I created in /var/lib/mailman3/templates theses folders and the files > /list/testliste01.mydomain.de/list:member:digest:footer + > list:member:regular:footer owned by list:list 644 > > A testmail went through but instead of the default footer no footer was > shown. By default Mailman searches for templates first in the var/templates directory and then in the templates directory in the Mailman installation. The details are described at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/i18n…. However, the default search is only applied if there is matching entry for the template name and context in the `templates` table in the database or if the uri in the entry is a `mailman://` uri. When you create a template in Postorius, that uri becomes something like `https://example.com/mailman3/api/templates/list/<list_id>/<template_name>` which basically says get the template from Postorius, and the template if any in var/templates is ignored. > In the sys.log I found the following error message: > Oct 29 11:28:04 myserver mailman3[33015]: Message: `Cannot retrieve template > at > http://localhost/postorius/api/templates/list/testliste01.mydomain.de/list:m > ember:regular:footer (<no authorization>)` So Mailman is trying to get the Postorius template. What is in the web server logs for this retrieval? > How can I solve this problem? What kind of authorisation is meant? list? > restadmin? > > I read in > https://docs.mailman3.org/en/latest/config-core.html#configure-templates > ... list specific templates invar/templates/lists/LIST-ID/LC/ ... > I guess the LC means Language Code. But in the database table templates no > LC subdirectory is mentioned (in my case must be de). If you delete the Postorius template, The entry in the templates table will be removed and the search will revert to var/templates, etc. > And I read (dont know where) .... The templates created in Postorius are > created in the postorius_emailtemplate table in Mailman`s database and > referenced via URLs like > `https://example.com/mailman3/api/templates/list/<list-id>/<template-name>`. > I.e., they are not stored in the file system. ... > > That`s true. I found in postgres database mailman3web in the table > mailman3web postorius_emailtemplate my > > id name data language created_at modified_at > context identifier > 15 list:member:digest:footer postorius footer digest 1x linefeed > 2021-10-29 11:17:40.664689+02 2021-10-29 11:26:48.692628+02 list > testliste01.mydomain.de > 16 list:member:regular:footer postorius footer non-digest 1x > linefeed 2021-10-29 11:18:29.166241+02 2021-10-29 11:27:24.519024+02 list > testliste01.mydomain.de > > But my question is how to integrate this into the mailman3-system. The > language isn`t set either. It is integrated. The language isn`t set because you are getting the template from Postorius and Postorius knows the language. On 10/31/21 4:13 AM, Wolfgang Bock via Mailman-users wrote: > regarding my mail before, here an additional information. > > I can show the templates with following command (anonymized): > https://active_domain.de/postorius/api/templates/list/testliste01.active_do… As it should be. > The complete syslog > (edited and reformatted by me) ``` > --- Logging error --- > Traceback (most recent call last): Oct 30 11:49:52 active_server mailman3[107630]: File "/usr/lib/python3/dist-packages/mailman/model/template.py", line 110, in get > contents = protocols.get(actual_uri, **auth) > File "/usr/lib/python3/dist-packages/mailman/utilities/protocols.py", line 39, in get > response.raise_for_status() > File "/usr/lib/python3/dist-packages/requests/models.py", line 943, in raise_for_status > raise HTTPError(http_error_msg, response=self) > requests.exceptions.HTTPError: 404 Client Error: Not Found for url: http://localhost/postorius/api/templates/list/testliste01.active_domain.de/… > During handling of the above exception, another exception occurred: > Traceback (most recent call last): > File "/usr/lib/python3.9/logging/__init__.py", line 430, in format > return self._format(record) > File "/usr/lib/python3.9/logging/__init__.py", line 426, in _format > return self._fmt % record.__dict__ > KeyError: `t` > During handling of the above exception, another exception occurred: ``` Your template is malformed. You have $ strings that are not defined as Mailman substitution variables. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

[MM3-users] Re: Relaying email from external SMTP server (office365 or Exchange)

by Waqas Ahmed Khan

Hi, I have successfully configured Office365 to relay emails from Mailman3. I used the below configuration. change following lines in mailman.cfg: smtp_host: your-domain.com.mail.protection.outlook.com smtp_port: 25 And then configure SMTP Relay Connector in Office365, so it can recognize your server. SMTP relay doesn't use a specific Office 365 mailbox to send email. Option3 of Link: https://docs.microsoft.com/en-us/exchange/mail-flow-best-practices/how-to-s… Could you Please confirm, what should be hardware configuration (ram, processor, disk) to run mailman3 server for medium size organization? This server will have 10-15 lists and some lists having 10k to 20k members. Also what should be DISK SPACE of the server for Archiving emails? Regards, *Waqas Ahmed Khan* p: +923212608044 Skype: waqas-ahmed00 <waqas.ahmed0(a)gmail.com> waqas.ahmed0(a)gmail.com [image: LinkedIn] <http://pk.linkedin.com/pub/waqas-ahmed-khan/15/96a/39a/> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_cam…> Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_cam…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Tue, Jun 23, 2020 at 8:23 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/22/20 7:58 AM, Waqas Ahmed Khan wrote: > > Hi, > > > > I have installed mailman3 with postfix. The server is working fine. To > > protect the IPs from blacklisting, I want to relay all emails from > > postfix/mailman to external SMTP servers like O365, Gmail, or our > exchange > > server. > > > I would not recommend using O365 or Gmail as outgoing MTAs. I don't > really know about )365, but I don't think Gmail likes you to send mail > via a gmail server if it is not From: (or maybe envelope from or both) a > gmail or googlemail address. > > > > Could you please confirm is this possible. And how to do its > configuration. > > > It is possible and there are two ways to do it. You can configure this > in Postfix to relay all outgoing mail via some other server. > > > You can configure it in Mailman by setting in the [mta] section of > mailman.cfg > > smtp_host: > smtp_port: > > and presumably for authentication > > smtp_user: > smtp_pass: > > Also see > > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.… > and following for other relevant settings. > > -- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

4 years, 10 months

[MM3-users] Re: Hyperkitty Recommended mySQL Database Setup & Archive Importing

by matthew＠alberti.us

I should clarify a bit. That connection string I mentioned in the previous post is in the docker-compose.yaml file for the docker-mailman containers. For web, it seems the settings.py file for the mailman-web container is configured to parse connection string, but there isn't (I don't think) any provision to set additional options, such as the encoding. So there doesn't appear to be a straightforward way, using the container yaml approach, to pass the 'OPTIONS' for the encoding. It does however look like it is possible to override the whole database connection settings using settings_local.py, but unsure. That would I think be the way to do it, setting the whole database configuration settings per https://gitlab.com/mailman/mailman-suite/-/blob/master/mailman-suite_project /settings.py#L156 in the settings_local.py file. For core, the connection string seems to accept a tailing "?charset=utf8&use_unicode=1" per https://mailman.readthedocs.io/en/stable/src/mailman/docs/database.html So for core, maybe just updating the connection string to include "?charset=utfmb4&use_unicode=1" will just work? The link lists utf8 as the recommend encoding... maybe that should be updated? I realize this may be drifting more towards concerning the docker container setup vs. non-containerized core and web. But either way, these seem to be mysql specific caveats that I've certainly missed. Hopefully this helps someone else. Seems the takeaway is that, for mysql databases only, the use of utf8mb4 is recommended, and it needs to be explicitly identified in the database settings for BOTH core and web, and probably somehow at database creation time? Now to see what the best procedure is to put these configuration changes in place, and also update the database? - Matt Alberti -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, December 9, 2020 9:35 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Hyperkitty Recommended mySQL Database Setup & Archive Importing On 12/9/20 6:06 PM, matthew(a)alberti.us wrote: > Thanks Mark. Also, just to confirm, should the database connection > string also be updated? In both the core and web configuration, I have > something > like: > > DATABASE_URL=mysql+pymysql://mailman:password@database/mailmandb > > Note the trailing UTF-8 encoding stuff isn't there. Should we be > specifying > utf8mb4 there as well? In the mailman.cfg database section, you probably want url: mysql+pymysql://myuser:mypassword@mymysqlhost/mailman?charset=utf8mb4&us mysql+e_unicode=1 I don't know why you would have a DATABASE_URL setting in the web configuration. Exactly where is this? I don't think it would be meaningful in any Django settings. -- 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 4 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I got this on maillog: [root@localhost log]# cat maillog Jul 24 11:33:13 localhost postfix/postfix-script[2044]: warning: not set-gid or not owner+group+world executable: /usr/sbin/postqueue Jul 24 11:33:13 localhost postfix/postfix-script[2066]: warning: not set-gid or not owner+group+world executable: /usr/sbin/postdrop Jul 24 11:33:13 localhost postfix/postfix-script[2081]: starting the Postfix mai l system Jul 24 11:33:13 localhost postfix/master[2083]: daemon started -- version 2.10.1 , configuration /etc/postfix Jul 24 11:35:29 localhost postfix/postfix-script[2115]: warning: not set-gid or not owner+group+world executable: /usr/sbin/postqueue Jul 24 11:35:29 localhost postfix/postfix-script[2116]: warning: not set-gid or not owner+group+world executable: /usr/sbin/postdrop Jul 24 11:35:29 localhost postfix/postfix-script[2123]: starting the Postfix mai l system Jul 24 11:35:29 localhost postfix/master[2125]: daemon started -- version 2.10.1 , configuration /etc/postfix Jul 24 13:55:31 localhost postfix/postfix-script[2095]: warning: not set-gid or not owner+group+world executable: /usr/sbin/postqueue Jul 24 13:55:31 localhost postfix/postfix-script[2096]: warning: not set-gid or not owner+group+world executable: /usr/sbin/postdrop Jul 24 13:55:31 localhost postfix/postfix-script[2105]: starting the Postfix mai l system Jul 24 13:55:32 localhost postfix/master[2110]: daemon started -- version 2.10.1 , configuration /etc/postfix Jul 24 15:57:26 localhost postfix/postfix-script[2079]: warning: not set-gid or not owner+group+world executable: /usr/sbin/postqueue Jul 24 15:57:26 localhost postfix/postfix-script[2086]: warning: not set-gid or not owner+group+world executable: /usr/sbin/postdrop Jul 24 15:57:26 localhost postfix/postfix-script[2093]: starting the Postfix mai l system Jul 24 15:57:26 localhost postfix/master[2095]: daemon started -- version 2.10.1 , configuration /etc/postfix Jul 24 16:33:01 localhost postfix/postfix-script[1993]: warning: not set-gid or not owner+group+world executable: /usr/sbin/postqueue Jul 24 16:33:01 localhost postfix/postfix-script[1996]: warning: not set-gid or not owner+group+world executable: /usr/sbin/postdrop Jul 24 16:33:01 localhost postfix/postfix-script[2003]: starting the Postfix mai l system Jul 24 16:33:01 localhost postfix/master[2005]: daemon started -- version 2.10.1 , configuration /etc/postfix Jul 24 17:29:21 localhost postfix/postfix-script[2077]: warning: not set-gid or not owner+group+world executable: /usr/sbin/postqueue Jul 24 17:29:21 localhost postfix/postfix-script[2079]: warning: not set-gid or not owner+group+world executable: /usr/sbin/postdrop Jul 24 17:29:21 localhost postfix/postfix-script[2092]: starting the Postfix mai l system Jul 24 17:29:21 localhost postfix/master[2096]: daemon started -- version 2.10.1 , configuration /etc/postfix El lun., 24 jul. 2017 a las 17:23, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/24/2017 02:52 PM, Rafael Mora wrote: > > I did that but I don't have a maillog for today 07.24.2017 > > > The current log is just named 'maillog' the ones with dates are older > logs rotated by logrotate. > > -- > 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/ > -- Atentamente / Best Regards Ing. Rafael Mora

7 years, 8 months

[MM3-users] Re: Mailman notify generating emails for request that aren't visible.

by Simon Coggins

The version of postorius is 1.3.4 django-mailman3 1.3.5 mailman 3.3.4 mailman-hyperkitty 1.1.0 mailmanclient 3.3.2 postorius 1.3.4 --- [https://www.cqu.edu.au/] Mr Simon Coggins Principal Systems Engineer | Digital Services Directorate CQUniversity Australia, Level 6.14, 160 Ann Street, Brisbane, QLD 4000 P +61 7 3295 1182 | X 51182 | M +61 408 115 861 | E s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au> [https://www.cqu.edu.au/social-media] I respectfully acknowledge the Traditional Owners of the land on which we work and learn, and pay respect to the First Nations Peoples and their Elders, past, present and future. This communication may contain privileged or confidential information. If you have received this in error, please return to sender and delete. CRICOS: 00219C | RTO Code 40939 On 1 Nov 2021, at 12:04 pm, Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> wrote: On 10/31/21 6:11 PM, Simon Coggins wrote: > Hi, > > We’re running mailman 3.3.4 (about to upgrade to 3.3.5 this week). I enabled mailman notify cron a few weeks ago to email out any pending requests for admins. I’ve now got multiple lists that keep emailing out the same outstanding holds but they can’t visible in the GUI. The requests are all duplicates as well. This is a redacted example email: > > -----Original Message----- > From: mailman-alerts(a)example.com<mailto:mailman-alerts@example.com><mailto:mailman-alerts@example.com> > Sent: Monday, 1 November 2021 8:10 AM > To: somelist-owner(a)lists.example.com<mailto:somelist-owner@lists.example.com><mailto:somelist-owner@lists.example.com> > Subject: The somelist(a)lists.example.com<mailto:somelist@lists.example.com><mailto:somelist@lists.example.com> list has 4 moderation requests waiting. > > The somelist(a)lists.example.com<mailto:somelist@lists.example.com><mailto:somelist@lists.example.com> list has 4 moderation requests waiting. > > Held Unsubscriptions: > User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com><mailto:john.smith@maildomain.com> > User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com><mailto:john.smith@maildomain.com> > User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com><mailto:john.smith@maildomain.com> > User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com><mailto:john.smith@maildomain.com> > > Please attend to this at your earliest convenience. Your lists are configured with Un-Subscription Policy moderate or confirm, then moderate so unsubs require Moderator approval. What Postorius version is this? Prior to 1.3.3, unsubsubscription requests were not visible in Postorius. In 1.3.3_+ they are available in the Subscription requests dropdown at https://example.com/mailman3/lists/listname.example.com/unsubscription_requ…<https://example.com/mailman3/lists/listname.example.com/unsubscription_requ…> although they may not be counted in the Subscription requests count badge. -- 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>

3 years, 5 months

[MM3-users] Re: Delete Django profiles not signed up to a list

by Allan Hansen

Mark, Will this be part of an upcoming update or micro update to Mailman? Yours, Allan Hansen P.O. Box 2423 Cypress, CA 90630 > On Mar 31, 2023, at 15:49, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 3/31/23 14:17, Andrew Hodgson wrote: >> Hi. >> Has anyone managed to get this script running using the Mailman-Web setup in a venv? It was working when Settings.py was in the /opt/mailman/mm directory but since moving to Mailman-Web has it in /etc/mailman3. I have been trying to import Mailman-Web to get the Django environment running but every time I do this I get a not configured exception raised. > > > First, get the latest version of the script from https://www.msapiro.net/scripts/clean_users.py - not the one in this threat attached to https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > Then, you need to change `/opt/mailman/mm` in three places to `/etc/mailman3` as in > ``` > --- /opt/mailman/mm/bin/clean_users.py 2021-05-08 20:03:31.657565251 -0700 > +++ clean_users.py 2023-03-31 15:48:31.772383287 -0700 > @@ -2,13 +2,13 @@ > import os > import sys > > -sys.path.insert(0, '/opt/mailman/mm') > +sys.path.insert(0, '/etc/mailman3') > # The above line is required. The next line doesn't hurt, but it doesn't work > # because the PYTHONPATH environment setting is processed by Python's setup > # and must be in the environment when Python starts to be effective. > -os.environ['PYTHONPATH'] = '/opt/mailman/mm' > +os.environ['PYTHONPATH'] = '/etc/mailman3' > os.environ['DJANGO_SETTINGS_MODULE'] = 'settings' > -os.environ['MAILMAN_CONFIG_FILE'] = '/opt/mailman/mm/mailman.cfg' > +os.environ['MAILMAN_CONFIG_FILE'] = '/etc/mailman3/mailman.cfg' > > import django > django.setup() > ``` > Also, look at this > ``` > # If we delete the Django user and there is a Mailman user with no memberships > # shall we delete the Mailman user too. > DELETE_MAILMAN_USER = False > # Shall we delete the Django user if there is a Mailman user with no > # memberships or only if there is no Mailman user. > DELETE_DJANGO_IF_MAILMAN = True > ``` > and consider whether you want to set `DELETE_MAILMAN_USER = True` to also delete the Mailman user if any, and/or set `DELETE_DJANGO_IF_MAILMAN = False` to not delete the django user if there is a Mailman user with no memberships. > > -- > 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://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 hansen(a)rc.org

2 years

[MM3-users] Re: Still unable to get mailman3 working on Ubuntu 20.04 LTS

by Mark Sapiro

On 1/9/22 3:26 AM, Michael Heseltine wrote: >> This isn't your immediate problem, but it is an issue. The above isn't >> too informative. What do you get if you run >> >> /opt/mailman/mm/bin/django-admin qcluster >> >> manually? > > I get the following: > >> # /opt/mailman/mm/bin/django-admin qcluster >> 11:50:41 [Q] INFO Q Cluster autumn-sixteen-tango-march starting. >> 11:50:41 [Q] INFO Process-1:1 ready for work at 3725610 >> 11:50:41 [Q] INFO Process-1:2 ready for work at 3725611 >> 11:50:42 [Q] INFO Process-1:3 ready for work at 3725612 >> 11:50:42 [Q] INFO Process-1:4 ready for work at 3725613 >> 11:50:42 [Q] INFO Process-1:5 monitoring at 3725614 >> 11:50:42 [Q] INFO Process-1 guarding cluster autumn-sixteen-tango-march >> 11:50:42 [Q] INFO Process-1:6 pushing tasks at 3725615 >> 11:50:42 [Q] INFO Q Cluster autumn-sixteen-tango-march running. > > And then nothing until I end the command with Ctrl-C. This is what I would expect. It seems to be working. I'm not sure why it fails when run from systemd. Are you running memcached? systemctl status memcached.service That needs to be installed and running for qcluster. > Sorry, I didn't realize that they were truncated. Here are ( I hope) the full logs from /var/log/syslog: > >> Jan 8 21:24:57 lists systemd[1]: Started GNU Mailman web interfaces. >> Jan 8 21:24:57 lists gunicorn[3707354]: !!! >> Jan 8 21:24:57 lists gunicorn[3707354]: !!! WARNING: configuration file should have a valid Python extension. >> Jan 8 21:24:57 lists gunicorn[3707354]: !!! >> Jan 8 21:24:57 lists gunicorn[3707354]: Traceback (most recent call last): >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/arbiter.py", line 209, in run >> Jan 8 21:24:57 lists gunicorn[3707354]: self.sleep() >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/arbiter.py", line 357, in sleep >> Jan 8 21:24:57 lists gunicorn[3707354]: ready = select.select([self.PIPE[0]], [], [], 1.0) >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/arbiter.py", line 242, in handle_chld >> Jan 8 21:24:57 lists gunicorn[3707354]: self.reap_workers() >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/arbiter.py", line 525, in reap_workers >> Jan 8 21:24:57 lists gunicorn[3707354]: raise HaltServer(reason, self.WORKER_BOOT_ERROR) >> Jan 8 21:24:57 lists gunicorn[3707354]: gunicorn.errors.HaltServer: <HaltServer 'Worker failed to boot.' 3> >> Jan 8 21:24:57 lists gunicorn[3707354]: During handling of the above exception, another exception occurred: >> Jan 8 21:24:57 lists gunicorn[3707354]: Traceback (most recent call last): >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/bin/gunicorn", line 14, in <module> >> Jan 8 21:24:57 lists gunicorn[3707354]: sys.exit(gunicorn.app.wsgiapp.run()) >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/app/wsgiapp.py", line 67, in run >> Jan 8 21:24:57 lists gunicorn[3707354]: WSGIApplication("%(prog)s [OPTIONS] [APP_MODULE]").run() >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/app/base.py", line 231, in run >> Jan 8 21:24:57 lists gunicorn[3707354]: super().run() >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/app/base.py", line 72, in run >> Jan 8 21:24:57 lists gunicorn[3707354]: Arbiter(self).run() >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/arbiter.py", line 229, in run >> Jan 8 21:24:57 lists gunicorn[3707354]: self.halt(reason=inst.reason, exit_status=inst.exit_status) >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/arbiter.py", line 342, in halt >> Jan 8 21:24:57 lists gunicorn[3707354]: self.stop() >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/arbiter.py", line 393, in stop >> Jan 8 21:24:57 lists gunicorn[3707354]: time.sleep(0.1) >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/arbiter.py", line 242, in handle_chld >> Jan 8 21:24:57 lists gunicorn[3707354]: self.reap_workers() >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/arbiter.py", line 525, in reap_workers >> Jan 8 21:24:57 lists gunicorn[3707354]: raise HaltServer(reason, self.WORKER_BOOT_ERROR) >> Jan 8 21:24:57 lists gunicorn[3707354]: gunicorn.errors.HaltServer: <HaltServer 'Worker failed to boot.' 3> >> Jan 8 21:24:58 lists systemd[1]: gunicorn.service: Main process exited, code=exited, status=1/FAILURE >> Jan 8 21:24:58 lists systemd[1]: gunicorn.service: Failed with result 'exit-code'. I'm not sure about this one either. You might want to look at https://stackoverflow.com/questions/24488891/gunicorn-errors-haltserver-hal… or other hits from https://www.google.com/search?q=gunicorn+worker+failed+to+boot Are your files /etc/systemd/system/gunicorn.service /opt/mailman/mm/bin/gunicorn opt/mailman/mm/gunicorn.conf the same as recommended at https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At… https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At… https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: Hyperkitty no longer archiving

by Hirayama, Pat

Hi Mark! > -----Original Message----- > From: Mark Sapiro <mark(a)msapiro.net> > Sent: Tuesday, November 22, 2022 12:19 PM > To: mailman-users(a)mailman3.org > Subject: [MM3-users] Re: Hyperkitty no longer archiving > > First, my apologies for not taking note of your MAILMAN_ARCHIVER_FROM > setting in your OP. No worries. I tried to include everything that might be needed for you and the other frequent posters to be able to give me an answer, and all of you respond to a LOT of posts. > On 11/22/22 08:52, Hirayama, Pat wrote: > > Steve wrote: > >> 2. Does settings.py have "from settings_local import *" in it? > > > > Yes. I assume that overrides the MAILMAN_ARCHIVER_FROM and other > related settings defined at the top of the settings.py file? Or should I update > settings.py based on what is in settings_local.py? > > > Assuming the `from settings_local import *` is at the end of > settings.py, anything defined in settings_local.py will override the > definition in settings.py. There's no need to change settings.py. This is the end of settings.py: # # HyperKitty-specific # # Only display mailing-lists from the same virtual host as the webserver FILTER_VHOST = False POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000' try: from settings_local import * except ImportError: pass I'm assuming that is close enough to the end? <snip> > > The > ``` > ERROR 2022-11-22 00:25:40,365 7 hyperkitty.views.mailman Access to the > archiving API endpoint was forbidden from IP 172.31.0.1, your > MAILMAN_ARCHIVER_FROM setting may be misconfigured > ``` > message comes from > https://urldefense.com/v3/__https://gitlab.com/mailman/hyperkitty/- > /blob/master/hyperkitty/views/mailman.py*L62__;Iw!!GuAItXPztq0!hLVF14 > B0x45qVgO6PBHbLDw0TH9RiV8rrAVWDBuswab7QFb56LlCxdyihoc- > 2F4ZHdqDTdXzj4YgcLM$ > which only occurs if '172.31.0.1' is not in MAILMAN_ARCHIVER_FROM. Given > that it is in MAILMAN_ARCHIVER_FROM as defined in settings_local.py, the > only thing I can conclude is that the Django settings actually used is > not the settings.py you think it is. > > I don't know offhand even what wsgi service is used in the docker > container or how it is configured, but it needs to set its working > directory to the directory containing settings.py. > So, looking at the Django container, I see this process popping up periodically. I think that means that it is running from the directory specified by "--pythonpath"" (which is where settings.py and settings_local.py are located). I am further assuming that "--settings settings" is ok without a .py extension. 53972 mail 0:00 {django-admin} /usr/local/bin/python /usr/local/bin/django-admin runjobs quarter_hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project/. --settings settings 53978 mail 0:00 {django-admin} /usr/local/bin/python /usr/local/bin/django-admin runjobs minutely --pythonpath /opt/mailman/mailman-suite/mailman-suite_project/. --settings settings > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan >

2 years, 5 months

[MM3-users] Re: Updating from Ubuntu-20.04 LTE installation

by Abhilash Raj

On Sat, May 23, 2020, at 8:28 PM, Mark Sapiro wrote: > On 5/23/20 7:02 PM, Peter Adebahr via Mailman-users wrote: > > > > Our installation was done by "apt-get install" in Ubuntu 20, thus still > > running MM 3.2.2 (and python 3.8.2). > > > > Do you have any advise, how to upgrade from there to your current > > version? I know this might be a bit dangerous, but with today's VMs the > > risk is much less than it used to be: > > > It shouldn't be difficult, but I can't give you details because I don't > know exactly how the Debian/Ubuntu package installs things. Also I don't > know whether "current version" refers to the 3.3.1 release or the head > of the https://gitlab.com/mailman/mailman master branch. > > > > Do you think it would be possible, just to replace the code and library > > parts, keeping the database and config files as is? > > > Yes. It should be fairly straightforward. You first need to find where > the Mailman Core package is. You should be able to just replace the > contents of the `mailman` package directory with ours. You may be able > to do this via pip > > pip install --upgrade mailman > > globally or within Mailman's virtualenv if it is installed in a virtualenv. This is probably not a good idea, global install quite often breaks a lot of stuff (Like I broke Yum on my work computer since I wanted something newer than 10yo python packages). A better idea would be to install Mailman from scratch inside a virtualenv somewhere in /opt/mailman and then letting it consume the same configurations. I think Ubuntu/Debian have their configurations in `/etc/mailman3/` and Mailman Core installed anywhere should just pick that up without any special work. Same goes for Postorius/Django stuff. You can switch to a different Django project and just point to Debian/Ubuntu's settings.py (location of which should be in README.debian of the Debian package I presume). > However, there are caveats. There are Debian patches at > <https://sources.debian.org/patches/mailman3/3.2.2-1/>. The big `0002` > patch replaces importlib_resources with importlib.resources because > importlib_resources is not available in Debian. Most of the patches > apply to tests, and for the actual working code, we fixed this > differently as of Mailman 3.3.1, so I don't think you need the Debian > patches. > > > -- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

4 years, 10 months

[MM3-users] Re: django-allauth failures, but only for some users (independent of browser?)

by Jered Floyd

I'll dig at that; thanks. I've just managed to get one of my Google accounts into this "broken" state, although I'm not entirely sure how I did it (or where the broken state is stored). This happened after I tried using the "Sign In" button on a list info page rather than the one in the upper right corner, but that may just be a red herring. I'll report back if I find anything. --Jered ----- On Dec 6, 2023, at 3:21 PM, Mark Sapiro mark(a)msapiro.net wrote: > On 12/6/23 11:00, Jered Floyd wrote: >> > These errors are generated to me as the admin, and in the elided > environment section SITE_ID is indeed 0, but I'm at a loss to imagine > why this happens only sometimes! > > For me, on a test installation with SITE_ID = 0, this only occurs at > https://example.com/accounts/social/connections/ > > Other URLs such as https://example.com/accounts/password/change/ and > https://example.com/accounts/email/ do not throw this exception. > > Here's the code: > ``` > def get_current(self, request=None): > """ > Return the current Site based on the SITE_ID in the project's > settings. > If SITE_ID isn't defined, return the site with domain matching > request.get_host(). The ``Site`` object is cached the first > time it's > retrieved from the database. > """ > from django.conf import settings > > if getattr(settings, "SITE_ID", ""): > site_id = settings.SITE_ID > return self._get_site_by_id(site_id) > elif request: > return self._get_site_by_request(request) > > raise ImproperlyConfigured( > 'You\'re using the Django "sites framework" without having ' > "set the SITE_ID setting. Create a site in your database and " > "set the SITE_ID setting or pass a request to " > "Site.objects.get_current() to fix this error." > ) > ``` > > I tried patching it from > ``` > if getattr(settings, "SITE_ID", ""): > ``` > to > ``` > if getattr(settings, "SITE_ID", None) is not None: > ``` > but that's even worse. It throws a bunch of > "django.contrib.sites.models.Site.DoesNotExist: Site matching query does > not exist." errors. > > Somehow, get_current is being called without a request object in the > cases where it fails. > > -- > 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://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 jered(a)convivian.com

1 year, 4 months

[MM3-users] Re: A little stuck with installation of MM3 - ModuleNotFoundError: No module named 'flufl.lock'

by Mark Sapiro

On 7/25/20 12:54 PM, Odhiambo Washington wrote: > > Finally, I have adapted your init script to get some rudimentary one that I > could use on FreeBSD. > I have to change /opt/mailman to be owned by mailman3:mailman3 (because I > have "live" MLs on this server, using mailman-2.1.34. > I am not sure if they can co-exist. I suppose they could, but what might be > the security implication, if any?? I manage more than one server that supports both Mailman 2.1 and Mailman 3 running as user `mailman`. I'm not aware of any security issues. > This is what the init script looks like (rudimentary!!): > (venv) [root@gw /usr/local/etc/rc.d]# less mailman3 > ### BEGIN INIT INFO > # Provides: GNU Mailman > # Short-Description: Mailman3 Service > # Description: service control for Mailman3 > ### END INIT INFO > > PATH=/opt/mailman/mm/bin:/opt/mailman/mm/venv/bin:/usr/sbin:/usr/bin:/bin:/sbin: > DESC="GNU Mailman service" > DAEMON=/opt/mailman/mm/bin/mailman > NAME=mailman > USER=mailman3 > GROUP=mailman3 > > # Needed by click > export LANG=en_US.UTF-8 > > # Exit if the package is not installed > [ -x "$DAEMON" ] || exit 0 > > # Load the VERBOSE setting and other rcS variables > #. /lib/init/vars.sh > > # Define LSB log_* functions. > # Depend on lsb-base (>= 3.2-14) to ensure that this file is present > # and status_of_proc is working. > #. /lib/lsb/init-functions > > case "$1" in > start) > [ "$VERBOSE" != no ] && echo "Starting $DESC" "$NAME" > # use --force to remove a stale lock. > /usr/local/bin/sudo -u $USER $DAEMON start --force T don't recommend using --force in init scripts. It *shouldn't* matter because even with --force the master shouldn't break the lock if the pip that set it still exists, but I prefer not to use it. > ;; > stop) > [ "$VERBOSE" != no ] && echo "Stopping $DESC" "$NAME" > /usr/local/bin/sudo -u $USER $DAEMON stop > ;; > status) > /usr/local/bin/sudo -u $USER $DAEMON status > ;; > reopen) > /usr/local/bin/sudo -u $USER $DAEMON reopen > ;; > restart) > log_daemon_msg "Restarting $DESC" "$NAME" > /usr/local/bin/sudo -u $USER $DAEMON restart > ;; > *) > echo "Usage: $SCRIPTNAME {start|stop|status|reopen|restart}" >&2 > exit 3 > ;; > esac > > It does start mailman3 for sure, but also complains after a few seconds > with the message: > > (venv) [root@gw /usr/local/etc/rc.d]# > */opt/mailman/mm/venv/lib/python3.7/site-packages/mailman-3.3.2b1-py3.7.egg/mailman/rest/wsgiapp.py:180: > DeprecatedWarning: Call to deprecated function __init__(...). API class may > be removed in a future release, use falcon.App instead.* > * **kws)* Hmm... strange, My various MM 3 installs are running falcon 1.4.0, 2.0.0 and 3.0.0a1 and I don't see this warning, but it is only a deprecation warning. It doesn't mean it won't work. > But: > > (venv) [root@gw /usr/local/etc/rc.d]# ps ax | grep mailman ... It seems Mailman core and the rest runner and its workers are all running. > > Assuming that I am using mod_wsgi with Apache, and that I have configured > apache right using > https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At… > .. > should I be able to access the MM3 web UI?? Yes, I think so. > At that point, I am feeling somewhat confused as to what to try next. > > (venv) [root@gw /opt/mailman/mm/var/logs]# less mailman.log > Jul 25 22:53:16 2020 (40670) Master started > Jul 25 22:53:18 2020 (42036) bounces runner started. > Jul 25 22:53:18 2020 (45205) out runner started. > Jul 25 22:53:19 2020 (41191) archive runner started. > Jul 25 22:53:19 2020 (46670) retry runner started. > Jul 25 22:53:19 2020 (44567) nntp runner started. > Jul 25 22:53:19 2020 (43069) in runner started. > Jul 25 22:53:19 2020 (46960) virgin runner started. > Jul 25 22:53:20 2020 (45720) pipeline runner started. > Jul 25 22:53:20 2020 (47326) digest runner started. > Jul 25 22:53:20 2020 (43755) lmtp runner started. > Jul 25 22:53:20 2020 (45922) rest runner started. > [2020-07-25 22:53:20 +0300] [45922] [INFO] Starting gunicorn 20.0.4 > [2020-07-25 22:53:20 +0300] [45922] [INFO] Listening at: > http://127.0.0.1:8001 (45922) > [2020-07-25 22:53:20 +0300] [45922] [INFO] Using worker: sync > [2020-07-25 22:53:20 +0300] [54732] [INFO] Booting worker with pid: 54732 > [2020-07-25 22:53:20 +0300] [55467] [INFO] Booting worker with pid: 55467 > Jul 25 22:53:21 2020 (42743) command runner started. The above is all fine, but it is just Mailman core. > How do I access the web UI for MM3 now? The Apache config points to /opt/mailman/mm/wsgi.py, a sampole of which is at <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…>. Do you have that? If you installed the Apache config literally, the location for Mailman 3 is defined by <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…> and the URL would be http(s)://your.server/mm3 - have you tried that? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: Held messages: Long time waiating for response of the Mailman API

by Stephan Krinetzki

Mark Sapiro wrote: > On 1/24/22 15:06, Mark Sapiro wrote: > > On 1/18/22 06:24, Stephan Krinetzki wrote: > > Hello, > > We are using Mailman 3.3.5 with Hyperkitty 1.3.5. Mailman 3 is > > installed in a venv and deployed using Apache and uwsgi. This works > > quite well so far, only withheld messages cause us a problem: If we > > try to approve them via Postorius, the message is delivered to the > > list immediately, but the success message in Postorius takes a long > > time - on average the process hangs for three minutes until the > > message is no longer displayed. We have already adjusted the timeout > > in gunicorn.cfg, but this does not improve the situation. Are there > > any tips on how we can speed up the REST API? Or is it even a > > configuration error? > > There are two steps in handling the POST for a held message. The first > > step is accepting, rejecting or discarding the message. This is > > happening immediately. > > The second step is handling the poster's moderation action based on the > > choice from the Set member moderation dropdown in the view of the held > > message. This is processed by the code at > > https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/views/list…. > > If no selection has been made, the default value POSTed for > > moderation_choice is no-action and that code is skipped. If it is one > > of the choices Hold for moderation, Reject (with notification), > > Discard (no notification), Accept immediately (bypass other rules) > > or Default processing that is processed. So presumably a selection has > > been made and processing is stuck on getting the member or setting the > > member's moderation action. > > Possibly the logs of your database manager will have information. > > Some additional info. > By gunicorn.cfg, do you mean the file at mailman/config/gunicorn.cfg? If > you are using gunicorn as a wsgi server, that is separate from the > gunicorn serving the REST API and its config doesn't affect the REST > API. The relevant config is mailman/config/gunicorn.cfg?. > Also, I doubt the issue is with the REST API per se, but rather it is in > Mailman core's processing of the particular endpoint and if that is > slow, it is most likely some kind of database issue. Hi Mark, yes, we are using a local copy of the gunicorn.cfg. It is in the home directory of our mailman3 instance (like the mailman.cfg, same directory). We will now look into the postgresql database - maybe there is an index missing or something like that. Thank you for help.

3 years, 2 months

[MM3-users] Re: Newbie hyperkitty question

by Stephen Daniel

Thanks. Very helpful. On Tue, Jan 11, 2022 at 2:03 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/11/22 8:27 AM, Stephen Daniel wrote: > > Mailman users -- > > > > I am setting up a new mailman3 installation, and this is my first > > experience with the suite. All of the software is up and running, but I > > cannot tell if hyperkitty is actually running. > > > In Postorius, in the list's `info` view can you click the Archives > button and see archived messages? That's HyperKitty. > > If the messages aren't there with the hyperkitty archiving option > enabled, check `mailman.log` for why. > > Also do messages from the list have an Archived-At: header? > > > > When I look at my test mailing list, two archive options are available, > > hyperkitty and "prototype", and both are enabled. I can see that my > email > > is being archived, but I think "prototype" is what is doing the > archiving. > > I see that a test message will end up in > > > /opt/mailman/mm/var/archives/prototype/<LISTNAME>@<LISTDOMAIN.org>/new/164.... > > and nowhere else. This suggests that "prototype" is archiving, but > > hyperkitty is not. > > > No this says the prototype archiver is working. It says nothing about > Hyperkitty. > > > > So, this opens up a raft of questions on hyperkitty: > > > David Newman has answered some of this, but ... > > > > - How do I tell if hyperkitty is actually running? > > > It doesn't actually run. it is a Django web UI and a web API that serves > things on request. > > > > - Does hyperkitty have a web-UI for admins or users? How would I > access > > it? > > See above. > > > > - I can not find any documentation on hyperkitty, other than > > installation instructions and change logs. Does documentation exist? > > No, not really. > > > > - How do I set policies on how long archives are kept? > > - Assuming I want to back up my archives, what do I need to back up? > > > Messages are kept forever unless you do something to delete them. > HyperKitty's messages are stored in the database configured in the > DATABASES setting in your Django settings. How you backup the database > depends on the database manager. You already found the prototype > archiver's messages. > > > -- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

3 years, 3 months

[MM3-users] Re: debian's 3.2.1 mailman package too unreliable in production - Mail held occasionally causes server errors, and unexplained queue/bad messages -

by Mark Sapiro

On 10/20/20 6:30 PM, Alex Schuilenburg via Mailman-users wrote: > We have an issue where a mailing list has had a message sent to it from > a non-member, so the message has been held, but when the list owner or > I attempt to list the held messages for the list we get a Server Error: > "An error occurred while processing your request.". Details of the server error should be in Django's log which I think in the Debian package is named mailmansuite.log. > I see the mail being held in the mailman log with the non-subscriber > reason, and followed the suggestions in > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > which worked to look at and discard that held message. The problem > is, there are more and we have over 900 mailing lists > > FYI, we are running:Mailman Core VersionGNU Mailman 3.2.1 (La Villa > Strangiato)Mailman Core API Version3.0Mailman Core Python Version3.7.3 > (default, Jul 25 2020, 13:03:44) [GCC 8.3.0] > > So we are looking at setting up a virtualenv to run the latest mailman3 > 3.3.1 as the 3.2.1 package from debian is looking unstable - barely > usable. Actually, the latest Mailman core is 3.3.2rc2 with the final due by the end of October. While I would never discourage people from installing Mailman from our source distributions, without more understanding of your actual errors, it is difficult to know if that will help. > For example, while poking around I found 641 messages in > queue/bad , but when I inspect them they look fine. If, as mentioned > elsewhere, I rename them to .pck, put them in queue/shunt, and "mailman > unshunt" the mail finally gets delivered. Why work now? Some kind of > transient bug? If they are in queue/bad because of permissions errors, it is not surprising that moving them to .pck files in queue/shunt is successful. > Is 3.3.1 the way to go? > > On that last error, I've now enabled debug and hope to catch why > messages are being dropped into queue/bad instead of being delivered. > Already I have found errors in the mailman log such as: > > PermissionError: [Errno 13] Permission denied: > '/var/lib/mailman3/queue/out/1603233694.919073+d907eb9512ce11fda515c19d > 723537fc4cb15da2.pck'Oct 20 23:41:35 2020 (9793) Skipping and > preserving unparseable message: > 1603233694.919073+d907eb9512ce11fda515c19d723537fc4cb15da2Oct 20 > 23:41:35 2020 (9787) Uncaught runner exception: [Errno 13] Permission > denied: > '/var/lib/mailman3/queue/archive/1603233694.9209244+a0c1f3aab51d3d202aa > 37911ab453f094b50b450.pck'Oct 20 23:41:35 2020 (9793) Uncaught runner > exception: [Errno 13] Permission denied: > '/var/lib/mailman3/queue/out/1603233694.9260252+138142eeb15b16b5da16934 > 954d1d3aeb1331198.pck'Oct 20 23:41:35 2020 (9793) Traceback (most > recent call last): File "/usr/lib/python3/dist- > packages/mailman/core/runner.py", line 158, in _one_iteration msg, > msgdata = self.switchboard.dequeue(filebase) File > "/usr/lib/python3/dist-packages/mailman/core/switchboard.py", line 150, > in dequeue with open(filename, 'rb') as fp:PermissionError: [Errno > 13] Permission denied: > '/var/lib/mailman3/queue/out/1603233694.9260252+138142eeb15b16b5da16934 > 954d1d3aeb1331198.pck'Oct 20 23:41:35 2020 (9790) Uncaught runner > exception: [Errno 13] Permission denied: > '/var/lib/mailman3/queue/in/1603233694.9129462+8be9ab12e5dfeab086a1ab8b > 3917550aea313505.pck'Oct 20 23:41:35 2020 (9793) Skipping and > preserving unparseable message: > 1603233694.9260252+138142eeb15b16b5da16934954d1d3aeb1331198Oct 20 > 23:41:35 2020 (9793) Uncaught runner exception: [Errno 13] Permission > denied: > '/var/lib/mailman3/queue/out/1603233694.9269004+5f8572edfb07e0e28b9f0b7 > 928a1184b8c8048ba.pck'Oct 20 23:41:35 2020 (9793) Traceback (most > recent call last): File "/usr/lib/python3/dist- > packages/mailman/core/runner.py", line 158, in _one_iteration msg, > msgdata = self.switchboard.dequeue(filebase) File > "/usr/lib/python3/dist-packages/mailman/core/switchboard.py", line 150, > in dequeue with open(filename, 'rb') as fp:PermissionError: [Errno > 13] Permission denied: > '/var/lib/mailman3/queue/out/1603233694.9269004+5f8572edfb07e0e28b9f0b7 > 928a1184b8c8048ba.pck'Oct 20 23:41:35 2020 (9793) Skipping and > preserving unparseable message: > 1603233694.9269004+5f8572edfb07e0e28b9f0b7928a1184b8c8048ba Were the runners all running as user `list` when the above errors occur. > The mailman3 user, "list", owns and has full rights all the way down: > # ls -ld /var/lib/mailman3/queue/*drwxrwx--- 2 list list 4096 Oct 21 > 01:45 /var/lib/mailman3/queue/archivedrwxrwx--- 2 list list 77824 Oct > 21 00:15 /var/lib/mailman3/queue/baddrwxrwx--- 2 list list 4096 Oct 19 > 10:44 /var/lib/mailman3/queue/bouncesdrwxrwx--- 2 list list 4096 > Oct 5 17:18 /var/lib/mailman3/queue/commanddrwxrwx--- 2 list > list 4096 Oct 21 00:00 /var/lib/mailman3/queue/digestdrwxrwx--- 2 list > list 4096 Oct 21 00:20 /var/lib/mailman3/queue/indrwxrwx--- 2 list > list 4096 Aug 11 18:44 /var/lib/mailman3/queue/nntpdrwxrwx--- 2 list > list 4096 Oct 21 01:45 /var/lib/mailman3/queue/outdrwxrwx--- 2 list > list 4096 Oct 21 01:45 /var/lib/mailman3/queue/pipelinedrwxrwx--- 2 > list list 4096 Aug 11 18:44 /var/lib/mailman3/queue/retrydrwxrwx--- 2 > list list 69632 Oct 21 01:45 /var/lib/mailman3/queue/shuntdrwxrwx--- 2 > list list 4096 Oct 21 00:20 /var/lib/mailman3/queue/virgin > so I'm kinda running out of options why this particular problem is > happening. Any pointers? Or just toss the mailman 3.2.1 debian > package out and go for a virtualenv 3.3.1 mailman? Unexplained permissions errors are often SELinux issues. Is SELinux enabled? If so, have you tried disabling it? -- 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

[MM3-users] Re: digests are created but not sent out

by "Jörg M. Schulz"

Arrgh, you got it. There are messages in the shunt directories. But, also in mailman log. Uncaught runner exception: 'ascii' codec can't encode character '\xdf' in position 157: ordinal not in range(128) Jan 09 12:24:06 2019 (17491) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 173, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 266, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/runners/digest.py", line 324, in _dispose mime = mime_digest.finish() File "/usr/lib/python3/dist-packages/mailman/runners/digest.py", line 185, in finish footer = MIMEText(footer_text.encode(self._charset), so the footers may not contain special characters. Will review this one. This is the only thing I hate with python... > Am 09.01.2019 um 18:02 schrieb Mark Sapiro <mark(a)msapiro.net>: > > On 1/9/19 1:37 AM, "Jörg M. Schulz" wrote: >> >> Normal, non-digest messages are sent correctly. Administrative messages as well. >> >> Using GNU Mailman 3.2.0 (La Villa Strangiato) >> >> Where could I look for errors / stuck queues? >> >> /var/lib/mailman3/lists >> /var/lib/mailman3/lists/mailman.unswolke.de >> /var/lib/mailman3/lists/mailman.unswolke.de/digest.2.3.mmdf >> /var/lib/mailman3/lists/mailman.unswolke.de/digest.3.2.mmdf >> /var/lib/mailman3/lists/mailman.unswolke.de/digest.4.2.mmdf >> /var/lib/mailman3/lists/mailman.unswolke.de/digest.2.6.mmdf >> /var/lib/mailman3/lists/mailman.unswolke.de/digest.2.4.mmdf >> /var/lib/mailman3/lists/mailman.unswolke.de/digest.4.1.mmdf >> /var/lib/mailman3/lists/mailman.unswolke.de/digest.3.1.mmdf >> /var/lib/mailman3/lists/mailman.unswolke.de/digest.mmdf >> /var/lib/mailman3/lists/mailman.unswolke.de/digest.4.3.mmdf > > > When a digest is to be sent by 'mailman digests', the digest.mmdf file > is renamed to digest.x.y.mmdf (x and y are the volume and issue numbers) > and an entry placed in queue/digests to send that digest. The digest > runner then picks up that entry, prepares the digest, queues it in > queue/virgin to be sent to the recipients if any and removes the > digest.x.y.mmdf file. > > Since the digest.x.y.mmdf files are not removed, either the digest > runner is not running at all in which case there will still be entries > in queue/digests or it is encountering an error in processing in which > case there should be messages with tracebacks in Mailman's error log and > probably messages in queue/shunt. > > -- > 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/>

6 years, 3 months

[MM3-users] Re: new list not working

by Christian

There are no such messages as you describe. After turning on debugging I got this from a test message sent to the new list: Mar 10 04:39:51 2023 (1005) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Mar 10 04:39:51 2023 (1005) Peer: ('127.0.0.1', 51982) Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) handling connection Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) >> b'LHLO zarathustra.ccalternatives.org' Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) >> b'MAIL FROM:<christian(a)naturalintelligence.us> SIZE=3499' Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) sender: christian(a)naturalintelligence.us Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) >> b'RCPT TO:<redlatinleg(a)lists.ccalternatives.org>' Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) recip: redlatinleg(a)lists.ccalternatives.org Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) >> b'DATA' Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) >> b'QUIT' Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) connection lost Mar 10 04:39:51 2023 (1005) ('127.0.0.1', 51982) Connection lost during _handle_client() -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Thursday, March 9, 2023 7:51 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: new list not working On 3/9/23 13:26, Christian via Mailman-users wrote: > Smtp.log > > ++++++ > > Mar 09 20:57:09 2023 (9401) Available AUTH mechanisms: LOGIN(builtin) > PLAIN(builtin) > > Mar 09 20:57:09 2023 (9401) Peer: ('127.0.0.1', 35982) > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) handling connection > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'LHLO zarathustra.ccalternatives.org' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'MAIL FROM:christian@naturalintelligence.us SIZE=3653' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) sender: > christian(a)naturalintelligence.us > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'RCPT TO:redlatinleg@lists.ccalternatives.org' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) recip: > redlatinleg(a)lists.ccalternatives.org > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'DATA' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) >> b'QUIT' > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) connection lost > > Mar 09 20:57:09 2023 (9401) ('127.0.0.1', 35982) Connection lost > during _handle_client() > What else is in the smtp.log? There should be messages like <timestamp> (<pid>) <message-id> smtp to redlatinleg(a)lists.ccalternatives.org for nn recips, completed in n.nnn seconds <timestamp> (<pid>) <message-id> post to redlatinleg(a)lists.ccalternatives.org from christian(a)naturalintelligence.us nnn bytes If there aren't, try setting [logging.smtp] level: debug in mailman.cfg, restarting Mailman core and see what you then get in smtp.log. -- 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/ WPMR4JUQOQ6FMT24V3W6WWJQQU4Q6O7E/ This message sent to csa(a)web-analysts.net

2 years, 1 month

[MM3-users] Re: can't get mail into mailman3 in docker

by matthew＠alberti.us

Sorry for the double-tap. Apparently https://github.com/maxking/docker-mailman/pull/441 changed the behavior that I said was the default. We might need to see your docker-compose.yaml, with sensitive info removed, to know more about your setup. - Matt Alberti -----Original Message----- From: matthew(a)alberti.us <matthew(a)alberti.us> Sent: Saturday, August 7, 2021 8:21 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: can't get mail into mailman3 in docker I use the docker-mailman setup. Below is the partial contents of my mailman-extra.cfg. I think by default, you would use the Docker assigned private network IP addresses for communicating with the containers. In my setup, 172.19.199.1 is the host (where postfix is) and 172.19.199.2 is mailman-core... # EMAIL SERVER / MTA CONFIGURATION [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: 172.19.199.2 lmtp_port: 8024 smtp_host: 172.19.199.1 smtp_port: 25 configuration: /etc/postfix-mailman.cfg This is all really going to depend on your particular setup. I'm late to the thread; but let me know if that improves the situation. - Matt Alberti -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Saturday, August 7, 2021 2:04 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: can't get mail into mailman3 in docker On 8/6/21 11:28 AM, bob B wrote: > I see nothing for today when the error happens in > /opt/mailman/var/logs/smtp.log > > But the log has a bunch of these, but these stopped around the 4th > > Aug 04 19:46:04 2021 (28) Available AUTH mechanisms: LOGIN(builtin) > PLAIN(builtin) Aug 04 19:46:04 2021 (28) Peer: ('127.0.0.1', 33912) > Aug 04 19:46:04 2021 (28) ('127.0.0.1', 33912) handling connection Aug > 04 19:46:04 2021 (28) ('127.0.0.1', 33912) EOF received Aug 04 > 19:46:04 2021 (28) ('127.0.0.1', 33912) Connection lost during > _handle_client() Aug 04 19:46:04 2021 (28) ('127.0.0.1', 33912) > connection lost These are normal messages from the startup of Mailman's lmtp runner. If you correlate these with mailman.log, you'll probably see the server starting at these times. The fact that there is nothing in this log correlating with the Postfix message 2021-08-06T09:08:41.974225-04:00 dockerhost postfix/lmtp[109783]: D630B3083ED0: to=<test(a)mailman-docker.###.####>, relay=localhost[127.0.0.1]:8024, delay=0.11, delays=0.05/0.02/0.04/0, dsn=4.4.2, status=deferred (lost connection with localhost[127.0.0.1] while receiving the initial server greeting) seems to say that Postfix isn't really connecting to Mailman's lmtp and this is consistent with netstat -l not showing something listening on port 8024. I note you have lmtp_host: localhost in the [mta] section in mailman-extra.cfg. Try changing that to lmtp_host: 127.0.0.1 -- 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ _______________________________________________ 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/

3 years, 8 months

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Onyeibo Oku

Help! Regards Onyeibo On Thu Oct 13, 2022 at 6:03 AM WAT, Onyeibo Oku wrote: > On Wed, 12 Oct 2022 17:52:47 -0700 > Mark Sapiro <mark(a)msapiro.net> wrote: > > Thanks Eggert and Sapiro. > > > > > As Eggert suggests, see > > https://docs.mailman3.org/en/latest/install/virtualenv.html and > > follow that. > > I already started out on the above route. Its an adaptation because I > am running Fedora. I had no problem with system-wide installations via > dnf package management. However, some parts of the documentation does > not add up. > > > You don't need to download the source from GitLab. > > Following that doc will get the latest releases from PyPI via pip. > > Those are still somewhat out of date - we really should make new > > releases - so if you want the latest from GitLab, there are a couple > > of ways to do it. Perhaps the easiest is to just run the various `pip > > install` commands as documented and then upgrade Mailman core in your > > venv with ``` > > pip install --upgrade git+https://gitlab.com/mailman/mailman@master > > ``` > > and update the various mailman web packages with > > ``` > > pip install --upgrade git+https://gitlab.com/mailman/xxx@master > > ``` > > where xxx is mailman-web, mailman-hyperkitty, django-mailman3, > > postorius, hyperkitty. I.e., run it 5 times, once for each value of > > xxx. > > > > I will come to this eventually (assuming that does not break things > later). I aim to get it all working with regular pip packages first. I > have installed mailman core already. > > Fedora expects mailman files to reside at /usr/lib/mailman. It appears > to ship with a mailman unix user. I adapted to those system defaults. > > Now I observe that "su - mailman" gives me the proper prompt but > .bashrc doesn't kick in. I still have to manually change to the > virtual environment despite setting the automatic change in .bashrc. > However, "su mailman" runs .bashrc but the prompt says "bash X.XX $". > Is this normal? > > Subsequent parts of the doc show the path "/opt/mailman/mm/var/*" which > should correspond to "/usr/lib/mailman/mm/var/*" on my instance. > However, I don't see any instructions on how to get the "/mm" folder > and the associated sub-folders. I just have "/usr/lib/mailman" > > I am lost > > "pip list" within the venv environment confirms that I have "mailman > 3.3.5". What am I missing? > > Regards > Onyeibo > > > _______________________________________________ > 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/

2 years, 6 months

[MM3-users] Re: Broken web UI after upgrade

by Odhiambo Washington

On Sat, Dec 17, 2022 at 9:33 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/16/22 22:21, Mark Sapiro wrote: > > > > I suggest you look at ownership and permissions. > > > > ``` > > find /opt/mailman/mm/static/ -not -user mailman > > find /opt/mailman/mm/static/ -not -perm -u+rw > > find /opt/mailman/mm/static/ -type d -not -perm -u+x > > ``` > > and the same on > > /opt/mailman/mm/venv/lib/python3.9/site-packages/hyperkitty/ > > > > > >> If the above doesn't reveal anything substantial, then let me know and I > >> can bump up the verbosity. > > > > > > I don't know if --verbosity 3 will reveal anything or not. You could try. > > > Did you see the post at > < > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>? > > Have you tried > ``` > django-admin clear_cache > (venv) mailman@list:~$ /opt/mailman/mm/bin/django-admin clear_cache Cache "default" has been cleared! (venv) mailman@list:~$ ls -al /opt/mailman/mm/static/CACHE/ total 16 drwxr-xr-x 4 mailman mailman 4096 Dec 16 22:01 . drwxr-xr-x 9 mailman mailman 4096 Dec 4 06:38 .. drwxr-xr-x 2 mailman mailman 4096 Dec 16 22:01 css drwxr-xr-x 2 mailman mailman 4096 Dec 16 22:01 js (venv) mailman@list:~$ ls -al /opt/mailman/mm/static/CACHE/css/ total 8 drwxr-xr-x 2 mailman mailman 4096 Dec 16 22:01 . drwxr-xr-x 4 mailman mailman 4096 Dec 16 22:01 .. (venv) mailman@list:~$ ls -al /opt/mailman/mm/static/CACHE/js/ total 8 drwxr-xr-x 2 mailman mailman 4096 Dec 16 22:01 . drwxr-xr-x 4 mailman mailman 4096 Dec 16 22:01 .. (venv) mailman@list:~$ So all the css files that were in /opt/mailman/mm/static/CACHE/css/ are gone after running `django-admin clear_cache`. After that, I did run my mailman-post-update script again which created dirfferent files under CACHE/css/ as the date shows (venv) mailman@list:~$ ls -al /opt/mailman/mm/static/CACHE/ total 20 drwxr-xr-x 4 mailman mailman 4096 Dec 16 22:46 . drwxr-xr-x 9 mailman mailman 4096 Dec 4 06:38 .. drwxr-xr-x 2 mailman mailman 4096 Dec 16 22:46 css drwxr-xr-x 2 mailman mailman 4096 Dec 16 22:46 js -rw-r--r-- 1 mailman mailman 621 Dec 16 22:46 manifest.json (venv) mailman@list:~$ ls -al /opt/mailman/mm/static/CACHE/css/ total 176 drwxr-xr-x 2 mailman mailman 4096 Dec 16 22:46 . drwxr-xr-x 4 mailman mailman 4096 Dec 16 22:46 .. -rw-r--r-- 1 mailman mailman 162923 Dec 16 22:46 output.1d3a3c0dd51d.css -rw-r--r-- 1 mailman mailman 1209 Dec 16 22:46 output.9a7b11621c5a.css -rw-r--r-- 1 mailman mailman 569 Dec 16 22:46 output.e68c4908b3de.css (venv) mailman@list:~$ I then rebooted the system just to be sure everything is restarted. And the PROBLEM IS SOLVED :-) Thank you very much for your time spent in following this up with me to the conclusion. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 4 months

[MM3-users] Re: Installing mailman 3

by Abhilash Raj

When you set DEBUG=False, Django doesn't serve static files because of which you see only text and no styles. http://docs.mailman3.org/en/latest/pre-installation-guide.html#django-stati… If you do set DEBUG=False, you need to serve the static pages somehow. Alternatively in you case, you can remove the part of the `settings.py` which changes the Emailbackend when `DEBUG=False` so that you don't have to worry about serving static files and still send out emails. On Wed, Aug 2, 2017, at 09:46 AM, Rafael Mora wrote: > For testing purpose I turned back to false the DEBUG var and everything > started working fine with HyperKitty > > I don't understand... this is the trace when I click Login from Postorius > to HyperKitty > > [02/Aug/2017 16:43:42] "GET /postorius/lists/ HTTP/1.1" 200 3645 > [02/Aug/2017 16:43:48] "GET /accounts/login/?next=/postorius/lists/ > HTTP/1.1" 200 10950 > [02/Aug/2017 16:43:49] "GET /static/CACHE/css/hyperkitty.2f591b4e31fe.css > HTTP/1.1" 200 156657 > > > What should I check? > > > > > > > > > El mié., 2 ago. 2017 a las 10:56, Mark Sapiro (<mark(a)msapiro.net>) > escribió: > > > On 08/02/2017 07:55 AM, Rafael Mora wrote: > > > HyperKitty is looking for some files in /static/CACHE/... but it doesn't > > > find them: > > > > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/b3547a2ab51b.css HTTP/1.1" > > > 404 107 > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/4c17bb8058aa.css HTTP/1.1" > > > 404 107 > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/2fa1cba00450.css HTTP/1.1" > > > 404 107 > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" > > 404 > > > 105 > > > [02/Aug/2017 14:53:39] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" > > 404 > > > 105 > > > > > > > > > Should I run any command to activate the CACHE dir? > > > > > > You need to ensure you have a working sass compiler. As I said at > > < > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > >, > > See the third bullet under > > <http://docs.list.org/en/latest/prodsetup.html#dependencies>. > > > > Then you need to run commands like > > > > django-admin collectstatic --clear > > django-admin compress > > > > > > -- > > 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/ > > > -- > > Atentamente / Best Regards > > Ing. Rafael Mora > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- thanks, Abhilash Raj

7 years, 8 months

[MM3-users] Re: Postorius claims 2 messages held when there are none - out of sync

by Mark Sapiro

On 6/26/23 11:53 AM, Ken Alker wrote: > > Is the var/messages hierarchy also where all the archived emails are > stored for future viewing via the web interface? No. They are stored in the hyperkitty_email and hyperkitty_attachment tables in the database. >> Also, there is a long thread at >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/threa >> d/UWCUQYU7Q5X5LWNII57ZZ4DDXE4DEFX7/ and maybe others that might be >> relevant. > > I have never used the mailman shell before, but based on the referenced > thread I learned to do this (note that the thread also taught me how to > rewrite it to narrow down to just the list with issues so I didn't > delete held messages in other lists, if my case): > > for verification: > > venv) mailman@speedy:~/web/logs$ mailman shell -l > sbarc-list(a)lists.netlojix.com > Welcome to the GNU Mailman shell > Use commit() to commit changes. > Use abort() to discard changes since the last commit. > Exit with ctrl+D does an implicit commit() but exit() does not. > The variable 'm' is the sbarc-list(a)lists.netlojix.com mailing list > >>> requests = IListRequests(m) > >>> first = True > >>> for request in requests.held_requests: > ... key, data = requests.get_request(request.id) > ... if first: > ... first = False > ... print(m.list_id) > ... print (f"""\ > ... Sender: {data['_mod_sender']} > ... Subject: {data['_mod_subject']} > ... Date: {data['_mod_hold_date']} > ... Reason: {data['_mod_reason']} > ... """) > ... > and then to delete the two messages: > > (venv) mailman@speedy:~/web/logs$ mailman shell -l > sbarc-list(a)lists.netlojix.com > Welcome to the GNU Mailman shell > Use commit() to commit changes. > Use abort() to discard changes since the last commit. > Exit with ctrl+D does an implicit commit() but exit() does not. > The variable 'm' is the sbarc-list(a)lists.netlojix.com mailing list > >>> requests = IListRequests(m) > >>> first = True > >>> for request in requests.held_requests: > ... key, data = requests.get_request(request.id) > ... if first: > ... first = False > ... print(m.list_id) > ... print(f'request id: {request.id}, deleting') > ... requests.delete_request(request.id) > ... > sbarc-list.lists.netlojix.com > request id: 27, deleting > request id: 28, deleting > >>> > > The result of this, however, was that the web interface still claimed I > had two held messages. I wasn't sure if there was some cron-type > "sweeper" process I had to wait to auto-run or if I had to manually do > something to create an update. I then realized that the sample script > had a ' >>> commit ()" ' at the end, which I'd missed. So, I re-entered > the script (but it didn't spit out that it deleted anything this time) > and got an error when I did the commit. Was this in the same `mailman shell` interaction or a new one? What was the error? > So, I figured the messages HAD > been delete and the commit wasn't really necessary. When I went back to > the web interface, the number of held messages was at 0 and I no longer > get the original error when clicking on "Held messages", so my issue is > solved. But this does leave me with some educational questions: > > 1) Did I affect something somehow with my "commit", or was there a job > that cleaned things up (if so, what job)? I'm not sure of the sequence of events, but I think you probably looked in Postorius before you quit `mailman shell` and then you quit `mailman shell` with ctrl-D which did an implicit commit. > 2) Is the "commit" even necessary (I saw it in someone else's script in > the thread)? It is necessary to explicitly commit() or quit with ctrl-D to actually update the database. > 3) Is there a way to save a script and then execute it via shell rather > than typing it in every time (it appears from the examples that people > are typing them in every time, which is super tedious; I didn't paste > for fear of doing something damaging, but maybe that would work)? Yes, you can save a script in the bin/ directory in your venv and run it with `mailman shell -r`. See `mailman shell --details`. > 4) Are the request.id's of the messages dynamic/changing, or are they > fixed for life? I thought I'd delete based on exact request.id without > looping but I was afraid maybe they were changing over time and that > this wouldn't be a good idea. Might be nice to know for the future. The request.id is constant for that request object. The request object is fixed for a specific held message request. I.e., a specific held message's request object and its request.id and other attributes are fixed until that request is handled. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: Sending to mangled 'From' addresses.

by hansen

Thank you, Mark. Yes, the problem is with the mail clients which harvest addresses inappropriately (I never asked them to). I just found the header filter option, which I has been looking for under ’Settings'. Sorry for taking your time. It works great! Yours, Allan > On Jun 1, 2024, at 09:49, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 5/31/24 22:23, hansen via Mailman-users wrote: >> Due to the DMARC mitigation action ‘Replace From: with list address’, it happens often on my lists that someone sends a message to a mangled address, hoping that the message goes to the person listed as the sender. This happens mostly because the mail clients collect previous addresses and use them when as type-ahead candidates for new messages, which may be unrelated to the lists. > > > DMARC mitigation action ‘Replace From: with list address’ will also place the poster's address in Reply-To: (or Cc: depending on list configuration), so a simple `reply` from a reasonable MUA should go just to the poster. > > >> For example, say the mail client captures my address as >> “Allan Hansen via <listname>” <listaddress> >> then later, when the person wants to send a message to me, the type-ahead puts this string in the ’To:’ field: >> “Allan Hansen via <listname>” >> and, to make it worse, the actual email address, <listaddress>, is often hidden. > > > If this is the result of a `reply` and not `reply-all` the client is not behaving reasonably. > > >> The result is that the email gets sent to the list instead of to me, together with (often) personal and (sometimes) embarrassing information. > > > That is a problem with the client, but I suppose such clients are not uncommon. > >> Is there a way to reject messages sent to recipients where the name part of the recipient is of the above format, i.e., >> "Allan Hansen via <listname>" > > You could add a header filter on the To header with a regexp like `^.*via <listname>` and the desired action. > >> Should I get onto the other list to request this as an enhancement? > > I don't think that's necessary in this case, as Header filters should do it. > > In general, the best way to request an enhancement is to file an issue with the appropriate GitLab project at `https://gitlab.com/mailman` > > -- > 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://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 hansen(a)rc.org

10 months, 2 weeks

[MM3-users] Re: Custom templates (was: Re: Re: nginx configuration on a multitasking server)

by David Newman

On 1/14/22 6:35 PM, Mark Sapiro wrote: > On 1/14/22 6:11 PM, David Newman wrote: >> On 1/14/22 4:54 PM, Mark Sapiro wrote: >>> >>> It should work. I suspect you need to go to the list's Settings -> >>> Automatic Responses and set `Admin immed notify` to Yes. >> >> >> It's enabled. I think this triggers notifications only for new >> subscription requests, not pending ones. > > > Yes. That will send a single notification at the time of the request > using the `list:admin:action:subscribe.txt` template. Notices of pending > requests are sent by the `mailman notify` command using the > `list:admin:notice:pending.txt` template. > > ... >>> You can test `mailman notify` at any time by running it by hand. >> >> >> Thanks. This still isn't working as intended. I took these steps: >> >> 1. Created the file >> '/opt/mailman/mm/var/templates/lists/test.lists.domain.tld/en/list:admin:action:pending.txt' > > > The template name is `list:admin:notice:pending.txt`, not > `list:admin:action:pending.txt`. Thats why it didn't work. Bingo. Thanks -- the template works as intended now. > > ... >> 2. Restarted the mailman3 and mailmanweb services > > > You only needed to restart Mailman core. OK > > > ... >> What I'm trying to do here is replicate a feature from MM2.1, where >> pending notifications had URLs embedded in the message. That's not >> available out of the box in MM3, and if there's a place for feature >> requests I'd be glad to ask that this be made the default. > > > The place for feature requests for Mailman core (which this is) is > https://gitlab.com/mailman/mailman/-/issues, however, this is not > straightforward as Mailman core doesn't know if you even have Postorius > or some other web management UI installed or what the URL to access it > might be. Thus it's not just a simple matter of editing templates. It > would also require a configuration setting for the base URL for the web > admin UI and changes in logic to provide an appropriate replacement > depending on whether or not the base URL was configured. Understood, thanks. Although this distinction is very important for server admins, it's likely not meaningful for many list owners and moderators. For them, MM2.1 sent an email saying "go here" and MM3/Django/Postorius/Hyperkitty doesn't, at least not out of the box. There is some pending template in use by default, just not one with a URL included. Is this something better handled in the venv and/or Web installation docs? Or should I file a feature request for core, or Postorious or someplace else? Thanks very much! dn > >

3 years, 3 months

[MM3-users] Re: Reply w/Email Clients - From: vs. Reply-To:

by Jay Hamilton-Roth

On Nov 17, 2020, at 5:31 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 11/17/20 2:34 PM, j(a)manygoodideas.com wrote: >> I'm setting up a new list, and a number of new list members are reporting a problem with replying to the thread. Their email clients seem to ignore the Reply-To: field and instead use from From: field. > > > Are you saying that a 'reply' , not 'reply-all' will reply to the From: > only and ignore Reply-To:? If so, the email clients that are doing that > are badly behaved. I can't say they are non-compliant as RFC 5322 > <https://www.rfc-editor.org/rfc/rfc5322.html#section-3.6.2> only says: > > The originator fields also provide the information required when > replying to a message. When the "Reply-To:" field is present, it > indicates the address(es) to which the author of the message suggests > that replies be sent. > > > I.e., Reply-To: is only a 'suggestion', but well behaved clients will > follow it. That's exactly what I'm saying. And there's more than a few of these badly behaved clients. >> When they use Reply All, the email is addressed to both the From: and Reply-To:. > > Reply All should reply to the Reply-To:, To: and Cc: addresses and to > From: if there is no Reply-To:. Whether Reply All should include From: > if there is a Reply-To is not well defined. > > >> Reading through previous threads here, I've tried a number of things: >> >> 1) DMARC mitigation action is "Replace From: with list address" >> 2) For Alter Messages - Set "Reply goes to list" >> >> The goal is that we want a reply to go to the list, not the person posting. Since Reply-To seems to be ignored by some clients, I'm hoping there's a way to force the "From" field to become the list address. Thanks in advance for your suggestions! > > If Alter Messages -> Reply goes to list is set to Reply goes to list, > Reply-To: will include the list posting address. What are the clients > that ignore this? Complaints should go to the providers of those. Complaints sent. > > Tf DMARC mitigation action is "Replace From: with list address", that > will happen to messages to which DMARC mitigation action applies. If you > want it to apply to all messages, set DMARC Mitigate unconditionally to > Yes. That fixed it. Thanks again, Mark! > -- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 5 months

[MM3-users] Re: Adding Mass Subscribe custom template error

by Arte Chambers

Thanks! Looks resolved however I'm not 100% sure which steps fixed it: My Steps: ``` cat /etc/hosts 127.0.1.1 list.louisvillecommunitygrocery.com list 127.0.0.1 localhost ``` Updated ``` POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000/' POSTORIUS_TEMPLATE_BASE_URL = 'https://example.com' ``` Restarted mailman3 AND mailmanweb service Updated /etc/mailman3/gunicorn.conf adding workers=9 Restarted mailman3 AND mailmanweb service Deleted custom template from Postorious Created new custom template from Postorious Added test user to list User was added with no errors and also received the custom Template. Thanks Mark, Gerald Bonus question: how should I calculate how many workers I should have on my system? Thank you, Paul 'Arte Chambers' Robey 502-408-6922 On Wed, Jan 29, 2025 at 2:36 PM <vogt(a)spamcop.net> wrote: > > Sounds somewhat like the problem I have had: > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > The problem for me was that I am using gunicorn but did not increase the number of workers… > _______________________________________________ > 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 paul.m.robey(a)gmail.com Thank you, Paul 'Arte Chambers' Robey 502-408-6922 On Wed, Jan 29, 2025 at 2:54 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > On 1/29/25 11:20, Arte Chambers via Mailman-users wrote: > > Ok I did install using the > > https://docs.mailman3.org/en/latest/install/virtualenv.html > > > > I added > > ``` > > POSTORIUS_TEMPLATE_BASE_URL='https://www.example.com/' > > ``` > > I hope you didn't add the above literally without replacing > www.example.com with your actual host name. > > It should be > ``` > POSTORIUS_TEMPLATE_BASE_URL = 'list.louisvillecommunitygrocery.com' > ``` > > > to /etc/mailman3/settings.py and restarted mailman services > > > > However I'm still getting the same error from mailman.log > > > > requests.exceptions.ReadTimeout: HTTPConnectionPool(host='localhost', > > port=8000): Read timed out. (read timeout=5) > > I don't understand why it should still be trying to connect to > localhost:8000. Also, I don't understand why localhost:8000 times out. > What is your setting for localhost in /etc/hosts? it should be > `127.0.0.1`. If it is `::1` that could be the issue. > > > Not sure if I'm editing the correct config file. > > /etc/mailman3/settings.py should be correct. > > -- > 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://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 paul.m.robey(a)gmail.com

2 months, 3 weeks

[MM3-users] Re: Installing mailman 3

by Rafael Mora

content of the file maillog-20170723 (I didn't find mail.log in /var/log): [root@localhost log]# cat maillog-20170723 Jul 17 10:29:19 localhost postfix/postfix-script[1702]: warning: not set-gid or not owner+group+world executable: /usr/sbin/postqueue Jul 17 10:29:19 localhost postfix/postfix-script[1760]: warning: not set-gid or not owner+group+world executable: /usr/sbin/postdrop Jul 17 10:29:19 localhost postfix/postfix-script[1781]: starting the Postfix mail system Jul 17 10:29:20 localhost postfix/master[1791]: daemon started -- version 2.10.1, configuration /etc/postfix Jul 21 15:19:31 localhost postfix/postfix-script[9273]: refreshing the Postfix mail system Jul 21 15:19:31 localhost postfix/master[1791]: reload -- version 2.10.1, configuration /etc/postfix Jul 21 15:34:54 localhost postfix/postfix-script[9327]: fatal: cannot execute /usr/sbin/postconf! Jul 21 16:30:03 localhost postfix/postfix-script[9471]: refreshing the Postfix mail system Jul 21 16:30:03 localhost postfix/master[1791]: reload -- version 2.10.1, configuration /etc/postfix Jul 21 16:52:46 localhost postfix/postfix-script[9528]: refreshing the Postfix mail system Jul 21 16:52:46 localhost postfix/master[1791]: reload -- version 2.10.1, configuration /etc/postfix Jul 21 16:52:46 localhost postfix/qmgr[9532]: error: open database /var/lib/mailman/var/data/postfix_domains.db: No such file or directory Jul 21 16:10:47 localhost postfix/postfix-script[2099]: warning: not set-gid or not owner+group+world executable: /usr/sbin/postqueue Jul 21 16:10:47 localhost postfix/postfix-script[2105]: warning: not set-gid or not owner+group+world executable: /usr/sbin/postdrop Jul 21 16:10:47 localhost postfix/postfix-script[2112]: starting the Postfix mail system Jul 21 16:10:47 localhost postfix/master[2114]: daemon started -- version 2.10.1, configuration /etc/postfix Jul 21 16:10:47 localhost postfix/qmgr[2116]: error: open database /var/lib/mailman/var/data/postfix_domains.db: No such file or directory output command 'postconf -n': [root@localhost log]# postconf -n alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix data_directory = /var/lib/postfix debug_peer_level = 2 debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin ddd $daemon_directory/$process_name $process_id & sleep 5 html_directory = no inet_interfaces = localhost inet_protocols = all local_recipient_maps = hash:/var/lib/mailman/var/data/postfix_lmtp mail_owner = postfix mailq_path = /usr/bin/mailq.postfix manpage_directory = /usr/share/man mydestination = $myhostname, localhost.$mydomain, localhost newaliases_path = /usr/bin/newaliases.postfix owner_request_special = no queue_directory = /var/spool/postfix readme_directory = /usr/share/doc/postfix-2.10.1/README_FILES recipient_delimiter = + relay_domains = hash:/var/lib/mailman/var/data/postfix_domains sample_directory = /usr/share/doc/postfix-2.10.1/samples sendmail_path = /usr/sbin/sendmail.postfix setgid_group = postdrop transport_maps = hash:/var/libmailman/var/data/postfix_lmtp unknown_local_recipient_reject_code = 550 What's wrong? Thanks El sáb., 22 jul. 2017 a las 22:33, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/22/2017 05:29 PM, Rafael Mora wrote: > > > > How can I config Mailman/Postfix to send the confirmation email for the > > superuser I created this morning??? > > > What is in Postfix's logs relevant to the attempt to send the mail > (probably /var/log/mail.log)? > > What is the output from 'postconf -n' > > -- > 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/ > -- Atentamente / Best Regards Ing. Rafael Mora

7 years, 9 months

[MM3-users] Re: The message is larger than the 40 KB maximum size

by Mohsen Masoudfar

Thank you so much Mark. I appreciate your help! I dropped the list and recreated it, the default value worked for the new list. Using Mailman shell is very helpful. I checked the mailman.log and found the issue. Thanks Mohsen -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Monday, September 21, 2020 9:42 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: The message is larger than the 40 KB maximum size [EXTERNAL EMAIL] On 9/21/20 9:23 AM, Mohsen Masoudfar wrote: > > 1- I tried to set up the max_message_size in WUI under: listname > settings > Message Acceptance > Maximum message size to 0. > After hitting save button, I got the error message: " An error occured: Unknown attribute: max_message_size" This is <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.co…> fixed by <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.co…> in Mailman core 3.2.0. Either upgrade Mailman core or set it via `mailman shell` > 2- I checked the python files and found this file, where, it seems, the default value is defined: > /usr/lib/python3/dist-packages/mailman/styles/base.py : mlist.max_message_size = 40 > > I changed this value to 0, saved the file, restarted the mailman and postgresql (not sure if needed) and sent an email with a large attachment to my test list with just two members. I got the response email: > The message is being held because: The message is larger than the 40 KB maximum size Changing that file only affects the default setting for new lists. It doesn't affect any existing list. To change this you can either update Mailman's database to set max_message_size = 0 in the entry for the list in the mailinglist table or do something like $ /opt/mailman/mm/bin/mailman shell -l list.example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list.example.com mailing list >>> m.max_message_size 40 >>> m.max_message_size = 0 >>> commit() > 3- I totally agree that the most important issue is the fact that the message vanished with the production list. > I repeated the same with a (test) list which has two members, I got the email mentioning the 40 KB limit and I could release it. This is how I am running my tests now. I repeated it with the original list (with 197 members) the message disappeared again. I can send an email to the list with 197 members, without this attachment and it works. > > 4- I checked the folders, under /var/lib/mailman3/queue/, all folders > are empty: archive/ bad/ bounces/ command/ digest/ in/ nntp/ > out/ pipeline/ retry/ shunt/ virgin/ OK, but what if anything is in Mailman's mailman.log? -- 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…

4 years, 7 months

[MM3-users] Re: CSS Hyperkitty ERROR

by Johan Alsina

Johan Alsina wrote: > Stephen J. Turnbull wrote: > > Hi, i installed mailman3 with virtualenv, all is working fine, the > > admin site works fine, the mailman(postorious) site works fine, but > > when im in hyperkitty the site shows without the css style.. in my > > web browser dev tool it shows like they loaded ok.. > > I think you need to figure out why the dev tool can see the CSS files > > but other environments can't. It sounds exactly like all the other > > Any ideas? :/ > > My static files are loading from > > /static/CACHE/css/output.a0f71925131b.css and > > /static/hyperkitty/libs/fonts/font-awesome/css/font-awesome.min.css > > I've run into the "no styles" issue on a number of new hosts where the > > Johan Alsina via Mailman-users writes: > > problems I couldn't diagnose. :-/ > > problem was that somewhere on the path to the CSS files was a > > directory, typically owned by root, without "x" permissions for > > "other" users. That difference across trees is weakly consistent with > > a "somewhere in between" permissions problem. > > Steve > > Hi Steve, thanks for answer, i tried all about permissions and paths and i thins all its ok.. here you can see my paths/permissions.. > General: https://freeimage.host/i/3ok1LDN > Django project: https://freeimage.host/i/3ok1ZxI > Mark Sapiro wrote: > > On 3/17/25 6:46 PM, Johan Alsina via Mailman-users wrote: > > Hi, i installed mailman3 with virtualenv, all is working fine, the admin site works fine, the mailman(postorious) site works fine, but when im in hyperkitty the site shows without the css style.. in my web browser dev tool it shows like they loaded ok.. > > Have you run mailman-web collectstatic and mailman-web compress? See > > https://docs.mailman3.org/en/latest/install/virtualenv.html#collect-static-f... > > If you have, try running them again as mailman-web collectstatic --clear and mailman-web compress. > > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > > San Francisco Bay Area, California better use your sense - B. Dylan > > Hi Mark, thanks for the answer. Yes, i tried all variations about collectstatic, clear_cache, etc.. comands with no difference. I dont get any error and the files are collected ok.. > Like i said before, i think the problem comes with the css files in /static/CACHE.. because the ones that are in /static/hyperkitty are loading ok.. > css files in /static/CACHE not loading: https://freeimage.host/i/3okk6CJ > img files in /static/hyperkitty loading: https://freeimage.host/i/3okkPEv > I tried to move /static/CACHE inside of /static/hyperkitty but when i run collectstatic the files goes again to the default path.. > Thanks in advance.. Sorry, the links about css files and img files are in the wrong order css files in /static/CACHE not loading: https://freeimage.host/i/3okkPEv img files in /static/hyperkitty loading: https://freeimage.host/i/3okk6CJ

1 month

[MM3-users] Re: Apache Conf

by Thomas G

Yes, of course. Nginx and Apache works on the same server. (Nginx is stopped) I would like switch to Apache to add in front of hyperkitty a ldap connection. I need to re-compile nginx for this feature. It's directly available in apache with a module. In fact, a tried directly to integrade LDAP with django ( https://gitlab.com/mailman/postorius/issues/132) without results. Le ven. 19 oct. 2018 à 20:18, Abhilash Raj <maxking(a)asynchronous.in> a écrit : > > > On Fri, Oct 19, 2018, at 12:17 PM, Thomas G wrote: > > Hi tried both. > > > > Same result. > > > > xxxx - - [19/Oct/2018:21:14:22 +0200] "GET /static/postorius/js/script.js > > HTTP/1.1" 404 4051 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:60.0) > > Gecko/20100101 Firefox/60.0" > > > And, you have verified that the files exist at `/opt/mailman/static` on > your host? > > > > > > > Le ven. 19 oct. 2018 à 18:59, Mark Sapiro <mark(a)msapiro.net> a écrit : > > > > > On 10/19/18 10:29 AM, Guiseppin Thomas wrote: > > > > Hi, > > > > Currently, I use a nginx configuration for mailman. It's work > perfectly. > > > > > > > > I tried to do the same with Apache, but the statics files are not > > > > delivered (404). > > > ... > > > > <VirtualHost *:80> > > > > ServerName mailing.ddd.fr > > > > > > > > ErrorLog ${APACHE_LOG_DIR}/mailing.error.log > > > > CustomLog ${APACHE_LOG_DIR}/mailing.access.log combined > > > > > > > > <Location /static/> > > > > Alias "/opt/mailman/static/" > > > > </Location> > > > > > > > > <Location /> > > > > ProxyPass http://localhost:8000/ > > > > ProxyPassReverse http://localhost:8000/ > > > > ProxyPreserveHost On > > > > </Location> > > > > </VirtualHost>/ > > > > > > > > > In Apache, location > > > <http://httpd.apache.org/docs/2.4/mod/core.html#location> is not > > > appropriate for resources in the file system. > > > > > > Try > > > > > > Alias /static/ /opt/mailman/static/ > > > > > > not within a location block. > > > > > > -- > > > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > > > _______________________________________________ > > 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) >

6 years, 6 months

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I´m getting this: (env) [mailman@localhost etc]$ mailman stop Shutting down Mailman's master runner (env) [mailman@localhost etc]$ mailman start Starting Mailman's master runner (env) [mailman@localhost etc]$ Traceback (most recent call last): File "/usr/local/lib/python3.6/asyncio/base_events.py", line 1043, in create_s erver sock.bind(sa) OSError: [Errno 98] Address already in use During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/var/lib/mailman/env/bin/runner", line 11, in <module> sys.exit(main()) File "/var/lib/mailman/env/lib/python3.6/site-packages/mailman/bin/runner.py", line 198, in main runner.run() File "/var/lib/mailman/env/lib/python3.6/site-packages/mailman/runners/lmtp.py ", line 242, in run self.lmtp.start() File "/var/lib/mailman/env/lib/python3.6/site-packages/aiosmtpd/controller.py" , line 55, in start raise self._thread_exception File "/var/lib/mailman/env/lib/python3.6/site-packages/aiosmtpd/controller.py" , line 35, in _run ssl=self.ssl_context)) File "/usr/local/lib/python3.6/asyncio/base_events.py", line 466, in run_until _complete return future.result() File "/usr/local/lib/python3.6/asyncio/base_events.py", line 1047, in create_s erver % (sa, err.strerror.lower())) OSError: [Errno 98] error while attempting to bind on address ('127.0.0.1', 8024 ): address already in use Traceback (most recent call last): File "/var/lib/mailman/env/bin/runner", line 11, in <module> sys.exit(main()) File "/var/lib/mailman/env/lib/python3.6/site-packages/mailman/bin/runner.py", line 194, in main runner = make_runner(*args.runner, once=args.once) File "/var/lib/mailman/env/lib/python3.6/site-packages/mailman/bin/runner.py", line 94, in make_runner return runner_class(name, slice) File "/var/lib/mailman/env/lib/python3.6/site-packages/mailman/runners/rest.py ", line 53, in __init__ self._server = make_server() File "/var/lib/mailman/env/lib/python3.6/site-packages/mailman/rest/wsgiapp.py ", line 234, in make_server handler_class=AdminWebServiceWSGIRequestHandler) File "/usr/local/lib/python3.6/wsgiref/simple_server.py", line 153, in make_se rver server = server_class((host, port), handler_class) File "/usr/local/lib/python3.6/socketserver.py", line 453, in __init__ self.server_bind() File "/usr/local/lib/python3.6/wsgiref/simple_server.py", line 50, in server_b ind HTTPServer.server_bind(self) File "/usr/local/lib/python3.6/http/server.py", line 136, in server_bind socketserver.TCPServer.server_bind(self) File "/usr/local/lib/python3.6/socketserver.py", line 467, in server_bind self.socket.bind(self.server_address) OSError: [Errno 98] Address already in use Why does it say Address already in use? El mar., 1 ago. 2017 a las 15:10, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 8/1/17 12:52 PM, Rafael Mora wrote: > > I made a change for test purpose on the mailman.cfg file and I got this: > > > > > > (env) [mailman@localhost etc]$ mailman restart > > Restarting the Mailman runners > > PID unreadable in: /var/lib/mailman/var/etc/var/master.pid > > [Errno 2] No such file or directory: > > '/var/lib/mailman/var/etc/var/master.pid' > > Is the master even running? > > > > How do I solve this? > > > Try > > mailman stop > mailman start > > -- > 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/ > -- Atentamente / Best Regards Ing. Rafael Mora

7 years, 8 months

[MM3-users] Re: Apple Mail encoding again

by Rainer Herbst

Dear all, my first post was to optimistic - the user tested some other combinations and when he tries to send a signed HTML mail, the server again refuses to accept it with "Diagnostic-Code: smtp; 501 Message has defects". The user suggested that the problem is caused by a line containing only "-- " somewhere in the text, but I can not confirm this. Please find enclosed the refused mail (anonymized). Regards Rainer On Mi, 20 Apr 2022 10:51:38 +0200 Rainer Herbst <rainer.herbst(a)aip.de> wrote: > Dear all, > > as the original poster, I have asked the user to send a test mail >through our mailman3 system (docker image > maxking/mailman-core:0.4.2) and the mail passed. > > The user is now on Apple Mail 16, maybe that does the trick. Please >find enclosed the anonymizied mail source. > > Best regards and thanks for caring even if the problems seems to >affect only a small number of users! > Rainer > > On Fr, 15 Apr 2022 09:03:41 -0700 > Mark Sapiro <mark(a)msapiro.net> wrote: >> On 4/14/22 21:33, Stephen J. Turnbull wrote: >>> >>> Whether we *want* to do that depends on how much trouble that causes >>> for our main constituency (list and site admins), and whether we can >>> provide discoverable documentation of the problem. My take is that >>> this seems to be an extremely rare problem, and at least some MUAs >>>are >>> able to read the message, so we should let it through. >> >>First, we are not silently dropping this message. We are rejecting it >>at LMTP time so the sender should be notified. >> >> Then the broader question is should we accept all messages with >>defects, almost all of which are spam, or only certain defects and >>which ones. >> >> I note that Apple has now released Mail 16 so maybe they've fixed >>this. My macs are still on Big Sur, so I can't test this. >> >> >> -- >> 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> > > Viele Grüße > > Rainer Herbst > Leiter IT-Service > Phone: +49 331 7499-257 > e-mail: rainer.herbst(a)aip.de > https://www.aip.de > > ----------------------------------------------------------------------------------------------- > Leibniz-Institut für Astrophysik Potsdam (AIP) > An der Sternwarte 16, 14482 Potsdam > > Vorstand: Prof. Dr. Matthias Steinmetz, Wolfram Rosenbach > Stiftung bürgerlichen Rechts > Stiftungsverzeichnis Brandenburg: 26 742-00/7026 > ----------------------------------------------------------------------------------------------- Viele Grüße Rainer Herbst Leiter IT-Service Phone: +49 331 7499-257 e-mail: rainer.herbst(a)aip.de https://www.aip.de ----------------------------------------------------------------------------------------------- Leibniz-Institut für Astrophysik Potsdam (AIP) An der Sternwarte 16, 14482 Potsdam Vorstand: Prof. Dr. Matthias Steinmetz, Wolfram Rosenbach Stiftung bürgerlichen Rechts Stiftungsverzeichnis Brandenburg: 26 742-00/7026 -----------------------------------------------------------------------------------------------

3 years

[MM3-users] Re: hyperkitty failed to create a thread

by Danil Smirnov

Hi guys, I've updated my containers (though can't confirm for sure the fix is in there; but I see that the 'latest' tag of 'mailman-web' has been rebuilt in the last night). Could you advise how to rebuild the failing threads please? I've done index update with 'django-admin update_index' command but it seems irrelevant to the issue, I still have all those messages separated: https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org/2019/2/ Thank you very much! Danil сб, 16 февр. 2019 г. в 18:46, Abhilash Raj <maxking(a)asynchronous.in>: > > > On Thu, Feb 14, 2019, at 11:51 AM, Danil Smirnov wrote: > > Thank you very much for the quick fix, Mark and Abhilash! > > > > Abhilash, could you include the fix into the "latest" version of > > mailman-web container please? > > They are nightly builds, if the fix was merged and the CI went through, > they should > already be in there. > > > > > Btw I wasn't able to find a changelog of Mailman docker images anywhere > and > > 'Releases' page in Github is quite outdated too... Is there any other > > place I should check? > > I have admittedly been too busy to write release notes, but the recent > releases > have seen not too much changes other than version bumps for the included > Mailman packages. > > > > > Danil > > > > вт, 12 февр. 2019 г., 4:06 Mark Sapiro <mark(a)msapiro.net>: > > > > > On 2/11/19 9:47 AM, Danil Smirnov wrote: > > > > > > > > What could be a reason of HyperKitty failing to create a thread from > > > > chained emails? > > > > > > > > For example, see "RECENTLY ACTIVE DISCUSSIONS" on page > > > > https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org/ > > > > > > > > "Openvpn and Network mapping" discussion displayed as five threads > > > instead > > > > of only one... > > > > > > > > Any ideas how to improve HyperKitty ability to detect threaded > messages? > > > > > > > > > Thanks for the report. > > > > > > The MR at <https://gitlab.com/mailman/hyperkitty/merge_requests/125> > > > will fix this. > > > > > > -- > > > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > > > _______________________________________________ > > 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) >

6 years, 2 months

[MM3-users] Re: [ERROR] Error handling request List archivers

by Shashikanth Komandoor

Thank you Mark for guiding me to the benefit of putting the list and so I have added the list. Along with the [archiver.hyperkitty], [mta] and [database], few lines of my mailman.cfg look like below: *[webservice]workers = 4timeout = 900* The above block of webservice is added yesterday for testing or trail as I am getting the above issue. And there is no line that is calling *gunicorn* in my mailman.cfg. Apart from that I tried to locate and see the content of the gunicorn.cfg file as below : *(venv3) [root@lsmgr mailman]# cat /var/lib/mailman/mailman/src/mailman/config/gunicorn.cfg[gunicorn]# All the options that can be put here are available at# http://docs.gunicorn.org/en/stable/settings.html#settings <http://docs.gunicorn.org/en/stable/settings.html#settings># No of seconds to wait before killing the worker processes.graceful_timeout = 30* Please confirm the time I have to change is *graceful_timeout *in *gunicorn.cfg* and if I have changed how do I restart the *gunicorn*. I have never used or never known about this *gunicorn* but still running the service in production. Please help me and also suggest if I could provide you any more data from giving resolution. <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…> <#m_5710631741815235215_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Thu, Jul 23, 2020 at 3:47 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/22/20 9:13 AM, Shashikanth Komandoor wrote: > > > Never mind please I am sending to you only instead of group as I am > sending you the production content along with the mail. > > I don't see anything there that can't be posted to the > mailman-users(a)mailman3.org list. If your concern is revealing the > support-tnvc.lsmgr.nic.in list id, just replace it with <list-id> or > list.example.com or similar. > > Messages sent to me personally rather than the list suffer many > problems. They are my absolute last priority, and I am only one person, > the collective knowledge of the list is greater. Also, at times I am off > line for several days or longer. > > Finally, there is no opportunity for other members of the community to > benefit from an off-list exchange. > > > When I am trying to browse one of my lists, I am getting "[ERROR] > > Error handling request /3.1/lists/support-tnvc.lsmgr.nic.in/archivers > > <http://support-tnvc.lsmgr.nic.in/archivers>" in the mailman.log and the > > full error message is in attachment. > > Try increasing your gunicorn worker timeout from the default 30 seconds. > I.e., add > > timeout = 90 > > to your gunicorn.cfg and restart gunicorn. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > -- 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>

4 years, 9 months

Search results for query "sapiro"