On Mon, Jan 25, 2021 at 01:03:07AM -0500, John Kaufmann wrote:
... The best practice when dealing with a piece of mail that has been
identified as so spammy that you don't want to receive it is not to
file it away in a spam folder, but to reject it at SMTP time.
... At least with an SMTP-time reject, the sending system knows that
the mail has not been safely sent. If it is a human sender than they
can take appropriate action if a mistake has been made.
Unfortunately Debian's listserv doesn't like it when you do this...
[so I] abandon the SMTP reject best practice policy for mails from
Debian lists.
You don't have that option, because you don't run your MTA. But the
people who run your MTA are doing the right thing by rejecting email
that they consider too spammy. So although it may be worth asking if
there's anything they can do, it's likely they won't want to do
anything differently there.
I cannot currently post to the SOGo list because their spam
filter (UCEPROTECT) claims that my ISP currently hosts 6
spammers. In response, they block all mail from that ISP (called
UCEPROTECT Level2 protection). Again, getting my ISP to care
about this is an ongoing challenge.
Now this one is different. UCEPROTECT doesn't have a good reputation
amongst DNSBLs. They routinely list entire providers for a small
number of incidents and they require a payment to be removed.