POP3 config

[mdeneen]

Hi! My setup has been working fine for several months now. I've run into a bit of a conundrum though. I have a single node server, running 4.5.6 OS on Centos4.5. I'm confused as to how zimbra utilizes ports.

Here are the relative entries extracted from zmprov gacf

zimbraImapBindPort: 7143
zimbraImapProxyBindPort: 143
zimbraImapSSLBindPort: 7993
zimbraImapSSLProxyBindPort: 993
zimbraPop3BindPort: 7110
zimbraPop3ProxyBindPort: 110
zimbraPop3SSLBindPort: 7995
zimbraPop3SSLProxyBindPort: 995

I am not using perdition. Our users access IMAP SSL on 993. Another subset of users use POP3s on 995.

I was hoping to allow port 110 and 995 for pop3, one plain-text and the other ssl. Do my ports seem backwards in the config above? It looks like it is setup for perdition, but really -- it's not!

tcp        0      0 :::993                      :::*                        LISTEN
tcp        0      0 :::995                      :::*                        LISTEN
tcp        0      0 :::143                      :::*                        LISTEN

#zmperditionctl status
imap4 is not running
imap4s is not running
pop3 is not running
pop3s is not running

So, my question is... is it possible to have both 110 and 995 work for pop3?

Mark

[mdeneen]

I was looking at the wrong config! I need to get it at the server level, not up at the global level.

Mark

[jamarty]

Hi -

4.5.6 on Centos4.5, no perdition, no firewall

Right now clients can connect to Pop3s on 995 from anywhere. I did what I think I need to enable clear-text Pop3 on 110.

Tue Jun 10 10:49:14 2008 main::getServerConfig::165 zimbraPop3BindOnStartup=yes
Tue Jun 10 10:49:14 2008 main::getServerConfig::165 zimbraPop3BindPort=110
Tue Jun 10 10:49:14 2008 main::getServerConfig::165 zimbraPop3CleartextLoginEnabled=yes
Tue Jun 10 10:49:14 2008 main::getServerConfig::165 zimbraPop3NumThreads=20
Tue Jun 10 10:49:14 2008 main::getServerConfig::165 zimbraPop3ProxyBindPort=110
Tue Jun 10 10:49:14 2008 main::getServerConfig::165 zimbraPop3SSLBindOnStartup=yes
Tue Jun 10 10:49:14 2008 main::getServerConfig::165 zimbraPop3SSLBindPort=995
Tue Jun 10 10:49:14 2008 main::getServerConfig::165 zimbraPop3SSLProxyBindPort=995
Tue Jun 10 10:49:14 2008 main::getServerConfig::165 zimbraPop3SSLServerEnabled=yes
Tue Jun 10 10:49:14 2008 main::getServerConfig::165 zimbraPop3ServerEnabled=yes

I can see from netstat that we're listening to both 110 and 995:

 netstat -an |grep "995\|110" |grep LISTEN
tcp        0      0 :::995                      :::*                        LISTEN
tcp        0      0 :::110                      :::*                        LISTEN

From the local machine I can telnet to both ports and get a connection, on port 110 I can type on POP commands like "USER so-and-so@mydomain.com" and it all works.

From any remote machine on the same or different LAN, I can telnet to port 995 and get a connection, but trying to connect to port 110 results in a "No route to host" error. Looks like a classic firewall issue, but I can't find a firewall process anywhere on the system. Nothing's getting logged in any log files. Any ideas what else to look for or what you think I'm most likely confused about here?

Thanks muchly,

Jamie