[Users] [Bug 4419] New: Existing IMAP account clashes with new POP3 account

[noreply at thewildbeast.co.uk]

https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4419

            Bug ID: 4419
           Summary: Existing IMAP account clashes with new POP3 account
           Product: Claws Mail
           Version: 3.17.3
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: POP3
          Assignee: users at lists.claws-mail.org
          Reporter: juhuseq at boximail.com

An IMAP profile was first created for an account at danwin1210.me.  The IMAP
server is simply "danwin1210.me" in this case (contrary to most services which
use something like "imap.server.tld").  This profile was named "Danwin - IMAP"

Then for archival purposes, a POP3 profile was created for the same email
account.  This profile was named "Danwin - POP3"  The server is also simply
"danwin1210.me".  Quite strangely, there is a "Default Inbox" field on the
"Receive" page of the POP3 account preferences, and it's pre-populated with:
"#imap/danwin - IMAP/INBOX".  It's bizarre that the new POP3 profile would be
aware of the IMAP account without any action on my part to associate them. 
This "Default Inbox" field has zero documentation
https://www.claws-mail.org/manual/claws-mail-manual.html yet the syntax is
cryptic so it's unclear how this field should be set.  So it was left as-is.

On the main screen, the left frame shows folders for "Danwin - IMAP", but not
for "Danwin - POP3".  Yet the "Get Mail" pulldown menu shows both.  (even after
a restart)

I believe a few bugs are evident in this scenario:

bug 1) The "Default Inbox" field is undocumented.
bug 2) The two profiles get intermingled, and the POP3 account does not appear.
bug 3) If the intermingling/merging of IMAP & POP3 profiles of the same account
is deliberate (by design), then the user should be notified in some way, and
told what to expect.

-- 
You are receiving this mail because:
You are the assignee for the bug.