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

[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, 11 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, 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

4 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

2 years, 6 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

8 months, 1 week

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

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

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

5 years, 3 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.

1 year, 5 months

[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

3 years, 8 months

Search results for query "sapiro"