auth problems on postfix mysql

2014-09-08 Thread nobody73
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi List , i have followed the guide on workaround and at the end of it i have authentications issues with thunderbird ,on workaround there is a local test for authentication and it was successfull .Thunderbird says i have chosen the wrong auth mechan

Re: auth problems on postfix mysql

2014-09-08 Thread nobody73
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 these are more logs: dovecot: imap-login: Disconnected (no auth attempts in 4 secs): user=, rip=1.2.3.4, lip=4.5.6.7, TLS handshaking: SSL_accept() failed: error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca: SSL alert number 48, sess

Re: auth problems on postfix mysql

2014-09-08 Thread Wietse Venema
nobody73: > these are more logs: > > dovecot: imap-login: Disconnected (no auth attempts in 4 secs): > user=, rip=1.2.3.4, lip=4.5.6.7, TLS handshaking: SSL_accept() > failed: error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert > unknown ca: SSL alert number 48, session= This mailing list is

Re: auth problems on postfix mysql

2014-09-08 Thread Nicolás
El 08/09/2014 14:39, nobody73 escribió: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Auth-sql.conf.ex has passdb { driver = sql args = /etc/dovecot/dovecot-sql.conf.ext } [...] where in passdb dovecot-sql.conf.ex has: default_pass_scheme = PLAIN-MD5 If this is the only content of y

Re: Postfix and SASL auth on OpenBSD 5.5.

2014-09-08 Thread giacomo
Hi, I send you the configuration of Postfix. $ postconf -nf alias_database = hash:/etc/postfix/aliases alias_maps = hash:/etc/postfix/aliases broken_sasl_auth_clients = yes command_directory = /usr/local/sbin config_directory = /etc/postfix daemon_directory = /usr/local/libexec/postfix data_dire

Re: Postfix and SASL auth on OpenBSD 5.5.

2014-09-08 Thread Viktor Dukhovni
On Mon, Sep 08, 2014 at 10:47:02PM +0200, giacomo wrote: > I send you the configuration of Postfix. Change the password for this account: Username: d.lis...@gruppoisil.com Compromised Password: lisaia > smtpd_sasl_auth_enable = yes > smtpd_sasl_local_domain = $mydomain > smtpd_sasl_secu

Correct cert handling when hosting multiple domains?

2014-09-08 Thread Quanah Gibson-Mount
Hi, A number of our zimbra customers deploy where they are hosting accounts for multiple domains (At least one client hosts over 100,000 domains). These deployments generally use a single set of MTAs for their MX records, which works fine as long as TLS is not involved. However, with the inc

Re: Correct cert handling when hosting multiple domains?

2014-09-08 Thread Viktor Dukhovni
On Mon, Sep 08, 2014 at 04:43:36PM -0700, Quanah Gibson-Mount wrote: > A number of our zimbra customers deploy where they are hosting accounts for > multiple domains (At least one client hosts over 100,000 domains). These > deployments generally use a single set of MTAs for their MX records, whic

Re: Correct cert handling when hosting multiple domains?

2014-09-08 Thread Wietse Venema
Viktor Dukhovni: > On Mon, Sep 08, 2014 at 04:43:36PM -0700, Quanah Gibson-Mount wrote: > > > A number of our zimbra customers deploy where they are hosting accounts for > > multiple domains (At least one client hosts over 100,000 domains). These > > deployments generally use a single set of MTAs

Re: Correct cert handling when hosting multiple domains?

2014-09-08 Thread Viktor Dukhovni
On Mon, Sep 08, 2014 at 08:22:54PM -0400, Wietse Venema wrote: > I'd like to hear a bit more on this from other people than Viktor. > There is a difference between "technically perfect" (e.g., telling > everyone to adopt DNSSSEC and DANE or else don't bother), and what > is "currently justifiable"

Re: Correct cert handling when hosting multiple domains?

2014-09-08 Thread Stefan Foerster
* Wietse Venema : > Viktor Dukhovni: > > Which works just fine with a single certificate, because TLS in > > SMTP in generally unauthenticated. If all the various domains > > share the same MX hostnames, many implementations that log > > "speculative" authentication results (no actual enforcement,