Brent Rossow
Posts: 10
Smile Score: +6
About Me
I am a MacUpdate Desktop user
Gender: Male


Visit Stats
Member Since: 16 Sep 2012
Profile Views: 1,056

Brent Rossow's Posts
Average Rating from Brent:
(1)

sort: smiles | time

Brossow rated on 01 Nov 2012
[Version 2.13]



burypromote
+1
brossow tipped on 30 Oct 2007
A workaround was posted to the Mail.appetizer mailing list yesterday. I don't have the message here on my work computer, but I believe the following is the correct procedure:

1. Ensure that Mail.app is not running.

2. Launch Terminal and enter these two commands:

defaults write com.apple.mail EnableBundles 1
defaults write com.apple.mail BundleCompatibilityVersion 3

3. Move the Mail.appetizer bundle from the folder ~/Library/Mail/Bundles (Disabled) back to ~/Library/Mail/Bundles.

4. Launch Mail.app -- all should be well again.

Hope this is right -- going from memory and using an XP machine at work so I can't verify. At worst it won't work but won't do any damage. :-)
[Version 1.2b4]


4 Replies

burypromote
+1

+6
brossow replied on 30 Oct 2007
Perhaps stating the obvious, that workaround is for Leopard. Forgot to mention that....
burypromote
+1

+6
brossow replied on 01 Nov 2007
Should note here that it seems even with the workaround above, full functionality isn't gonna happen with the current version of M.a and Leopard. Specifically, the buttons don't work as expected, HTML messages are shown as raw source, and only new messages in the Inbox are shown -- new messages filtered to other folders do not show up. :-(
burypromote
+1

+6
brossow replied on 29 Nov 2007
Best tip after using the workaround for a few days is this: wait for an update from the author. The functionality is so limited with the workaround that it's not worth messing with. :-(
burypromote
+1

+6
brossow replied on 29 Nov 2007
To be completely fair, prior to Leopard's release there was utterly no need for an update since the last version, however long ago it may have been. It worked perfectly and did absolutely everything it was intended to do, and it did it FOR FREE.

Perhaps if you sent the author of this FREE software $129 so he could purchase his own copy of 10.5 there'd be an update coming along a little more quickly. Until someone does that, however, expecting a developer to shell out $129 in order to update FREE software is unreasonable at best.
There are currently no troubleshooting comments by this member.

Displaying 1-2 of 2
Please login or create a new
MacUpdate Member account
to use this feature


- -