![]() ![]() ![]() Unfortunately, I don’t use Time Machine at present, so the old file is gone. The permissions and the file size for the plist-file are identical - Had I thought about it, I’d moved the file and not deleted it, so I could compare the contents. I don’t know why recreating the plist was necessary for it to actually run, since SpamSieve had previously decided that the new plist would be identical to the old one. SpamSieve is just trying to get you to fix that checkbox. With the wrong ownership flag, SpamSieve reports an error installing the launch agent plist because it knows that the system won’t load it until the ownership is fixed. If you do: ls -lea ~/Library/LaunchAgents/ĭoes it look different from before (other than the date)? I would be really curious to know what changed after it saved the new file. So in theory deleting the file, as you did, wouldn’t have any effect. It already tries to fix the permissions/ownership if they are wrong and saves the plist if it detects that it’s different than would be saved. It’s needed because that’s what tells SpamSieve to install the launch agent, which isn’t needed if you aren’t using Apple Mail. Permissions for the launch agent itself has probably been OK all this time: 7694974 -rwxr-xr-x 1 administrator admin 140960 Feb 27 17:51 SpamSieveLaunchAgent I haven’t downloaded new software or changed settings recently. I don’t understand how setting change suddenly by themselves. There was only one, not two, rules in Entourage Rules for SpamSieve, so I added a second. If I get this correctly, the ownership flag prevented the plugin from being installed, but the plist-file needed to be recreated in order for the launch agent to actually run. Still not working None of these look like my problem, but I still rechecked Entourage rules, SpamSieve setup, etc. It seems that it was all that was needed in addition to manually clearing “Ignore ownership”. You can confirm this by checking SpamSieve’s log to see whether it says that it predicted those messages to be spam. ![]() a server junk filter) is moving the messages to the Spam mailbox. The most likely explanation is that something else (e.g. (I guess it makes sense having this setting on when moving drives between computers where the user account in question isn’t always the same User ID, but besides that it seems to me like it’s never really needed.)Ĭould future versions of SpamSieve possibly decide to recreate the plist-file under certain circumstances? I’ve never seen a problem with SpamSieve’s whitelist not working (unless it’s turned off). It doesn’t help that they seem to be default on. It’s so easy to forget these “Ignore ownership” checkboxes whenever initializing new drives. I deleted the com.c-command…plist file, started SpamSieve, installed the Apple plugin again (don’t know if that was needed), saw the plist-file had been recreated, and now it works. It might help to delete the .plist file so that SpamSieve creates a new one.Īnother possibility is that there’s a problem with the permissions on the SpamSieve launch agent itself (SpamSieve.app/Contents/Frameworks/amework/Resources/SpamSieveLaunchAgent), which is referenced by the plist. That looks OK to me, and the permissions are the same as for your other launch agents. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |