Open Bug 1972154 Opened 2 months ago Updated 2 months ago

The account setting for 'Keep mesage archives in' should be Archive, not Archives

Categories

(Thunderbird :: Preferences, defect)

Thunderbird 128
defect

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: siffe, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:139.0) Gecko/20100101 Firefox/139.0

Steps to reproduce:

  • opened Account Settings > Copies & Folders

Actual results:

  • saw that under Message Archives > Keep message archives in:, the first choice is "Archives" Folder on:

Expected results:

The actual TB-generated archives folder is named Archive, not Archives. This inconsistency caused some confusion here.

Also, I'm not sure about the reason for the double quotes, which indicates a direct quotation. A single quote to draw attention would be more appropriate, but even that is questionable IMO. (Same for Drafts and Templates).

Thunderbird creates "Archives" (with s). Some other services use Archive (like iCloud)

Yeah, it appears Fastmail creates its own archive folder named Archive, which a) prevents TB from creating its Archives folder, and b) doesn't accept messages I try to archive. I'll file an issue with Fastmail and wait for Bug 1909104 to be implemented.

Never mind; I can create the TB Archives folder under local folders.

condition also exists on 128, correct?

Severity: -- → S4
Version: Thunderbird 139 → Thunderbird 128

(In reply to Wayne Mery (:wsmwk) from comment #4)

condition also exists on 128, correct?

Yes. I re-filed the issue with Fastmail, as I realized that some might want to locate the TB Archives folder under the Inbox vs. under Local Folders.

Tech says he has no problem. What's strange is that his FM-generated archive folder is also named Archives; mine is Archive. He says he can see that Archives folder and the TB-generated Archives folder, and that archiving works as expected. I posted my problem here out of curiosity after discovering it while helping someone else. I also tried a new profile with no resolution. At this point, as I don't even use the archive function and there haven't been any other complaints, I'd say I have some sort of local problem so the bug can be closed.

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