Title: which courier?
Post by: bg011ca on February 20, 2004, 09:01:17 AM
Post by: bg011ca on February 20, 2004, 09:01:17 AM
Hi there.
One question if I may, please.
While installing stuff, following instruction from web, I have noticed that Toaster is installing courier-imap-1.7.0, while last one for freBSD is version 2.2.0,1.
Do I go with Toaster or do I put one from Ports
Thanks
One question if I may, please.
While installing stuff, following instruction from web, I have noticed that Toaster is installing courier-imap-1.7.0, while last one for freBSD is version 2.2.0,1.
Do I go with Toaster or do I put one from Ports
Thanks
Title: which courier?
Post by: matt on February 20, 2004, 12:35:23 PM
Post by: matt on February 20, 2004, 12:35:23 PM
Stick with Ports until the broken authentication stuff is fixed in courier. Hint: you'll see the toaster use the newer version when that happens.
Matt
Matt
Title: which courier?
Post by: davidcl on February 20, 2004, 06:07:08 PM
Post by: davidcl on February 20, 2004, 06:07:08 PM
I'm not sure Matt said what he meant here. I think Matt means that authentication is broken in 2.2.0, so DON'T install it from ports, use the version installed by the toaster.
No?
No?
Title: which courier
Post by: matt on February 21, 2004, 05:59:39 PM
Post by: matt on February 21, 2004, 05:59:39 PM
Ahem, stick with the version the toaster installs by default. Yeah, what David said. 
the preauthvchkpw stuff has been broken on courier-imap for an eternity. I saw a bunch of the needed code fixes will be in the next "release" of courier-imap and when that happens, I'll test it on my servers and if it works well there, then, and only then, will it turn it loose on Mail::Toaster users.
PS: If you're clever and can do a little C hacking, it's easy to work around the problems in current releases of courier-imap. There is no other reason not to use current versions.
the preauthvchkpw stuff has been broken on courier-imap for an eternity. I saw a bunch of the needed code fixes will be in the next "release" of courier-imap and when that happens, I'll test it on my servers and if it works well there, then, and only then, will it turn it loose on Mail::Toaster users.
PS: If you're clever and can do a little C hacking, it's easy to work around the problems in current releases of courier-imap. There is no other reason not to use current versions.