search for: 0password

Hi List, I just updated an old sendmail installation to a modern postfix/dovecot system with mysql backend. Everything works fine but SMTP-AUTH fails with some clients. The problem is, that with PLAIN (old) clients send the base64 coded form: USERNAME\0USERNAME\0PASSWORD which, as i understand dovecot interprets as MASTERUSER\0USERNAME\PASSWORD. New clients send \0USERNAME\0PASSWORD which works fine. I don`t like to use masterusers, because then everyone would be able to log in as someone else. When i don`t have a passdb with master=yes in my dovecot.conf, Doveco...

...I'm working on "avelsieve" SqurrelMail plug-in to implement SIEVE "file" back end for dovecot. 1. My be someone my explain me, how to use client auth socket to authenticate against dovecot-auth unix socket. As fas as I understood login must be sent in form "user\0\user\0password" as base64 encoded string. pp code (I'm using socket used by postfix auth): -------------------- <?php $authstr = base64_encode('test at virtual.net\0test at virtual.net\0test'); $fp = fsockopen("unix:///var/spool/postfix/private/auth",0, $errno, $errstr, 30); if (!$f...

...and Outlook Express 6, authentification always fails. Turning on the Dovecot auth debug on reveals the reason: Dovecot SASL expects, in accordance with the standards, the following format of the SMTP AUTH command (using the PLAIN auth mechanism): AUTH PLAIN base64_encode("username\0username\0password") whereas the M$ clients send as the second argument only base64_encode("username\0password"), which naturally leads to authentification failure. Postfix apparently does not play any role in this game, as it simply passes the received command arguments to dovecot. Before I start ha...

On Apr 10, 2015, at 12:14 AM, Steffen Kaiser <skdovecot at smail.inf.fh-brs.de> wrote: > pass"word > > is no atom and Dovecot should reject it. No, not passwords should be rejected. > Maybe the former version did not checked the atoms 100% RFC conform. Where is the definition that passwords have to be atomic? And if it is there, it should be changed. Nothing anywhere at

...cotSASL and so made the changes mentioned there, also setting auth_mechanisms = plain login in conf.d/10-auth.conf . With this setup, we're able to use AUTH LOGIN method on an SMTP session, but using AUTH PLAIN fails. What we receive in the SMTP session is: auth plain `echo -e -n `\0user\0password' | mimencode` 535 Incorrect authentication data (it's actually the output of that command that we put there), and in the dovecot log we see: 2012-05-24 15:04:20 auth: Debug: client in: AUTH 1 PLAIN service=smtp secured rip=127.0.0.1 lip=127.0.0.1 nologin resp=<h...

I'm trying to use Dovecot SASL with postfix 2.3.3 and when trying to send mail I get the debug output below. I don't know enough about whats going on to know where the problem is but something clearly is not right. I would send the configurations for postfix and dovecot except they are clearly talking to each other so I kinda doubt its a configuration issue. The machine can afford to be

...+OK pass password -ERR Authentication failed. (i can successfully find this auth trial and fail on 10.254.116.9 logs) but on SMTP authentication, i have: [root at correio dovecot]# perl -MMIME::Base64 -e \ 'print encode_base64("teste\@proxieddomain.com.br\0teste\@proxieddomain.com.br\0password");' xxxxxxxxx(not the real encoded pass)xxxxxxxxxxxxxxxx= [root at correio dovecot]# [root at correio dovecot]# telnet localhost 587 Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'. 220 mail.domain.com.br ESMTP EHLO test 250-mail.domai...

Hello list, my name is Steven and of course: I got a problem... we are using dovecot 0.99 because it?s the actual stable version for RedHat 4 Enterprise. I am trying to authenticate using "PLAIN" but I don?t know how. that?s what I am doing: telnet conny.MYDOMAIN.de 143 Trying IP.AD.RE.SS... Connected to conny.MYDOMAIN.de. Escape character is '^]'. * OK dovecot ready. a1

...o both postfix and dovecot have read/write access to the socket. the credentials sent are the same whether they're sent via a true pop3 client or via the command line. when sent via the command line, they're generated via perl -MMIME::Base64 -e 'print encode_base64("\0username\0password");'and i've verified they're correct via decode_base64 config stuff: # postconf -n biff = no command_directory = /usr/sbin config_directory = /etc/postfix content_filter = smtp-amavis:[127.0.0.1]:10024 daemon_directory = /usr/libexec/postfix debug_peer_level = 2 enable_server_...

...e : /etc/dovecot/conf.d/10-master.conf unix_listener /var/spool/postfix/private/auth { mode = 0660 user = postfix group = postfix } - login to your server, port 465, with a client like openssl : openssl s_client -connect mail.example.org:465 EHLO whateveryouwant AUTH PLAIN \0root\0password (in base 64, ofc) You should be able to login, and produce the first log trace I have included. My question is, is this a feature or a bug ? The hardcoded impossibility to login as root to dovecot, and the honouring of the variables {first,last}_valid_{u,g}id, are those specific to login to d...