Gareth,
Thank you for your response.
I can imagine how this could turn into Oil and Gas incident and I
certainly wouldn't want that for myself or anyone else. I'm still
debating the privacy of CC:ing the group. As the majority of us do, I've
received lots of abuse emails.... but none quite like this. What I
have done here is brought the issue to the herd for protection instead
of isolating the incident and keeping away from the rest of you. At the
time I felt that everyone on the relay list might want to know about the
individual, but in hindsight it was spam to most.
I apologize for the spam.
John
On Mar 29, 2017, at 03:23, Gareth Llewellyn
<gareth@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
<mailto:gareth@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>> wrote:
Whilst your complainant seems to have a bee in their bonnet I'm not
sure you're doing anyone anyone any favours by CC'ing pseudo-private
correspondence into a mailing list.
As a fellow ISP owner running Tor Exits (AS28715) I also enjoy the
"right" to treat abuse requests according to rules that only I write
(UK legislation not withstanding) but IMHO we have a responsibility
proportional to our "mere conduit" superpowers, both to the privacy of
Tor users *and* crazy abuse@ emails from individuals.
This could turn into another Mozilla / Oil and Gas thing
( https://arstechnica.co.uk/security/2017/03/firefox-gets-complaint-for-labeling-unencrypted-login-page-insecure/
)
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx <mailto:tor-relays@xxxxxxxxxxxxxxxxxxxx>
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays