++ 25/05/15 12:48 -0400 - t...@t-3.net:
A lot of trouble would be prevented for exit node operators if, when they
brought their relays up for the first time, they ensured that the exit policy
rejected port 25. Even if they desire to run as unrestricted a relay as
possible, in my experience, that
On 05/22/2015 12:19 AM, Speak Freely wrote:
The problem is compounded by the fact each BL company is racing
it's way
to the bottom, adding each others finds to their own lists.
SpamHaus has
OVER 1 *BILLION* addresses listed.
I lost several relays (11) from OVH because DanTor recorded my
++ 25/05/15 13:47 -0400 - t...@t-3.net:
Doing nothing on email ports but still ending up on a meaningful number of
RBLs doesn't sound right. Maybe all it took to piss the ISP off was for one
of them to do it.
Maybe. Maybe there has been some internal policy change within Leaseweb,
maybe there
On 05/25/2015 08:17 PM, Rejo Zenger wrote:
++ 25/05/15 12:48 -0400 - t...@t-3.net:
A lot of trouble would be prevented for exit node operators if,
when they
brought their relays up for the first time, they ensured that the
exit policy
rejected port 25. Even if they desire to run as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
The lists of SECTOOR might be used wrongly but they sound like they
belong to the ever growing list of 'shitty blacklists'. In my work for
a hosting company I receive complaints regarding malpractices of such
lists on a daily basis. For example
blaatenator:
* Port 25
* Port 194
* Port 465
* Port 587
* Port 994
* Port 6657
* Ports 6660-6670
* Port 6697
* Ports 7000-7005
* Port 7070
* Ports 8000-8004
* Port 9000
* Port 9001
* Port 9998
* Port
Were you using the recommended reduced exit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I forgot to mention the list of 'shitty blacklists' offers hardly any
way to request delisting when the event occurs an IP address gets
handed out to a different user. As far as I have seen SECTOOR belongs
on this list based on the fact that
++ 21/05/15 22:04 +0200 - Jurre van Bergen:
I got the same message yesterday, I asked leaseweb to put our exit
node(hviv103) in a dirty ip-block and asked sectoor for a
clarification on what happened. No reply to date of any party.
This DNSBL has a fairly straightforward listing for an
++ 21/05/15 22:35 +0200 - Tim Semeijn:
The lists of SECTOOR might be used wrongly but they sound like they
belong to the ever growing list of 'shitty blacklists'. In my work for
In my personal opinion: you are barking at the wrong tree. It's your
freedom to create a list of whatever you like
The problem is compounded by the fact each BL company is racing it's way
to the bottom, adding each others finds to their own lists. SpamHaus has
OVER 1 *BILLION* addresses listed.
I lost several relays (11) from OVH because DanTor recorded my relays,
then CBL recorded DanTor, then SpamHaus Zen
Hi all,
FYI: Yesterday I got the notice below from Leaseweb. I picked them
because Leaseweb is mentioned in the Good/Bad ISP
https://trac.torproject.org/projects/tor/wiki/doc/GoodBadISPs post.
Apparently a blacklist named SECTOOR added a whole IP block of Leaseweb
to block my Exit relay. Since
I got the same. Restricting the exit policy to 80/443 until Sectoor replies.
Tom
Jurre van Bergen schreef op 21/05/15 om 22:04:
Hi,
I got the same message yesterday, I asked leaseweb to put our exit
node(hviv103) in a dirty ip-block and asked sectoor for a
clarification on what happened. No
Hi,
I got the same message yesterday, I asked leaseweb to put our exit
node(hviv103) in a dirty ip-block and asked sectoor for a
clarification on what happened. No reply to date of any party.
For now, I have shutdown the server.
Sorry to hear :(
Best,
Jurre
On 05/21/2015 09:36 PM, blaatenator
13 matches
Mail list logo
