For the last five years I have been running a captive portal gateway I
developed at a number of airports to manage free wireless. There are more that
25K connection each day, and port 25 is blocked for every one of them.
Yes we get complaints, but not often, one every two or three months or so.
On 6/27/12, Götz Reinicke wrote:
> Long story short: I advised the use of port 587 two hours ago.
>
> FYI since than I had 169 outgoing connections to port 20 and 1 to 587. :)
Seriously, just force them. I got so tired of one particular app/mail
server that keep getting blacklisted because of laz
on 6/27/2012 7:26 AM Götz Reinicke spake the following:
> Am 27.06.12 16:08, schrieb Tilman Schmidt:
>> Am 27.06.2012 11:15, schrieb Götz Reinicke:
>>> Am 27.06.12 10:29, schrieb Fajar Priyanto:
>>
1. Many malware have their own smtp and can send spam directly.
To overcome this, block por
Götz Reinicke wrote:
> Am 27.06.12 16:08, schrieb Tilman Schmidt:
>> Am 27.06.2012 11:15, schrieb Götz Reinicke:
>>> Am 27.06.12 10:29, schrieb Fajar Priyanto:
>>
1. Many malware have their own smtp and can send spam directly.
To overcome this, block port tcp 25 on your gateway, and only
Am 27.06.12 16:08, schrieb Tilman Schmidt:
> Am 27.06.2012 11:15, schrieb Götz Reinicke:
>> Am 27.06.12 10:29, schrieb Fajar Priyanto:
>
>>> 1. Many malware have their own smtp and can send spam directly.
>>> To overcome this, block port tcp 25 on your gateway, and only allow
>>> your mailserver.
Am 27.06.12 16:08, schrieb Tilman Schmidt:
> Am 27.06.2012 11:15, schrieb Götz Reinicke:
>> Am 27.06.12 10:29, schrieb Fajar Priyanto:
>
>>> 1. Many malware have their own smtp and can send spam directly.
>>> To overcome this, block port tcp 25 on your gateway, and only allow
>>> your mailserver.
6 matches
Mail list logo
