Displaying 20 results from an estimated 300 matches similar to: "sometimes no shared cipher after upgrade from 2.2 to 2.3"
2019 Aug 21
0
sometimes no shared cipher after upgrade from 2.2 to 2.3
On 21/8/2019 16:12, Kristijan Savic - ratiokontakt GmbH via dovecot wrote:
> We recently upgraded from dovecot 2.2 to 2.3.7.1-1
>
> Not many, but some users are experiencing difficulties. The dovecot directors
> log:
>
> Aug 21 14:28:49 director01 dovecot: pop3-login: Disconnected (no auth attempts
> in 0 secs): user=<>, rip=redacted, lip=10.0.0.120, TLS handshaking:
2019 Aug 21
2
sometimes no shared cipher after upgrade from 2.2 to 2.3
> SSL3 is no longer included in the cipher sets. Try this:
>
> ssl_min_protocol = SSLv3
Thanks. Unfortunately, no dice - same error.
Any other tips? I was under the impression "no shared cipher" was rather the
problem?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This
2019 Mar 06
2
Strange behaviour with BLF-CRYPT and SHA*-CRYPT pasword schemas
Greetings,
this is less of a bug report or a help request, but we would like to know if
someone can explain the following:
Environment: Centos 7 with Dovecot 2.3.4-2
default_pass_scheme = BLF-CRYPT
password hash in database : BLF-CRYPT
login = works
default_pass_scheme = SHA512 or SHA256-CRYPT
password hash in database : BLF-CRYPT
login = also works
default_pass_scheme = BLF-CRYPT
password
2019 Mar 07
2
Strange behaviour with BLF-CRYPT and SHA*-CRYPT pasword schemas
> You could configure default scheme as CRYPT. It covers these all. Otherwise
> you need to make sure passwords have {SCHEME} prefix when it differs from
> default or oddities occur. ---
Thank you for the tip with CRYPT.
Is there any explanation for this behaviour though?
Why are BCRYPT hashes accepted when default_pass_scheme is set to SHA512-CRYPT
and not vice versa? Is this
2019 Apr 16
2
Sieve operation "send copy" not working since upgrade from dovecot 2.2.31-1 to 2.3.5.1-1
I hope that someone can help me here.
Software: CentOS 7.6.1810, dovecot-2.3.5.1, dovecot-pigeonhole-2.3.5.1, exim
4.91-1
Example filter:
# rule:[test]
if header :contains "subject" "meow"
{
redirect :copy "ks at ratiokontakt.de";
}
Mail log:
Apr 16 11:29:02 frontend-17 dovecot:
lmtp(testi at mrhoang.de)<25201><QPgZHF6gtVxxYgAARS1pjg>:
2019 Apr 16
0
Sieve operation "send copy" not working since upgrade from dovecot 2.2.31-1 to 2.3.5.1-1
On 16.4.2019 13.34, Kristijan Savic - ratiokontakt GmbH via dovecot wrote:
> I hope that someone can help me here.
>
> Software: CentOS 7.6.1810, dovecot-2.3.5.1, dovecot-pigeonhole-2.3.5.1, exim
> 4.91-1
>
> Example filter:
>
> # rule:[test]
> if header :contains "subject" "meow"
> {
> redirect :copy "ks at ratiokontakt.de";
2019 Mar 06
0
Strange behaviour with BLF-CRYPT and SHA*-CRYPT pasword schemas
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
<br>
</div>
<blockquote type="cite">
<div>
On 6 March 2019 18:16 Kristijan Savic - ratiokontakt GmbH via dovecot <
<a href="mailto:dovecot@dovecot.org">dovecot@dovecot.org</a>> wrote:
2015 Feb 23
2
Quota-status service on Director
Hello,
I'm trying to configure the quota-status service, but it seems I'm not successful with my director setup (2.2.9). I activate the quota-status service like this on my director server:
$ cat 91-quota-status.conf
##
## Quota-Status configuration.
##
# Load Module quota-status and listen on TCP/IP Port for connections.
service quota-status {
? executable = quota-status -p postfix
?
2016 Oct 10
2
Quota-status service on Director
Hi!
quota-status is not supported in proxy configuration. You should use
quota_warning and quota_over_flag scripts instead.
Aki
On 08.10.2016 03:51, Michael Kliewe wrote:
> Hello,
> any news on this topic? I tried it again with Dovecot 2.2.25, but it's
> still not possible to run the quota-status services on the directors.
> They try to access the mailbox of the user, which they
2019 Mar 07
0
Strange behaviour with BLF-CRYPT and SHA*-CRYPT pasword schemas
On 7.3.2019 14.00, Kristijan Savic - ratiokontakt GmbH wrote:
>> You could configure default scheme as CRYPT. It covers these all. Otherwise
>> you need to make sure passwords have {SCHEME} prefix when it differs from
>> default or oddities occur. ---
> Thank you for the tip with CRYPT.
>
> Is there any explanation for this behaviour though?
>
> Why are BCRYPT
2019 Aug 21
0
sometimes no shared cipher after upgrade from 2.2 to 2.3
On 21/8/2019 18:51, Kristijan Savic - ratiokontakt GmbH via dovecot wrote:
>
>> SSL3 is no longer included in the cipher sets. Try this:
>>
>> ssl_min_protocol = SSLv3
>
> Thanks. Unfortunately, no dice - same error.
>
> Any other tips? I was under the impression "no shared cipher" was rather the
> problem?
Yes this is exactly the problem but the
2017 Feb 17
3
Problem with Let's Encrypt Certificate
Hey Robert,
thanks for your reply.
Am 17.02.2017 um 19:28 schrieb Robert L Mathews:
> Looking at your dovecot -n, you're using two different files here:
>
> ssl_cert = </etc/ssl/sebode-online.de/chain.pem
> ssl_key = </etc/ssl/sebode-online.de/key.pem
>
> Are you sure these two files match, and contain the right things in the
> right order?
>
Yes,
2019 Sep 23
0
Quota plug-in, do the directors also need it enabled?
I am having an issue with the quota display not showing up in e.g. Roundcube.
There are multiple Dovecot servers and three directors. A load balancer also
does it's thing.
The quota plug-in is enabled everywhere, except on the directors. Do those
also need it enabled?
--
Kristijan Savic
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
2011 Mar 03
1
OCFS2 1.4 + DRBD + iSCSI problem with DLM
An HTML attachment was scrubbed...
URL: http://oss.oracle.com/pipermail/ocfs2-users/attachments/20110303/0fbefee6/attachment.html
2017 Feb 17
7
Problem with Let's Encrypt Certificate
Hello Folks,
my StartCom SSL-Certificate expires soon and so I wanted to switch to
Let's Encrypt Certificates instead. Unfortunatelly Thunderbird seems not
to like it, although all -tested- other Clients work without any problems.
When I connect with Thunderbird it sends an "Encrypted Alert" directly
after the TLS handshake although Dovecot wants to continue the session.
In the
2012 Apr 22
6
git down?
Hi,
trying to compile but have problems:
+ /root/xen-unstable.hg-rev/tools/../scripts/git-checkout.sh git://
xenbits.xensource.com/qemu-xen-unstable.git82db8de16530f016809264d3179823999d702849
qemu-xen-traditional-dir
Cloning into qemu-xen-traditional-dir-remote.tmp...
fatal: read error: Connection reset by peer
git down?
Best Regards,
Kristijan Lecnik
2013 Jun 26
4
fresh install of xen, problems booting qemu-dm
Hi,
i have just install debian wheezy and xen-hypervisor-4.1-amd64
helped with
http://wiki.debian.org/Xen
http://wiki.xenproject.org/wiki/Xen_Beginners_Guide#Installing_Debian_Squeeze
created test.cfg
http://pastebin.com/D5Wsx6eB
xl create test.conf
Parsing config file test.conf
xc: info: VIRTUAL MEMORY ARRANGEMENT:
Loader: 0000000000100000->0000000000174170
TOTAL:
2001 Mar 23
2
[beginner] Can't launch sol.exe!
When I try to launch sol for testing i've got:
#/usr/local/bin/wine sol
Could not stat /mnt/fd0 (Aucun fichier ou répertoire de ce type), ignoring
drive A:
Could not stat /cdrom (Aucun fichier ou répertoire de ce type), ignoring
drive D:
/usr/local/bin/wine: warning: $DISPLAY variable ignored, using '10.0.0.14:0'
_X11TransSocketINETConnect: Can't connect: errno = 111
2011 Mar 22
6
bug resolve yet for export OCFS2 volume to NFS client ?
I found this from ocfs1.4 document:
g) NFS
OCFS2 volumes can be exported as NFS volumes. This support is limited to
NFS version 3, which translates to Linux kernel version 2.4 or later.
Users must mount the NFS volumes on the clients using the nordirplus
mount option. This disables the READDIRPLUS RPC call to workaround a bug
in NFSD, detailed in the following link:
2017 Sep 27
0
Quota-status service on Director
Hi,
is quota-status still not supported in proxy configuration ?
Any chance it will be in the future ?
Dimos
On 10/10/2016 09:06 ??, Aki Tuomi wrote:
> Hi!
>
> quota-status is not supported in proxy configuration. You should use
> quota_warning and quota_over_flag scripts instead.
>
> Aki
>
> On 08.10.2016 03:51, Michael Kliewe wrote:
>> Hello,
>> any news on