AW: AW: dovecot & iOS

Hmm, i would change to: mail_location = maildir:~/Maildir:INBOX=~/Maildir/Inbox:LAYOUT=fs:CONTROL=~/Maildata/.CONTRO L:INDEX=~/Maildata/.INDEX so that i have mails in ~/Maildir and .CONTROL and .INDEX in ~/Maildata -Ursprüngliche Nachricht- Von: dovecot

AW: AW: dovecot & iOS

So stop dovecot, change setting, move files, start dovecot...? -Ursprüngliche Nachricht- Von: dovecot [mailto:dovecot-boun...@dovecot.org] Im Auftrag von Aki Tuomi Gesendet: Dienstag, 11. April 2017 11:09 An: dovecot@dovecot.org Betreff: Re: AW: dovecot & iOS The easiest way if you have

Released Pigeonhole v0.4.18 for Dovecot v2.2.29.

Hello Dovecot users, Here's the definitive 0.4.18 release. There were no changes since the release candidate. Changelog v0.4.18: + imapsieve plugin: Implemented the copy_source_after rule action. When this is enabled for a mailbox rule, the specified Sieve script is executed for the message

Re: IMAP hibernate and scalability in general

On Mon, 10 Apr 2017 23:11:24 +0300 Timo Sirainen wrote: > On 10 Apr 2017, at 21.49, Mark Moseley wrote: > > > > Timo, any sense on where (if any) the point is where there are so many > > connections on a given login process that it would get too busy to keep up? > > I.e.

Re: Vpopmail Error

This patch worked for me on CentOS 7: diff -uNr dovecot-2.2.29/src/auth/userdb-vpopmail.c dovecot-2.2.29-new/src/auth/userdb-vpopmail.c --- dovecot-2.2.29/src/auth/userdb-vpopmail.c 2017-02-20 02:34:52.0 -0700 +++ dovecot-2.2.29-new/src/auth/userdb-vpopmail.c 2017-04-11

Re: Vpopmail Error

Stupid copypaste... can you do the change manually, it fails on tabs vs. spaces errors now. We'll get the commit out bit later. Aki > On April 11, 2017 at 8:29 PM Bobber wrote: > > > Not working: > > > patching file userdb-vpopmail.c > > Hunk #1 FAILED at 54. > > 1 out of

Re: Vpopmail Error

Not working: patching file userdb-vpopmail.c Hunk #1 FAILED at 54. 1 out of 1 hunk FAILED -- saving rejects to file userdb-vpopmail.c.rej Original Message Subject: Re: Vpopmail Error From: Aki Tuomi To: dovecot@dovecot.org, Bobber

Re: Vpopmail Error

