Am 22.03.2014 21:47, schrieb Anonymous12:
>>>>>> package: libsasl2-modules >>>>>> This package provides the following SASL modules: LOGIN, >>>>>> PLAIN, ANONYMOUS, NTLM, CRAM-MD5, and DIGEST-MD5 (with DES support) >>>> >>>> ok, you are even too lazy to read what others googled for you >>>> just install libsasl2-modules >>>> >>>>> This is list of packages installed (Which might be useful to know): >>>>> >>>>> root@vps44713:~# cat list.txt >>>>> libmail-sendmail-perl install >>>>> libmail-spf-perl install >>>>> libmailtools-perl install >>>>> mail-stack-delivery install >>>>> postfix install >>>>> dovecot-imapd install >>>>> dovecot-managesieved install >>>>> dovecot-pop3d install >>>>> dovecot-sieve install >>>> >>>> a obscure list with no relevance to SASL and even missing >>>> the already statet "libsasl2-2 is already the newest version" >>>> >>>> please re-consider if you really have the basic knowledge >>>> to maintain a MTA - this is a job with *high* responsibility >>> >>> Allright then. Pastebin => http://pastebin.com/924Pyrru >> >> no need for that - grep exists >> "command | grep -i sasl" is what i expect from a sysadmin >> >> *when* have you installed "libsasl2-modules"? >> *did you* restart postfix after that, if not why? >> did you retry? >> what is the content of "/etc/postfix/sasl_passwd"? >> what is the current output of "telnet localhost 25" followed be EHLO? > > root@vps44713:~# cat list.txt | grep -i sasl > libsasl2-2 install > libsasl2-modules install > php-auth-sasl install looks good > root@vps44713:~# cat list.txt | grep -i dovecot > dovecot-core install > dovecot-imapd install > dovecot-managesieved install > dovecot-pop3d install > dovecot-sieve install > > root@vps44713:~# cat list.txt | grep -i mail-stack > mail-stack-delivery install not relevant for postfix client SASL > I have no clue when i have installed "libsasl2-modules" well, the intention of my first post was to get informations which sasl relevant packages are installed so anybody using Ubuntu can work with them, the rdhat packages where an example because my systems are redhat-based > I think that it was automatically installed as requiment. > > Contents of: "/etc/postfix/sasl_passwd": > > root@vps44713:~# cat /etc/postfix/sasl_passwd > # destination credentials > [mail.riseup.net]:587 user:pass looks good, needs to bex *exactly* written like the relayhost which is the case > Real ones got replaced with user:pass. > > Telnet to localhost 25: > 220 example.com ESMTP Postfix > ehlo localhost > 250-example.com > 250-PIPELINING > 250-SIZE 10240000 > 250-VRFY > 250-ETRN > 250-STARTTLS > 250-ENHANCEDSTATUSCODES > 250-8BITMIME > 250 DSN > > Does that answer the questions? i hoped to get the AUTH mechs supported but maybe you also enabled auth only via SSL in one of your previous posts you wrote >> OS is debian based. >> 250-AUTH LOGIN PLAIN >> 250-AUTH=LOGIN PLAIN the problem is that there is no CRAM-MD5 and most likely the other side does not like PLAIN but since you are using "smtpd_sasl_type = dovecot" it does not matter what your smtpd supports because different authentication libraries are used ____________________________________________ break: openssl s_client -starttls smtp -crlf -connect mail.riseup.net:587 shows after the SSL stuff and the "EHLO command" that the other host supports LOGIN / PLAIN, so i am somehow out of ideas did you *really* restart postfix and try again send a new message? while doing so please post the *complete log* of the trensaction 250 DSN EHLO test 250-fruiteater.riseup.net 250-PIPELINING 250-SIZE 25600000 250-ETRN 250-AUTH LOGIN PLAIN 250-AUTH=LOGIN PLAIN 250-ENHANCEDSTATUSCODES 250-8BITMIME 250 DSN
