> No, this not a `which is better' troll. > > Rather, I am installing both, trying to determine which is better for > our situation. > > From the point of view of current users and administrators, what should > I look for/at in each? Which are the biggest advantages of squirrelmail > over sqwebmail? What are the features in squirrelmail that you vastly > prefer over sqwebmail? If you point these out to me, then I can compare > them side-by-side, and make up my own mind. > > Clearly, both have advantages/disadvantages, pluses/minuses. During a > brief trial of each, by my lonesome, I am bound to miss something. > > What do you think?
just use http://www.inter7.com/sqwebmail.html and check if squirrelmail provides same feature. sqwebmail is minimal email client. It is written in C and accesses Maildirs directly. It provides: a) personal and global ldap address books b) pgp support when keyrings are stored under user privileges c) receipt on delivery support (if server allows it) d) spell checking support e) calendaring support if courier-pcp is used. f) maildrop filtering support g) multiple identities can be entered during email composition. squirrelmail is modular email client. It is written in php and accesses mailboxes through IMAP server. It provides: a) personal and global address books stored in csv, sql or ldap. b) pgp support when keyrings are stored under webserver privileges or on user's station (by third party plugin) c) receipt on delivery and receipt on read support. Receipt on delivery works only when server supports it. d) spell checking support e) calendaring support in own calendar format f) filtering support with own functions or external programs (there are at least three different plugins) g) multiple identities can be stored in user prefs. h) different themes controlled by end user. i) http://www.squirrelmail.org/plugins_category.php?category_id=all sqwebmail uses template based translations. Support of translation has to be added during program compilation. Program detects translation by browser language prefs. squirrelmail uses gettext based translations. New translation is added by editing one php script and adding appropriate gettext message files. User controls translation in interface preferences. sqwebmail before 3.6.2 used SUID based CGI scripts. From 3.6.2 it uses unprivileged CGI and special service accessed through unix socket. Before 3.6.2 it was possible to use this email client on older machines for occasional email checking. From 3.6.2 it is not that easy. squirrelmail needs cookie support in browser. Frames support is required for full interface operations. sqwebmail works in cookie less and frame less browsers. sqwebmail is a small email client that can be run on older machines. It is good when you only need to check your email sometimes and use other program for main email operations. squirrelmail is full featured behemoth that requires good machine. P.S. You shouldn't compare squirrelmail vs sqwebmail. These are two different programs. If you need all functions of email program, you don't use sqwebmail. If you need lightweight webmail program, you don't use squirrelmail. -- Tomas ------------------------------------------------------- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 -- 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