>Засада какая-то :(
>
>добился
>
>egrep TrustAuthMech /etc/mail/sendmail.cf
>
>C{TrustAuthMech}LOGIN PLAIN
>R$* $| $={TrustAuthMech} $#RELAY
>
>egrep AuthMechanisms /etc/mail/sendmail.cf
>
>O AuthMechanisms=LOGIN PLAIN
>
>Все равно 250-AUTH не появляется. Что ему щас то не нравится?
>
>на AUTH выдает 503 authentication not enabled. В логах никаких ругательств ни
>от сасла ни от сендмыла. если сам SENDMAIL собран с поддержкой SASLv2,
то осталось ПРАВИЛЬНО собрать sendmail.cf из sendmail.mc
общее правило сборки sendmail.cf из sendmail.mc используя препроцессор m4:
#!/bin/sh
#--lavr define CF_DIR PATH
SENDMAIL_CF_DIR="/usr/share/sendmail/cf"
#--lavr define path to m4
M4="/usr/bin/m4"
${M4} -D_CF_DIR_=${SENDMAIL_CF_DIR}/ ${SENDMAIL_CF_DIR}/m4/cf.m4 $1 > $2
все это расписано в документации sendmail, /path/sendmail_sources/cf/README:
...
...
+--------------------------+
| INTRODUCTION AND EXAMPLE |
+--------------------------+
Configuration files are contained in the subdirectory "cf", with a
suffix ".mc". They must be run through "m4" to produce a ".cf" file.
You must pre-load "cf.m4":
m4 ${CFDIR}/m4/cf.m4 config.mc > config.cf
Alternatively, you can simply:
cd ${CFDIR}/cf
./Build config.cf
where ${CFDIR} is the root of the cf directory and config.mc is the
name of your configuration file. If you are running a version of M4
that understands the __file__ builtin (versions of GNU m4 >= 0.75 do
this, but the versions distributed with 4.4BSD and derivatives do not)
or the -I flag (ditto), then ${CFDIR} can be in an arbitrary directory.
For "traditional" versions, ${CFDIR} ***MUST*** be "..", or you MUST
use -D_CF_DIR_=/path/to/cf/dir/ -- note the trailing slash! For example:
m4 -D_CF_DIR_=${CFDIR}/ ${CFDIR}/m4/cf.m4 config.mc > config.cf
...