Re: Imap Backend Propsal

> I did that for notls and novalidate-cert on the anchor. > But honestly I'm not sure! The docs for imap_open don't show notls as the default, > but apparently *several* people have commented there that it is something that is > commonly required. The problem that I see with setting it to be notls by default, > is I can't see a way to easily exlude it in those cases where it wouldn't or > shouldn't be added. it's been some time, but here's what I still remember about all of this. TLS and SSL are both possible, and different. Both MAY have the novalidate option. Some servers assume TLS by default(Rh8.0 among others), and thus need the notls option. Then again, my Debian IMAP server didn't like the notls option at all, while the POP3 did :( Once again, another big mess in the land that is called E-mail :( > My URI has *just* ssl being specified in the argument if the 's' is added to the > protocol (based on docs for imap_open), my question is, is that going to be a > problem cause I don't want the program to *say* 'ssl' when the user means 'tls'. > At this point it can be easily corrected by not specifing 's' on the protocol and > adding that or anything extra to the path via the anchor. How about adding an extra $options argument to the connection function, in which the user can specify the notls, validate-cert, and other options? IIRC there's quite a list available, so it'd be nice and an easy solution to just add this argument :) You can also make the URI itself alot easier to read, since you remove the connection `options' from it :) Cipri