PS: the spamsieve log shows it’s still automatically moving some stuff to the Spam folder as of just today it’s me doing it manually that’s not working. I’m totally without a clue of what to do next if anyone can assist/recommend? scriptrunner Error running script: /Users//Library/Mail/Bundles/SpamSieve.mailbundle/Contents/Resources/TigerTrainSpam.scpt (null) I don’t have scriptrunnercrash.log but in the cosole log there is a message: I downloaded and unzipped the script from page one of this thread but I get an error that Script Editor cannot open the script. Hello: my ‘mark as spam’ also stopped working recently. When I run the script editor, it doesn’t give a line in which the error occurs.Ĭannot move messages to Spam any longer / no crash log present I’ll send you the crash log file, as requested. Perhaps I just don’t quite understand the color coding. In this way, I presumed that it was judged to probably be spam but with a certain margin of error. As for the second message from the same sender, when it was highlighted, it was highlighted blue and not gray. Regarding your question about how I think the SS recognized the spam, I figure that since the e-mail message was highlighted gray and moved to the spam folder, after running the script and the apply rules command, that it was recognized as a true spam. Before I ran the script in script editor, in using just SS, it neither changed color nor did it get transfered to the spam folder.Īs for the script, I should have said that I downloaded and ran the script. I had anticipated that when I highlight the message in question and ask that SS treat the message as spam, that it would 1. On the other hand, maybe there something else going on. I’m not really a techie and maybe I’m missing something obvious. When I run the script on this e-mail (that I already ran on the first one) I get the same error code mentioned before in this thread. In the console app I get this message : Feb 21 10:18:50 Dougs-iMac crashdump: crash report written to: Users/douglaslivie/Library/Logs/CrashReporter/ I reran the “train as spam” command and the second e-mail would not change to gray - ie. After using it, the first of two e-mails was recognized as spam. I also installed the first mail script that is provided in this post. I reinstalled the apple mail script twice while mail was running and once when it wasn’t to try and get it to work. No problem training other e-mail messages. Initially, I could not get SS to train as spam mail coming from a particular user. I would be happy to answer any questions that they have about it.I’ve read this thread with interest because I’m having similar problems. Of course, if the developers of these or other clients wish to also provide direct integration with SpamSieve, the interface that Mailsmith and SpamSieve use to communicate is completely open. SpamSieve continues to work with e-mail clients other than Mailsmith, and 1.3.1 adds some improvements specifically for users of Emailer, Entourage, Eudora, and PowerMail. New purchases of Mailsmith between now and July 30 will include a free copy of SpamSieve, and there is an additional 10% discount if you order before June 30. For extra speed, Mailsmith sends SpamSieve decoded versions of the messages (there's no sense in both programs decoding them) and strips out large non-text attachments that can be slow to transfer through the Apple event pipe. You can also add an address to SpamSieve's whitelist by Control-clicking on the message's sender and choosing Add to Address Book from the contextual menu. It sweats the details: Mailsmith knows not to bounce or animate its Dock icon after receiving a batch of messages that are all spam. Mailsmith can automatically move spam messages to its (spam) folder, but if you want more control there are also new filter criteria called Is Spam and Is Not Spam. For instance, I have it set so that correcting a false positive re-applies Mailsmith's filters to the message, thus filing it in the proper folder. You can choose what happens when you manually mark messages as spam or good. No more AppleScripts or filters: enabling SpamSieve in Mailsmith is as easy as clicking a checkbox.īare Bones Software has seamlessly integrated SpamSieve with Mailsmith's powerful filtering system. Besides adding support for the Mac OS X Address Book, PGP, background queries, clickable links, digest bursting, better mailbox pop-ups, and a refined interface, it features direct integration with SpamSieve. It's about making SpamSieve 1.3 a little faster, better, and smaller to tide people over to the next major release. SpamSieve 1.3.1 and Mailsmith 2.0 are out.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |