Closed Bug 1836966 Opened 2 years ago Closed 2 years ago

Message List - Thread Pane - column headers - incorrectly named 'Spam' should be 'Junk Status'

Categories

(Thunderbird :: Folder and Message Lists, defect)

Thunderbird 114
defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: anjeyelf, Unassigned)

Details

(Whiteboard: [snnot3p])

Windows OS
New installation of beta 114.0b6
New beta profile
Created imap gmail account

In Message List / Thread Pane area.
select 'columns to display' icon
Drop down list includes 'Spam'

The drop down list has never used the word 'Spam'.
Thunderbird historically and generically does not use the word 'Spam'.
Account Settings uses 'Junk Settings' and 'Junk Controls' and there is 'Global Junk Preferences'. Message Filters use 'Set Junk Status to' - 'Junk'
Pop accounts by default use 'Junk' folders.

'Junk' is the perfect word because it refers to items you do not want to see in Inbox and want redirected to the 'Junk' folder and not all those items are necessarilly spam.

Servers tend to use the word 'Spam' even if it's not spam. I've never understood that logic. So IMAP accounts are likely to see folders using the word Spam, but the Folder Pane is the only place where Spam folder might be seen.

As Thunderbird uses the word Junk, it makes it a lot easier to know if using Pop or Imap and instructing users when they need help.

Request the column header called 'Spam' is renamed to 'Junk Status'

"Spam" is a term more universally used throughout the broader mail ecosystem and most recognizable to users.

So if I remember correctly, we are/will be transitioning to "spam" as the terminology for this area. But we are currently not consistent in our terminology throughout the UI.

Flags: needinfo?(alessandro)
Whiteboard: [snnot3p]

Indeed, we're moving towards Spam for the default en-US locale.
"Junk" is also sometimes used as derogatory term so we're slowly removing it.

Status: NEW → RESOLVED
Closed: 2 years ago
Flags: needinfo?(alessandro)
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.