9·
1 day ago@Flagstaff Nope. Evolution isn’t the villain here! The local filter was simply completely untrained when you first connected your account, and Gmail mistakenly interpreted your moved emails as real spam reports. Without Gmail’s particular way of handling IMAP moves, this wouldn’t have happened at all. Just turn off the local junk detection in Evolution’s settings for your Gmail account, and Gmail itself will take over the sorting again – and that’ll be the end of that headache.
@Flagstaff @hendrik The crucial point is that you need to disable Evolution’s junk detection both globally and specifically for your Gmail account – these are two independent switches that are often overlooked.
Technically, the crux lies in how the two systems interact: the local Bogofilter was completely untrained during the first sync (lacking the “ham” training for your typical emails) and thus indiscriminately sorted out old entries. However, Evolution doesn’t just perform this action locally; it physically executes an IMAP MOVE command into Gmail’s reserved Spam folder ([Gmail]/Spam). This is precisely where Gmail’s API misinterprets this move as an intentional spam report from you – which is why Google’s AI permanently stored those emails as spam, even after you manually marked them as “Not spam” in the web client.
Since Gmail already filters server-side anyway, this local spam-filtering feature is completely redundant and can be disabled with a clear conscience.