GNOME Bugzilla – Bug 554175
IMAP folders being called "mbox"
Last modified: 2009-12-31 04:32:46 UTC
Please describe the problem: I have several IMAP accounts. With one account however, the folders seem to be getting treated with the "mbox" prefix rather than the proper imap:user@server. To illustrate... I have a vFolder which I try to add folder from that given IMAP account. So I edit the properties of that vFolder... I click Add, choose the IMAP account's Inbox folder but what gets added is "mbox:INBOX". It seems whatever folders I try to add from this specific IMAP account, they are prefixed with "mbox:" not "imap:user@server/" like they should be. If I add a folder from a different IMAP account, it works just fine. Steps to reproduce: Probably not easily or this bug would be reported already. I don't think there are really any "steps" to reproducing it Actual results: Expected results: Does this happen every time? Other information:
I should add, this problem is experienced in other places where references to folders are made. For example, in the account preferences where you set the folder sent mail should go to, if I choose the Sent folder on this particular IMAP account I get simply "sent" and not imap:user@server/Sent, like I should.
Akhil, can you verify this?
(In reply to comment #2) > Akhil, can you verify this? Any luck? I'm available most any time to provide any assistance in debugging this situation.
Still no action on this bug and not fixed for the 2.24.1 release. Pity. This is somehow related to bug 554182. If I disable GSSAPI (not that that feature is working in 2.24 -- another regression) authentication then this considering of the IMAP mailbox as "mbox:" stops happening and it's referred to as it's proper imap:// url.
*** Bug 543626 has been marked as a duplicate of this bug. ***
Reporter of the bug 543626 had confirmed that it has been working fine in 2.26.x. Could you please try out in 2.26.x or later and report back, thanks.
Closing this bug report as no further information has been provided. Please feel free to reopen the bug if the problem still occurs with a newer version of GNOME 2.28.2 or later, thanks.