hello sorki ze ciagle sie wlecze ten temat ale czy Tobie to ruszylo ? po zastosowaniu tych zmian ?? bo ja probowalem na ten sposob i ze swoja sciezka do saslauthd... i nadal mam problemy z autoryzacja :( moze masz jakis przepis na to ? swoj wedlog ktorego robiles smtp_auth ??
co powinno znajdowac sie w pliku /etc/sasldb2 ?? w logach mam: Apr 19 22:39:04 wena postfix/master[20061]: reload configuration Apr 19 22:39:09 wena postfix/smtpd[1629]: connect from vl198.neoplus.adsl.tpnet.pl[80.50.131.198] Apr 19 22:39:09 wena postfix/smtpd[1629]: warning: SASL authentication problem: unable to open Berkeley db /etc/sasldb2: No such file or directory Apr 19 22:39:09 wena postfix/smtpd[1629]: warning: SASL authentication failure: no secret in database Apr 19 22:39:09 wena postfix/smtpd[1629]: warning: vl198.neoplus.adsl.tpnet.pl[80.50.131.198]: SASL NTLM authentication failed Apr 19 22:39:36 wena postfix/smtpd[1629]: warning: vl198.neoplus.adsl.tpnet.pl[80.50.131.198]: SASL NTLM authentication failed Apr 19 22:39:38 wena postfix/smtpd[1629]: warning: SASL authentication problem: unable to open Berkeley db /etc/sasldb2: No such file or directory Apr 19 22:39:38 wena postfix/smtpd[1629]: warning: vl198.neoplus.adsl.tpnet.pl[80.50.131.198]: SASL LOGIN authentication failed Apr 19 22:39:39 wena postfix/smtpd[1629]: lost connection after AUTH from vl198.neoplus.adsl.tpnet.pl[80.50.131.198] Apr 19 22:39:39 wena postfix/smtpd[1629]: disconnect from vl198.neoplus.adsl.tpnet.pl[80.50.131.198] wczesniej w ogole sasl nie potrzebowal .db hmm pozdr. bieniu ----- Original Message ----- From: "Radoslaw Antoniuk" <[EMAIL PROTECTED]> To: "Debian-PL" <[email protected]> Sent: Thursday, April 17, 2003 11:07 AM Subject: Fw: postfix+sasl2 (postfix+tls package from testing distribiution - sarge) > ----- Original Message ----- > From: "LaMont Jones" <[EMAIL PROTECTED]> > To: "Rados?aw Antoniuk" <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > Sent: Thursday, April 17, 2003 5:01 AM > Subject: Re: postfix+sasl2 (postfix+tls package from testing > distribiution - sarge) > > > > On Thu, Apr 17, 2003 at 02:21:12AM +0200, Rados?aw Antoniuk wrote: > > > There's a bug in the _package_ and i would be grateful if you > fixed > > > that soon. > > > Firstly, the package should require libsasl2. But this is to be > > > discussed. > > > > No, it shouldn't. Not until there is a LDAP library that will allow > > me to link with both LDAP and SASL2. That is in progress, and > should > > happen sometime soon. Until then, we're stuck with SASL1. > > > > > Secondly, if we want to use saslauthd as the authentication > mechanism, > > > we should: > > > 1) make directories: > > > mkdir /var/spool/postfix/var > > > mkdir /var/spool/postfix/var/run > > > mkdir /var/spool/postfix/var/run/saslauthd > > > > > > 2) start saslauthd in the following way (for shadow): > > > saslauthd -a shadow -m /var/spool/postfix/var/run/saslauthd/mux > > > > > > 3) run smtp in chroot (in master.cf) NOT as described in all > howtos - > > > to change default to non-chrooted environment. > > > > > > I advise to change it in the packages because there are a lot of > > > people trying to set up this configuration and it took us a week > to > > > get to the point , what were the dependencies and why do we have > > > "cannot connect to saslauthd" message in logs. > > > > I'll be looking into the whole sasl and TLS install situation in the > > near future. > > > > lamont > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] >
