Jaz wrote:
Gordon Messmer wrote:
Jaz wrote:
I still get 'Connection refused' -- even after a full reboot. Any
other ideas?
Is IMAPDSTART=YES in the imapd configuration file?
Yes, it's the last line. There are also these (among others):
...
Should I comment these last two, and add instead:
IMAP_CAPABILITY="$IMAP_CAPABILITY AUTH=PLAIN"
If your TLS settings are referencing "$IMAP_CAPABILITY", then that
setting is probably defined earlier in the file.
If it's configured to start (which it appears to be), I'd trace
execution of the rc script and check the listening ports afterward.
Start by running your rc script under "sh -x", like so:
/usr/local/libexec/imapd.rc stop
sh -x /usr/local/libexec/imapd.rc start > /tmp/imaprc.txt 2>&1
Then, as Malcolm suggested, check your ports. If you're using a GNU system:
netstat -tlnp | grep courier
Finally, if you don't see :143 listed, check your logs for errors. I'm
not sure how large the script output is going to be, so you can email it
directly to me if you don't see :143 listed as an open port.
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
