similar to: Re : dovecot --Err Plaintext authentication disabled

Hi Following my last posts, i succeed to connect pop3 in localhost but not in mydomain.org (with dovecot 0.99 it worked) I have this error : -ERR Plaintext authentication disabled. Thanks

Try adding auth_debug_password=yes Aki On 01.02.2018 10:27, yuryb wrote: > We have FreeBSD-server with dovecot installed on it as IMAP-server. My > user and password database is a text file with plaintext passwords. > Clients connect to imap-server via TLS protocol and plaintext > password. All works fine. But I want to configure ability to authorize > with a client certificates.

We have FreeBSD-server with dovecot installed on it as IMAP-server. My user and password database is a text file with plaintext passwords. Clients connect to imap-server via TLS protocol and plaintext password. All works fine. But I want to configure ability to authorize with a client certificates. I have generated a client certificate and imported it to email-client. Also I have configured

You probably need to also enable auth_debug=yes auth_verbose=yes also, are you sure you just don't have wrong password? Aki On 01.02.2018 12:08, yuryb wrote: > I have added "auth_debug_password=yes" to "10-logging.conf" and > restarted dovecot.?But I do not see any information about the password > in the logs. Does this mean that the thunderbird does not

I have added "auth_debug_password=yes" to "10-logging.conf" and restarted dovecot.?But I do not see any information about the password in the logs. Does this mean that the thunderbird does not send the password??Although it asks for the password and I enter one. New log: dovecot: master: Warning: Killed with signal 15 (by pid=19769 uid=0 code=kill) dovecot: master: Dovecot

Hi: It appears that at least at one time, Dovecot supported plaintext authentication from localhost, even if disable_plaintext_auth = yes. To wit, the example configuration file reads: # Disable LOGIN command and all other plaintext authentications unless # SSL/TLS is used (LOGINDISABLED capability). Note that 127.*.*.* and # IPv6 ::1 addresses are considered secure, this setting has no effect

Hi, I use dovecot (pop) with gentoo but it's not securize. I would like to use pops but i don't how to do this. I think i have to use certificates... This my dovecot.conf : protocols = imap imaps pop3 pop3s imap_listen = * pop3_listen = * imaps_listen = * pop3s_listen = * ssl_disable = no login = imap login = pop3 default_mail_env = maildir:%h/.maildir mbox_locks = fcntl dotlock auth =

dovecot-bounces at dovecot.org wrote: > I noticed that... > > # Disable LOGIN command and all other plaintext authentications unless > # SSL/TLS is used (LOGINDISABLED capability). Note that 127.*.*.* and > # IPv6 ::1 addresses are considered secure, this setting has > no effect if > # you connect from those addresses. > #disable_plaintext_auth = yes > > ...was

Dear Mailing list, I have a Dovecot v2.2.9 server that authenticate against a Openldap server. I want to configure Dovecot to use TLS for LDAP authentication. I have tried to fetch/send emails using Thunderbird: - IMAP succeed to fetch mail - SMTP failed to send mail The Dovecot server produce the following log : Jun 29 08:44:00 mail postfix/submission/smtpd[634]: connect from

Hello, After client (Thunderbird, now version 31.0) updated today, it stopped connecting to Dovecot IMAP4S. The infamous "SSL alert number 42" is reported. Mail server uses local (created for intranet) CA certificate as root. I would appreciate pieces of advice on how to handle that without enabling plaintext authentication over insecure channels. Other intranet services work with

Folks, I'm trying to configure my dovecot installation to require client certificates for external/Internet connections, while still allowing my local network to not need certificates. This configuration is for Dovecot 2 (2.0.8 in Fedora 14), and I've tried to use the "remote" block to give different definitions for my local network vs the defaults. While most options seem to

Hello all, I've set up a new instance of dovecot 2.0.9 to use as a POP3/IMAP proxy. On trying to login I am told '-ERR Plaintext authentication disallowed on non-secure (SSL/TLS) connections'. I have set 'disable_plaintext_auth = no' (see output of doveconf attached). More curious still is that *this happens for SSL connections too*. Something seems very wrong here. Yelp?

When I upgraded my debian-based imap server from squeeze to wheezy yesterday, SSL stopped working. I am using a http://cacert.org signed server sertificate, and I am reusing the certificates that were used on the 1.x dovecot of debian squeeze. My three MUAs that worked against the previous 1.x dovecot with the same certificate, now fails in various ways. Any hints and guesses as to how to debug

I'd like to disable plaintext authentication (e.g. only allow authentication that does STARTTLS or connects on SSL/TLS only ports) only for certain (most) IP addresses. I want to exempt a few addresses (users coming over known VPNs). Fortunately, all this is coming in over a firewall (Sonicwall) in which I can NAT traffic by IP address to go to specific port numbers. So, if I can establish

Unlike test47, test49 refuses to authenticate pop3s if disable_plaintext_auth = yes Checked the crypto with: snort -vde tcp port 995 The connection is being made with ssl so it looks like the plaintext auth preventer is broken. -kim __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

Le 19/06/2015 09:04, Steffen Kaiser a ?crit : > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Fri, 19 Jun 2015, Mickael Choisnard wrote: > >> Date: Fri, 19 Jun 2015 08:29:08 +0200 >> From: Mickael Choisnard <mickael.choisnard at free.fr> >> To: dovecot at dovecot.org >> Subject: [Dovecot] question about /var/mail/xxx >> >> Hi,

Hi, I need your help to use dovecot with sendmail I use a fresh debian 8 jessie and i installed sendmail and dovecot 2. Sendmail works fine. All mails go to /var/mail/xxx this is problem for dovecot. dovecot cannot get it. # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.1 auth_mechanisms = plain login auth_verbose = yes auth_verbose_passwords = yes

I was not able to find specific help for configuring the crt file for CaCert. I gleaned from examples the following order: server certificate CaCert class 3 certificate Cacert root certificate However, when I try to configure my mail reading for IMAP, Dovecot shows the following error in the log: dovecot: imap-login: Aborted login (no auth attempts): I am assuming, based on searches for this

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 19 Jun 2015, Mickael Choisnard wrote: > Date: Fri, 19 Jun 2015 08:29:08 +0200 > From: Mickael Choisnard <mickael.choisnard at free.fr> > To: dovecot at dovecot.org > Subject: [Dovecot] question about /var/mail/xxx > > Hi, > I need your help to use dovecot with sendmail > I use a fresh debian 8 jessie and i

Hi, I recently moved from courier-imap to dovecot, to be able to work with managesieve. I use version 1.2.5, on suse 10.3. I used the script to migrate the courier maildir to dovecot format. It seems to work fine except for one problem : I use a number of aliasses and with Thunderbird I can select which alias (e-mail-address) to use as my identity when sending a mail. I sniffed with wireshark,