| Hi Guys if you block port 25 no mail will come in:). And for port 143 as long as you encrypt password you should be ok pop use pop3s.
My 2 cents. Inviato da iPhone
Thanks, so you're not disabling 110 and 143, you're controlling
access via firewall rules. Blocking anything except things like
web access on the local machine, or if it's a corporate server on
the inside, allowing those. My server doesn't have any "internal"
users, so I could block everything except localhost 127.0.0.1.
And port 25 also isn't disabled, but it does that negotiation
automatically? I guess I wasn't aware of that, but that's great.
Thanks for that info.
Gary
Not quite what you say - removed
But
- On public networks my servers block 110 and 143
- This is pretty common practice I think
- I don’t think you would have any issue if you disabled
- SMTP initially negotiates unencrypted but upgrades to TLS
Has anyone removed all the unencrypted ports on your
server?
I still have a bunch of people logging in with pop3,
but I'm trying to get users to change those. And port 25
is still configured on my server. I'm not sure how much
use that has.
I would like to get everyone off these ports and
completely disable them on my server. Not sure about port
25, whether that would cause a problem with server-server
communications, I need to do some checking to see how much
that is used.
Just curious if anyone else has done this or tried it
and had problems. And if there are any additional gotchas
or things you need to configure if you disable these.
Thanks, Gary
--
---------------------------------------------------------------------
To unsubscribe, e-mail:
[email protected]
For additional commands, e-mail:
[email protected]
|
