[Geary] Feature request: Browse mail by contact panel

[Gunwald Neuhausen <gunwald gmx de>]

I would like to propose a new function to Geary, which – in my humble opinion – would solve the unsolved problem, how to browse through the huge amount of mails many of us getting every day.
Nowadays almost every mail client offer a folder view to browse through different mail accounts and their IMAP folders. With out any question this is useful, but I think, their would be a better way to browse our mail: To browse them by contact. There for I would propose to integrate Geary with the evolution data server, to enable it to show instead of the folder view a contact view.

• This contact view could look similar to the left column of Gnome contacts.
• It would list the contacts stored in the evolution data server, but ordered by the last mails I got or send to them. That means, if I would have got an mail form contact A three minutes ago, but from contact B 10 seconds ago, B would be in the first place.
• Clicking on the contact would list all mails I ever got from it in the second pane.
• Middle click on it would list all mails I ever send to that contact.
• The contact panel would also offer a search field, to search only in the listed contacts.
• Of course the folder tree view should not be completely removed, but you should switch between the the contact panel and the classic folder tree.

What do you think, of such a feature?

Am 18.09.2016 um 14:00 schrieb geary-list-request gnome org:

Send geary-list mailing list submissions to
	geary-list gnome org

To subscribe or unsubscribe via the World Wide Web, visit
	https://mail.gnome.org/mailman/listinfo/geary-list
or, via email, send a message with subject or body 'help' to
	geary-list-request gnome org

You can reach the person managing the list at
	geary-list-owner gnome org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of geary-list digest..."


Today's Topics:

   1. Re: IMAP / gmail performance? (Michael Gratton)
   2. Re: hidden geary (Michael Gratton)
   3. Re: hidden geary (STRE?NIK)


----------------------------------------------------------------------

Message: 1
Date: Sun, 18 Sep 2016 17:36:14 +1000
From: Michael Gratton <mike vee net>
To: Kristian Rink <kawazu428 gmail com>
Cc: geary-list gnome org
Subject: Re: [Geary] IMAP / gmail performance?
Message-ID: <1474184174 25004 1 mail quuxo net>
Content-Type: text/plain; charset=UTF-8; format=flowed

On Fri, Sep 16, 2016 at 5:02 PM, Kristian Rink <kawazu428 gmail com> 
wrote:

The last of these symptoms is something I kind of managed to track 
down
using sql and network logging: Our corporate IMAP server is pretty
large (in terms of mail spool size and in terms of available IMAP
folders for different internal purposes). A load of messages in there
contain *large* attachments (documents between 5 and 50 megabytes of
size). Generally, mail traffic in most of these folders is extremely
high during daytime. Looking at the logs, it seems geary generally 
gets
extremely busy periodically iterating across all these folders and
permanently synchronizing / downloading new messages.

Hmm, so are most of these folders in a shared/public IMAP namespace, 
that you know of? I.e. folders not in your own personal account? If so, 
do you need access to them from Geary?

Unfortunately I haven't found any way to influence this behaviour.
Expectation would be to simply tell the IMAP client to please ignore
certain folders or subfolder hierarchies in the IMAP tree but I
couldn't figure out how to do that (if it's possible with geary after
all...).

This is usually what IMAP mailbox subscriptions are for, and which 
would likely take care of this for you ? assuming you don't actually 
want to subscribe to those folders. Currently, Geary doesn't pay 
attention to that however: 
<https://bugzilla.gnome.org/show_bug.cgi?id=713449>

Not storing attachments in the database 
<https://bugzilla.gnome.org/show_bug.cgi?id=714061> and not downloading 
attachments by default 
<https://bugzilla.gnome.org/show_bug.cgi?id=714094> might also help.

//Mike