Comments on: Mac OS X 10.4.1 and SpamSieve 2.3.1

By: Michael

Michael — Tue, 17 May 2005 18:03:35 +0000

Installing SpamSieve's Mail plug-in will have the side effect of enabling all the others that are in the Bundles folder. It's not sufficient to drag them around because they have to be enabled from within Mail's preferences.

By: Wes Meltzer

Wes Meltzer — Tue, 17 May 2005 17:45:08 +0000

Michael, out of curiosity, do you know of a way to re-enable any, err, non-SpamSieve Mail plugins? Would dragging them out of the Bundles folder before the update work?

I use a whole bunch of these plugins, having switched back to Mail to appease Northwestern's monumentally stupid e-mail servers. I'd love to get rid of the 10.4.0 bugs, but if that means giving up plugins that make my life easier... it's a tough call.

By: Michael

Michael — Tue, 17 May 2005 15:08:09 +0000

They're not officially supported, even under Tiger. Because of that, I was very reluctant to write the plug-in in the first place, but I'm glad that I did because the unsupported plug-in is much more reliable than using the supported AppleScript interface. The "API" is more stable, too.

By: Evan DiBiase

Evan DiBiase — Tue, 17 May 2005 15:02:07 +0000

I was under the impression that Mail plugins are not officially supported. Has this changed in Tiger?

By: Michael

Michael — Tue, 17 May 2005 14:40:38 +0000

You also had the beta version that worked with Mail in 10.4.1. :-)

By: John Gruber

John Gruber — Tue, 17 May 2005 14:26:10 +0000

I broke my usual rule—which is to wait at least one or two business days before installing an OS update to see if any widespread problems are reported—and upgraded to 10.4.1 soon after it was released. I found 10.4.0 to be so buggy that I figured 10.4.1 almost certainly couldn't be worse.

(Of course, since I use Mailsmith instead of Apple Mail, SpamSieve continued to work just fine.)