I'm trying to get the Washington IMAP server going on SuSE 9.0, but don't seem to be able to log in. I have it enabled in the /etc/xinet.d/imap and nmap shows port 143 open. However, whenever I try to connect with a mail program, login is refused. Using telnet to port 143 returns: "Escape character is '^]'. * OK [CAPABILITY IMAP4REV1 LOGIN-REFERRALS STARTTLS LOGINDISABLED] linux.home IMAP4rev1 2003.338 at Sun, 27 Jun 2004 17:25:29 -0400 (EDT)" Any ideas? tnx jk
On Sunday 27 June 2004 4:54 pm, james.knott@rogers.com wrote:
I'm trying to get the Washington IMAP server going on SuSE 9.0, but don't seem to be able to log in. I have it enabled in the /etc/xinet.d/imap and nmap shows port 143 open. However, whenever I try to connect with a mail program, login is refused. Using telnet to port 143 returns:
"Escape character is '^]'. * OK [CAPABILITY IMAP4REV1 LOGIN-REFERRALS STARTTLS LOGINDISABLED] linux.home IMAP4rev1 2003.338 at Sun, 27 Jun 2004 17:25:29 -0400 (EDT)"
Any ideas?
tnx jk I went thru all of that. Suse compiled the imapd to connect only securely thru ssl. It's not that difficult, once you know what you are doing. You do have to edit some config files.
Namely, Log in as root and edit the /etc/xinetd.d/imap file, and add a stanza like so: # # imaps - SSL-encrypted imap mail daemon # service imaps { disable = no socket_type = stream protocol = tcp wait = no user = root server = /usr/sbin/imapd server_args = -s flags = IPv4 } Make sure it says "imaps", not "imap". It will listen for secure imap connections on port 993. Make sure to configure your client to use ssl on port 993, but not Star TLS. Make sure your firewall passed 993 too. Next you have to issue a certificate. As root open a terminal program. cd to /etc/ssl/certs. Run the following command: openssl req -new -x509 -nodes -out imapd.pem -keyout imapd.pem -days 365 When you connect, some clients complain that the cert is not trustworthy, or known. You issued it so don't worry. Click on. You can find good info on imap and more at David Krider's site http://www.davidkrider.com/suse_8.2.php#imap Clear info on issuing certs on Suse at http://portal.suse.com/sdb/en/2003/05/imap_ssl.html That should get you going. (As a side note, not to discourage you, but I'm a bit disappointed with imap in this way. Unless I'm missing something, uw imap only shows mail in the /var/spool/mail dirs. I haven't fouund a good mix between that and Kmail which brings mail from there to the home/user/mail folders in a different format which imapd wont see. Courier imap will see these folders, so now I need to set up a way to move mail from the spool to the home dir. But, if your not using kmail or anything locally you won't have this problem). Jim Flanagan
linuxjim wrote:
On Sunday 27 June 2004 4:54 pm, james.knott@rogers.com wrote:
I'm trying to get the Washington IMAP server going on SuSE 9.0, but don't seem to be able to log in. I have it enabled in the /etc/xinet.d/imap and nmap shows port 143 open. However, whenever I try to connect with a mail program, login is refused. Using telnet to port 143 returns:
"Escape character is '^]'. * OK [CAPABILITY IMAP4REV1 LOGIN-REFERRALS STARTTLS LOGINDISABLED] linux.home IMAP4rev1 2003.338 at Sun, 27 Jun 2004 17:25:29 -0400 (EDT)"
Any ideas?
tnx jk
I went thru all of that. Suse compiled the imapd to connect only securely thru ssl. It's not that difficult, once you know what you are doing. You do have to edit some config files.
Don't you just love it, when someone "protects" you from yourself. My imap server is used only on my local network or via vpn,so there's no one worry about.
Namely,
Log in as root and edit the /etc/xinetd.d/imap file, and add a stanza like so:
# # imaps - SSL-encrypted imap mail daemon # service imaps { disable = no socket_type = stream protocol = tcp wait = no user = root server = /usr/sbin/imapd server_args = -s flags = IPv4 }
Make sure it says "imaps", not "imap".
It will listen for secure imap connections on port 993. Make sure to configure your client to use ssl on port 993, but not Star TLS. Make sure your firewall passed 993 too.
Next you have to issue a certificate.
I have to give that a try, next time I install 9.0. My current system is Red Hat 7.3 and before installing SuSE, I do a full image backup, to another drive. That way, it's easy to do a full install, if (when?) necessary. It takes about an hour to backup or restore. After playing around with this all afternoon, I restored the RH system and will have to reinstall SuSE at some other time, before I can try this. Incidentally, I'd have preferred to use 9.1, but the mouse/KVM problem prevents that. tnx jk
participants (3)
-
James Knott
-
james.knott@rogers.com
-
linuxjim