We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Dalšne informacije

changes to adaptive junk filtering in tbird 102

  • 2 wótegronje
  • 0 ma toś ten problem
  • 15 naglědow
  • Slědne wótegrono wót tommyb1

more options

with the update to 102, the adaptive junk filter correctly moves spam to the junk folder, but it is no longer marked as junk. that makes the menu option of Tools| Delete mail marked as junk in folder only remove those junk emails that i have manually marked. i have searched and cannot find a setting to reverse this. thanks.

with the update to 102, the adaptive junk filter correctly moves spam to the junk folder, but it is no longer marked as junk. that makes the menu option of Tools| Delete mail marked as junk in folder only remove those junk emails that i have manually marked. i have searched and cannot find a setting to reverse this. thanks.

Wubrane rozwězanje

to be specific, it is a pop account. messages that the adaptive junk filter moved to the junk folder do not have the red junk icon. messages in the inbox moved to the junk folder by manually clicking the greyed out junk icon arrive in the junk folder with the red junk icon. however, the update to 102.0.3 has fixed the problem. thanks.

Toś to wótegrono w konteksće cytaś 👍 0

Wšykne wótegrona (2)

more options

imap account? Or pop? the messages do not have the flame icon?

more options

Wubrane rozwězanje

to be specific, it is a pop account. messages that the adaptive junk filter moved to the junk folder do not have the red junk icon. messages in the inbox moved to the junk folder by manually clicking the greyed out junk icon arrive in the junk folder with the red junk icon. however, the update to 102.0.3 has fixed the problem. thanks.