I'm experiancing some stange problems with the pop3 mail server on an ISPConfig system. If I setup a pop3 account in something like outlook, and I hit "send and retrieve", I get the mail. But it I setup another email account in outlook for another address e.g [email protected] and hit "send and recieve" I get the following message: But what is wierd is that if I tell outlook to retrieve the mail of just the one user that just failed, I get the mail fine. I have multiple clients having the same problems on a variety of different domains. I've checked the /var/log/maillog fine and it logs this when I get the error in outlook: I can't seem to see what is causing this? I've changed the smtpd_tls_loglevel setting to 3 in the main.cf file but that doesn't seem to show any more information. Any ideas? Cheers, Benjamin
Are you using Norton AV on the PC and use TLS to connect with Outlook to your server? If yes, please have a look at the Norton site, where this is a known issue with Norton. Google for "Norton TLS"and you'll find an overwhelming amount of evidence
No I'm not using Norton AV, I'm using AVGFree. Also I'm just authenticating using normal usernames and passwords, no TLS that I know of. This is happending on multiple users machines. I tried disabling AVGFree but this didn't change anything. Cheers, Benjamin
Using Centos 4.4. Output or netstat is: Code: Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 *:mysql *:* LISTEN 2865/mysqld tcp 0 0 *:sunrpc *:* LISTEN 2543/portmap tcp 0 0 *:81 *:* LISTEN 18952/ispconfig_htt tcp 0 0 *:625 *:* LISTEN 2563/rpc.statd tcp 0 0 *:ftp *:* LISTEN 9317/proftpd: (acce tcp 0 0 isa.colo.mel.eventur:domain *:* LISTEN 15903/named tcp 0 0 localhost.localdomai:domain *:* LISTEN 15903/named tcp 0 0 localhost.localdomain:ipp *:* LISTEN 22393/cupsd tcp 0 0 localhost.localdom:postgres *:* LISTEN 4789/postgres tcp 0 0 *:smtp *:* LISTEN 9834/master tcp 0 0 localhost.localdomain:rndc *:* LISTEN 15903/named tcp 0 0 *:imaps *:* LISTEN 2892/dovecot tcp 0 0 *:pop3s *:* LISTEN 2892/dovecot tcp 0 0 *:pop3 *:* LISTEN 2892/dovecot tcp 0 0 *:imap *:* LISTEN 2892/dovecot tcp 0 0 *:http *:* LISTEN 19088/httpd tcp 0 0 *:ssh *:* LISTEN 2745/sshd tcp 0 0 localhost:rndc *:* LISTEN 15903/named tcp 0 0 *:https *:* LISTEN 19088/httpd tcp 0 0 isa.colo.mel.eventure.:http livebot-65-55-210-84.:45236 TIME_WAIT - tcp 0 0 isa.colo.mel.eventure.:pop3 dsl-220-235-94-146.vic:1197 TIME_WAIT - tcp 0 2368 isa.colo.mel.eventure.n:ssh dsl-220-235-94-146.vic:1196 ESTABLISHED 23930/1 Thanks, Benjamin
Yes, my /etc/selinux/config file reads: Code: SELINUX=disabled # SELINUXTYPE= type of policy in use. Possible values are: # targeted - Only targeted network daemons are protected. # strict - Full SELinux protection. SELINUXTYPE=targeted
