Hi, I'm completely new to imap. I'm running Suse 8.2 with KDE 3.2. I've installed imapd and have it running in xinetd, from the suse cd. I'm trying to get a mail client to connect, but have not been successful. I ran the openssl req..... as outlined in the suse help page and I think that worked fine. However I can't get a client to connect. I've tried both on internal IP address, and from external to IP domain. It advises that a connection could not be established. (I don't think this is relevant, but I've tried Outlook, Pegasus, and Thunderbird). I can telnet in from internal and external, and get OK [COMPATABILITY IMAP4REV1 STARTTLS LOGINDISABLED]..... From here I don't know what else to do or type. Any advice? Also, I don't know if the client should be configured to use direct SSL or StartTLS. Thanks for any advice. Jim Flanagan
Download that version of IMAP with no SSL support http://www.oxixares.com/rpms/SuSE_9.0/ ----- Original Message ----- From: "linuxjim" <linuxjim@jjfiii.com> To: <suse-linux-e@suse.com> Sent: Thursday, February 26, 2004 3:50 PM Subject: [SLE] help with IMAP
Hi,
I'm completely new to imap. I'm running Suse 8.2 with KDE 3.2. I've installed imapd and have it running in xinetd, from the suse cd.
I'm trying to get a mail client to connect, but have not been successful. I ran the openssl req..... as outlined in the suse help page and I think that worked fine. However I can't get a client to connect. I've tried both on internal IP address, and from external to IP domain. It advises that a connection could not be established. (I don't think this is relevant, but I've tried Outlook, Pegasus, and Thunderbird).
I can telnet in from internal and external, and get OK [COMPATABILITY IMAP4REV1 STARTTLS LOGINDISABLED].....
From here I don't know what else to do or type. Any advice?
Also, I don't know if the client should be configured to use direct SSL or StartTLS.
Thanks for any advice.
Jim Flanagan
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On 02/26/2004 09:50 PM, linuxjim wrote:
I'm completely new to imap. I'm running Suse 8.2 with KDE 3.2. I've installed imapd and have it running in xinetd, from the suse cd.
I'm trying to get a mail client to connect, but have not been successful. I ran the openssl req..... as outlined in the suse help page and I think that worked fine. However I can't get a client to connect.
Did you add a imaps section to /etc/xinetd/imap? Add the following if you already made the certificate as per the help page. service imaps { disable = yes socket_type = stream protocol = tcp wait = no user = root server = /usr/sbin/imapd flags = IPv4 }
I've tried both on internal IP address, and from external to IP domain. It advises that a connection could not be established.
Are you trying on port 143 (imap) or 993 (imaps)? You should check the box to use ssl, and it should use 993 port.
I can telnet in from internal and external, and get OK [COMPATABILITY IMAP4REV1 STARTTLS LOGINDISABLED].....
Are you telneting to the correct port for ssl imap?
From here I don't know what else to do or type. Any advice?
Check the above, and if that doesn't work, come back to the list. I have it working (8.2), so it does work (but had a problem with importing the certificate in OE. It would work but would never save the certificate. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
Hi Joe, On Thursday 26 February 2004 09:36, Joe Morris (NTM) wrote:
On 02/26/2004 09:50 PM, linuxjim wrote:
I'm completely new to imap. I'm running Suse 8.2 with KDE 3.2. I've installed imapd and have it running in xinetd, from the suse cd.
I'm trying to get a mail client to connect, but have not been successful. I ran the openssl req..... as outlined in the suse help page and I think that worked fine. However I can't get a client to connect.
Did you add a imaps section to /etc/xinetd/imap? Add the following if you already made the certificate as per the help page. service imaps { disable = yes socket_type = stream protocol = tcp wait = no user = root server = /usr/sbin/imapd flags = IPv4 }
All lines were already in there, except disable=yes. I have not added this. (Note, the help file says to make disable =no).
I've tried both on internal IP address, and from external to IP domain. It advises that a connection could not be established.
Are you trying on port 143 (imap) or 993 (imaps)? You should check the box to use ssl, and it should use 993 port.
I can telnet to port 143 and get the "OK" message, but when I try to telnet to port 993 I get "Connect Failed." I do this from local internal IP range on a different computer.
I can telnet in from internal and external, and get OK [COMPATABILITY IMAP4REV1 STARTTLS LOGINDISABLED].....
Are you telneting to the correct port for ssl imap?
From here I don't know what else to do or type. Any advice?
Check the above, and if that doesn't work, come back to the list. I have it working (8.2), so it does work (but had a problem with importing the certificate in OE. It would work but would never save the certificate.
-- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
Thanks for your help Joe. Jim Flanagan
On 02/27/2004 09:32 AM, linuxjim wrote:
All lines were already in there, except disable=yes. I have not added this. (Note, the help file says to make disable =no).
Yes, correct. I decided not to enable it here at home. I have it enabled at the office..
I can telnet to port 143 and get the "OK" message, but when I try to telnet to port 993 I get "Connect Failed." I do this from local internal IP range on a different computer.
Is tcp 993 open in your firewall? If you followed the help instructions, it should now be working. I assume you restarted xineted after enabling imaps. Does a tail -f /var/log/messages or mail give any helpful info? -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
On Friday 27 February 2004 04:39, Joe Morris (NTM) wrote:
On 02/27/2004 09:32 AM, linuxjim wrote:
All lines were already in there, except disable=yes. I have not added this. (Note, the help file says to make disable =no).
Yes, correct. I decided not to enable it here at home. I have it enabled at the office..
I can telnet to port 143 and get the "OK" message, but when I try to telnet to port 993 I get "Connect Failed." I do this from local internal IP range on a different computer.
Is tcp 993 open in your firewall? If you followed the help instructions, it should now be working. I assume you restarted xineted after enabling imaps. Does a tail -f /var/log/messages or mail give any helpful info?
993 is open, but for now I working on an internal IP net. imap seems to be listenting on 143, not 993. This line is in /var/log/mail: Feb 26 21:45:53 jjfiii imapd[2440]: Login disabled user=bob auth=bob host=[192.xxx.xxx.xxx] This is where I attempted to log in via telnet from a local machine (192.xxx.xxx.xxx) to user "bob". I set up two openssl certs. One for 192.xxx.xxx.xxx, and another for my IP domain, jjfiii.com. I cannot connect via either one. Thanks, Jim
-- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
On 02/29/2004 03:50 AM, linuxjim wrote:
993 is open, but for now I working on an internal IP net. imap seems to be listenting on 143, not 993.
Imap will listen on 143, imaps will listen on 993. Imap will look for plaintext password, Imaps will be using ssl encryption. The imap package by default (and as compiled by SuSE since 8.2) disables plaintext password (thus the login disabled message below), so since you have generated the ssl certificate, you should setup your client to use ssl and port 993 (should be automatic 993 if you configure it for imap with ssl support.
This line is in /var/log/mail: Feb 26 21:45:53 jjfiii imapd[2440]: Login disabled user=bob auth=bob host=[192.xxx.xxx.xxx]
Must have been to port 143, which is effective disabled unless you recompile, or I believe 9.0 has another option (I still use 8.2) to enable plaintext password (check the docs).
This is where I attempted to log in via telnet from a local machine (192.xxx.xxx.xxx) to user "bob".
I set up two openssl certs. One for 192.xxx.xxx.xxx, and another for my IP domain, jjfiii.com. I cannot connect via either one.
I checked mine, and I have a imapd.pem and a ipop3d.pem. The name is significant for it to find the correct certificate. Not certain it is necessary, but try generating a certificate called imapd.pem. HTH. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
On Saturday 28 February 2004 17:25, Joe Morris (NTM) wrote:
On 02/29/2004 03:50 AM, linuxjim wrote:
993 is open, but for now I working on an internal IP net. imap seems to be listenting on 143, not 993.
Imap will listen on 143, imaps will listen on 993. Imap will look for plaintext password, Imaps will be using ssl encryption. The imap package by default (and as compiled by SuSE since 8.2) disables plaintext password (thus the login disabled message below), so since you have generated the ssl certificate, you should setup your client to use ssl and port 993 (should be automatic 993 if you configure it for imap with ssl support.
Im not sure how to configure imapd, other than recompile it, which I also don't know how to do. I can telnet to it at 143, but not 993. But on port 143 I cannot connect. When I issued the cert, I did not configure it to for a particular port.
This line is in /var/log/mail: Feb 26 21:45:53 jjfiii imapd[2440]: Login disabled user=bob auth=bob host=[192.xxx.xxx.xxx]
Must have been to port 143, which is effective disabled unless you recompile, or I believe 9.0 has another option (I still use 8.2) to enable plaintext password (check the docs).
This is where I attempted to log in via telnet from a local machine (192.xxx.xxx.xxx) to user "bob".
I set up two openssl certs. One for 192.xxx.xxx.xxx, and another for my IP domain, jjfiii.com. I cannot connect via either one.
I checked mine, and I have a imapd.pem and a ipop3d.pem. The name is significant for it to find the correct certificate. Not certain it is necessary, but try generating a certificate called imapd.pem. HTH.
There are 3 imapd.pem files. 1. imapd.pem (which was already there) 2. imapd-192.xxx.xxx.xxx.pem which I issued 3. imapd-jjfiii.com.pem also which I issued, as per the Suse web instructions At this point I'm not sure it matters which port I connect to (143 or 993), as long as the cert is working OK. It seems to be listenting on 143 and not 993, why I don't know. I beleive you did say you have it working, so that gives me hope. Thanks for the help. Jim Flanagan
On 03/02/2004 09:13 AM, linuxjim wrote:
There are 3 imapd.pem files. 1. imapd.pem (which was already there) 2. imapd-192.xxx.xxx.xxx.pem which I issued 3. imapd-jjfiii.com.pem also which I issued, as per the Suse web instructions
This may cause problems. I believe imapd.pem is sufficient. I remember trying the -IP, etc., and decided by trial and errror imapd is best.
At this point I'm not sure it matters which port I connect to (143 or 993), as long as the cert is working OK.
It does matter, as 143 is imap protocol (no ssl), 993 is imaps (imap secure) protocol, which uses ssl. This should be running if you added and enabled imaps in /etc/xinetd/imap, and if it is running it will be using 993.
It seems to be listenting on 143 and not 993, why I don't know.
Are you sure it is enabled. Check Yast, Network services, Network services (inetd). Remember, imaps was not there originally, it had to be added. If it is indeed enabled, it will be listening on 993. If you can not connect, I would think your firewall is blocking 993. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
OK, I now have imaps running in xinetd. imap is not running. In order to accomplish this, I edited the /etc/xinetd.d/imap file as follows: under "service imap" I changed the first line to read disable=yes Then I added the following: ----------- # # impas - 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 } ------------- After restarting xinetd the imaps service is now running and the imap service is not. It appears to be listening on port 993. Regarding the previous certificates I issued, I deleted the two that had imapdxxx.yyy.xxx.yyy.pem. I then re-issued one for imapd.pem. Unfortunately still now when I try to connect, I still get an error. Perhaps I'm using the wrong user names. In the email (imap) client, I use only my user name and password as I would on my linux machine. Is this correct? Getting closer.... Thanks, Jim Flanagan On Monday 01 March 2004 20:06, Joe Morris (NTM) wrote:
On 03/02/2004 09:13 AM, linuxjim wrote:
There are 3 imapd.pem files. 1. imapd.pem (which was already there) 2. imapd-192.xxx.xxx.xxx.pem which I issued 3. imapd-jjfiii.com.pem also which I issued, as per the Suse web instructions
This may cause problems. I believe imapd.pem is sufficient. I remember trying the -IP, etc., and decide.> d by trial and errror imapd is best.
At this point I'm not sure it matters which port I connect to (143 or 993), as long as the cert is working OK.
It does matter, as 143 is imap protocol (no ssl), 993 is imaps (imap secure) protocol, which uses ssl. This should be running if you added and enabled imaps in /etc/xinetd/imap, and if it is running it will be using 993.
It seems to be listenting on 143 and not 993, why I don't know.
Are you sure it is enabled. Check Yast, Network services, Network services (inetd). Remember, imaps was not there originally, it had to be added. If it is indeed enabled, it will be listening on 993. If you can not connect, I would think your firewall is blocking 993.
-- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/07/2004 07:10 AM, linuxjim wrote: |Unfortunately still now when I try to connect, I still get an error. What is the error? |Perhaps I'm using the wrong user names. In the email (imap) client, I use only |my user name and password as I would on my linux machine. Is this correct? Yes. Imap directory is ~/<username>/Mail (fill in the username) When you make an IMAP account, you need to set up username, password, AND the directory to find the mail. You would also in this case tell your mail client to use ssl, which will change the port it checks from 143 to 993. - -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org iD8DBQFASmvAZ1XBlLwwaC0RAuu9AJ0eyc8ThNBQ+hjb+Nr/hHYwOvC2+gCdFgdc e4GE0PwNyzWsqHkBYpxLxUY= =Dm/m -----END PGP SIGNATURE-----
On Saturday 06 March 2004 18:24, Joe Morris (NTM) wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 03/07/2004 07:10 AM, linuxjim wrote: |Unfortunately still now when I try to connect, I still get an error.
What is the error?
|Perhaps I'm using the wrong user names. In the email (imap) client, I
use only
|my user name and password as I would on my linux machine. Is this correct?
Yes. Imap directory is ~/<username>/Mail (fill in the username) When you make an IMAP account, you need to set up username, password, AND the directory to find the mail. You would also in this case tell your mail client to use ssl, which will change the port it checks from 143 to 993.
Hi Joe, I guess I'm unclear on this. I had assumed that when imap is running, I can access my normal user mail folders thru imap, leaving folders where they are, e.g. "home/<username>/mail". Is this what you are saying? I did revise the client settings to reflect the change to port 993 and using SSL, but not StartTLS. Regarding the certs, keep in mind that I have postfix running on host.local. I set up a host name to listen on this comuters local IP address. That is why I originally issued 2 different certs, one for the domain.com name, and another for the local (internal) IP address. But, as stated earlier I deleted both and re-issued one for imapd.pem. Still not connecting. When I had imap running, I could telnet to it at port 143 and get a reply. Now that imaps is running when I telnet to port 993 I get only a blinking cursor. If I press any key, it exits back to the local telnet prompt, no visible reply from imapd. Jim Flanagan
- -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org
iD8DBQFASmvAZ1XBlLwwaC0RAuu9AJ0eyc8ThNBQ+hjb+Nr/hHYwOvC2+gCdFgdc e4GE0PwNyzWsqHkBYpxLxUY= =Dm/m -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/07/2004 11:40 AM, linuxjim wrote: |I guess I'm unclear on this. I had assumed that when imap is running, I can |access my normal user mail folders thru imap, leaving folders where they are, |e.g. "home/<username>/mail". Is this what you are saying? Yes, except Linux is case sensitive, so it would be Mail. ~<username>/Mail/ is the same (sorry I missed a slash and added one in the wrong place.) That is the setup on the IMAP account I have in my client. That way I can go into any users account in our server via imap just by changing the username, username element of the path, and password (usually to delete or forward email). |I did revise the client settings to reflect the change to port 993 and using |SSL, but not StartTLS. That should be correct. |Regarding the certs, keep in mind that I have postfix running on host.local. As far as imapd is concerned, postfix is not part of the equation. |I set up a host name to listen on this comuters local IP address. That is why I |originally issued 2 different certs, one for the domain.com name, and another |for the local (internal) IP address. But, as stated earlier I deleted both |and re-issued one for imapd.pem. Still not connecting. What are you putting in as the server name. Unless you run a local DNS, I would suggest just using the IP, i.e. 192.168.1.1 |When I had imap running, I could telnet to it at port 143 and get a reply. Now |that imaps is running when I telnet to port 993 I get only a blinking cursor. |If I press any key, it exits back to the local telnet prompt, no visible |reply from imapd. What happens if you ssh? My guess is telnet does not use ssl and therefore will not work. I don't really know, as I just use a mail client. It will ask you to accept the certificate (because it is self-signed and not automatically trusted, i.e. not issued by a known and trusted Certificate Authority), which since I trust it I accept it permanently. It will then work without asking again. What mail client have you tried? - -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org iD8DBQFASqh5Z1XBlLwwaC0RAu0HAJ4taHzUbVUj5Vkj0g6pTDuUrv5fOACfbM7b o2Kx5thIjSEyJpk5F8BhCEc= =RZPe -----END PGP SIGNATURE-----
On Saturday 06 March 2004 22:43, Joe Morris (NTM) wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 03/07/2004 11:40 AM, linuxjim wrote: |I guess I'm unclear on this. I had assumed that when imap is running, I
can
|access my normal user mail folders thru imap, leaving folders where
they are,
|e.g. "home/<username>/mail". Is this what you are saying?
Yes, except Linux is case sensitive, so it would be Mail. ~<username>/Mail/ is the same (sorry I missed a slash and added one in the wrong place.) That is the setup on the IMAP account I have in my client. That way I can go into any users account in our server via imap just by changing the username, username element of the path, and password (usually to delete or forward email).
|I did revise the client settings to reflect the change to port 993 and
using
|SSL, but not StartTLS.
That should be correct.
|Regarding the certs, keep in mind that I have postfix running on
host.local.
As far as imapd is concerned, postfix is not part of the equation.
|I set up a host name to listen on this comuters local IP address. That
is why I
|originally issued 2 different certs, one for the domain.com name, and
another
|for the local (internal) IP address. But, as stated earlier I deleted both |and re-issued one for imapd.pem. Still not connecting.
What are you putting in as the server name. Unless you run a local DNS, I would suggest just using the IP, i.e. 192.168.1.1
|When I had imap running, I could telnet to it at port 143 and get a
reply. Now
|that imaps is running when I telnet to port 993 I get only a blinking
cursor.
|If I press any key, it exits back to the local telnet prompt, no visible |reply from imapd.
What happens if you ssh? My guess is telnet does not use ssl and therefore will not work. I don't really know, as I just use a mail client. It will ask you to accept the certificate (because it is self-signed and not automatically trusted, i.e. not issued by a known and trusted Certificate Authority), which since I trust it I accept it permanently. It will then work without asking again. What mail client have you tried?
I am using Pegasus mail trying to connect from a local XP box. All it advises is that connection fails, no other message or info. Using Putty from the same machine, I can ssh to port 22 and log in, no problem. But when I try to connect to port 993 I get a message that session was terminated by remote host. Not much other info to go on. Jim Flanagan
- -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org
iD8DBQFASqh5Z1XBlLwwaC0RAu0HAJ4taHzUbVUj5Vkj0g6pTDuUrv5fOACfbM7b o2Kx5thIjSEyJpk5F8BhCEc= =RZPe -----END PGP SIGNATURE-----
On Saturday 06 March 2004 22:43, Joe Morris (NTM) wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 03/07/2004 11:40 AM, linuxjim wrote: |I guess I'm unclear on this. I had assumed that when imap is running, I
can
|access my normal user mail folders thru imap, leaving folders where
they are,
|e.g. "home/<username>/mail". Is this what you are saying?
Yes, except Linux is case sensitive, so it would be Mail. ~<username>/Mail/ is the same (sorry I missed a slash and added one in the wrong place.) That is the setup on the IMAP account I have in my client. That way I can go into any users account in our server via imap just by changing the username, username element of the path, and password (usually to delete or forward email).
|I did revise the client settings to reflect the change to port 993 and
usinghttp://www.catb.org/~esr/
|SSL, but not StartTLS.
That should be correct.
|Regarding the certs, keep in mind that I have postfix running on
host.local.
As far as imapd is concerned, postfix is not part of the equation.
|I set up a host name to listen on this comuters local IP address. That
is why Ihttp://www.catb.org/~esr/
|originally issued 2 different certs, one for the domain.com name, and
another
|for the local (internal) IP address. But, as stated earlier I deleted both |and re-issued one for imapd.pem. Still not connecting.
What are you putting in as the server name. Unless you run a local DNS, I would suggest just using the IP, i.e. 192.168.1.1
|When I had imap running, I could telnet to it at port 143 and get a
reply. Now
|that imaps is running when I telnet to port 993 I get only a blinking
cursor.
|If I press any key, it exits back to the local telnet prompt, no visible |reply from imapd.
What happens if you ssh? My guess is telnet does not use ssl and therefore will not work. I don't really know, as I just use a mail client. It will ask you to accept the certificate (because it is self-signed and not automatically trusted, i.e. not issued by a known and trusted Certificate Authority), which since I trust it I accept it permanently. It will then work without asking again. What mail client have you tried?
I tried connecting from another 8.2 box using Kmail. On setting up receive, I pressed Check what the server supports, and got the message "Could not connect to server xxx.xxx.xxx.xxx".
- -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org
iD8DBQFASqh5Z1XBlLwwaC0RAu0HAJ4taHzUbVUj5Vkj0g6pTDuUrv5fOACfbM7b o2Kx5thIjSEyJpk5F8BhCEc= =RZPe -----END PGP SIGNATURE-----
On Saturday 06 March 2004 22:43, Joe Morris (NTM) wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 03/07/2004 11:40 AM, linuxjim wrote: |I guess I'm unclear on this. I had assumed that when imap is running, I
can
|access my normal user mail folders thru imap, leaving folders where
they are,
|e.g. "home/<username>/mail". Is this what you are saying?
Hi again Joe, I'm still tryng to connect using Pegasus mail on an XP box. Inside a firewall so that is not a problem. I have tried using security set at SSL, and StartTLS, neither work. There is a setting in Pegasus that allows it to ignore certificates, but that does not work either. I tried taking out the line in /etc/xinetd.d/imap that reads "server_args= -s", but no change there either. Any more suggestions are most welcome. Many thanks, Jim Flanagan
On 03/08/2004 10:32 PM, linuxjim wrote:
I'm still tryng to connect using Pegasus mail on an XP box. Inside a firewall so that is not a problem.
Are you saying there is no firewall between you and the imap server? The XP firewall is not on, nor a firewall on the Linux box running imaps? Have you tried ethereal to watch the traffic to get an idea of what it is doing?
I have tried using security set at SSL, and StartTLS, neither work.
I believe SSL is the correct setting.
There is a setting in Pegasus that allows it to ignore certificates, but that does not work either.
Is it possibly a Pegasus mail problem. Can you try Outlook Express, since it is a Windows box, or Mozilla/Netscape?
I tried taking out the line in /etc/xinetd.d/imap that reads "server_args= -s", but no change there either.
I would leave all the lines in there. Verify that either Outlook Express or Mozilla or Netscape exhibit the same behaviour. It may just be your mail client's ssl implementation. For me, Netscape worked flawlessly, OE worked but would not save the certificate permanently, so it was an iritation to always accept everytime. Never could get around that. Other than try another client, or try using ethereal to capture the session to examine what is happening, I don't know what else to suggest. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
Hi again Joe, Still plugging, see below... On Monday 08 March 2004 09:35, Joe Morris (NTM) wrote:
On 03/08/2004 10:32 PM, linuxjim wrote:
I'm still tryng to connect using Pegasus mail on an XP box. Inside a firewall so that is not a problem.
Are you saying there is no firewall between you and the imap server? The XP firewall is not on, nor a firewall on the Linux box running imaps? Have you tried ethereal to watch the traffic to get an idea of what it is doing?
I've tried "inside" my firewall/router, and "outside" from another location. There is no firewall running between my linux box and the XP box. I have a little nat router running DHCP. Samba works between the two. I can telnet and ssh from XP to Suse, and log on in either.
I have tried using security set at SSL, and StartTLS, neither work.
I believe SSL is the correct setting.
There is a setting in Pegasus that allows it to ignore certificates, but that does not work either.
Is it possibly a Pegasus mail problem. Can you try Outlook Express, since it is a Windows box, or Mozilla/Netscape?
Today I tried Outlook (not express) and the lateset Thunderbird 0.5. Both clients report "unable to connet to the server". Both are set up using SSL on port 993. Thunderbird had a setting for "use secure connection (SSL)" and "use secure authentication". I've tried both. No change.
I tried taking out the line in /etc/xinetd.d/imap that reads "server_args= -s", but no change there either.
I would leave all the lines in there. Verify that either Outlook Express or Mozilla or Netscape exhibit the same behaviour. It may just be your mail client's ssl implementation. For me, Netscape worked flawlessly, OE worked but would not save the certificate permanently, so it was an iritation to always accept everytime. Never could get around that. Other than try another client, or try using ethereal to capture the session to examine what is happening, I don't know what else to suggest.
I'm not familiar with ethereal, but will give it a try. Thanks again, Jim Flanagan
On Monday 08 March 2004 09:35, Joe Morris (NTM) wrote:
On 03/08/2004 10:32 PM, linuxjim wrote:
I'm still tryng to connect using Pegasus mail on an XP box. Inside a firewall so that is not a problem.
--------------- Joe, I sent you a short ethereal file off list. Jim
participants (3)
-
Joe Morris (NTM) -
John -
linuxjim