Within mozilla-mail, I set up my email account so that it moves emails from /var/spool/mail to ~/mbox by using imapd. After the upgrade of SuSE-8.2, it suddenly does not work anymore. I enabled imapd from xinetd configuration. Therefore, it should work. I hate experimenting with pop3 becasuse it will erase all my email filter setup. That will be a disaster. Does anyone experience same trouble? Thanks. G. H. S.
On Thursday 01 May 2003 18:20 pm, ghugh Song wrote:
Within mozilla-mail, I set up my email account so that it moves emails from /var/spool/mail to ~/mbox by using imapd.
After the upgrade of SuSE-8.2, it suddenly does not work anymore. I enabled imapd from xinetd configuration. Therefore, it should work.
I hate experimenting with pop3 becasuse it will erase all my email filter setup. That will be a disaster.
Does anyone experience same trouble?
Two of us have reported that we can't get squirrelmail to work, and it is based on imap. The problem we see is that passwords are considered invalid. Not sure how related to imap that is since I don't normally use imap.
Thanks.
G. H. S.
-- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 05/01/03 21:43 + +----------------------------------------------------------------------------+ "Johnson's Corollary: computers have a reset button for a reason."
On Thu, 2003-05-01 at 20:45, Bruce Marshall wrote:
On Thursday 01 May 2003 18:20 pm, ghugh Song wrote:
Within mozilla-mail, I set up my email account so that it moves emails from /var/spool/mail to ~/mbox by using imapd.
After the upgrade of SuSE-8.2, it suddenly does not work anymore. I enabled imapd from xinetd configuration. Therefore, it should work.
I hate experimenting with pop3 becasuse it will erase all my email filter setup. That will be a disaster.
Does anyone experience same trouble?
Two of us have reported that we can't get squirrelmail to work, and it is based on imap. The problem we see is that passwords are considered invalid. Not sure how related to imap that is since I don't normally use imap.
I've just spent the last few hours of my life figuring out the problem. The problem is that the imapd has been compiled to NEVER use plaintext passwords. The easiest way around this is to create an /etc/cram-md5.pwd file with the following: <username><tab><password> That will let you in. Be sure to specify CRAM-MD5 in your email client. I have no idea what this will do to squirrelmail. I installed it, but I've been jerking around with this, and haven't seen if you can even change the option there. The bad part about this is that there's ANOTHER password database to fool with now. To me, this is unacceptable. Furthermore, I haven't even tried to get this set up for SSL. Fun. Regards, dk
On Thu, 2003-05-01 at 17:20, ghugh Song wrote:
After the upgrade of SuSE-8.2, it suddenly does not work anymore. I enabled imapd from xinetd configuration. Therefore, it should work.
Here's the final deal. (See my other mail for a workaround.) What you can do to get "normal" imaps operation running is... 1) Create a stanza in /etc/xinetd.d/imap 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 } 2) Create an SSL cert. You might already have one from before. It goes in /etc/ssl/certs, and needs to be named "imapd.pem". If you need a new one, you can use this to create it (from http://www.washington.edu/imap/documentation/SSLBUILD.html): openssl req -new -x509 -nodes -out imapd.pem -keyout imapd.pem -days 365 HTH, dk -- David "Dunkirk" Krider, http://www.davidkrider.com Acts 17:28, "For in Him we live, and move, and have our being." Linux: Will you use the power for good... or for AWESOME?
On Fri, 2 May 2003, David Krider wrote:
On Thu, 2003-05-01 at 17:20, ghugh Song wrote:
After the upgrade of SuSE-8.2, it suddenly does not work anymore. I enabled imapd from xinetd configuration. Therefore, it should work.
Here's the final deal. (See my other mail for a workaround.) What you can do to get "normal" imaps operation running is...
1) Create a stanza in /etc/xinetd.d/imap 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 }
2) Create an SSL cert. You might already have one from before. It goes in /etc/ssl/certs, and needs to be named "imapd.pem". If you need a new one, you can use this to create it (from http://www.washington.edu/imap/documentation/SSLBUILD.html):
openssl req -new -x509 -nodes -out imapd.pem -keyout imapd.pem -days 365
HTH, dk
Wow! Thank you very much. Certainly, that is beyond my understanding. Indeed, I was about to post another question regarding SSL and Enigmail. etc. It is getting more difficult to use Unix in general. About 15 years ago, everything was so simple. Only one gigabyte of hard disc space contained everything - the system and my data. I used to compile a number of tools myself. X11R3 and TeX were the most important things. The size increase is not really a problem. But all those security related configuration requirements really became too much for me. Firewall, Engimail, SSL, ssh, Spamassasin, Procmail, PAM, Security feature of samba, etc. etc. etc. Regards, G. Hugh Song
On Fri, 2 May 2003, David Krider wrote:
On Thu, 2003-05-01 at 17:20, ghugh Song wrote:
After the upgrade of SuSE-8.2, it suddenly does not work anymore. I enabled imapd from xinetd configuration. Therefore, it should work.
Here's the final deal. (See my other mail for a workaround.) What you can do to get "normal" imaps operation running is...
1) Create a stanza in /etc/xinetd.d/imap 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 }
In the update directory of SuSE's official ftp site, there exists the updated imap, i.e., imap-2002-45.i586.rpm The problem persists, still the same. It provides the /etc/xinetd.d/imap file, but content is different from what I see. It is like: # imap - imap mail daemon service imap { socket_type = stream protocol = tcp wait = no user = root server = /usr/sbin/imapd flags = IPv4 } First, one can notice it is "imap", not "imaps". What is the catch here? What about "server_args = -s"? Is it significant in any way?
2) Create an SSL cert. You might already have one from before. It goes in /etc/ssl/certs, and needs to be named "imapd.pem". If you need a new one, you can use this to create it (from http://www.washington.edu/imap/documentation/SSLBUILD.html):
openssl req -new -x509 -nodes -out imapd.pem -keyout imapd.pem -days 365
I cannot understand how SuSE overlooked this problem before they brought SuSE-8.2 to the world. The above information should exist in the release note at least. This will be the biggest blunder that SuSE-8.2 has brought just as the CUPS trouble that SuSE-8.1 brought when it was introduced. Thanks a lot.
HTH, dk
-- David "Dunkirk" Krider, http://www.davidkrider.com Acts 17:28, "For in Him we live, and move, and have our being." Linux: Will you use the power for good... or for AWESOME?
-- 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 Fri, 2 May 2003, David Krider wrote:
2) Create an SSL cert. You might already have one from before. It goes in /etc/ssl/certs, and needs to be named "imapd.pem". If you need a new one, you can use this to create it (from http://www.washington.edu/imap/documentation/SSLBUILD.html):
openssl req -new -x509 -nodes -out imapd.pem -keyout imapd.pem -days 365
HTH, dk
-- David "Dunkirk" Krider, http://www.davidkrider.com Acts 17:28, "For in Him we live, and move, and have our being." Linux: Will you use the power for good... or for AWESOME?
The openssl command above forced me to put my name, organization and my email addess. That is strange. The above procedure seems to assume that the machine is a personal workstation. That really does not make sense. What am I missing here? Thanks. G. Hugh Song
participants (3)
-
Bruce Marshall
-
David Krider
-
ghugh Song