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

[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

3 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.

1 year, 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, 9 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, 8 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, 7 months

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

[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)

5 years, 5 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, 9 months

[MM3-users] Re: [NON-INTERNAL] Re: Missing Archived emails - Hyperkitty - CERT Issue

by Willie Castillo

The issue started right after the site's CERT expired. The CERT expired on 7/8/25. This is what's in the log... Jul 16 15:19:45 2025 (3777209) Connection to HyperKitty failed: HTTPSConnectionPool(host='XXX.com', port=443): Max retries exceeded with url: /hyperkitty/api/mailman/urls?mlist=jmats-versions%40XXX.com (Caused by SSLError(SSLCertVerificatio nError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (_ssl.c:1000)'))) The CERT has been updated but the 7/25 message is not archived still. ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Monday, July 28, 2025 8:10 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [NON-INTERNAL] [MM3-users] Re: Missing Archived emails - Hyperkitty - CERT Issue 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/28/25 13:07, Willie Castillo wrote: > I tried with a new post and still, not showing the messages from July 25th in the Archive. There must be a way to force the archiving of the messages from July 25th. > > List metrics > > Created at March 25, 2016, 11:15 a.m. > Last post at July 25, 2025, 12:01 p.m. > Digest last sent at July 25, 2025, 12:01 p.m. > Volume 135 Did the new post get archived? If so, why is last post at still July 25, 2025? If no, why not. The post must go to the archiver to cause the queue to be processed. If the post was archived and the July 25 messages are still queued, what's in Mailman's mailman.log. There should be error messages and tracebacks indicating 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://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

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

2 years, 1 month

Search results for query "sapiro"