But I find cyrus-imap too limited in what I would like to do with email (many extensions) and so I'm looking into moving to using the University of Washington IMAP server.
Um, I think you got that backwards there..
So, I set up imap to work with the inetd. SuSE 8.2 ships with a version that is configured for imap-ssl protocol only, no imap.
Ugh. Ugh ugh UGH!
What am I missing? Versions?
squirrelmail 1.2.10
Squirrelmail supported SSL/TLS starting with 1.4.0.
And that brings me to another question. If I have a home-brew certificate that doesn't have a bonafide registered CA will squirrelmail still work?
Yes.
Why, oh why, did you get rid of Cyrus in favor of uw-imap??
Thanks to everyone who replied.
Apologies for my remarks which may have upset so many, but I have my reasons. Mostly it's a comprimise between time, function, and my patience.
I thought it might be that I am running a very old version of squirrelmail. I just got Suse about a month ago and have been trying to get things up and running ever since. Quite the change from Debian (squirrelmail 1.4.x),but that's another mailing list.
As for the comments concerning cyrus-imap: cyrus may work OK, but it has it's limitations for me. Here are mine, and they are limitations by choice:
First, I decided to not run procmail at all if I could avoid it. Everything else in the data stream is a daemon and I would have a severe impact if I did run procmail. This was a wish.
To add to this, I can't run procmail on a per user basis unless I give each user a login id with a home directory. This kind of negates the idea of cyrus giving you the ability to have accounts for email that cannot access the machines.
Second, the sieve filtering script has little documentation on how to get it working. I have been for the past week tweaking my sieve scripts trying to effectively filter mailing lists that can be captured in procmail in one line.
A specific problem is that I could not find anything on how to filter for the existence of a header, regardless of the value it contains.
For me, sieve is nearly crippled. For an ISP or Company, sieve is pretty cool. Better than Exchange.
Third, sieve cannot shell. I cannot write my own functions for handling email through STDIN piping. Again, this is by design and has it's very good reasons for doing so, but I needed more than this.
Given all of this, I was kind of staring at a problem that if I were to use procmail with cyrus-imap then I would need general user accounts for everyone anyways and then I would have to figure out how to read the email in a non-readable set of directories (own and operated by cyrus) on per user basis so I could deliver the email or filter it or whatever.
The only alternative I could see was to write a root procmail script and hope it worked for everyone via cyrus' "delivery -l" option.
Personally I wanted to try a maildir based imap server and these (cyrus-imap, uw-imap) are the only two that come with the disks. I tried to get dovecot running and will probably try it again. It seems to have more what I'm looking for.
I am pretty certain that if I were to dig at it long enough, I could get a lot more functionality out of my cyrus-imap installation, but I've been trying to get a working server on SuSE for a month now and I had uw-imap working on Debian in a day. I've been at this for 5 years now and didn't expect to spend this much time mucking around with a distro.
I'm not out to start a flame war, but I think SuSE 8.2 is a pretty lame distribution on the whole. Nice packaging, easy admin, busted rpms and stupid configurations.
I also think cyrus-imap is a pretty impressive imap server.
If there were more users than my family and a few friends I could consider it more viable.
It needs more documentation. The cyrus-imap mailing list agrees, but then they reminded me that this was a freebie from CMU and if I wanted documentation I could write it myself. Seeing as I had been using Cyrus for about a week at that time, I didn't see myself being very qualified for it.
Thank you very much for your replies. As I expected, Suse screwed up in their configuration. They secured uw-imap by removing imap authentication and then supplied a squirrelmail package that couldn't handle imap-ssl. They would have been far better off to just comment a restriction in xinetd for localhost-imap.
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ -- squirrelmail-users mailing list List Address: [EMAIL PROTECTED] List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995 List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
