Thanks all for sharing thoughts.
Pulseservers suggested the additional restrictions mentioned here by Robin. That is what's in place on my node now.
niftybunny, I would also like to hear the details of your story.
Will keep you all informed in the event things go wrong with pulseservers.
Uncertainty around service providers is yet another reason I chose the ansible project as a starting point.
--
Colin
On February 23, 2017 4:23:35 PM PST, Robin
rok@sent.com wrote:
>I have a Exit Relay running on Pulseservers, my node got suspended once
>over abuse complaints (sending SPAM) but I adjusted the Exit Policy
>(ReducedExitPolicy, with some additional restrictions such as: No
>email/IMAP/SMTP/POP, SSH(22), RDP, FTP).
>A second abuse complainted was about a large number of SSH connections,
>so I adjusted the ExitPolicy, case closed.
>
>
>Besides that: Works fine.
>
>
>
>
>
>
>
>----- Original message -----
>
>From: anondroid
tor@anondroid.com
>
>To: tor-relays@lists.torproject.org
>
>Subject: Re: [tor-relays] New Relay Operator: Hostname
>
>Date: Thu, 23 Feb 2017 15:27:13 -0500
>
>
>
>> Just a warning: There is a good chance that Pulsserver will fuck
>> you over.
>> Source: Got fucked.
>
>
>
>Care to elaborate? Does "got fucked" translate to "got kicked off after
>repeated abuse complaints?" That would probably not surprise anyone
>who's tried to run an exit on a VPS.
>
>
>I'd be inclined to say Colin has done his due diligence, and there's
>not
>really any need to worry about OVH policies. On the other hand, there's
>not much point to running one if it's common knowledge it won't last
>long with this provider.
>
>
>
>
>_________________________________________________
>
>tor-relays mailing list
>
>tor-relays@lists.torproject.org
>
>
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays