• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Courier sorta dies on a relatively frequent basis

P

Paul Martin

Guest
Ever since the upgrade to v10, courier seems to die every half hour. Here's what it SHOULD look like when telnetting to port 143:

my vhosts # telnet localhost 143
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
* OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE ACL ACL2=UNION STARTTLS] Courier-IMAP ready. Copyright 1998-2004 Double Precision, Inc. See COPYING for distribution information.

Here's what it looks like whenever courier "dies":

my vhosts # telnet localhost 143
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.

The only thing that fixes it is bouncing the process. I have no idea why it's happening. Any help would be appreciated. Here's some technical info:

OS: CentOS x64 (fully patched)
Plesk: v10.0.1
Some stuff in /etc/courier-imap/imapd:
MAXDAEMONS=40
MAXPERIP=100
Frustration: pretty damned high
 
Try to use default config:

# cat /etc/courier-imap/imapd

ADDRESS=0

PORT=143

MAXDAEMONS=40

MAXPERIP=4

PIDFILE=/var/run/imapd.pid

TCPDOPTS="-nodnslookup -noidentlookup"

AUTHMODULES="authpsa"

AUTHMODULES_ORIG=""

DEBUG_LOGIN=0

IMAP_CAPABILITY="IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE"

IMAP_KEYWORDS=1

IMAP_CAPABILITY_ORIG="IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA AUTH=CRAM-MD5 AUTH=CRAM-SHA1 IDLE"

IMAP_IDLE_TIMEOUT=60

IMAP_CAPABILITY_TLS="$IMAP_CAPABILITY AUTH=PLAIN"

IMAP_CAPABILITY_TLS_ORIG="$IMAP_CAPABILITY_ORIG AUTH=PLAIN"

IMAP_DISABLETHREADSORT=0

IMAP_CHECK_ALL_FOLDERS=0

IMAP_OBSOLETE_CLIENT=0

IMAP_ULIMITD=65536

IMAP_USELOCKS=1

IMAP_ENHANCEDIDLE=0

IMAP_TRASHFOLDERNAME=Trash

IMAP_EMPTYTRASH=Trash:7

IMAP_MOVE_EXPUNGE_TO_TRASH=0

SENDMAIL=/usr/sbin/sendmail

HEADERFROM=X-IMAP-Sender

IMAPDSTART=YES

MAILDIRPATH=Maildir
POPLOCK_TIME=30
 
Igor: thanks for the quick reply. The only difference between the config you posted and mine is the "MAXPERIP" entry. Mine is set to 100, and yours is set to 4. I cranked it up because one of our clients is a business that has a lot of people, and they all use Thunderbird (known for opening/maintaining multiple IMAP connections). Could that be the cause of Courier having issues? If not, are there any other things I can try?
 
Using your configuration, Courier dies more often than it used to. I have an hourly cronjob to restart Courier, but it's insufficient, as Courier seems to die within roughly 20 mins. Advice?
 
This is a bump. I write "this is a bump" because the forums tell me that "bump" is too short.

So....bump.
 
Back
Top