15 messages in net.sourceforge.lists.courier-usersRe: [courier-users] imapcopy / imapsy...
FromSent OnAttachments
JazNov 17, 2005 6:59 am 
Jay LeeNov 17, 2005 7:20 am 
JazNov 17, 2005 7:49 am 
JazNov 17, 2005 8:23 am 
Jay LeeNov 17, 2005 11:22 am 
JazNov 17, 2005 11:43 am 
Malcolm WeirNov 17, 2005 12:15 pm 
Gordon MessmerNov 17, 2005 2:15 pm 
JazNov 17, 2005 2:35 pm 
Gordon MessmerNov 17, 2005 2:53 pm 
Jerry AmundsonNov 17, 2005 3:00 pm 
JazNov 17, 2005 3:26 pm 
Gordon MessmerNov 18, 2005 11:13 am 
Arturo 'Buanzo' BusleimanNov 18, 2005 11:16 am 
JazNov 18, 2005 11:37 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:Re: [courier-users] imapcopy / imapsync help pleaseActions...
From:Jaz (jaz@intrusic.com)
Date:Nov 17, 2005 3:26:41 pm
List:net.sourceforge.lists.courier-users

Gordon Messmer 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.

I guess I should mention that if I wind up reconfiguring IMAP to allow non-TLS connections, then I need it to also allow TLS, because all the users are setup with either 'use TLS if available' or 'force TLS'

I've established that Courier is not listening on 143. The question is: How do I setup Courier to allow both 143 non-SSL/TLS (for imapcopy to work), and 993 TLS so that my users aren't left high and dry as I move a few people to another server.

Oh, and can anyone help me with imapsync config file? I can't seem to make it happy. (If I exclude '-s' then it doesn't do anything.) Can it sync these servers?

------------------------------- $ mailsync -s -d -v -f .mailsync courier-imap Only simulating Listing store "courier-imap" Opening {imap.mycompany.com/user=test/ssl/novalidate-cert/norsh} with options 66 [Trying IP address [NON-IP]] [Courier-IMAP ready. Copyright 1998-2001 Double Precision, Inc. See COPYING for distribution information.] Authorizing against {mail.mycompany.com/imap} Items in store "courier-imap":

{imap.mycompany.com:993/imap/ssl/novalidate-cert/readonly/user="test"}<no_mailbox>{imap.mycompany.com}INBOX.Sent, marked Delimiter for store "courier-imap" is '.' Using driver imap for store courier-imap Sent

------------------------------- $ cat .mailsync | grep -v ^# store courier-imap { server {imap.mycompany.com/user=test/ssl/novalidate-cert/norsh} ref {imap.mycompany.com} pat INBOX.* prefix INBOX. passwd secret }

------------------------------- Thanks all -- you sure are patient with me... -Jaz