From: Peter Korsgaard <peter@korsgaard.com>
To: Edgar Bonet <bonet@grenoble.cnrs.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] Being kicked-off the mailing list
Date: Mon, 25 Mar 2024 10:10:48 +0100 [thread overview]
Message-ID: <87msqmd6cn.fsf@48ers.dk> (raw)
In-Reply-To: <3a03670a-7a1b-4fd9-a44a-b5ffff19dc94@grenoble.cnrs.fr> (Edgar Bonet's message of "Mon, 25 Mar 2024 09:32:10 +0100")
>>>>> "Edgar" == Edgar Bonet <bonet@grenoble.cnrs.fr> writes:
> Hello everybody!
> This must be the third time it happens, and I find it somewhat
> annoying... This morning I received an e-mail from buildroot-request
> informing me that my membership to this mailing list has been disabled
> due to “excessive bounces”.
> I tried to investigate and it turns out that “excessive bounces”
> actually means that exactly one message bounced, namely the message
> titled “Your mailbox is full” from Storage Accounts[1]. I discussed the
> issue with my e-mail provider and they say that bouncing messages that
> are 100%-certain phishing attempts is the desired behavior, and they
> will not disable the junk-mail filter, which is already very lax.
> Would it be possible to configure Buildroot's mail server to be a bit
> more tolerant to bounces? I understand the need to unsubscribe addresses
> that generate too many errors, but I find this “kick-out on first
> bounce” policy a bit extreme.
Sorry about that. I have bumped the mailman bounce_score_threshold from
5 to 10, hopefully that fixes it.
The documentation for that setting is:
Each subscriber is assigned a bounce score, as a floating point
number. Whenever Mailman receives a bounce from a list member, that
member's score is incremented. Hard bounces (fatal errors) increase the
score by 1, while soft bounces (temporary errors) increase the score by
0.5. Only one bounce per day counts against a member's score, so even if
10 bounces are received for a member on the same day, their score will
increase by just 1. This variable describes the upper limit for a
member's bounce score, above which they are automatically disabled, but
not removed from the mailing list.
I have also lowered bounce_info_stale_after from 3 to 1. The
documentation for that setting is:
The number of days after which a member's bounce information is
discarded, if no new bounces have been received in the interim. This
value must be an integer.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-03-25 9:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 8:32 [Buildroot] Being kicked-off the mailing list Edgar Bonet
2024-03-25 9:10 ` Peter Korsgaard [this message]
2024-03-25 10:43 ` Edgar Bonet
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=87msqmd6cn.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=bonet@grenoble.cnrs.fr \
--cc=buildroot@buildroot.org \
/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