Re: local.cf / Vendor code error ?

After I loaded the 10_recommended on the machine, the Vendor Code
error disappeared
and I have the second sendmail process.

bash-3.00# ps -ef | grep send
smmsp 442 1 0 07:40:16 ? 0:00 /usr/lib/sendmail -
Ac -q15m
root 441 1 0 07:40:16 ? 0:00 /usr/lib/sendmail -
bd -q15m -C /etc/mail/local.cf

When I run my little tripwire script to test the mailer, everything is
stuck in /var/spool/mqueue:

-rw------- 1 root smmsp 879 Dec 18 08:00 qflBIFeGfH000446
-rw------- 1 root smmsp 896 Dec 18 08:00 qflBIFeGfL000446
-rw------- 1 root smmsp 900 Dec 18 08:00 qflBIFs0js000654

but I saw a thread for that somewhere here.

Thanks.

Re: local.cf / Vendor code error ?

In article
<26dbf166-63b3-490f-986c-6d45e1db78c0@l32g2000hse.googlegroups.com>,
Gromit Wallace wrote:

> After I loaded the 10_recommended on the machine, the Vendor Code
> error disappeared
> and I have the second sendmail process.

The vendor code warning was a sign that you were using a non-Sun
sendmail binary with a Sun cf file, and that is not a workable
combination. Sun customizes their binary and uses that vendor code in
the cf file to make suure that the mistake of mixing Sun and non-Sun
Sendmail is noisy.

This sounds suspiciously as if you installed your own build of Sendmail
without removing Sun's Sendmail packages first. When you applied the
standard recommended patch cluster, it saw those packages as still being
installed and happily overwrote your Sendmail binary with the latest Sun
version. That leaves your system in a state that is hard to know, and
probably not worth trying to figure out. Your best options to clean
things up would be:

1. Remove, reinstall, and repatch the Sun Sendmail packages and live
with the Sun variant.

2. Remove the Sun Sendmail packages and rebuild your own version from
the standard source distribution.

--
Now where did I hide that website...