ISPs are asked to block yet another port

Its a sucky world sometimes. Perhaps Paul complained to
ATT/<other-unnamed-provider> with logs and such? :slight_smile:

oh yes. i tried *several* ways to get their attention. however, this
kind of activity is so common these days that a noc literally has no
choice but to focus their efforts on less common and more damaging
things than relayprobing. so i was not shocked that they did not
answer me.

> so if you're going to block tcp/25 SYNs on outbound, please make sure
> you block SYN/ACK's on input too, or else you just give the spammers a
> little more work to do instead of a lot more work to do.

Yup, this is in the works also... and yes, someone realized quickly enough
that the one-way filtering was dumb. oh well. live and learn!

that's good news, thanks for sharing it. any schedule for a fix :slight_smile: ??

> Its a sucky world sometimes. Perhaps Paul complained to
> ATT/<other-unnamed-provider> with logs and such? :slight_smile:

oh yes. i tried *several* ways to get their attention. however, this
kind of activity is so common these days that a noc literally has no
choice but to focus their efforts on less common and more damaging
things than relayprobing. so i was not shocked that they did not
answer me.

So, for <unnamed-provider-X> you have a Abuse Ticket number? Perhaps you
could send the one you think might apply to me off-list? :slight_smile:

> > so if you're going to block tcp/25 SYNs on outbound, please make sure
> > you block SYN/ACK's on input too, or else you just give the spammers a
> > little more work to do instead of a lot more work to do.
>
> Yup, this is in the works also... and yes, someone realized quickly enough
> that the one-way filtering was dumb. oh well. live and learn!

that's good news, thanks for sharing it. any schedule for a fix :slight_smile: ??

I do not know what the timeframe is :frowning: Sorry.