similar to: Unknown setting: ssl_ca_file

> I am using 0.99.10.7-1 on Debian, and I'm having some trouble with SSL. I > purchased a certificate from Thawte and I can't figure out how to tell > dovecot about the CA cert. Adding ssl_ca_file to my configuration produces > "Unknown setting: ssl_ca_file" on dovecot startup. > > Postfix has a smtpd_tls_CAfile argument and that part is working fine. > >

I am very fond of Dovecot, but it would be nice to have a more useful SSL implementation. When do you think we'll see a non-beta version that supports ssl_ca_file? I am running 0.99.11-3 from Debian testing. -- Jacob Elder

Hello, I still can't figure out why my users' passwords are expiring. Ever since we switched to LDAP, passwords expire every 14 days. Here is an example LDAP user entry: version: 1 # LDIF Export for: uid=sgoodrich,ou=Users,dc=trec,dc=us # Generated by phpLDAPadmin ( http://phpldapadmin.sourceforge.net/ ) on September 6, 2005 10:56 am # Server: TREC (localhost) # Search Scope: base #

This probably is a postfix problem, but I think there are lots of postfix experts/users on this list, and have heard a lot good things about this list, so I am just giving it a try. Thanks in advance! I am using dovecot-1.0.0-8_56.src.rpm downloaded from atrpms.net, and rebuilt from it(rpmrebuild ...). Postfix is 2.4.3. I followed documents at http://wiki.dovecot.org/LDA and LDA/Postfix, and

In dovecot-2.0.alpha3, setting "ssl_ca_file = /path/to/file" in conf.d/ssl.conf does not work, because imap-login chroots before opening the ca_file. Perhaps this parameter could be replaced with "ssl_ca = </path/to/file" as was done with ssl_cert and ssl_key. Tue Nov 17 11:19:38 server dovecot[1143]: imap-login: Fatal: Error reading configuration: Invalid settings:

hello all reader hello list hello centos network since I've installed dovecot deliver. e-mails no longer pass through amavisd. amavisd no longer work. c is to say I have no anti-spam and anti virus my postconf and dovecot -n [root at r13151 ~]# postconf -n alias_database = hash:/etc/aliases , hash:/etc/postfix/aliases alias_maps = hash:/etc/aliases , hash:/etc/postfix/aliases body_checks =

hello all reader hello list hello dovecot network since I've installed dovecot deliver. e-mails no longer pass through amavisd. amavisd no longer work. c is to say I have no anti-spam and anti virus my postconf and dovecot -n [root at r13151 ~]# postconf -n alias_database = hash:/etc/aliases , hash:/etc/postfix/aliases alias_maps = hash:/etc/aliases , hash:/etc/postfix/aliases body_checks

This issue is peripherally related to the following thread Re: [Dovecot] client certs with godaddy ssl cert This is running on CentOS 5.2 with latest Atrpms for Dovecot as of this weekend. # rpm -qa | grep dovecot dovecot-sieve-1.1.5-8.el5 dovecot-1.1.4-0_81.el5 With assistance from Rainer Frey (Inxmail GmbH), I am able to successfully use client ssl certs for imap access on both my Nokia

Hello! I have a boot problem with ISOLinux 2.00, downloaded yesterday. The CD works fine with every PC except on an IBM Thinkpad. If I poweron the TP and try to boot from CD I get back a "isolinux: disk error 01, ax = 4211,8B". Then, if I reboot (ctrl-alt-canc) your isolinux works fine. May you help me? -- Stefano Pettini spettini at inwind.it New ICQ number: 159144497 Notary of

I'm trying to bring dovecot up on Debian/stable using Christof Meerwald's unofficial packages (cmeerw.org/debian/). This package seems to work fine on Debian/testing. There error I'm getting on the stable box is: gnutls_handshake: A TLS fatal alert has been received.(Bad record MAC) Any guesses? -- Jacob Elder

Hey folks! For those who are interested in James Elder's publications: The links on his page work perfectly now. http://elderlab.yorku.ca/~elder/publications.html Thanks a lot, James! Everything seems to be alright now (although a little sluggish :-) Philipp -- James Elder wrote on 16-1-2001: > Hi Philipp, > > I have fixed up the links - please give it a try and let me know if

Hi list, I have noted over the last week or so my DNS servers are dumping lots of messages for bogus domain lookups. Examining the postfix queue with postqueue -p: I see many (Host or domain name not found. Name service error for name=bdgiedjhea.po6e4ina.com type=MX: Host not found, try again) Jake at bdgiedjhea.po6e4ina.com My question - why does this

> On June 1, 2017 at 1:42 PM Ralf Hildebrandt <Ralf.Hildebrandt at charite.de> wrote: > > > * Aki Tuomi <aki.tuomi at dovecot.fi>: > > > > > So I added > > > > ssl_ca_file = /etc/ssl/certs/ca-certificates.crt > > > > > > > > But alas: > > > > May 31 16:50:24 mproxy dovecot: config: Warning: Obsolete setting

* Aki Tuomi <aki.tuomi at dovecot.fi>: > > > So I added > > > ssl_ca_file = /etc/ssl/certs/ca-certificates.crt > > > > > > But alas: > > > May 31 16:50:24 mproxy dovecot: config: Warning: Obsolete setting in /etc/dovecot/conf.d/10-ssl.conf:36: ssl_ca_file has been replaced by ssl_ca = <file > > > > > > Gnarf! As you can

hi, I'm getting quite a few of these in the logs of our new dovecot mail server: Aug 20 09:50:03 mail2 dovecot: POP3(vwc406): Couldn't init INBOX: BUG: Unknown internal error Aug 20 09:50:03 mail2 dovecot: POP3(vwc406): Mailbox init failed top=0/0, retr=0/0, del=0/0, size=0 we migrated from courier and other mailboxes work. any idea what the cause might be or how I can fix it?

Finally, it''s out. All the details are here: http://leaf.sourceforge.net/article.php?sid=63 We will probably take a rest for a while :-) Enjoy! Jacques & Eric ------------------------------------------------------- This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate:

> On May 31, 2017 at 6:10 PM Ralf Hildebrandt <Ralf.Hildebrandt at charite.de> wrote: > > > * Ralf Hildebrandt <Ralf.Hildebrandt at charite.de>: > > > So I added > > ssl_ca_file = /etc/ssl/certs/ca-certificates.crt > > > > But alas: > > May 31 16:50:24 mproxy dovecot: config: Warning: Obsolete setting in

Hi. I've spent the past few hours trying to get SSL working right in Dovecot 1.0.5 and now I must turn to you for help. I purchased an SSL certificate from Go Daddy. I pointed ssl_cert_file to the .crt file and ssl_key_file to the .key file, but the client (Mail.app) complains: Mail was unable to verify the identity of this server, which has a certificate issued to

Hello, As far as I can read in the Dovecot SSL configuration wiki page, each CA cert must be followed by the related CA CRL in the client certificate verification context ("ssl_ca_file" setting). In my company we do have our own PKI and as soon as Client certificate is compromised we do revoke it and update the related CA's CRL. Does that mean that I have to issue a new

Going to check something in I get this, which I've never seen before....is it is safe to just hit P and go on? now what? svn commit config/i386/llvm-i386.cpp Error validating server certificate for 'https://llvm.org:443': - The certificate is not issued by a trusted authority. Use the fingerprint to validate the certificate manually! Certificate information: - Hostname: