Date:  Sat, 25 Mar 2006 00:07:35 +0900
From:  Hisao SHIBUYA <shibuya (at mark) alpha.or.jp>
Subject:  [coba-e:04347] Re: Critical: sendmail security update
To:  coba-e (at mark) bluequartz.org
Message-Id:  <DBA7A153-F0CF-49F6-B3F4-A36CE5606225 (at mark) alpha.or.jp>
In-Reply-To:  <Pine.LNX.4.64.0603241144230.31229 (at mark) spund.office.eastlink.de>
References:  <009d01c64e2a$c8ae58e0$2701a8c0 (at mark) cyberec> <BFFE5BC8-ABF1-429C-8049-5AC9C35FA2F6 (at mark) alpha.or.jp> <4F121F04-FD43-40E8-ACE2-EC1EDD0DF7D1 (at mark) alpha.or.jp> <9BEFA987-E2FA-42A5-B837-CA806F6E7C78 (at mark) alpha.or.jp> <Pine.LNX.4.64.0603241144230.31229 (at mark) spund.office.eastlink.de>
X-Mail-Count: 04347

Hi,

>> I release sendmail update for CentOS3 and CentOS4.
>> You can update with 'yumm update' from BlueQuartz repository.
>
> could you please explain, what is the difference between the  
> upstream sendmail package and the one out of the Bluequartz  
> repository? I mean, what did you change in the customized package?

I customize the following items.
- add popauth.m4 for poprelayd
- change path for aliases to /etc/mail/aliases instead /etc/aliases
- change /etc/pam.d/smtp.sendmail for BlueQuartz with pam_pwdb.so
- change sendmail.mc and sendmail.cf for BlueQuartz

I already remove these customize from original package om CVS, but I  
had problem
to replace original package from BlueQuartz's package. The aliases  
was removed
and replace sendmail.mc and sendmail.cf, so I made customized package  
for this
update.

I want to use original package for BlueQuartz with BlueQuartz  
configuration file.
But, it is little difficult to keep BlueQuartz configuration for update.

Hisao