[Mimedefang] problem with mimedefang: fails

[Ramón Alvarez Rayo]

hello,

i was revised every steps of the setup and it is ok,

Jun 10 16:26:12 ns sendmail[15586]: h5ALQCoa015586: Milter (mimedefang): to 
error state
Jun 10 16:26:12 ns sendmail[15586]: h5ALQCoa015586: Milter: initialization 
failed, temp failing commands
Jun 10 16:26:12 ns sendmail[15608]: h5ALQCoa015608: Milter (mimedefang): 
error connecting to filter: Connection refused by 
/var/spool/MIMEDefang/mimedefang.sock

also i'm getting the following messages:
Jun 10 16:28:41 ns sendmail[15802]: h5ALREq5015802: collect: premature EOM: 
unexpected close
Jun 10 16:28:41 ns sendmail[15802]: h5ALREq5015802: collect: unexpected 
close on connection from enitelinfvpn.tmx.com.ni, sender=<mitsui at ota.com>

my parameters in rc2.d/S90mimedefang are the followings:
# If you want the multiplexor, you need to uncomment this line
MULTIPLEXOR=yes

# Run the multiplexor and filters as this user, not root.  RECOMMENDED
MX_USER=mimedefang

# Syslog facility
SYSLOG_FACILITY=mail

# If you want to keep spool directories around if the filter fails,
# set the next one to yes
# KEEP_FAILED_DIRECTORIES=no

# The following apply only to the multiplexor and are used only when
# the MULTIPLEXOR variable is 'yes'

# "yes" turns on the multiplexor relay checking function
# MX_RELAY_CHECK=no
MX_RELAY_CHECK=yes

# "yes" turns on the multiplexor sender checking function
# MX_SENDER_CHECK=no
MX_SENDER_CHECK=yes

# "yes" turns on the multiplexor recipient checking function
# MX_RECIPIENT_CHECK=no
MX_RECIPIENT_CHECK=yes

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

# The multiplexor does not start all slaves at the same time.  Instead,
# it starts one slave every MX_SLAVE_DELAY seconds when the system is idle.
# (If the system is busy, the multiplexor starts slaves as incoming mail
# requires attention.)
# MX_SLAVE_DELAY=3
MX_SLAVE_DELAY=5

# The next setting is an absolute limit on slave activation.  The multiplexor
# will NEVER activate a slave within MX_MIN_SLAVE_DELAY seconds of another.
# The default of zero means that the multiplexor will activate slaves as
# quickly as necessary to keep up with incoming mail.
# MX_MIN_SLAVE_DELAY=0
MX_MIN_SLAVE_DELAY=0

# Set to yes if you want the multiplexor to log stats in
# /var/log/mimedefang/stats
# MX_STATS=no
MX_STATS=yes

# Set to yes if you want the stats file flushed after each entry
# MX_FLUSH_STATS=no

# Set to yes if you want the multiplexor to log stats to syslog
# MX_STATS_SYSLOG=no

# The socket used by the multiplexor
MX_SOCKET=$SPOOLDIR/mimedefang-multiplexor.sock

# Maximum # of requests a process handles
# MX_REQUESTS=200

# Minimum number of processes to keep.  The default of 0 is probably
# too low; we suggest 2 instead.
MX_MINIMUM=10

# Maximum number of processes to run (mail received while this many
# processes are running is rejected with a temporary failure, so be
# wary of how many emails you receive at a time).  This applies only
# if you DO use the multiplexor.  The default value of 2 is probably
# too low; we suggest 10 instead
MX_MAXIMUM=60

# Uncomment to log slave status; it will be logged every
# MX_LOG_SLAVE_STATUS_INTERVAL seconds
# MX_LOG_SLAVE_STATUS_INTERVAL=30

# Limit slave processes' resident-set size to this many kilobytes.  Default
# is unlimited.
# MX_MAX_RSS=10000

# Limit total size of slave processes' memory space to this many kilobytes.
# Default is unlimited.
# MX_MAX_AS=30000

# Number of seconds a process should be idle before checking for
# minimum number and killed
# MX_IDLE=300

# Number of seconds a process is allowed to scan an email before it is
# considered dead.  The default is 30 seconds; we suggest 300.
MX_BUSY=300

# SUBFILTER specifies which filter rules file to use
SUBFILTER=/usr/local/mimedefang/mimedefang-filter

what can i do? where is the problem ?

any help will be apreciated.

thanks

RA