On 2/17/20 2:35 AM, Benoit Panizzon via mailop wrote:
Now I got into discussion with the operator of several TOR exit
nodes. He claims that his ISP threatened to disconnect his TOR
servers because they were subject to a couple of abuse complaints
from our spamtraps.
It sound to me like /he/ h
Ah, yeah, I've been using it for a while. It often replies something like:
ab...@genonop.cf (default, no info)
In this case, I can use a verifysmtp command[*] like so:
~:tmp# verifysmtp ab...@genonop.cf
: verification failed
>>> mail.genonop.cf [89.40.114.11]:
>>> RCPT TO:
450
There's a domain-based abuse contact registration system already that
is relatively commonly used. Perhaps it is a bit US-centric. It is the
Network Abuse Clearinghouse run by John Levine and you can find it at
www.abuse.net.
Cheers,
Al Iverson
On Wed, Feb 19, 2020 at 3:44 AM Alessandro Vesely vi
Dnia 19.02.2020 o godz. 10:42:13 Alessandro Vesely via mailop pisze:
>
> By-domain abuse mailboxes are more difficult. Of course, it is inadvisable to
> send complaints to abuse@domain if domain is not SPF- or DKIM- (or DNSWL-)
> authenticated. Then, there are (authenticated) domains who miss an
A reminder:
On Thu, 16 Jan 2020, at 21:26, Michael Wise via mailop wrote:
And it appears to still be happening. Hmm.
1 month later, yes, MTA-STS at the receiving side of hotmail.com +
outlook.com is _still_ broken :} (I haven't tried other Microsoft
domains apart from @microsoft.com which
Hi all,
Whenever an abusive message lands in our inboxes, some of us report it to the
relevant abuse team. Large mailbox providers deploy buttons or folders
to automate such reporting. Smaller ones often don't have such equipment, and
send reports manually, if at all.
Besides feedback loops,