# [EMAIL PROTECTED] / 2003-07-13 09:39:53 -0400:
Roman Neuhauser wrote:
# [EMAIL PROTECTED] / 2003-07-01 10:25:29 -0400:
Since I've heard bad things about Courier's standards complicance, I
Care to share some details?
Do a google groups search for the keywords "courier imap compliance" or a search for "courier" where the author is "[EMAIL PROTECTED]" and you should get a handful of hits.
# [EMAIL PROTECTED] / 2003-07-13 09:55:10 -0400:
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&selm=Pine.LNX.4.50.0206050910320.6814-100000%40shiva0.cac.washington.edu
Well, MrSam's reaction to Crispin's complaints is somewhat
Actually, Sam has publicly stated numerous times that some of his code is non-compliant because he doesn't agree with the spec, and therefore won't change it. AFAIK, he has never taken part in any working group discussion on IMAP, which is where he should address these issues. Violating a spec after its been written, isn't the way to go about voicing your complaints.
unfortunate even if he has my sympathy. While we're pointing fingers: although I intended to switch to Cyrus (for unrelated reasons) I ended up installing another Courier-IMAPd: much easier, better documented, and I got to avoid SASL:
http://www.google.com/search?hl=en&ie=UTF-8&oe=UTF-8&q=sasl+vulnerability&btnG=Google+Search
Cyrus, and no other decent software package that I know of, still _depends_ on SASL v1.5.x. AFAIK, development of this version has stopped, although there have been bugfixes in CVS.
BTW, is anyone of you on [EMAIL PROTECTED]
http://marc.theaimsgroup.com/?t=105687915100001&r=1&w=2
Nope, I use Sendmail. I don't understand why people have such a hard time setting up SASL. If you use either sasldb2 or saslauthd, its trivial. If you use MySQL or LDAP (which I've never tried), it gets a little more complicated.
-- Kenneth Murchison Oceana Matrix Ltd. Software Engineer 21 Princeton Place 716-662-8973 x26 Orchard Park, NY 14127 --PGP Public Key-- http://www.oceana.com/~ken/ksm.pgp
