similar to: Using Dovecot SASL with postfix

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

I'm working on getting authentication for Postfix smtpd clients working with Dovecot. I've got both plain text and GSSAPI mechanisms working. Winbind also works for shell access and the command line test work fine. If I can get NTLM authentication working I can use Postfix as a drop in replacement for a MS MTA I want get rid of. I'm hoping the community might be able to offer some

I'm working on getting authentication for Postfix smtpd clients working with Dovecot. I've got both plain text and GSSAPI mechanisms working. Winbind also works for shell access and the command line test work fine. If I can get NTLM authentication working I can use Postfix as a drop in replacement for a MS MTA I want get rid of. I'm hoping the community might be able to offer some

Good day Folks, I am trying to setup a mail server based on dovecot(with imap and pop3) and postfix as a smtp on debian jessie/sid. The login its system user. After I have tried to configure the client (Icedove), this last can find the imap, pop3 and smtp servers; but the can't be verified. Please see below my dovecot, postfix configurations and log details. erickom at ajk:/etc/postfix$

Hi, can anyone tell me where these "unknown users" come from. As far as I see the fact, dovecot is asked by postfix to look for the password of the recipient-user (why ever). +++ Jan 7 19:43:09 f42252se postfix/smtpd[14625]: initializing the server-side TLS engine Jan 7 19:43:09 f42252se postfix/tlsmgr[14627]: open smtpd TLS cache btree:/var/lib/postfix/smtpd_scache Jan 7 19:43:09

Because cram-md5 needs the user's password for calculating responses, it cannot work with hashed passwords (one-way encrypted). The only supported password schemes are PLAIN and CRAM-MD5. Aki On 01.02.2017 09:33, Poliman - Serwis wrote: > I always restart dovecot after change config. ;) Sure, I commented out > added two lines by me, restarted dovecot and here it is: > > # 2.2.9:

On 01.02.2017 08:18, Poliman - Serwis wrote: > This is debug log files in syslog: > Feb 1 07:10:25 vps342401 dovecot: auth: Debug: client passdb out: > CONT#0112#011PDAxODg3ODIzMTUwMzgxNzMuMTQ4NTkyOTQyNUB2cHMzNDI0MDEub3ZoLm5ldD4= > Feb 1 07:10:26 vps342401 dovecot: auth: Debug: client in: CONT<hidden> > Feb 1 07:10:26 vps342401 dovecot: auth-worker(27069): Debug: sql( >

You are probably wanting to do passdb { driver = passwd-file args = scheme=cram-md5 /etc/dovecot/cram-md5.pwd } passdb { driver = sql args = /etc/dovecot/dovecot-sql.conf } Why you want to use cram-md5 is beyond me, because using SSL is much more safer. Aki On 01.02.2017 09:41, Poliman - Serwis wrote: > Default it was: "auth_mechanisms = plain login" and I added cram-md5.

Are you still trying to authenticate using cram-md5? Aki On 01.02.2017 09:51, Poliman - Serwis wrote: > It still use: > passdb { > driver = passwd-file > args = scheme=cram-md5 /etc/dovecot/cram-md5.pwd > } > > When I delete above and delete "cram-md5" in auth_mechanisms it still not > working. > > 2017-02-01 8:45 GMT+01:00 Aki Tuomi <aki.tuomi at

Can you check your logs? Aki On 01.02.2017 10:02, Poliman - Serwis wrote: > When I used backup copy of the dovecot.conf file I have this same error. So > I think that maybe something was written to database? I really would point > out that I only added > passdb { > driver = passwd-file > args = scheme=cram-md5 /etc/dovecot/cram-md5.pwd > } > > and comment out from

doveadm log errors can be helpful too On 01.02.2017 10:25, Poliman - Serwis wrote: > I can check each logs, I have root privileges. > > 2017-02-01 9:04 GMT+01:00 Aki Tuomi <aki.tuomi at dovecot.fi>: > >> Can you check your logs? >> >> Aki >> >> >> On 01.02.2017 10:02, Poliman - Serwis wrote: >>> When I used backup copy of the

I haven't doveadm logs in /var/log/. Are they default in another place or maybe should I turn on something? My config (default passdb block and auth_mechanisms, nothing more changed): root at vps342401:/etc/dovecot# doveconf -n # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.13.0-100-generic x86_64 Ubuntu 14.04.5 LTS auth_mechanisms = plain login listen = *,[::] log_timestamp = "%Y-%m-%d

This is debug log files in syslog: Feb 1 07:10:25 vps342401 dovecot: auth: Debug: client passdb out: CONT#0112#011PDAxODg3ODIzMTUwMzgxNzMuMTQ4NTkyOTQyNUB2cHMzNDI0MDEub3ZoLm5ldD4= Feb 1 07:10:26 vps342401 dovecot: auth: Debug: client in: CONT<hidden> Feb 1 07:10:26 vps342401 dovecot: auth-worker(27069): Debug: sql( do_not_reply at example.com,12.173.211.32): query: SELECT email as user,

Our new/fresh dovecot imap installation on CentOS (latest from yum repository, which is 2.2.10) is locking up with a panic on a consistent basis and denying service to subsequent clients. The behavior is repeatable. Have spent weeks debugging and trying different configurations with no success. Specific /var/log/maillog error messages are: 12:06:54 dovecot: auth: Error: talloc: access after

I always restart dovecot after change config. ;) Sure, I commented out added two lines by me, restarted dovecot and here it is: # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.13.0-100-generic x86_64 Ubuntu 14.04.5 LTS auth_mechanisms = plain login cram-md5 listen = *,[::] log_timestamp = "%Y-%m-%d %H:%M:%S " mail_max_userip_connections = 100 mail_plugins = " quota"

Hi! i hope that the right address. my problem is: i'm using a freebsd-server with postfix and sasl > pam to authentificate users via smtp_auth over a windows-pdc from the syslog, i get the message: User "Michael" granted access, also all wbinfo-command work, my e-mail-programm says: 435 error: authentification failed my debug.log tells me: group, endgrent, not found Apr 20

I haven't doveadm logs in /var/log/. Are they default in another place or maybe should I turn on something? My config (default passdb block and auth_mechanisms, nothing more changed): root at vps342401:/etc/dovecot# doveconf -n # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.13.0-100-generic x86_64 Ubuntu 14.04.5 LTS auth_mechanisms = plain login listen = *,[::] log_timestamp =

I'm trying to get NTLM authentication working with Dovecot to authenticate Postfix SMTP clients. I can authenticate postfix smtp clients using the plain text login mechanism through winbind. However, using the NTLM mechanism gives me an error in my maillog that says: "dovecot: auth: winbind(?,10.20.2.0): user not authenticated: NT_STATUS_UNSUCCESSFUL". At this point,

I'm trying to get NTLM authentication working with Dovecot to authenticate Postfix SMTP clients. I can authenticate postfix smtp clients using the plain text login mechanism via Dovecot and winbind. However, using the NTLM mechanism gives me an error in my maillog that says: "dovecot: auth: winbind(?,10.20.2.0): user not authenticated: NT_STATUS_UNSUCCESSFUL". At this

Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: connection established Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: master_notify: status 0 Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: name_mask: resource Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: name_mask: software Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: xsasl_dovecot_server_create: SASL service=smtp, realm=(null)