verifica in syslog pe masina cu cyrus ce zice de lmtp.
On Tue, 2003-07-29 at 11:58, Serghei Amelian wrote:
> On Tuesday 29 July 2003 14:29, Cristian Mitrana wrote:
> > Serghei Amelian wrote:
> > > On Tuesday 29 July 2003 09:33, Alexandru N. Barloiu wrote:
> > >>On Tue, 2003-07-29 at 09:30, Serghei Amelian wrote:
> > >
> > > Cum naiba transform fisierul lmtp_sasl_pass in lmtp_sasl_pass.db?
> > > Exista vreun utilitar? In main.conf am bagat asa:
> > >
> > > lmtp_sasl_auth_enable = yes
> > > lmtp_sasl_password_maps = hash:/etc/postfix/lmtp_sasl_pass
> > > lmtp_sasl_security_options = noanonymous
> >
> > Poti sa lasi fisierul chior, si nu mai ai nevoie sa scoti un *.db.
> > lmtp_sasl_password_maps = [file:]/etc/postfix/lmtp_sasl_pass
> >
> > mitu
>
> Eh, a mers si cu postmap. Acum am alta porcarie de care m-am mai lovit, da'
> rezolvarea e numai prin incercare si eroare :-(
>
> Urasc mesajele idioate care nu dau nici o informatie:
>
> delay=0, status=deferred (Authentication failed: cannot SASL authenticate to
> server blabla: no mechanism available)
>
> Nu zice ce mecanism incearca sa foloseasca, unde anume cauta pluginul, etc.
>
> in /usr/lib exista libsasl2.so.2, iar in /usr/lib/sasl2 este libplain.so.2 si
> libplain.so. Pe masina Cyrus, SASL este compilat doar cu pam si plain, deci
> teoretic nu ar trebui sa fie incompatibilitati.
>
> postconf zice:
>
> postconf -n | grep sasl
> lmtp_sasl_auth_enable = yes
> lmtp_sasl_password_maps = hash:/etc/postfix/lmtp_sasl_pass
> lmtp_sasl_security_options = noanonymous
> smtp_sasl_security_options = noanonymous
>
> Aveti idee, postfix incearca sa foloseasca alt mecanism de autentificare decat
> plain? Din cate stiu eu, daca nu exista noplaintext pe nicaieri nu ar trebui
> sa faca urat.
--
Alexandru N. Barloiu <[EMAIL PROTECTED]>
Dale Media
