Debian, Postfix, Courier-IMAP -> 0x800CCC0E error in Outlook

Discussion in 'Server Operation' started by Cojones, Jun 25, 2009.

  1. Cojones

    Cojones New Member

    Hello,

    I'm running a Debian server (postfix, courier-imap, courier-pop) with several domains and email addresses. If I use POP3 everything's just fine but whenever I try to use IMAP I get following error:
    Task 'Synchronizing subscribed folders for [email address].' reported error (0x800CCC0E) : 'Outlook cannot synchronize subscribed folders for [email address]. Error: Cannot connect to the server. If you continue to receive this message, contact your server administrator or Internet service provider (ISP).'

    But the problem is that it works at times but 3/4 times it doesn't. Does anyone know what the problem could be?

    Thank you
     
  2. falko

    falko Super Moderator ISPConfig Developer

    What's the output of
    Code:
    netstat -tap
    ? Any errors in your mail log?
     
  3. Cojones

    Cojones New Member

    Couldn't find any suspicious entries in my mail log.

    netstat seems pretty ok as well:
    Code:
    Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
    tcp        0      0 server8.local:8000      *:*                     LISTEN     11775/ruby
    tcp        0      0 server8.local:8001      *:*                     LISTEN     11778/ruby
    tcp        0      0 *:32769                 *:*                     LISTEN     1203/rpc.statd
    tcp        0      0 server8.local:8200      *:*                     LISTEN     12024/ruby
    tcp        0      0 server8.local:10024     *:*                     LISTEN     828/amavisd (master
    tcp        0      0 server8.local:8201      *:*                     LISTEN     12027/ruby
    tcp        0      0 server8.local:mysql     *:*                     LISTEN     1034/mysqld
    tcp        0      0 *:pop3                  *:*                     LISTEN     2052/couriertcpd
    tcp        0      0 *:imap2                 *:*                     LISTEN     2045/couriertcpd
    tcp        0      0 server8.local:spamd     *:*                     LISTEN     839/spamd.pid
    tcp        0      0 *:sunrpc                *:*                     LISTEN     583/portmap
    tcp        0      0 *:www                   *:*                     LISTEN     11048/apache2
    tcp        0      0 *:auth                  *:*                     LISTEN     1096/inetd
    tcp        0      0 server8.local:9876      *:*                     LISTEN     1315/vhcs2_daemon
    tcp        0      0 server8:domain          *:*                     LISTEN     15699/named
    tcp        0      0 server8.local:domain    *:*                     LISTEN     15699/named
    tcp        0      0 *:ftp                   *:*                     LISTEN     1235/proftpd: (acce
    tcp        0      0 *:ssh                   *:*                     LISTEN     1189/sshd
    tcp        0      0 *:smtp                  *:*                     LISTEN     15767/master
    tcp        0      0 server8.local:953       *:*                     LISTEN     15699/named
    tcp        0      0 *:https                 *:*                     LISTEN     11048/apache2
    
     
  4. falko

    falko Super Moderator ISPConfig Developer

    Is there maybe a firewall blocking access to port 143 (IMAP)? What's the output of
    Code:
    iptables -L
    ?
     
  5. Cojones

    Cojones New Member

    Wouldn't it be not working at all if it was blocked? Well, it's not:
    Code:
    Chain INPUT (policy ACCEPT)
    target     prot opt source               destination
               tcp  --  anywhere             anywhere            tcp dpt:smtp
               tcp  --  anywhere             anywhere            tcp dpt:imap2
               tcp  --  anywhere             anywhere            tcp dpt:pop3
               tcp  --  anywhere             anywhere            tcp dpt:www
               0    --  anywhere             anywhere
    
    Chain FORWARD (policy ACCEPT)
    target     prot opt source               destination
    
    Chain OUTPUT (policy ACCEPT)
    target     prot opt source               destination
               tcp  --  anywhere             anywhere            tcp spt:smtp
               tcp  --  anywhere             anywhere            tcp spt:imap2
               tcp  --  anywhere             anywhere            tcp spt:pop3
               tcp  --  anywhere             anywhere            tcp spt:www
               0    --  anywhere             anywhere
    
     
  6. falko

    falko Super Moderator ISPConfig Developer

    Are there any IMAP records at all in your mail log?
     
  7. Cojones

    Cojones New Member

    Yes:
    Code:
    Jun 28 06:39:22 myserver couriertcpd: LOGIN: ip=[::ffff:XX.XX.XX.XX], command=LOGIN
    Jun 28 06:39:22 myserver  couriertcpd: LOGIN: ip=[::ffff:XX.XX.XX.XX], username=[email protected]
    Jun 28 06:39:22 myserver  couriertcpd: LOGIN, user=[email protected], ip=[::ffff:XX.XX.XX.XX], protocol=IMAP
    
     
  8. falko

    falko Super Moderator ISPConfig Developer

    I'm sorry, but I don't know what's wrong... :(
     
  9. Cojones

    Cojones New Member

    Thanks anyways. Maybe someone else?
     
  10. Cojones

    Cojones New Member

    No one? :(
     
  11. jamiehook01

    jamiehook01 New Member

    Did you resolve this?

    Hello,

    Did you resolve this after as I am having exactly the same problem?

    Cheers,

    Jamie
     
  12. Cojones

    Cojones New Member

    Yes,
    I had to increase -maxperip parameter for the couriertcpd:
    root 2617 0.0 0.2 1940 524 ? S Feb16 0:32 /usr/sbin/couriertcpd -address=0 -maxprocs=40 -maxperip=20 -nodnslookup -noidentlookup 143 /usr/lib/courier/courier/imaplogin /usr/bin/imapd Maildi...

    That did the trick.
     
  13. carlosinfl

    carlosinfl New Member

    I use Dovecot for IMAP but does your IMAP server have a config file you can post? That may point to some clues.
     

Share This Page