Le mercredi 01 novembre 2006 à 17:46 +, bassslave a écrit :
> Sorry, my report was overhasty.
no problem, thank you for the comments on the issue
--
POP/TLS broken in evolution
https://launchpad.net/bugs/68798
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu
I imply the server would support tls, because I always used evolution
with pop/tls to receive the mails. As there was no notice that evolution
uses cleartext instead, there was no reason for me to doubt of the
server supports it.
But after asking the serverprovider, I found out that this is false.
marking the bug as reject then. What did you make your change your
opinion from the previous comment where you stated that it's supported
by the server and works with cleartext?
** Changed in: evolution (Ubuntu)
Status: Needs Info => Rejected
--
POP/TLS broken in evolution
https://launchp
Great. This report can be canceled.
It's not a bug, it's a feature;-)
--
POP/TLS broken in evolution
https://launchpad.net/bugs/68798
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
The http://www.gnome.org/projects/evolution/bugs.shtml page has hints
about debugging evolution. Running it with CAMEL_DEBUG=all should
provide useful informations on what the mailer is doing and the tlak to
the server
--
POP/TLS broken in evolution
https://launchpad.net/bugs/68798
--
desktop-b
SSL does not work. But I know that this is supported by the server.
Cleartext works.
How can I found out, if it only works in fallback-mode?
I haven't known about that before.
--
POP/TLS broken in evolution
https://launchpad.net/bugs/68798
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.
previous version of evolution used to do fallback on non-TLS mode if the
server was not supporting it, that might be why it worked. Does it work
if you pick an another authentification mode for that account?
** Changed in: evolution (Ubuntu)
Assignee: (unassigned) => Ubuntu Desktop Bugs
