Bug 3181 - Please add "Show IMAP server information" feature to Claws Mail
Summary: Please add "Show IMAP server information" feature to Claws Mail
Status: RESOLVED WONTFIX
Alias: None
Product: Claws Mail (GTK 2)
Classification: Unclassified
Component: Folders/IMAP (show other bugs)
Version: other
Hardware: All All
: P3 enhancement
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2014-05-25 21:43 UTC by nw9165-3201
Modified: 2014-05-27 12:50 UTC (History)
0 users

See Also:


Attachments

Description nw9165-3201 2014-05-25 21:43:25 UTC
DearClaws Mail developers,

just out of curiosity, I recently tried out Trojitá:

http://trojita.flaska.net/

So far, I like Claws Mail better ;).

However, Trojitá still has some features I liked.

One of them is the "IMAP Server Information" feature, which can be accessed via:

Menubar -> IMAP -> Debugging -> IMAP Server Information...

What is does is, it opens a dialog (window) which shows you the capabilities/features of the IMAP server that you are connected to (e.g. IMAP IDLE and so on) and also shows you what type of IMAP server you are connected to (e.g. Dovecot and so on).

Could you please add such a feature to Claws Mail as well?

It would be much appreciated.

Regards
Comment 1 Colin Leroy 2014-05-27 10:36:04 UTC
Hi,

You can see all of this, and more, in the Network Log window.
Comment 2 nw9165-3201 2014-05-27 12:36:37 UTC
Hello,

(In reply to comment #1)
> in the Network Log window

thanks for the hint, but:

(In reply to comment #1)
> You can see all of this

No, I can not. It looks like I can not see what kind of mail server I am connected to (Dovecot and so on) for example in the network log.

In Trojitá I can.

Regards
Comment 3 Colin Leroy 2014-05-27 12:50:42 UTC
Hi,

You can see it if the server says so. If it doesn't, I can't see how we could know it. We could try to guess it but that would be often wrong, and more importantly completely useless as IMAP is a standard.

Also, please don't reopen bugs that have been closed unless you have been invited to do so.

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