diff --git a/src/auth/userdb-vpopmail.c b/src/auth/userdb-vpopmail.c index 5042dcf..d344fcd 100644 --- a/src/auth/userdb-vpopmail.c +++ b/src/auth/userdb-vpopmail.c @@ -54,7 +54,7 @@ struct vqpasswd *vpopmail_lookup_vqp(struct auth_request *request, static const char *

Re: [Dovecot-news] v2.2.29.rc1 released

> On April 7, 2017 at 6:54 PM Aki Tuomi wrote: > > > > > On April 7, 2017 at 6:48 PM "Daniel J. Luke" wrote: > > > > > > On Apr 7, 2017, at 11:17 AM, Aki Tuomi wrote: > > >> On April 7, 2017 at 6:00 PM "Daniel J. Luke"

Re: Vpopmail Error

Still not working. I'm now getting this error: userdb-vpopmail.c: In function ‘userdb_vpopmail_get_quota’: userdb-vpopmail.c:65:13: error: assignment of member ‘key’ in read-only object tab[0].key = 'q'; ^ userdb-vpopmail.c:66:15: error: assignment of member ‘value’ in

Re: How to use quota with dovecot

1 On 11.04.2017 13:36, Mik J wrote: > Hello,Thank you to both of you for your answers.I just use imap.I'm going to > look at your examples and 15-lda.confHave a nice week > > Le Dimanche 9 avril 2017 17h44, chaouche yacine > a écrit : > > > > > On Saturday,

Re: How to use quota with dovecot

Hello,Thank you to both of you for your answers.I just use imap.I'm going to look at your examples and 15-lda.confHave a nice week Le Dimanche 9 avril 2017 17h44, chaouche yacine a écrit : On Saturday, April 8, 2017 9:47 AM, Mik J

Re: 2.2.29 failing tests

On 11.04.2017 12:13, Odhiambo Washington wrote: > On 11 April 2017 at 10:04, Timo Sirainen wrote: > >> On 11 Apr 2017, at 9.54, Timo Sirainen wrote: >>> On 11 Apr 2017, at 0.39, Peter wrote: It's failing tests on CentOS 6, it looks like

Re: 2.2.29 failing tests (was: Re: v2.2.29 released)

On 11 April 2017 at 10:04, Timo Sirainen wrote: > On 11 Apr 2017, at 9.54, Timo Sirainen wrote: > > > > On 11 Apr 2017, at 0.39, Peter wrote: > >> > >> It's failing tests on CentOS 6, it looks like it's expecting the IMAP > >> server to be

Re: AW: dovecot & iOS

The easiest way if you have only very few users is to just copy the files into correct place. Aki On 11.04.2017 12:04, Dirk Laurenz wrote: > Thanks, so how can i migrate this? > > -Ursprüngliche Nachricht- > Von: dovecot [mailto:dovecot-boun...@dovecot.org] Im Auftrag von Aki Tuomi >

AW: dovecot & iOS

Thanks, so how can i migrate this? -Ursprüngliche Nachricht- Von: dovecot [mailto:dovecot-boun...@dovecot.org] Im Auftrag von Aki Tuomi Gesendet: Montag, 20. März 2017 12:07 An: dovecot@dovecot.org Betreff: Re: dovecot & iOS On 20.03.2017 12:58, Steffen Kaiser wrote: > On Thu, 16 Mar

[Dovecot-news] CVE-2017-2669: Dovecot DoS when passdb dict was used for authentication

CVSS: 6.5 (CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H) Vulnerable versions: 2.2.26 - 2.2.28 Fixed version(s): 2.2.29 Broken by a3783f8a3c9cd816b51e77a922f82301512fcf22 Fixed by 30feb7a30f193197f1aab8a7b04a26b42735 Dovecot supports "dict" passdb and userdb:

Re: 2.2.29 failing tests

On 11/04/17 19:04, Timo Sirainen wrote: > No, I hadn't cherry-picked one change and due to some other reasons > didn't notice this unit test failing :( > > Fixed > by > https://github.com/dovecot/core/commit/3a1c64363a64cdfe9153eb6292d8923f38955d82 Thanks, I applied that patch and it builds and

Re: Vpopmail Error

On 10 Apr 2017, at 23.55, Bobber wrote: > > I'm trying to compile the latest Dovecot (v2.2.29) and when I run make I get > this error: > >> auth-userdb-vpopmail.o: In function `userdb_vpopmail_get_quota': >> /usr/local/src/dovecot-2.2.29/src/auth/userdb-vpopmail.c:64:

Re: 2.2.29 failing tests (was: Re: v2.2.29 released)

On 11 Apr 2017, at 9.54, Timo Sirainen wrote: > > On 11 Apr 2017, at 0.39, Peter wrote: >> >> It's failing tests on CentOS 6, it looks like it's expecting the IMAP >> server to be running when it isn't, perhaps this test should soft-fail? > > The test is

Re: 2.2.29 failing tests (was: Re: v2.2.29 released)

On 11 Apr 2017, at 0.39, Peter wrote: > > It's failing tests on CentOS 6, it looks like it's expecting the IMAP > server to be running when it isn't, perhaps this test should soft-fail? The test is itself running both the client and the server. Most of those errors are