Displaying 20 results from an estimated 6000 matches similar to: "Quota plug-in, do the directors also need it enabled?"
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:
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 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 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 Aug 21
4
sometimes no shared cipher after upgrade from 2.2 to 2.3
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:
SSL_accept() failed: error:1408A0C1:SSL routines:ssl3_get_client_hello:no
shared cipher,
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 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
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
2015 Oct 13
0
Dualstack IPv4/IPv6 setup with directors
On 13 Oct 2015, at 22:31, Heiko Schlittermann <hs at schlittermann.de> wrote:
>
> Hi,
>
> still using 2.2.9, I've two directors, and these directors
> use both IPv4/IPv6 addresses.
>
> `host directors.<domain>` returns one A and AAA for each
> of the two directors:
>
> directors.<domain> has address 149.x.y.96 (director1)
2015 Oct 13
2
Dualstack IPv4/IPv6 setup with directors
Hi,
still using 2.2.9, I've two directors, and these directors
use both IPv4/IPv6 addresses.
`host directors.<domain>` returns one A and AAA for each
of the two directors:
directors.<domain> has address 149.x.y.96 (director1)
directors.<domain> has address 149.x.y.97 (director2)
directors.<domain> has IPv6 address
2020 Mar 18
0
Quota plugin and director
Ciao Simone,
why you want each backend to recalc quota only for its managed users and
not run "doveadm quota recalc -A" only one time from a backend tha
recalc quota for all users?
Il 10/03/20 11:18, Simone Lazzaris ha scritto:
> Hello dovecot!
>
> I administer a dovecot installation with 30k users. I've got 4 dovecot
> directors as frontend and 10 backends.
>
2011 Jan 11
1
Connection queue full on my directors
I finally upgraded to v1.2.16 on my backend servers, with ldap instead of
previously mysql, and put a couple of dovecot v2.0.8 directors in front
of them (used haproxy previously). It seemed to work OK initially, but
after a few hours we got bit by "Connection queue full" problems on the
directors.
So I now set default_process_limit=512 and also:
service anvil {
2024 Feb 15
2
2024 X.Org Board of Directors Elections Nomination period is NOW
We are seeking nominations for candidates for election to the X.Org
Foundation Board of Directors. All X.Org Foundation members are eligible
for election to the board.
Nominations for the 2024 election are now open and will remain open
until 23:59 UTC on 26 February 2024.
The Board consists of directors elected from the membership. Each year,
an election is held to bring the total number of
2017 Feb 17
1
Problem with Let's Encrypt Certificate
Hey.
Thanks again for your help. I took the "dovecot -n" while the StartSSL
Certificate was active, so the chain.pem was correct.
Finally I found the issue! :-) But I still have no idea why the problem
happens with Thunderbird.
I used dehydrated to fetch the certificates from Let's Encrypt and as I
said, it works for most clients pretty well. (Tried: Mulberry, Claws
Mail, Outlook
2020 Mar 10
2
Quota plugin and director
Hello dovecot!
I administer a dovecot installation with 30k users. I've got 4 dovecot directors as frontend
and 10 backends.
The mailbox are now in maildir format, with maildir++ quota, on a shared netapp filer.
Indexes are local on each backend.
I'm reconfiguring the quota plugin: as a first step, I want to use the clone plugin to keep a
copy of the quota on a redis database. Next,
2012 Dec 27
1
Mixing v2.1 and 2.0 directors ?
I'm preparing to set up a new set of directors on
dovecot-ee-2.1.10.3-1, but would prefer to do this a bit gradually.
Will it be OK to set up a ring of directors with 2x
dovecot-ee-2.1.10.3-1 and 2x dovecot-2.0.14 ?
-jf
2007 Jun 23
0
[1062] trunk/wxruby2/swig/classes: Remove directors from some common classes where they are unnecessary
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><meta http-equiv="content-type" content="text/html; charset=utf-8" /><style type="text/css"><!--
#msg dl { border: 1px #006 solid; background: #369; padding:
2020 Oct 22
2
Directors and LMTP: mailAlternateAddress of same user
Good evening everyone,
I'd like to paste a problem i experience the last days with a mail
cluster system based on three dovecot servers and two directors in front
of them. The Directors are proxying the auth requests to the dovecot
servers below (LDAP). The protocols i use are imap/managesieve/lmtp.?
The setup works as intented, exept one detail. There are a lot of users
that happen to