> On 04/05/2021 22:27 Dan Egli <d...@newideatest.site> wrote: > > > On 5/4/2021 4:14 AM, Aki Tuomi wrote: > > Hi! > > To correctly enable/disable protocols, ensure they are (not) listed on > > protocols. > > > > doveconf protocols > > > > tells you this. > > > > Usually on debian based systems the easiest way is to uninstall > > `dovecot-pop3d` package. > > > > Aki > > > Aki, That's what I'm saying. The only place pop3 IS listed is in > doveconf protocols. I'm going to try settiing the ports to 0 and see if > that does the trick. > > And for those who keep mentioning the firewall, understand that I'm > beyond security paranoid. Simply blocking at the firewall is not enough. > I want to ensure that NO ONE is listening on that port, even if it's > just localhost. > > > -- > > Dan Egli > From my Test Server
Since people seem to be really adamant about the port solution, I just offer my own alternative. NOT LISTING pop3 in protocols, will disable, in dovecot, any pop3 listeners. If pop3, or imap, or whatever protocol, is listed in protocols, it will start those listeners. FWIW settings those ports to 0 will stop them from listening, it's just bit roundabout way to do it, when you could tell dovecot not to even load the whole protocol listeners. Aki
