Accidentally trained Good email as Spam

SpamSieve
, ,
1

I have a virtual phone number with voicemail for my business. A feature of the virtual phone service is I get emailed notifications of new voicemails as they arrive. My phone number was apparently sold to scammers, so now, in addition to legitimate voicemail notifications, I get multiple emails every day from the virtual phone service with voicemails telling me to call a certain number to opt out of something I never ordered. Without thinking, I trained one of these messages as Spam, before realizing that SpamSieve will treat ALL notifications from the virtual phone service as Spam. I have since trained one these email messages that remained in my Inbox as Good. Is this sufficient to reverse my initial error and ensure that the emails from the virtual phone service will appear in my Inbox?

2

Is your goal for SpamSieve to put all of the voicemail messages into the inbox (even if they’re from scammers) or do you want it to try to learn the difference? Do the messages include transcripts of the voicemails or just say that a certain number called you?

3

My goal is to put all of the voicemail messages into the Inbox. The differences between the messages the scammers are sending and legitimate messages are too subtle to expect SpamSeive to identify. There is no transcript for any of the voicemail messages; just the incoming phone number and an audio file embedded in the email.

4

OK, then I would suggest that you go to the Allowlist window in SpamSieve. There are probably rules there for the sender’s name and address, and you want to find these and check the boxes so that they are Enabled and Locked.

5

Thank you!

6

When accessing the Allowlist I get a message:

The operation couldn’t be completed. (NSSQLiteErrorDomain error 11.)

There are apparently 7,936 Rules in the Allowlist but none are displayed.

7

This error indicates that the database file is damaged. If you have a backup, you could quit SpamSieve and Mail and restore the folder ~/Library/Application Support/SpamSieve/Rules.spamsieve-rules from a backup, or you could delete that folder to start a new database.

Normally, I would expect a bad database to be detected at launch. If you send in a diagnostic report I can take a closer look into what happened.

8

Diagnostic Report sent

Thanks!

9

Thanks. You may want to look into whether there’s something wrong with this Mac’s storage, as I see three different database files that were corrupted, multiple times, going back to July.