![]() ![]() Does it rely on the “corpus” to scan incoming messages? Does it have far more advanced heuristics? Hopefully this is my goof and misunderstanding and we can get back on track. I’m willing to correct the rules and try again, but I wonder what the point of SpamSieve is. SpamSieve is on borrowed time, BuhoCleaner is revving up as we speak. But, what the hell is the point of training an app if I have to make adjustments to all the rules myself? How is this better than the built in mail rules? If I have to fix everything SpamSieve does, why not just make the rules myself? This is the exact waste of time I was looking to prevent. I’ll need to edit and delete about 90% of these, change is equal to to contains or use some RegEx magic. Maybe this is bad training on my part, maybe this is exactly how it works, but I’m not impressed. ![]() SpamSieve, what are you doing? Why are you so stupid? This is the “trainable” aspect? You have a database of 730 pointless rules. The rule isn’t going to work unless I get the exact same email, from the exact same address. That problem persists for other fields, for example there are dozens of rules where the subject is equal to followed by a load of gibberish. Obviously the From field will never be the same thing twice. Take the use of address: a useless set of rules. The rules are set to use is equal to for way too many fields. In looking at the Blocklist, I see why there are over 700 entries. ![]() There are two problems, there was a misconfiguration on my part, and the rules are overly specific. Even though it has 730+ blocklist rules, and filtered over 73k words, not a single message has been flagged as spam. It's a total waste of time and a pain in the ass to submit bugs to Apple.In my battle against the hundreds of spam messages I’m getting, I’ve installed SpamSieve, because the reviews say you train it to block all types of spam.Īfter flagging over 500 messages as spam, SpamSieve has blocked exactly zero (0). Years or months later after submitting a bug that happens not to be closed as duplicate of another bug, they get closed because a new version of macOS is released, and you are encouraged to resubmit your report if it still affects the new version, which inevitably it does.Įven if the bug is in some open source component, and you provide a patch, it is ignored and eventually closed as explained above. The bugs are never fixed, at least no bug that I have ever reported has been fixed. The bugs are almost always closed as duplicate of another bug, which, of course, you can't see because the bug tracker is private. Sometimes this happens even if they asked you to try the beta version! When you try to reproduce the bug on multiple versions, they close your bug if you reproduced it on beta versions, because beta versions are unsupported, even though the bug affects release versions. They take forever to answer, and ask for things that you have already provided in your original issue. I can’t recall whether Activity Monitor has any historical/time-series views built in? If it does, then if you hide Activity Monitor with those active, it should keep using CPU, to gather the data for that view, whether it’s rendering it or not. This might be down to Activity Monitor being written to respond to a message letting it know that its view is entirely obscured, and the Activity Monitor main-window view-controller deciding in response that there’s no point in it polling the system if all it’s going to do when re-visible is discard all the stuff it learned in the mean time and re-poll again to get the newest data for the view. ![]() > It does for me, which is why I keep it hidden when I’m not actively using it. (They might have a lower update rate, though.) I believe it’s just using the same call into the compositor that Mission Control uses to display your windows and spaces. Nah, it updates (.as far as I can recall.) Try opening a chat client, minimizing the chat window, and then sending a message from another device to yourself. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |