Below is an excerpt from the Apple Discussion boards from a post by pterobyte (aka Alex) of osx.topicdesk.com.
A word of caution before applying Security Update 2008-002 to OS X Server 10.4.11:
According to this document:
the security update updates ClamAV to 0.92.1. Which is fine.
What the document, doesn’t tell is that spamassassin, amavisd and what is worse, configuration files, get overwritten in the process as well (without software actually being updated).
This has some side effects which unfortunately vary from system to system and configuration to configuration.
If you never updated ClamAV, spamassassin or amavisd manually check that:
-/etc/mail/spamassassin/local.cf, /etc/mail/spamassassin/init.pre and /etc/amavisd.conf didn’t get overwritten thus loosing your personalised settings (if any)
-/etc/spam/clamav/clamd.conf and /etc/spam/clamav/freshclam.conf didn’t get overwritten thus loosing your personalised settings (if any)
If you have manually updated spamassassin or amavisd check that:
-/etc/mail/spamassassin/local.cf, /etc/mail/spamassassin/init.pre and /etc/amavisd.conf didn’t get overwritten thus loosing your personalised settings AND causing issues with your current versions.
-/usr/bin/amavisd didn’t get overwritten. If it did re-install amavisd as you did the first time
-/usr/bin/spamassassin didn’t get overwritten. If it did re-install spamassassin as you did the first time
I’ve upgraded a 10.3.9 Server to 10.4.7 today. This of course upgraded SquirrelMail to 1.4.5 and PHP to 4.4.1. As explained before, this combination causes moji-bake in Japanese.
Unfortunately, replacing libphp4.so with the 4.3.11 version like before will not do. Because MySQL was also upgraded to 5.x. To use a MySQL 5.x database, PHP’s MySQL API needs to be 4.1 or higher. In PHP 4.3.11 the API is version 3.23. If you run MySQL on the same machine, the option to swap libphp4.so is out of the question.
Now, applying the Japanese patch will fix Subject and Body moji-bake within SM, but will cause the subject to be encoded in EUC and the body to be encoded in ISO-2022-jp. That means, with mail client software other than SM, you’ll either have a Subject moji-bake or body moji-bake depending on your decoding scheme.
To fix this, you’ll have to tell SM to encode the Subject line in a different manner (ISO-2022-jp) instead of what the HTML header is telling it to (EUC-JP). To do this, you’ll need to edit/usr/share/squirrelmail/class/deliver/Deliver.class.php.
$headerÂ =Â 'Subject:Â '.encodeHeader($rfc822_header->subject)Â .Â $rn;
and comment it out.
Right under it, add:
$headerÂ =Â 'Subject:Â '.mb_convert_encoding($rfc822_header->subject,"ISO-2022-jp")Â .Â $rn;
This forces SM toÂ try to use ISO-2022-jp as the encoding method for the subject line. This may or may not happen, but what will happen is that the subject line will not be encoded in EUC-JP and will be encoded with the same encoding method as the Body of the message.
— UPDATE —
This is still the case with SquirrelMail all the way up to 1.4.16.
In the previous article “Instead of Bread, Eat Cake“, I wondered aloud about an iPhone without the cell phone feature. Apple answered that with the $199 iPod Touch and subsequently provided a model with external speakers and 2.0 software that essentially made a non-phone iPhone.
And now, Americans are paying for their mismanagement of global imperialism.
The extremely lowered price of the device means somebody is losing out on revenues. Somebody on the other side of the world might be starving. Thank you America, you have given the world the freedom to starve.
P.S. Some of us were ok with the government feeding us.
A week after the US elections, Apple’s new sales program will go into effect for the holiday season. Meaning, AppleStores across the United States will begin using aggressive sales tactics to get rid of its inventory. Neither new products nor new prices will be advertised, but make sure to ask your Apple sales specialist if they can’t do anything special for you.
Amazon.com has launced a new campaign for this holiday season that I have decided to call, “Frustration Free Packaging” for lack of a better name. I suspect that Amazon has been working on this project for much longer than a few months, but I think they are still missing the point.
In the Super-size-me lifestyle of Americans, we are used to seeing beautifully packaged products lining the shelves of mega-stores like Walmart or Target. These products are packaged in their see-thru plastic clamshells and self advertising displays, enticing children and adults to just pick one up.
This is because the manufacturers have learned not to trust the stores to do the selling anymore. This is just hilarious. We don’t call the employees at these stores, “sales people”, we call them “team members”. They don’t do sales, they are just members lurking on the premises.
Thus, manufacturers have come up with clever ways to incorporate their sales pitch on the product packaging. Adding words like “NEW!” and “Now with Laser Guided Missles!”, or even “As Seen On TV”. They are telling you, the customer, “Don’t ask the store for information, go online or watch our ad on TV instead”.
The paradox with this of course, is that unlike at the superstores, the packaging does not sell the products on Amazon.com. Nobody ever sees the box until they receive the product at home. It wouldn’t affect Amazon’s sale if they shipped every product in a plain brown box. Of course, I’m not saying to put everything in a plain brown box – and I bet most of the product description on Amazon comes straight off the boxes any ways.
In this culture of decreasing population of professional retail persons, we have come to rely heavily on highly complicated product packaging. This has forced a burden on consumers, which end up with product packaging that is hard to open, difficult to wrap, and impossible to recycle. Amazon, seems to be taking a step in the right direction, but I wonder if they will be able to keep on track and not get askewed into some stupid marketing scheme.