[Mimedefang] Don't know what happened

[Brad Tarver]

I set confMILTER_LOG_LEVEL to 21. The other things you suggested were
already set. I even recompiled MD with the debugging flag. I still don't
get any indications as to why MD won't start.

This is bad...

Is there a way to test from the command line other than 'service
mimedefang start' to get see errors?



-----Original Message-----
From: mimedefang-bounces at lists.roaringpenguin.com
[mailto:mimedefang-bounces at lists.roaringpenguin.com] On Behalf Of
Alexander Dalloz
Sent: Monday, January 05, 2004 9:41 PM
To: mimedefang at lists.roaringpenguin.com
Subject: Re: [Mimedefang] Don't know what happened


Am Di, den 06.01.2004 schrieb Brad Tarver um 02:22:
> But now MD won't even start. What can I set in 
> /etc/sysconfig/mimedefang or /etc/init.d/mimedefang to tell MD to log 
> startup/crash errors?
> 
> Any help would be greatly appreciated as my company depends heavily on

> MD's functionality.
> 
> Running RH9, sendmail-8.12.8-9.90 (RPM), kernel-smp-2.4.20-27.9 (RPM),

> MD 2.39, and SA 2.61.
> 
> Dual Xeon 700, 3.5GB ram.
> 
> Thanks,
> BT

In /etc/sysconfig/mimedefang:

# Set to the syslog facility.  Also set $SyslogFacility in your filter
SYSLOG_FACILITY=mail

# Set to yes if you want the multiplexor to log events to syslog
MX_LOG=yes

In /etc/mail/sendmailmc:

define(`confMILTER_LOG_LEVEL', `6')dnl

Rebuild the sendmail.cf afterwards and restart mimedefang and sendmail.

(I have exactly same software situation here, only no smp system, and
all is working great.)

Alexander


-- 
Alexander Dalloz | Enger, Germany
PGP key valid: made 13.07.1999
PGP fingerprint: 2307 88FD 2D41 038E 7416  14CD E197 6E88 ED69 5653