Bug 468494 - Evolution IMAP login fail: only avialable under layer
Summary: Evolution IMAP login fail: only avialable under layer
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: rawhide
Hardware: i386
OS: Linux
medium
high
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-10-25 08:34 UTC by Lebenskuenstler
Modified: 2008-11-06 10:38 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-11-06 10:38:25 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 552583 0 None None None Never

Description Lebenskuenstler 2008-10-25 08:34:07 UTC
Description of problem:

If it try to read my emails from my imap-server with evolution, ev. keeps asking for the password. The first two times it is just the normal dialog for inputing the password, the 3rd time it says: imap command failed: login only available under layer and keeps asking for the password.

Curious (to me at least) is, that ev. did fetch folder structure but not any messages.

My imap requires SSL and I am using DIGEST-MD5 for encryption of my password. F9's (and earlier) Evolution worked with same settings fine. 



Version-Release number of selected component (if applicable):
2.24.1

How reproducible:
every time

Steps to Reproduce:
1. launch Evolution
2. Fetch Mails (F9)

Comment 1 Lebenskuenstler 2008-11-05 05:29:36 UTC
Thus, I can add, this is not Fedora-specific. Ubuntu 8.10 using also Evolution 2.24 the same annoying behaviour.

Comment 2 Milan Crha 2008-11-05 09:34:53 UTC
Isn't this the other instance of the upstream bug [1], which I caused some time ago?

[1] http://bugzilla.gnome.org/show_bug.cgi?id=552583

Comment 3 Lebenskuenstler 2008-11-06 10:21:09 UTC
Seems so. I am marking my report as a duplicate.

Comment 4 Milan Crha 2008-11-06 10:38:25 UTC
Thanks for the info. I do not think we can mark as duplicate of the other/upstream bug, thus closing this as upstream.


Note You need to log in before you can comment on or make changes to this bug.