From: Michael Tremer <michael.tremer@ipfire.org>
To: Tom Rymes <tom@rymes.net>
Cc: "IPFire: Development-List" <development@lists.ipfire.org>
Subject: Re: Bounce messages
Date: Sun, 10 Aug 2025 14:03:05 +0100 [thread overview]
Message-ID: <150D8F08-7AF0-49B6-B759-E729BB8451CC@ipfire.org> (raw)
In-Reply-To: <A0CA4E6F-899E-4E06-B27B-E7BF89BAA438@rymes.net>
Hey Tom,
I think you can safely ignore this.
I updated the server that is hosting the mailing list to Debian 13 and for some reason, this emails got generated. I got one, too, but I don’t think it is a reason to be concerned.
Best,
-Michael
> On 10 Aug 2025, at 13:49, Tom Rymes <tom@rymes.net> wrote:
>
> I’ve gotten a second message from the list indicating that 700+ messages have bounced, but that things are back to normal.
>
> I can’t find any reason that messages should be bouncing, and the number seems impossibly high, given the reasonably light traffic on the list.
>
> Has anyone else had this happening?
>
> Tom
next prev parent reply other threads:[~2025-08-10 13:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-10 12:49 Tom Rymes
2025-08-10 13:03 ` Michael Tremer [this message]
2025-08-10 13:14 ` Adolf Belka
2025-08-10 13:06 ` Adolf Belka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=150D8F08-7AF0-49B6-B759-E729BB8451CC@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
--cc=tom@rymes.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox