Sorry, this is going to be a braindead question for most of you...
I don't (want to) use POP3, but I do have POP3S running. I start it with this:
/usr/lib/courier-imap/libexec/pop3d-ssl.rc start
But we recently discovered that telnetting to port 110 shows that Courier seems
to be listening there ("+OK Hello there."). Why would this happen?
There's the separate question of why port 110 is open on the firewall level
(/etc/sysconfig/iptables and service iptables status both do not show anything
with port 110 at all, so I thought it would be closed), but maybe I should ask
about that somewhere else.
Just at the application level, though, why is Courier listening on port 110 at
all? Does pop3d-ssl.rc start up the unencrypted service because of the shared
configuration files? Ouch. How can I stop this?
Thanks
PS - I checked another (very similar) machine I have similar setup for, and
interestingly, when I telnet to port 110, it responds, but it looks encrypted
(I
don't see plaintext). Why could this be different between the two systems with
the same software?
Sorry for the newb sysadmin questions
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Courier-imap mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
