similar to: Multidomain / IP Address Setup (Dovevot 2.2.10 on CentOS7 ) is failing: Fatal: Couldn't parse private ssl_key: error:0906D06C:PEM

Hello Alex Am 14.08.2015 um 19:57 schrieb Alexander Dalloz: > What have you done to exclude that SELinux interferes? > Just some sysinfo: CentOS Linux release 7.1.1503 (Core) (i run yum update every day) sestatus: SELinux status: enabled SELinuxfs mount: /sys/fs/selinux SELinux root directory: /etc/selinux Loaded policy name: targeted

On 08/14/15 20:30, dravion.smith at gmx.net wrote: > > ### CORRECTION > Am 15.08.2015 um 03:22 schrieb dravion.smith at gmx.net: >> >> #### BUT #### >> If i try something like this in /etc/dovecot/conf.d/10-ssl.conf >> local_name imap.mydomain01.tld >> local imap.mydomain01.tld { >> protocol imap { >> ssl_cert = >>

I think you should post doveconf -n output. On 08/14/15 20:30, dravion.smith at gmx.net wrote: > > ### CORRECTION > Am 15.08.2015 um 03:22 schrieb dravion.smith at gmx.net: >> >> #### BUT #### >> If i try something like this in /etc/dovecot/conf.d/10-ssl.conf >> >> local imap.mydomain01.tld { >> protocol imap { >> ssl_cert = >>

Am 14.08.2015 um 13:22 schrieb dravion.smith at gmx.net: > Hi, > I want to say hello and here is my big problem ;D > > Iam trying to archive a Postfix/Dovecot 2.2.10 CentOS7 Multidomain Setup > with multiple (valid > StartSSL Certs), but iam only able to run a single Domain Cert server only. > > ps: I need a multiple domainssetup for every customer and it is not an >

>I think you should post doveconf -n output. with your dovecot -n output provided this mail would not need to be sent >On 08/14/15 20:30, dravion.smith at gmx.net wrote: >> >> ### CORRECTION >> Am 15.08.2015 um 03:22 schrieb dravion.smith at gmx.net: >>> >>> #### BUT #### >>> If i try something like this in /etc/dovecot/conf.d/10-ssl.conf

### CORRECTION Am 15.08.2015 um 03:22 schrieb dravion.smith at gmx.net: > > #### BUT #### > If i try something like this in /etc/dovecot/conf.d/10-ssl.conf > > local imap.mydomain01.tld { > protocol imap { > ssl_cert = > </etc/ssl/domains/mydomain01.tld/imap/imap.mydomain01.tld.crt.pem > ssl_key = >

Am 15.08.2015 um 08:16 schrieb Christian Kivalo: > [snip] > > Note that you will still need a top-level "default" ssl_key and ssl_cert as well, or you will receive errors. > > in addition to your two domain specific ssl certs have you also defined a "default" ssl_key and ssl_cert as required as required by the documentation? > > regards > - c Did you

Am 15. August 2015 08:58:04 MESZ, schrieb "dravion.smith at gmx.net" <dravion.smith at gmx.net>: > >Am 15.08.2015 um 08:16 schrieb Christian Kivalo: > >> [snip] >> >> Note that you will still need a top-level "default" ssl_key and >ssl_cert as well, or you will receive errors. >> >> in addition to your two domain specific ssl

/etc/ssl $ sudo doveconf -n # 2.2.15: /etc/dovecot/dovecot.conf # OS: OpenBSD 5.7 amd64 ffs auth_mechanisms = plain login default_client_limit = 500 disable_plaintext_auth = no first_valid_uid = 1000 imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags mail_location = maildir:/var/vmail/%d/%n/Maildir managesieve_notify_capability = mailto managesieve_sieve_capability =

Am 15.08.2015 um 09:04 schrieb Christian Kivalo: > provide your multi ssl doveconf -n output. - c No. I leave this shit alone and running dovecot in multiinstance mode and now its works.

>But can you explain why you use globally: > >ssl_cert = </etc/ssl/dovecot.pem >ssl_key = </etc/ssl/private/dovecot.pem > >and certs for any additional Domain each? > >## >local_name mail.pettijohn-web.com { > ssl_cert = </etc/ssl/mail.pettijohn-web.com.crt > ssl_key = </etc/ssl/private/mail.pettijohn-web.com.key >} >## he configured the top

Hi, im searching for multidomain threads in this list but just found some from late 2014 where Andrew said it is not supported. Could you guy please tell me if this is supported now, I mean, just one DC with two completely distinct domains?

We're setting up a server with qmail/vpopmail and dovecot. In addition to vpopmail users we want non-virtual, local users to be able to authenticate and have them read the Maildir in their real $HOME. vpopmail userdb/passwd works fine. Now how do I tell dovecot to use passwd (or PAM) userdb/passdb authentication too? /etc/dovecot.conf: [...] auth = default auth_mechanisms = plain

Hello List, I have a problem with the CA on my Puppetmaster. This Puppetmaster is connected to different Networks with different sub domainnames. The Puppet clients connecting via different Interfaces. There is no routing between subnets. Only one subnet can connect successfully. This is because the subject in the Certificate is the name of this subnet. All other clients get: Could not

I'm using Dovecot 2.2.5. I'm setting up and new IMAPS server for personal use (i.e. only me). I have success with self-signed certificates but not with others (e.g. StartSSL.com) With StartSSL certs: I've been able to connect and test commands via: openssl s_client -connect imaps.unixathome.org:993 Can you configure your iPhone or Macbook to access the above? Authentication

Hi to all, I would design an application for multidomain support and my question is what is the best practice to do this kind of application ? Eg.: I think to write my application handling the multidomain into routing map: map.connect ":domain/:controller/:action" map.connect ":domain/:controller/:action/:id" Assuming that I hanlde 3 domains for 3 different customers:

Hello anyone used OpenSSL before? Why do we need to pay for expensive SSL certs when there is OpenSSL which is provided free? Is there a difference? I''ve got an ecommerce website, and wondering if OpenSSL is enough? Your thoughts will be appreciated -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this

On Jun 15, 2016, at 7:57 AM, ????????? ???????? <nevis2us at infoline.su> wrote: > > Nowadays it's quite easy to get normal ssl certificates for free. E.g. > > http://www.startssl.com > http://buy.wosign.com/free Today, I would prefer Let?s Encrypt: https://letsencrypt.org/ It is philosophically aligned with the open source software world, rather than act as bait

Hello, It seems that Dovecot ignores the new /ssl_cert and ssl_key /settings. Using them in the dovecot configuration results in the error: Fatal: Couldn't parse private ssl_key: error:0906D06C:PEM routines:PEM_read_bio:no start line: Expecting: ANY PRIVATE KEY] Using the old /ssl_//cert//_file/ and /ssl_key_file/ results in their being obsolete warning but no fatal error.

The port is determined with port=nnn setting. You can't return per-protocol port like that, you need to look at the protocol requested by user and return port based on that, or you can omit port to default into "standard port". not using ssl/starttls is default. > On 17 September 2018 at 16:35 Alexander Chekalin <alexander.chekalin at gmail.com> wrote: > > >