comfyanonymous
feat: use matrix.to for matrix links
Yes, I believe the spam marking fails, so the DB entry is not updated, but the underlying message file is moved anyway, so it is not found the next time.
@mattfbacon thanks for reporting. i got a similar message from github that couldn't be (un)trained. those messages contain a long string (more than 32 kilobytes) of unicode 0x3164 ("hangul filler") characters (perhaps as part of an attempt to obfuscate text, or to circumvent spam filters!). when updating the database with hammy/spammy words, we didn't check for that maximum word size. the commit above adds that check. i can now mark that message from github as ham/spam.
btw, if you mark such messages from github as spam a few times consecutively, mox will start treating all messages from that sender (i.e. github) as spam. that may not be what you want. i typically put such messages (i.e. those that are spammy, but sent through a mostly benign service) in a mailbox called "NeutralTrash", that doesn't get automatic junk/nonjunk flags (with the default account config).
i still have to look into how/if this is related to the message that was deleted from the file system.
Hey @mjl-, thanks for the explanation. Funnily enough, the exact problem you described about the github notifications address being blocked caused your reply to go to spam so I didn't see it until now 😅
If I mark some other, non-spam emails from the github notifications address as not spam, will that fix the issue?
I was coming here after facing the exact same error with the same message.
It made my database corrupted, because the message file was moved but not updated in database, leading to other errors. I had to restore the file from database, remove the message file that was created. I finally had to modify the content of the message by hand to avoid this error when trying to delete it
