You somewhat made a mistake here - you've got to have an exit policy that (minimally) rejects ports 25 and 465, or else your relay becomes a giant abuse tool for spammers, scammers, and phishers instead of what you intended it to be (which was a standard-functioning Tor relay).
You might try telling your ISP that you made a mistake in your configuration which allowed spam email to go out, and you're willing to correct that error and move forward.
ExitPolicy reject *:25 ExitPolicy reject *:465
On 14-07-30 05:11 AM, tor@t-3.net wrote:
You somewhat made a mistake here - you've got to have an exit policy that (minimally) rejects ports 25 and 465, or else your relay becomes a giant abuse tool for spammers, scammers, and phishers instead of what you intended it to be (which was a standard-functioning Tor relay).
You might try telling your ISP that you made a mistake in your configuration which allowed spam email to go out, and you're willing to correct that error and move forward.
ExitPolicy reject *:25 ExitPolicy reject *:465
Most SMTP servers i have seen listening on port 465 and 587 require authentication, so it shouldnt be necessary to block those ports. Can anyone name some that dont need authentication to send email?
tor@t-3.net:
You somewhat made a mistake here - you've got to have an exit policy that (minimally) rejects ports 25 and 465, or else your relay becomes a giant abuse tool for spammers, scammers, and phishers instead of what you intended it to be (which was a standard-functioning Tor relay).
Please don't blame the victim. If this ISP acted differently than what they initially promised, then they are the problem.
At this point the isp is clearly the victim! This guy doesn't have his own ips and ipv4 is rare, so risking a complete ip range to get on blacklists will be unacceptable for any company. I can fully understand them, because dealing with spamhaus mafia is a nightmare. Lets hope they wont getting tor unfriendly because of this, i run there exits for 2 years on some vps's without a problem and i hope they don't start killing them now Am 30.07.2014 14:39 schrieb "Lunar" lunar@torproject.org:
tor@t-3.net:
You somewhat made a mistake here - you've got to have an exit policy that (minimally) rejects ports 25 and 465, or else your relay becomes a giant abuse tool for spammers, scammers, and phishers instead of what you
intended
it to be (which was a standard-functioning Tor relay).
Please don't blame the victim. If this ISP acted differently than what they initially promised, then they are the problem.
-- Lunar lunar@torproject.org
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays@lists.torproject.org
-
krishna e bera -
Lunar -
tor＠afo-tm.org -
tor＠t-3.net