Bug 332911 - Offer autocomplete (or dropdown) for "Sent" folder choice
Summary: Offer autocomplete (or dropdown) for "Sent" folder choice
Status: CONFIRMED
Alias: None
Product: trojita
Classification: Applications
Component: Desktop GUI (show other bugs)
Version: git
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Trojita default assignee
URL:
Keywords:
: 356121 (view as bug list)
Depends on: 332909
Blocks:
  Show dependency treegraph
 
Reported: 2014-04-01 15:38 UTC by Jan Kundrát
Modified: 2021-03-09 07:26 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Kundrát 2014-04-01 15:38:37 UTC
Imported from https://projects.flaska.net/issues/634 :

I want to save outgoing email. I tried "Sent" as outgoing folder, which leads to a popup
"APPEND: Invalid mail box name." There is no help as to what would be valid names. So I tried "INBOX/Sent", which gives the same popup.
Only "INBOX.Sent" worked, but nowhere do I get a clue that my mailserver's hierarchy delimited is ".". So "INBOX.Sent" is less than intuitive unless I know my IMAP server very well.

I would suggest that a drop drown or autocompletion of existing folders could help immensively here.

(BTW, are we saving to the Sent folder before actually sending out the email? In this case we could end up with a mail in the Outbox that was actually never sent (in case of a network error or another error). I believe email should only be put in the "Sent" folder if they actually went out successfully).

Sebastian Spaeth wrote:
> I would suggest that a drop drown or autocompletion of existing folders could help immensively here.

Agreed. The blocker for this is the same thing which prevents a pop-up menu for moving/copying messages (see #604). Trojita discovers the mailboxes in a very dynamic manner, only loading the items in each depth of the hierarchy when they are actually needed. This is great for performance (and recommended by various IMAP howtos and best-priactice RFCs), but doesn't play that well with QMenu, the Qt class which takes care of the popup menus.

This is surely doable, but it will need some time before it's implemented.

> (BTW, are we saving to the Sent folder before actually sending out the email? In this case we could end up with a mail in the Outbox that was actually never sent (in case of a network error or another error). I believe email should only be put in the "Sent" folder if they actually went out successfully).

This is a bit complicated. Trojita has to support many ways of sending messages, one of them is via the BURL extension which you've already encountered. In order for this to be useful, one simply has to have the already composed message available on the IMAP server. One could argue that another mailbox should get used, but I don't believe that this is actually needed. RFC 5550, section 5.10 says that the $SubmitPending and $Submitted flags shall be manipulated to distinguish the "about-to-be-sent" messages, those which are currently in the process of being submitted, and those which have been succesfully submitted already. The problem might be that Trojita currently has no way of signalling this status of these messages, i.e. the GUI doesn't show up anything intuitive to inform the user that "this message hasn't been sent yet".
Comment 1 Erik Quaeghebeur 2015-10-25 21:29:28 UTC
If I'm not mistaken, the $SubmitPending and $Submitted keywords are not added to messages (being) sent (in the current head, aff95e266f1f3e0162e11419443fbbdb615eb455).

Even if the GUI doesn't show this yet, it may already be a first step to add these flags as appropriate. Once the keywords are in place, using modified icons isn't that big a step. (KMail uses the non-registered $SENT keyword and a postage stamp icon to indicate submitted messages.)
Comment 2 Jan Kundrát 2015-10-25 22:02:37 UTC
These two keywords actually are being added; if not, please file a separate bugreport with an IMAP log so that we can take a look at it. It would help if it is from a new connection so that even the initial greeting is present.
Comment 3 Jan Kundrát 2015-11-30 16:54:45 UTC
*** Bug 356121 has been marked as a duplicate of this bug. ***
Comment 4 Justin Zobel 2021-03-09 07:26:13 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.