{"id":1031,"date":"2005-05-17T00:19:09","date_gmt":"2005-05-17T05:19:09","guid":{"rendered":"\/?p=1031"},"modified":"2016-07-28T09:48:52","modified_gmt":"2016-07-28T13:48:52","slug":"mac-os-x-1041-and-spamsieve-231","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2005\/05\/17\/mac-os-x-1041-and-spamsieve-231\/","title":{"rendered":"Mac OS X 10.4.1 and SpamSieve 2.3.1"},"content":{"rendered":"<img decoding=\"async\" src=\"http:\/\/c-command.com\/images\/spamsieve-icon.gif\" align=\"right\" alt=\"SpamSieve Icon\" \/>\r\n\r\n<p>\r\nIt&rsquo;s not every Monday that Apple releases an OS update two hours after\r\nthe close of business (on the East Coast) that breaks your software.\r\nThe good news is that, although I didn&rsquo;t expect 10.4.1 to be released\r\nthis soon, I was aware of the problem and was almost ready to release <a href=\"http:\/\/c-command.com\/spamsieve\/\">SpamSieve 2.3.1<\/a>, which <a href=\"http:\/\/c-command.com\/spamsieve\/manual#version-history\">includes<\/a> accuracy improvements and some other Tiger-related changes.\r\n<\/p>\r\n\r\n<p>\r\nThe issue with 10.4.1 is that various Mail plug-ins have been causing <a href=\"http:\/\/docs.info.apple.com\/article.html?artnum=301584\">problems<\/a> with Apple Mail in 10.4. To the best of my knowledge, SpamSieve&rsquo;s was not among these. (I&rsquo;ve received no reports of crashes or other Mail problems with any release versions of Mac OS X and SpamSieve, except for a few crashes that were caused by an old PGP plug-in.) But Apple has no way of knowing that, and they understandably don&rsquo;t want their mail program to crash or misbehave because of other people&rsquo;s code. So <a href=\"http:\/\/docs.info.apple.com\/article.html?artnum=301517\">10.4.1 disables all Mail plug-ins<\/a>. And it does so in such a way that you can&rsquo;t re-enable them by dragging them out of the <tt>Bundles (Disabled)<\/tt> folder or by running the plug-in&rsquo;s installer. Obviously, the idea was to get the plug-in developers to issue updates.\r\n<\/p>\r\n\r\n<p>\r\nBut I don&rsquo;t think Apple quite accomplished what it might have wanted\r\nto, on a technical level, because plug-ins are either all enabled or\r\nall disabled. If you install 10.4.1 first, and then update to SpamSieve\r\n2.3.1, SpamSieve will work and all the other plug-ins will remain\r\ndisabled. Perhaps you&rsquo;ll re-install them one-by-one as the developers\r\nissue updates. But if you install SpamSieve 2.3.1 first, and then\r\nupdate to 10.4.1 (or if you install some other incompatible plug-in\r\nafter installing SpamSieve 2.3.1) all the plug-ins will be enabled, and\r\nyou&rsquo;re essentially back to the 10.4 situation.\r\n<\/p>\r\n\r\n<p>\r\nThe non-technical aspects of this update also leave something to be\r\ndesired. Apple didn&rsquo;t tell developers that it was going to make this\r\nchange; their first acknowledgment of it was today. I discovered that\r\n10.4.1 disabled SpamSieve while running a seed, and luckily it wasn&rsquo;t\r\nhard to figure out how to get it working again. But I couldn&rsquo;t be sure\r\nthat my solution was correct, because Apple has yet to officially tell\r\ndevelopers how to make their plug-ins &ldquo;compatible&rdquo; or to reply to my\r\ninquiry as to same.\r\n<\/p>\r\n\r\n<p>\r\nWhat I&rsquo;m most surprised about is how many people told Software Update\r\nto go right ahead within an hour or two of 10.4.1&rsquo;s release. I won&rsquo;t be\r\nclicking that button on my development machine for a few days.\r\n<\/p>","protected":false},"excerpt":{"rendered":"<p>It&rsquo;s not every Monday that Apple releases an OS update two hours after the close of business (on the East Coast) that breaks your software. The good news is that, although I didn&rsquo;t expect 10.4.1 to be released this soon, I was aware of the problem and was almost ready to release SpamSieve 2.3.1, which [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"apple_news_api_created_at":"","apple_news_api_id":"","apple_news_api_modified_at":"","apple_news_api_revision":"","apple_news_api_share_url":"","apple_news_coverimage":0,"apple_news_coverimage_caption":"","apple_news_is_hidden":false,"apple_news_is_paid":false,"apple_news_is_preview":false,"apple_news_is_sponsored":false,"apple_news_maturity_rating":"","apple_news_metadata":"\"\"","apple_news_pullquote":"","apple_news_pullquote_position":"","apple_news_slug":"","apple_news_sections":"\"\"","apple_news_suppress_video_url":false,"apple_news_use_image_component":false,"footnotes":""},"categories":[2],"tags":[372],"class_list":["post-1031","post","type-post","status-publish","format-standard","hentry","category-technology","tag-spamsieve"],"apple_news_notices":[],"_links":{"self":[{"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/posts\/1031","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/comments?post=1031"}],"version-history":[{"count":1,"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/posts\/1031\/revisions"}],"predecessor-version":[{"id":15383,"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/posts\/1031\/revisions\/15383"}],"wp:attachment":[{"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/media?parent=1031"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/categories?post=1031"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mjtsai.com\/blog\/wp-json\/wp\/v2\/tags?post=1031"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}