[BlueOnyx:25903] Re: OpenDKIM support for BlueOnyx 5210R released

[Michael Stauber]

Hi all,

OpenDKIM support has now been released to the YUM repositories of 
BlueOnyx 5210R as well.

Special note to AV-SPAM users on BlueOnyx 5210R:
==================================================

If you use the AV-SPAM Package on BlueOnyx 5210R, then please make sure 
to install all YUM updates. The AV-SPAM YUM repository has a new RPM 
that hotfixes some problems with the generation of sendmail.mc and 
sendmail.cf that include both the AV-SPAM as well as the OpenDKIM milter 
provisions. The combination of AV-SPAM + OpenDKIM works fine ou of the 
box if Postfix is the MTA, but if your MTA is still sendmail, you need 
all YUM updates to be installed to get the Sendmail related hotfix.

Additionally: AV-SPAM 7.1.17-1 for BlueOnyx 5210R has just been 
released. This already includes all fixes and will work fine on BlueOnyx 
5210R in conjunction with OpenDKIM.

Additional info (technical, just for the record):

In the past the AV-SPAM used to rotate in a special sendmail.mc template 
whenever you enabled/disabled one of the AV-SPAM services. A handler 
then used GUI methods to edit the sendmail.mc to insert the AV-SPAM 
milters of activated services and finally a sendmail.cf was built.

As the AV-SPAM managed only its own milters, this naturally would drop 
the OpenDKIM milter settings from sendmail.mc that the OpenDKIM update 
brought with it.

Therefore the OpenDKIM implementation changed the whole milter handling 
for Sendmail: Like we do with Postfix related milters 
(/etc/postfix/milters.d) there is now a new directory for Sendmail 
Milters: /etc/mail/milters.d/ into which milter config file snippets can 
be stored. If present, the GUI will take these into account and will 
integrate these snippets into sendmail.mc and sendmail.cf on GUI 
triggered rebuilds of these.

A hotfix RPM was released to the AV-SPAM YUM repository to make older 
AV-SPAM installs compatible with this new feature. Likewise: A new 
AV-SPAM (v7.1.17-1) was just released to NewLinQ, which already has 
these fixes implemented.

-- 
With best regards

Michael Stauber