Displaying 20 results from an estimated 10000 matches similar to: "Feature request: ssl-cert config"
2018 Jul 23
0
dovecot sometimes sends non-default SSL cert if IMAP client won't send SNI
Can you provide some details on what those openssl commands returned?
Aki
On 20.07.2018 12:14, Martin Johannes Dauser wrote:
> Hi,
>
> I recognised some funny behaviour on my server. IMAP clients which
> won't send an Server Name Indication (SNI) sometimes get the wrong
> certificate. I would expect that those clients always get the default
> certificate (of my new
2018 Jul 20
2
dovecot sometimes sends non-default SSL cert if IMAP client won't send SNI
Hi,
I recognised some funny behaviour on my server. IMAP clients which
won't send an Server Name Indication (SNI) sometimes get the wrong
certificate. I would expect that those clients always get the default
certificate (of my new domain), instead in about 20 to 50% of
connections the certificate of my old domain will be presented.
(sample rate was 3 times 30 connections)
Clients sending SNI
2018 Jul 24
1
dovecot sometimes sends non-default SSL cert if IMAP client won't send SNI
Sure, and thanks for trying to help!
These are the two correct answers when SNI is included. The
certificates are fully chained. Both certificates carry the same
subject mail.cs.sbg.ac.at but differ in Subject Alternative Name (SAN).
X509v3 Subject Alternative Name:?
? DNS:mail.cs.sbg.ac.at, DNS:smtp.cs.sbg.ac.at, DNS:imap.cs.sbg.ac.at,
DNS:pop.cs.sbg.ac.at
X509v3 Subject Alternative Name:?
?
2019 Dec 15
3
Local lmtp proxy on backend server
I receive a local mail when I do a 'mail test' on a backend svr1 with
this[0] configuration. However when I just add only one configuration
change 'lmtp_proxy = yes' I am getting these errors[1]. I would expect
this email to still be delivered locally, should this be working or do I
misunderstand the lmtp proxy functionality?
[0]
passdb {
args =
auth_verbose = default
2019 Dec 16
1
Local lmtp proxy on backend server
I added this:
passdb {
driver = passwd
skip = authenticated
}
Which enables indeed local delivery, I also noticed this. Maybe the
password field check shoud not be done, when you enable skip
authentication?
Dec 16 10:26:37 svr1 dovecot: auth-worker(12046): Debug: passwd(test):
lookup
Dec 16 10:26:37 svr1 dovecot: auth-worker(12046): passwd(test): invalid
password field '*'
2019 Dec 16
0
Local lmtp proxy on backend server
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
<br>
</div>
<blockquote type="cite">
<div>
On 15/12/2019 23:09 Marc Roos <
<a href="mailto:m.roos@f1-outsourcing.eu">m.roos@f1-outsourcing.eu</a>> wrote:
</div>
<div>
2020 Apr 16
2
Bug maybe already resolved? Sieve rule does not accept special use folder names
Sieve rule fileinto Spam fails, while fileinto Junk succeeds
mailbox Spam {
special_use = \Junk
auto = no
}
dovecot-pigeonhole-2.2.36-3.el7_7.1.x86_64
dovecot-2.2.36-3.el7_7.1.x86_64
CentOS Linux release 7.7.1908 (Core
2020 Apr 16
2
Bug maybe already resolved? Sieve rule does not accept special use folder names
I do not have the log file anymore from the home dir. It just complains
that the folder Spam does not exist.
dovecot: lmtp(xxxx): oG8YI6enmF7FIAAAI7dPvA: sieve: Execution of script
/xxxx/.dovecot.sieve failed, but implicit keep was successful (user
logfile /xxx/.dovecot.sieve.log may reveal additional details)
-----Original Message-----
From: Stephan Bosch [mailto:stephan at rename-it.nl]
2019 Dec 16
0
Local lmtp proxy on backend server
Hi Aki,
I also tried with changing the original ldap source to svr2. Although
everywhere svr2 is configured, still mails keep being delivered locally
on svr1. Do I need to configure more than 20-lmtp.conf?
[@svr1 conf.d]# cat 20-lmtp.conf | grep -v '^#'
lmtp_proxy = yes
protocol lmtp {
# Space separated list of plugins to load (default is global
mail_plugins).
mail_plugins
2013 Sep 15
1
Dovecot replies with default SSL certificate instead of the vhost's
Hello,
I'm using dovecot v2.0.21.
According to http://wiki2.dovecot.org/SSL/DovecotConfiguration,dovecot 2.x supports different SSL certificate for different virtual hosts by using "local_name" directive, but I can't get it to work.
When testing the certificate using "openssl s_client -connect domain.com:pop3s" I get the default certificate instead of
2019 Sep 26
0
CESA-2019:2836 Important CentOS 7 dovecot Security Update
CentOS Errata and Security Advisory 2019:2836 Important
Upstream details at : https://access.redhat.com/errata/RHSA-2019:2836
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
11077bf3f1d84c1f6859b8fa47c9392fcd509f8d6bc7b9b988e6ed7577ed04f8 dovecot-2.2.36-3.el7_7.1.i686.rpm
2019 Sep 27
0
CentOS-announce Digest, Vol 175, Issue 4
Send CentOS-announce mailing list submissions to
centos-announce at centos.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-request at centos.org
You can reach the person managing the list at
centos-announce-owner at centos.org
When
2020 Apr 16
2
Bug maybe already resolved? Sieve rule does not accept special use folder names
It is a 'special use' folder, so it only appears to exist in mail
clients.
# spam folders merging
mailbox Junk {
special_use = \Junk
auto = create
}
mailbox Spam {
special_use = \Junk
auto = no
}
mailbox "Junk E-mail" {
special_use = \Junk
auto = no
}
On 16/04/2020 23:19, Marc Roos wrote:
> I do not have the log file anymore from the
2018 Mar 10
0
Unexpected config results with local_name + multiple SSL certs
On 2018-02-25 (09:31 MST), David Favor <david at davidfavor.com> wrote:
>
> }
> local_name imap.cydec.com {
> ssl_cert = </etc/letsencrypt/live/imap.cydec.com/fullchain.pem
> ssl_key = # hidden, use -P to show it
> }
Doesn't this still require a default t(top level) cert besides the one specified for local_name?
Also, is there any reason to use local_name if
2020 Apr 16
1
Bug maybe already resolved? Sieve rule does not accept special use folder names
Hmmm, confusing, clients should then display the mailbox name redirected
by the server.
If a user in a front end just sees the 'Junk E-mail', that is the name
he is going to be using in his mailbox rules. If he does not know that
this is actually the Junk folder on the server, he will make an
incorrect message rule.
So I guess you have to correct this server side, before storing
2018 Feb 25
3
Unexpected config results with local_name + multiple SSL certs
Working with SSL on fresh install of latest Ubuntu Artful + Dovecot
seems broken somehow.
Application is Dovecot listening for many SSL sites...
Likely I've missed adding something simple to the config, related
to local_name usage.
Be great if someone can point out what I've missed, to setup
multiple SSL certs for different host.domain entries in config.
Thanks.
_______
This works as
2020 Apr 16
0
Bug maybe already resolved? Sieve rule does not accept special use folder names
On 16/04/2020 23:38, Marc Roos wrote:
> It is a 'special use' folder, so it only appears to exist in mail
> clients.
>
> # spam folders merging
> mailbox Junk {
> special_use = \Junk
> auto = create
> }
> mailbox Spam {
> special_use = \Junk
> auto = no
> }
> mailbox "Junk E-mail" {
> special_use
2020 Apr 16
0
Bug maybe already resolved? Sieve rule does not accept special use folder names
On 16/04/2020 23:19, Marc Roos wrote:
> I do not have the log file anymore from the home dir. It just complains
> that the folder Spam does not exist.
>
> dovecot: lmtp(xxxx): oG8YI6enmF7FIAAAI7dPvA: sieve: Execution of script
> /xxxx/.dovecot.sieve failed, but implicit keep was successful (user
> logfile /xxx/.dovecot.sieve.log may reveal additional details)
So, does that
2019 Nov 27
1
Cert for ip range?
On Wed, Nov 27, 2019 at 11:31 AM Aki Tuomi <aki.tuomi at open-xchange.com>
wrote:
>
> > On 27/11/2019 21:28 Mark Moseley via dovecot <dovecot at dovecot.org>
> wrote:
> >
> >
> > On Tue, Nov 26, 2019 at 11:22 PM Aki Tuomi via dovecot <
> dovecot at dovecot.org> wrote:
> > >
> > > On 21.11.2019 23.57, Marc Roos via dovecot
2020 Apr 16
0
Bug maybe already resolved? Sieve rule does not accept special use folder names
On 16/04/2020 21:04, Marc Roos wrote:
> Sieve rule fileinto Spam fails, while fileinto Junk succeeds
>
>
> mailbox Spam {
> special_use = \Junk
> auto = no
> }
>
> dovecot-pigeonhole-2.2.36-3.el7_7.1.x86_64
> dovecot-2.2.36-3.el7_7.1.x86_64
> CentOS Linux release 7.7.1908 (Core
I can't tell without insight in the error message and your full