Benches Security

14

Security Update 2008-002 and Mail Services on O...

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

A word of caution before applying Security Update 2008-002 to OS X Server 10.4.11:

According to this document:
http://docs.info.apple.com/article.html?artnum=307562
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

HTH,
Alex

14 replies

Sign in or join Beachball Help to reply.

  1. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Thanks Alex for all the support you provide to the community!

    I assume we fall in the later, spamassasin and amavisd have been manually changed.

    Is it safe to back up the files that you point to then reinstate them after the update, of is there also a risk that the software components will be over written and require re-installation of the versions currently running?

    Thanks

  2. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Mark,

    just make a backup of the config files and /usr/bin/amavisd and restore after the update. That should be enough.

    Alex

  3. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Any effect on Leopard?

  4. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    No.

  5. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Thanks Alex.

    Interestingly in my case it seems that /etc/spam/clamav/clamd.conf and /etc/spam/clamav/freshclam.conf have changes in them.

    clamd.conf used to be all commented out before installing the security update, where as now I have logFile and PidFile defined, either that or I pulled the wrong file from the backup.

    freshclam.conf has a lot more configuration parameters included and enabled in it.

  6. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Help! I downloaded this update just tonight and when I tried to restart my machine I can't get past the start up screen Mac OS X...Starting Mac OS X with the blue bar. The blue bar loads but doesn't take me to my desktop...1½ hours later, it's still there. I know things load slowly after updates, but what do I do??????

    THANKS!

  7. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Alex,

    I ran the update and then copied back my Spamassassin and amavisd configurations. But when I checked my ClamAV settings, they still showed version 91.2 rather than 92.1. So, I decided to manually update them as I had done previously using your handout.

    Unfortunately, I get an error at the configure step. The error is that my gcc has bug PR28045. The only changes to my 10.4.11 Server setup have been based on your helpful guidelines. In your judgement, is it okay to try and update my gcc through cpan or similar method, or should I leave ClamAV alone.

    Regards,
    Brian Tully

  8. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Brian,

    I assume you have an Intel CPU and have not downloaded the most recent version of my ClamAV tutorial, correct?

    If yes, get the latest version which addresses this: http://osx.topicdesk.com/content/view/62/62/
    (Need a different config string for Intel as of ClamAV 0.92.x)

    HTH,
    Alex

  9. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Thanks pterobyte for Your support,

    I have update 2008-002 last week, I never updated ClamAV, spamassassin or amavisd manually,
    and check / reload personalized settings after installation.

    The system has worked very fine in the last days, but today I have had postfix queue with more messages not delivered and following error:

    host 127.0.0.1[127.0.0.1] said: 451 4.5.0 Error in processing, id=01334-01, virus_scan FAILED: virus_scan: ALL VIRUS SCANNERS FAILED: ClamAV-clamd av-scanner FAILED: Too many retries to talk to /var/clamav/clamd.sock (Can't connect to UNIX socket /var/clamav/clamd.sock: No such file or directory) at (eval 42) line 266.; ClamAV-clamscan av-scanner FAILED: /usr/local/bin/clamscan unexpected exit 50, output="ERROR: Can't initialize the virus database" at (eval 42) line 435. (in reply to end of DATA command)

    I have tried with unload/load amavisd and reload postfix,
    not launch mailbfr to fix db , I was losing too much time and for productivity reasons I have temporary reload prev backup of 2008-002.

  10. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    ClamAV-clamd av-scanner FAILED: Too many retries to talk to /var/clamav/clamd.sock

    Apple's standard configuration for amavisd on Tiger does not try to talk to clamd. So you must have changed something. At the very least you tried to enable this in amavisd.conf

    mailbfr -f will fix the cyrus database and has absolutely nothing to do with postfix or content filter problems. It should not be used unless you have db issues.

  11. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Alex,

    You are correct, Intel and I had version 1.08 of your manual. Unfortunately, even though I ran the configure with the new settings, I got the same error. My only variance from your instructions was to use ClamAV 92.1 rather than 92. Any other ideas?

    Thanks again,

    Brian

  12. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Brian,

    the latest version of the tutorial is 1.1.2.

    Before going through it, you should delete any older clamav sources in /SourceCache

    Just to be clear, you also need to make sure gcc 4 is selected and use this configure string:
    CFLAGS="-O0" ./configure --prefix=/usr/local --mandir=/usr/share/man --sysconfdir=/private/etc/spam/clamav/new --disable-shared --enable-bigstack --with-user=clamav --enable-static --with-group=clamav --with-dbdir=/var/clamav --with-datadir=/var/clamav

    HTH,
    Alex

  13. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Alex,

    I deleted everything out of the /SourcCache folder and then ran the command using gcc 4.0 as root. Unfortunately, I got the same error.

    Could some of the prerequisites/updates I did for amavisd cause this problem? Is it prudent to update gcc using cpan, that is if one exists?

    Thanks again for your help,

    Brian Tully

  14. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Brian,

    Could some of the prerequisites/updates I did for amavisd cause this problem

    Highly unlikely.

    Is it prudent to update gcc using cpan, that is if one exists?

    CPAN is for updating PERL modules. You can't update gcc through it. That said, there is no need to update gcc.

    -

    Mail me your complete terminal session if you like and I'll have a look.

    Alex