Description of Problem:
Evolution doesn't seem to care for SSLv3 much. I'm guessing it's not library
related since libssl, sasl, etc. are used for other applications that don't seem
to have this problem.
If I force my POP server to accept only SSLv3, Evolution freaks and terminates
the connection while trying to POP. Oddly, it seems to make it through the SSL
wrapper but dies at Qpopper. Other mail clients don't seem to have this problem.
What makes it more odd is that if I change the settings to SSLv2, HUP the Inetd
process, try Evolution (which will work with v2 fine), and then switch it back
to v3 (HUP Inetd again)... Evolution works. And I used Netcat and Ethereal to
verify it was all SSLv3. And it continues to work...
Until I restart Evolution and have to do the dance again. So I changed me server
to not force SSLv3 but it'd be ideal to use SSLv3 or TLS instead of SSLv2.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Choose a SSLv3 forced POP server.
2. POP from it.
Unexpected end of connection. EOF, etc.
I expect it to pull my mail.
I haven't tried it with another POP server or IMAP. Since I don't have this
problem with other clients I'm not pointing at my server (yet).
Let me know what else you'll want/need. I didn't paste a bunch more here in case
something obvious pops out or it's a known issue. I didn't find anyting on
Evolution mailing lists to indicate as much. Which makes me think I should, just
in case, submit this over at Ximian too.
Evolution uses libnss3 from the mozilla project as opposed to openssl, which is
what is used by most projects out there. Do you get similar behavior from
Mozilla mail also exhibits the same behavior. Good call.
So is libssl/ssl3/sasl/etc. really requirements then? I guess they must be down
the chain somewhere. Anyhow.
So you're going to reassign this as a Mozilla(-nss) bug? Or I'm I entirely too
Yep, the openssl backend for evolution-mail was removed around 0.99 or so due to
licensing concerns, leaving only the libnss3 one.
Since this sounds more like a libnss3 bug than evolution itself, moving to mozilla.
Problem still exists with:
Just thought you'd want to know. Regards, -Ali