On 4/12/21 11:56 AM, Ben Cooksley wrote:
There isn't an exact threshold.
The issue is that email providers (such as Google, Outlook.com -
Microsoft, Yahoo and GMX) keep track of email servers sending patterns.
Should we deviate from these patterns, then their systems will
automatically impose restrictions - including at times totally refusing
to accept further email.
It can also impact on decisions made by their spam filters, which can
lead to legitimate email going to spam folders and therefore being
missed by people. Depending on the age of the bug, it may also lead to
people marking email as spam - which will have an negative impact on the
reputation metrics they maintain, and increase the long term risk of
email going to the spam folder.
This impacts on much more than just Bugzilla, as all KDE.org
"transactional" email is sent through one server - so a block against
Bugzilla will also block email from Identity, Gitlab and Phabricator
among others.
It also has spillover implications to our mailing lists (which use a
separate server for handling their email) as all actions that take place
on Bugzilla lead to an email being sent to the kde-bugs-d...@kde.org
<mailto:kde-bugs-d...@kde.org> mailing list. Consequently, it will also
knock out delivery for those providers used by people subscribed to that
list.
When we have had these incidents in the past it has sometimes taken
several days for the mail queue to drain for all of the involved
providers and for email delivery behaviour to totally return to normal.
This was very frustrating for the affected contributors at the time, and
there was nothing we could do for them except wait - and is therefore
something we should avoid.
Thanks for the explanation. Can I ask you to do your magic to silently
move all bugs in the Klipper product to the Plasmashell | Clipboard
component? Looks like it's about 100 bugs.
Nate
