Spamhaus informed me, and I quote:

>> Alright, the fact that the VM is a TOR node is what definitely
>> tripped the robot (amongst other things, but this was the tipping
>> point). I fixed the logic and it should never happen again [...]

There was neither a break-in, nor mail sent to trigger the Spamhaus
listing. Just some robot erroneously inferring bad behaviour from Tor
network affiliation. I'd like the hours spent on a wild goose chase
back, please.

Thank you to all mailing list members who responded and tried to help.

-Ralph
_______________________________________________
mailop mailing list
[email protected]
https://list.mailop.org/listinfo/mailop

Reply via email to