Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Mainly Debian, some Fedora for the bleeding edge fix
Posts: 92
Original Poster
Rep:
I also tried Cyrus IMAP and Courier, but the version of squirrelmail that ships with suse is pre-configured to use uw-impad, which is was the one i tryed.
I gave that up and got Cyrus imap working, but then SuSe has mandatory ssl compiled in to the imap server (silly if it is only accesed by localhost for squirrelmail).
So i finally dumped Suse and got it working on FreeBSD instead with Cyrus IMAP and Sendmail.
This "security feature" with mandatory ssl, reeeaally smells like microsoft windows "security"... hurraahh for FREEBSD :-D
Suse 9.0 default IMAP installation does not let you autenticate in clear text. This clearly advertised when you check the IMAP setting. This solution uses ONLY the default setting of Suse 9.0.
The version of squirrelmail provided with Suse 9.0 support TLS but does not support the STARTTLS command but required a dedicated port for the TLS IMAP server. This is explained in the documentation.
THE SOLUTION.
1) Activate IMAP and IMAPS from YAST. You can also do from /etc/xinit.d/imap if you knwo what you do :-)
2) configure squirrelmail to find your IMAPS server without using the STARTTLS command which is not supported.
# su to rrot
# go on the squirrelmail default directory
cd /srv/www/htdocs/squirrelmail
#start the configure script.
./configure
# select Server setting menu
2
# select Update IMAP Settings
A
# select IMAP Port and provide your dedicated IMAPS port (default 993)
993
# Activate TLS option
7
# your IMAP sub menu look like this
# IMAP Settings
# --------------
# 4. IMAP Server : localhost
# 5. IMAP Port : 993
# 6. Authentication type : login
# 7. Secure IMAP (TLS) : true
# 8. Server software : other
# 9. Delimiter : detect
# save your configuration
S
# you can read email from squirrel
# If SMTP is running you can also send mails.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.