[CentOS] mail server best practices question

Mon May 10 20:30:19 UTC 2010
Les Mikesell <lesmikesell at gmail.com>

On 5/10/2010 2:51 PM, Benjamin Franz wrote:
> On 05/10/2010 11:37 AM, Ralph Angenendt wrote:
>> Am 10.05.10 13:01, schrieb Coert:
>>
>>> Hello all,
>>>
>>> About a year ago I set up a mail server on CentOS using this howto:
>>> http://wanderingbarque.com/howtos/mailserver/mailserver.html
>>> I managed to add amavisd-new with clamav and spamassassin.
>>> It runs very well, but it runs on CentOS 5.2, and if I try to upgrade,
>>> amavisd-new and clamav break.
>>>
>> Oh please don't say what happens. If you use amavisd-new and clamav from
>> rpmforge (or from epel), they don't break when updating. And please
>> don't tell me you ran clamav non-updated since CentOS 5.2 - it had
>> several security issues since then.
>>
> Actually, they do (break when updating, that is).
>
> The problem is at least one of the packagers for clamd/amavisd-new
> blindly overrides the path to clamd.sock by overwriting the config file
> leaving the two out-of-sync (and so unable to function).
>
> It is easily fixed by resetting the path - but you do have to watch out
> for it on upgrades.

Is this a result of having multiple uncoordinated 3rd party repositories 
enabled during an update and flipping repositories as the version 
numbering jumps (more or less expected behavior...) or are you saying 
that a single packager flipped the format in an incompatible way?

-- 
    Les Mikesell
     lesmikesell at gmail.com