4 messages in net.sourceforge.lists.courier-users[courier-users] couriertcpd misery
FromSent OnAttachments
Masha NieuwenhuizenMar 28, 2001 5:21 pm 
Sam VarshavchikMar 28, 2001 5:36 pm 
Masha NieuwenhuizenMar 29, 2001 1:54 am 
Yuan P LiMar 29, 2001 2:47 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[courier-users] couriertcpd miseryActions...
From:Masha Nieuwenhuizen (mas@yahoo.com)
Date:Mar 28, 2001 5:21:28 pm
List:net.sourceforge.lists.courier-users

Good morning,

Although the package compiles quite nicely on my NetBSD/sparc (release 1.5), I just can't get the couriertcpd server to run.

It fails to start, giving the following error: root@drakkar:/usr/lib/courier-imap/libexec# ./imapd.rc start bind: Can't assign requested address ll_daemon_start: Resource temporarily unavailable

Courier-IMAP is only required as a complimentary IMAP/IMAP-SSL service towards the IMP webmail package. The POP3 daemons are not required. In fact, this functionality is currently running nicely using the default qmail daemons and some stunnel magic.

The problems seems to be nested in the $SSLADDRESS and $ADDRESS variables in the config files. Whenever set to a real (and correct) IP, the couriertcpd fails with the above error. If the default value of "0" is used, the daemons start without a glitch, although they refuse to respond to any connections, nor do they show up as listening sockets when looked at with netstat.

Effectively, it's a rather pointless 'solution'.

Changing the address fields in the config files to '130.161.58.123' or "130.161.58.123" or "drakkar.ricardis.tudelft.nl" doesn't (and probably shouldn't) do the trick.

I'm currently at a loss, so perhaps you can shed some light. To make that at least slightly easier, here are a few details on my configuration

qmail 1.03 vmailmgr 0.96 courier-imap 1.3.6 openssl 0.9.5a

Also, the collected data from the config files for the etc/imapd file.

##VERSION: $Id: imapd.dist.in,v 1.4 2001/03/16 03:37:41 mrsam Exp $ ADDRESS=131.165.58.123 -- the IP address used is a correct one, also in DNS records PORT=143 MAXDAEMONS=40 MAXPERIP=4 PIDFILE=/var/run/imapd.pid TCPDOPTS="-nodnslookup -noidentlookup" AUTHMODULES="authvmailmgr authcustom authcram authuserdb authpwd" IMAP_CAPABILITY="IMAP4rev1 CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT" IMAP_IDLE_TIMEOUT=60 IMAP_CAPABILITY_TLS="$IMAP_CAPABILITY AUTH=PLAIN" IMAP_DISABLETHREADSORT=0 IMAP_CHECK_ALL_FOLDERS=0 IMAP_OBSOLETE_CLIENT=0 IMAP_ULIMITD=65536 IMAP_USELOCKS=0 IMAP_EMPTYTRASH=7 IMAP_MOVE_EXPUNGE_TO_TRASH=0 IMAPDSTART=YES

The options for imapd-ssl hardly have changed from the distribution files and are sure to include the exact same, correct IP address.

The trouble I had with the couriertcpd package is rather odd, I suspect. I wouldn't mind trying tcpserver instead (most of the qmail services already run with it without any glitches). I can't find any pointers on how to correctly do so, however.

To make sure I did a fair check on connecting to the services, I disabled the hosts.allow and hosts.deny files on my machine. Also, it has no firewall enabled at the moment.

Netstat -a shows the pop3 and pop3s (qmail, not courier!) daemons to be working fine. Also, connecting to these daemons works fine.

Any ideas are greatly appreciated.

Thanks in advance,