On Wed, 15 Feb 2017 08:43:23 +0530 Rajesh M wrote:
> christian
>
> the servers i currently own are dell servers. The servers i plan to buy are
> Dell R530, 2U rack servers with 8 x 3.5 inch drives, with 64 gb ram each,
> Hardware raid. I am thinking of 2 X 300 gb ssds raid1 and 6 x 2 tb drives
christian
the servers i currently own are dell servers. The servers i plan to buy are
Dell R530, 2U rack servers with 8 x 3.5 inch drives, with 64 gb ram each,
Hardware raid. I am thinking of 2 X 300 gb ssds raid1 and 6 x 2 tb drives in
raid10 for data. I do not have any experience in setting
On Tue, 14 Feb 2017, KT Walrus wrote:
Another related security situation I've encountered is when a fraudster
has phished a user's password. A user/admin changes the password,
but forgets to invalidate dovecot's cached entry, allowing the fraudster
contunuing access to the mail account until th
> On Feb 14, 2017, at 5:50 PM, Joseph Tam wrote:
>
> Another related security situation I've encountered is when a fraudster
> has phished a user's password. A user/admin changes the password,
> but forgets to invalidate dovecot's cached entry, allowing the fraudster
> contunuing access to the
Rajesh M wrote:
i wish to improve the performance further by caching the logins.
current the same is kept disable because when user's change passwords
then they are not able to immediately login with the new password for
some time. How to solve this issue.
Dovecot shouldn't be doing that. Ac
On 14/02/2017 14:44, Stephan Bosch wrote:
Op 13-2-2017 om 18:15 schreef Ben:
Hi,
I am seeing the followin error in my logs (doveconf -n at the bottom
of this mail):
Feb 13 16:59:59 mxf dovecot: lmtp(45560, b...@example.com): Error:
cs3NOQ7moVj4sQX: sieve: sieve file backend: invalid op
On 14/02/2017 14:44, Stephan Bosch wrote:
Don't specify the "sieve_dir" setting when you're using the new location
syntax for the "sieve" setting. That setting is deprecated and causes
the "sieve" setting to be interpreted differently for backwards
compatibility.
Thanks for the pointer, alt
On Mon, 13 Feb 2017 16:45:21 +0100
Luciano Mannucci wrote:
> where am I supposed to add the -D option in order to get the core file
> dumped so I can examine it?
I think I've got it. I've set my config to:
service pop3-login {
executable = pop3-login -D
inet_listener pop3s {
address = *
Op 13-2-2017 om 18:15 schreef Ben:
Hi,
I am seeing the followin error in my logs (doveconf -n at the bottom
of this mail):
Feb 13 16:59:59 mxf dovecot: lmtp(45560, b...@example.com): Error:
cs3NOQ7moVj4sQX: sieve: sieve file backend: invalid option
`active=~/.dovecot.sieve'
Feb 13 16:
Am 14.02.2017 um 12:44 schrieb Aki Tuomi:
> Is the Erledigt2 folder somehow related to this?
Oh, the user just created Erledigt2 as a workaroud as long as Erledigt
is not accessible while I executed the command for my previous mail.
What concerns me is that on the filesystem Erledigt2, Erledigt/E
On 14.02.2017 13:44, Sven Strickroth wrote:
> Hi,
>
> out of the sudden I've an inaccessible folder with Dovecot 2.2.27
> (c0f36b0) from Debian Jessy backports.
>
> $ doveadm mailbox list -u m...@example.com
> INBOX/Erledigt
> INBOX/Erledigt/Erledigt
> INBOX/Versicherung gesendet
> Sent
> INBOX
>
Hi,
out of the sudden I've an inaccessible folder with Dovecot 2.2.27
(c0f36b0) from Debian Jessy backports.
$ doveadm mailbox list -u m...@example.com
INBOX/Erledigt
INBOX/Erledigt/Erledigt
INBOX/Versicherung gesendet
Sent
INBOX
However, it is not accessible any more, my IMAP client tells me:
"
Hi,
the actual OpenSSL version detection in dovecot is insufficient.
The implementation only checks for SSL_CTRL_SET_ECDH_AUTO.
That was effective for OpenSSL 1.0.2, but in 1.1.0 it is removed.
Thats the code part:
#ifdef SSL_CTRL_SET_ECDH_AUTO
/* OpenSSL >= 1.0.2 automatically handles ECD
13 matches
Mail list logo
