Has anyone been able to get ipop3d to work correctly? I've been unable to get email from my new 8.2 server with the package imap installed. I was using qpopper on the old SuSE 7.1 server which this one is to replace. I'm using imap because someday I might wish to expand into imap-land. Cyrus looks too complicated, I don't have phantom users, everone needs a home dir and shell acount on this box, so I don't like the way Cyrus seems to require extra setup work for every user. Anyway, I get the following from evolution (the client, another SuSE 8.2 box) when it is configured for POP Host: mail.<mydomain> (this resolves properly) I'm on a local LAN, DNS is working. Username: <myusername> Use Secure connection (SSL): Never Authentication type: Password Error is this:-> Unable to connect to POP server mail.<mydomain> Error sending password: -ERR Unknown AUTHORIZATION state command. Kmail with the following settings: Encryption: None Authentication Method: Clear Text Error is this: -> Could not login to mail.<mydomain>. The server said: "Unknown AUTHORIZATION state command" In evolution, if I try "check for supported types" I get "Password" only as an option. If the use secure connection (SSL): box is set to Always then it says "Error while 'Checking Service': Could not connect to POP server mail.<mydomain> In Kmail if I do "Check What the Server Supports" then the only radio buttons left are: Encryption: None Use TLS for secure mail download AND Authentication Method Clear text Neither one works. Kmail says "Could not connect to host Your POP3 server does not support TLS. Disable TSL, if you want to connect without encryption." In evolution with SSL set to always, I get Error while 'Fedtcing Mail' Failed to connect to POP server mail.<mydomain> in secure mode: -ERR STLS failed: Server certificate not installed. But I followed the instructions here... http://sdb.suse.de/en/sdb/html/imap_ssl.html No change. (I'm also patched up with YOU). Help! -Mettius
On Fri, 2003-05-23 at 02:19, mettius wrote:
Has anyone been able to get ipop3d to work correctly? I've been unable to get email from my new 8.2 server with the package imap installed.
Yes
Error is this:-> Unable to connect to POP server mail.<mydomain> Error sending password: -ERR Unknown AUTHORIZATION state command.
The package that comes with SuSE does not use clear text passwords anymore. You will either need to recompile the package or you need to change a few things to get it to use CRAM-MD5. I asked this question on the list before. A savior on the list told me how. Google for "[SLE] pop3 doesn't work in 8.2" and in there is you anwser. -- Marshall "Nothing is impossible, we just do not have all the anwsers to make the impossible, possible."
No luck locating this article. I found one for imap on SDB, and I've done this but it doesn't work. Thanks, -Erich On Fri, 2003-05-23 at 05:43, Marshall Heartley wrote:
On Fri, 2003-05-23 at 02:19, mettius wrote:
Has anyone been able to get ipop3d to work correctly? I've been unable to get email from my new 8.2 server with the package imap installed.
Yes
Error is this:-> Unable to connect to POP server mail.<mydomain> Error sending password: -ERR Unknown AUTHORIZATION state command.
The package that comes with SuSE does not use clear text passwords anymore. You will either need to recompile the package or you need to change a few things to get it to use CRAM-MD5. I asked this question on the list before. A savior on the list told me how. Google for "[SLE] pop3 doesn't work in 8.2" and in there is you anwser.
-- Marshall
"Nothing is impossible, we just do not have all the anwsers to make the impossible, possible."
--
On Fri, 2003-05-23 at 11:24, mettius wrote:
No luck locating this article. I found one for imap on SDB, and I've done this but it doesn't work.
Here is the anwser that I got. Try this. Put the fole that is to be created on the emil server. Well, first, your email client must be able to do CRAM-MD5 passwords. I imagine yours does, but you'll probably have to specify the change. By default, the imap-2002 server is looking for a file /etc/cram-md5.pwd. All you need to do is put your usernames and passwords in this file like so: <username><tab><password> This is all in /usr/share/doc/packages/imap/md5.txt, but it might be a little overwhelming if you've never dealt with this before. Like that file says, the downside is that now you need to replicate your passwords in this file for everyone you want to give POP or IMAP access to. If it works for you, I do not get the credit for figuring it out. David Krider does. He was the one who anwsered my question. Good Luck -- Marshall "Nothing is impossible, we just do not have all the anwsers to make the impossible, possible."
Marshall PMFJI, but I'm having similar problems here and am not getting anywhere fast. I've managed to get the mail working fine from my various Linux box 's using the /etc/cram-mb5 file etc, but I simply can't get the M$ box's to work at all (I've one I need pop access for and the other IMAP). Don't suppose you can tell me what settings I should be using (do I need to have the secure ports being monitored for example (and if so, how)). I've tried all combinations of Secure Password Authentication and server requires SSL connection, but still no go I'm afraid. Thanks in advance. Peter Nunn. On Sat, 24 May 2003 01:48 am, Marshall Heartley wrote:
On Fri, 2003-05-23 at 11:24, mettius wrote:
No luck locating this article. I found one for imap on SDB, and I've done this but it doesn't work.
Here is the anwser that I got. Try this. Put the fole that is to be created on the emil server.
Well, first, your email client must be able to do CRAM-MD5 passwords. I imagine yours does, but you'll probably have to specify the change. By default, the imap-2002 server is looking for a file /etc/cram-md5.pwd. All you need to do is put your usernames and passwords in this file like so:
<username><tab><password>
This is all in /usr/share/doc/packages/imap/md5.txt, but it might be a little overwhelming if you've never dealt with this before. Like that file says, the downside is that now you need to replicate your passwords in this file for everyone you want to give POP or IMAP access to.
If it works for you, I do not get the credit for figuring it out. David Krider does. He was the one who anwsered my question.
Good Luck
-- Marshall
"Nothing is impossible, we just do not have all the anwsers to make the impossible, possible."
More information, I've managed to get the IMAP box connceted now, but the pop one still refuses. I've added the pop3s entry to xinetd but still no connection. Thanks. Peter. On Sat, 24 May 2003 02:44 pm, Peter Nunn wrote:
Marshall PMFJI, but I'm having similar problems here and am not getting anywhere fast.
I've managed to get the mail working fine from my various Linux box 's using the /etc/cram-mb5 file etc, but I simply can't get the M$ box's to work at all (I've one I need pop access for and the other IMAP).
Don't suppose you can tell me what settings I should be using (do I need to have the secure ports being monitored for example (and if so, how)).
I've tried all combinations of Secure Password Authentication and server requires SSL connection, but still no go I'm afraid.
Thanks in advance.
Peter Nunn.
On Sat, 24 May 2003 01:48 am, Marshall Heartley wrote:
On Fri, 2003-05-23 at 11:24, mettius wrote:
No luck locating this article. I found one for imap on SDB, and I've done this but it doesn't work.
Here is the anwser that I got. Try this. Put the fole that is to be created on the emil server.
Well, first, your email client must be able to do CRAM-MD5 passwords. I imagine yours does, but you'll probably have to specify the change. By default, the imap-2002 server is looking for a file /etc/cram-md5.pwd. All you need to do is put your usernames and passwords in this file like so:
<username><tab><password>
This is all in /usr/share/doc/packages/imap/md5.txt, but it might be a little overwhelming if you've never dealt with this before. Like that file says, the downside is that now you need to replicate your passwords in this file for everyone you want to give POP or IMAP access to.
If it works for you, I do not get the credit for figuring it out. David Krider does. He was the one who anwsered my question.
Good Luck
-- Marshall
"Nothing is impossible, we just do not have all the anwsers to make the impossible, possible."
On Sat, 2003-05-24 at 01:15, Peter Nunn wrote:
More information, I've managed to get the IMAP box connceted now, but the pop one still refuses. I've added the pop3s entry to xinetd but still no connection. What is the error message??? If it is the same that the other reader had, then you need to make sure that your M$ program does CRAM-MD5. It should be a setting that you set when configuring the email account. Give that a shot.
-- Marshall "Nothing is impossible, we just do not have all the anwsers to make the impossible, possible."
I've given up on trying to get POP working between my windows box's and my SuSE 8.2 server (IMAP works better anyway). However, I get the following annoying message on the machines each time they try and get mail from the server. The server you are connected to is using a security certificate that could not be verified. A certificate chain processed correctly, but terminated in a root certificate which is not trusted by the trust provider. Do you want to continue using this server? Now, while its not a problem to press yes each time, I'd rather not if I can. I've done some hunting on google and come up with lots of people having the same problem, but really only one possible answer (and that was to do with changing the .pem file into something else) but its in german and I really can't follow what its doing (and don't want to risk killing my working linux clients). Can someone please point me in the right direction here. Thanks again.. I hope I'll be up and running soon and can leave you all alone again. Peter Nunn.
Peter Nunn wrote:
I've given up on trying to get POP working between my windows box's and my SuSE 8.2 server (IMAP works better anyway).
However, I get the following annoying message on the machines each time they try and get mail from the server.
The server you are connected to is using a security certificate that could not be verified.
A certificate chain processed correctly, but terminated in a root certificate which is not trusted by the trust provider.
Do you want to continue using this server?
the new or current imapd is setup to work with imaps instead of imap. You can recompile the imapd and use the NO AUTH switch....or something like that. I don't recall exactly, but it is in the docs of imapd. I did that once....a while back.
Now, while its not a problem to press yes each time, I'd rather not if I can.
I've done some hunting on google and come up with lots of people having the same problem, but really only one possible answer (and that was to do with changing the .pem file into something else) but its in german and I really can't follow what its doing (and don't want to risk killing my working linux clients).
Can someone please point me in the right direction here.
Thanks again.. I hope I'll be up and running soon and can leave you all alone again.
Peter Nunn.
On 05/24/2003 01:15 PM, Peter Nunn wrote:
More information, I've managed to get the IMAP box connceted now, but the pop one still refuses. I've added the pop3s entry to xinetd but still no connection.
Did you generate a ipop3d ssl cert? The new imap/pop server WILL do plain text passwords IF the connection itself is encrypted, i.e. ssl. I have Windows using the pop server. You need to create the ipop3d.pem file (check and adapt from imap entry in sdb), and change your xinet.d to add the pop3s (which you said you did [enabled?]), then change your Windows clients to use ssl, which in Netscape (Windows) changes the port automatically to 995 instead of 110. If your firewall also protects from internal, you may need to open that port as well. The advantage (to me) of using the ssl versus /etc/cram-md5 file is it uses users linux usernames/passwords. For me, this is a help, and it encrypts the whole session, not just the password. 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 05/23/2003 02:19 PM, mettius wrote:
Has anyone been able to get ipop3d to work correctly?
Yes.
I've been unable to get email from my new 8.2 server with the package imap installed. I was using qpopper on the old SuSE 7.1 server which this one is to replace. I'm using imap because someday I might wish to expand into imap-land.
qpopper will work as is. the imap package will also, just do a search in the sdb for imapd. Basically, you need to create a SSL certificate, and add a pop3s entry in xinetd. You may also need to open port 995 on your firewall. You will also need to tell your clients to use ssl. It works well AND secure. :-) . You could also recompile, but you will lose some security. -- 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.
qpopper will work as is. the imap package will also, just do a search in the sdb for imapd. Basically, you need to create a SSL certificate, and add a pop3s entry in xinetd. You may also need to open port 995 on your firewall. You will also need to tell your clients to use ssl. It works well AND secure. :-) . You could also recompile, but you will lose some security.
I did this, but no luck. I added the following entry in /etc/xinetd.d/imap # # imap - pop3 mail daemon (pop3s) # service pop3s { disable = no socket_type = stream protocol = tcp wait = no user = root server = /usr/sbin/ipop3d flags = IPv4 } (I also restarted xinetd). I created two certificates per the imap article on the SDB, one for mail.<mydomain> and the other for mercury.<mydomain>. mail.<mydomain> is in my dns zone as such: mail CNAME mercury It resolves correctly for nslookup and ping. There is no firewall between the client and the server in this scenario. Any further suggestions? Thanks, -Erich
-- 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.
--
participants (5)
-
Joe Morris (NTM) -
Marshall Heartley -
mettius -
Oskar Teran -
Peter Nunn