-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 DEBO Jurgen E. G. wrote: > <snip> > > First, I suggest You verify Your authentication. Start-tls is initiated, > in that case the pasword has to be plain-text, not cram. >
First off, starttls is not initiated, as then he would have had to enter starttls to start it in the first place. Second, auth login takes a base 64 username and base 64 password which he supplied. Dont trust me on that? Please read the RFC's for it. If he was using cram-md5 he wouldnt have issued a AUTH LOGIN. He would have issued a AUTH CRAM-MD5. - ------------------------------------------------------------------------ Anyways, id like to second anything the thread starter said. I have been on the system myself (not like that matters, i know), but he has read all the documentation, and anything there is to know about SMTP auth, so its not a mistake some place. For some reason something is going wrong some place, and i am thinking it could be in the base64.c file, however i have no clue most of it. I highly doubt its vchkpw as vchkpw gets handed just the info it needs, and works with pop3, so it _should_ work with smtp auth as well. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFAsTt9JukONu5DUaQRAkJaAJ9qSXy95Cej2AMBedJ9ohKKI51nHgCfcvpM 708uHSBbjo65tOpLZSRhabY= =JDLs -----END PGP SIGNATURE-----
