Re: Translatable strings

I just checked, and #3 can be used to create a subfolder below INBOX, even on Gmail. It can then be deleted 
from the folder context menu, so the user has full control over a folder hierarchy on an IMAP host.

On 11/23/2016 09:15:09 PM Wed, Peter Bloomfield wrote:
Hi Albrecht,

On 11/21/2016 03:33:13 PM Mon, Albrecht Dreß wrote:
Hi Peter:
An other question is why we have /three/ options for accessing IMAP in Balsa, which is extremely confusing 
1. "Remote IMAP mailbox" - which is actually only /one/ remote folder for which the path needs to be specified
2. "Remote IMAP folder" - which is the IMAP support all other MUA's provide afaict, minus the possibility to
3. "Remote IMAP subfolder"

To be honest, I never understood the use case of #1 and #3.  The standard way to access IMAP I know from 
Thunderbird, kmail and Lookout is actually limited to #2 (including the option to subscribe/unsubscribe 
folders).  In this (and *only* in this!) use case, the user can name the top-level item according to e.g. the 
provider name, and /then/ it would be possible to translate the IMAP top-level item.

Well, #1 is backward compatibility. It was the first IMAP access implemented in Balsa, so it was left in when 
folder access (#2) was added. The third option, #3, is for managing the structure of folders on the IMAP 
host. I used to use it when my IMAP account was on a Courier server, which was pretty much IMAP-compliant, 
but I haven't tried it since my campus switched to Gmail. I assume it's still useful for users with a real 
IMAP server hosting their mail.

I'd be very happy to see #1 removed!

balsa-list mailing list
balsa-list gnome org

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]