Re: version conflict in freebsdports?

2018-01-23 Thread @lbutlr
> On 23 Jan 2018, at 18:49, Vlad K. wrote: > > On 2018-01-24 02:22, @lbutlr wrote: >> I have dovecot 2.2.33 installed. When trying to install >> dovecot2-pigeonhole (v 0.4.19) I get the following when it tries to >> install dovecot 2.2.31_1 > > > dovecot2 was renamed to dovecot back in August

Out of memory on lmtp vsz_limit

2018-01-23 Thread Terence Lau
Hi, We've been getting these types or errors for quite a while now ... Fatal: master: service(lmtp): child 63477 returned error 83 (Out of memory (service lmtp { vsz_limit=4096 MB }, you may need to increase it) ... and these errors have been decreasing in occurrence as we increased the defaul

Re: version conflict in freebsdports?

2018-01-23 Thread Vlad K.
On 2018-01-24 02:22, @lbutlr wrote: I have dovecot 2.2.33 installed. When trying to install dovecot2-pigeonhole (v 0.4.19) I get the following when it tries to install dovecot 2.2.31_1 dovecot2 was renamed to dovecot back in August, so was dovecot2-pigeonhole to dovecot-pigeonhole, as dovecot

version conflict in freebsdports?

2018-01-23 Thread @lbutlr
I have dovecot 2.2.33 installed. When trying to install dovecot2-pigeonhole (v 0.4.19) I get the following when it tries to install dovecot 2.2.31_1 I run portsnap fetch update daily, and I ran it again after this error, but same result. ===> Installing for dovecot2-2.2.31_1 ===> Checking if

Re: PDFs getting mangled

2018-01-23 Thread Stephan Bosch
Op 1/22/2018 om 8:58 PM schreef Stephan Bosch: > Op 1/21/2018 om 4:34 PM schreef Stephan Bosch: >> Op 1/20/2018 om 11:01 PM schreef Adam Weinberger: On 20 Jan, 2018, at 10:05, Adam Weinberger wrote: > On 19 Jan, 2018, at 4:39, Aki Tuomi wrote: > > > > On 19.01.2

Re: Dovecot 2.3.0 TLS

2018-01-23 Thread Mark Moseley
On Tue, Jan 23, 2018 at 10:05 AM, Aki Tuomi wrote: > > > On January 23, 2018 at 7:09 PM Arkadiusz Miśkiewicz > wrote: > > > > > > On Thursday 11 of January 2018, Aki Tuomi wrote: > > > > > Seems we might've made a unexpected change here when we revamped the > ssl > > > code. > > > > Revamped, in

Auth cache prevents login when non-password fields change

2018-01-23 Thread Tom Sommer
The auth cache contains all fields returned by "password_query" (in itself a little odd), including the fields "nologin" and "reason". If a user is cached with "nologin=Y" and the database-source is changed so nologin condition is no longer true, then the cache prevents login for as long as th

Re: Panic: data stack: Out of memory when allocating bytes

2018-01-23 Thread Josef 'Jeff' Sipek
On Tue, Jan 23, 2018 at 14:03:27 -0500, Josef 'Jeff' Sipek wrote: > On Tue, Jan 23, 2018 at 18:21:38 +0100, Thomas Robers wrote: > > Hello, > > > > I'm using Dovecot 2.3 and sometimes i get this: > > > > --- snip --- > > Jan 23 14:23:13 mail dovecot: imap(b...@tutech.de)<4880>: > > Panic: data st

Re: Panic: data stack: Out of memory when allocating bytes

2018-01-23 Thread Josef 'Jeff' Sipek
On Tue, Jan 23, 2018 at 18:21:38 +0100, Thomas Robers wrote: > Hello, > > I'm using Dovecot 2.3 and sometimes i get this: > > --- snip --- > Jan 23 14:23:13 mail dovecot: imap(b...@tutech.de)<4880>: > Panic: data stack: Out of memory when allocating 134217768 bytes Interesting... imap is trying

Re: Dovecot 2.3.0 TLS

2018-01-23 Thread Aki Tuomi
> On January 23, 2018 at 7:09 PM Arkadiusz Miśkiewicz wrote: > > > On Thursday 11 of January 2018, Aki Tuomi wrote: > > > Seems we might've made a unexpected change here when we revamped the ssl > > code. > > Revamped, interesting, can it support milions certs now on single machine? > (so

Panic: data stack: Out of memory when allocating bytes

2018-01-23 Thread Thomas Robers
Hello, I'm using Dovecot 2.3 and sometimes i get this: --- snip --- Jan 23 14:23:13 mail dovecot: imap(b...@tutech.de)<4880>: Panic: data stack: Out of memory when allocating 134217768 bytes Jan 23 14:23:13 mail dovecot: imap(b...@tutech.de)<4880>: Fatal: master: service(imap): child 4880 ki

Re: Dovecot 2.3.0 TLS

2018-01-23 Thread Arkadiusz Miśkiewicz
On Thursday 11 of January 2018, Aki Tuomi wrote: > Seems we might've made a unexpected change here when we revamped the ssl > code. Revamped, interesting, can it support milions certs now on single machine? (so are certs loaded by demand and not wasting memory) > Aki -- Arkadiusz Miśkiewicz

Re: rewrite copy to trash->delete->expunge mail with move??

2018-01-23 Thread LuKreme
On Jan 22, 2018, at 01:35, Chi Min Wang wrote: > CONFIDENTIALITY NOTICE:This e-mail and any attachments are confidential and > may be legally privileged. > If you are not the intended recipient, (i) please do not read or disclose to > others, and (ii) please > notify immediately the sender by re

Re: How to set autoexpunge rule for single user mailbox in dovecot conf?

2018-01-23 Thread Steffen Kaiser
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 23 Jan 2018, Alexey Murz Korepov wrote: I need to set autoexpunge rule only for one single user and one mailbox (mail folder), so apply it only for user al...@example.com mailbox INBOX. How can I set namespace in dovecot config, that will ap

Re: LAYOUT=fs

2018-01-23 Thread Aki Tuomi
On 23.01.2018 12:58, Jungersen, Danjel - Jungersen Grafisk ApS wrote: > > > On 23 Jan 2018 at 11:30, Aki Tuomi wrote: > > > > > On 23.01.2018 11:27, Jungersen, Danjel - Jungersen Grafisk ApS wrote: >

Re: LAYOUT=fs

2018-01-23 Thread Jungersen, Danjel - Jungersen Grafisk ApS
On 23 Jan 2018 at 11:30, Aki Tuomi wrote: On 23.01.2018 11:27, Jungersen, Danjel - Jungersen Grafisk ApS wrote: On 22 Jan 2018 at 10:28, Aki Tuomi wrote: On 22.01.2018 00:46, Jungersen, Danjel - Jungersen Grafisk ApS wrote: Hi there. I have read what I could fi

Re: How to set autoexpunge rule for single user mailbox in dovecot conf?

2018-01-23 Thread Aki Tuomi
You can do passdb {   driver = passwd-file   args =  /path/to/some/file   skip = unauthenticated } and put in this file al...@example.com::noauthenticate userdb_namespace/inbox/mailbox/INBOX/autoexpunge=31d or nopassword instead of noauthenticate. Please keep replies in-list. Aki On 23.0

Re: How to set autoexpunge rule for single user mailbox in dovecot conf?

2018-01-23 Thread Aki Tuomi
Configure namespace {    mailbox {    } } and return from userdb namespace//mailbox//autoexpunge=value Ak On 23.01.2018 11:57, Alexey Murz Korepov wrote: > I need to set autoexpunge rule only for one single user and one > mailbox (mail folder), so apply it only for user al...@example.com >

How to set autoexpunge rule for single user mailbox in dovecot conf?

2018-01-23 Thread Alexey Murz Korepov
I need to set autoexpunge rule only for one single user and one mailbox (mail folder), so apply it only for user al...@example.com mailbox INBOX. How can I set namespace in dovecot config, that will apply only to single user? -- Best regards, Alexey Murz Korepov. Email, Jabber: mur...@gmail.com

Re: LAYOUT=fs

2018-01-23 Thread Aki Tuomi
On 23.01.2018 11:27, Jungersen, Danjel - Jungersen Grafisk ApS wrote: > > > On 22 Jan 2018 at 10:28, Aki Tuomi wrote: > > > > > On 22.01.2018 00:46, Jungersen, Danjel - Jungersen Grafisk ApS wrote: > Hi there. > > I have rea

Re: LAYOUT=fs

2018-01-23 Thread Jungersen, Danjel - Jungersen Grafisk ApS
On 22 Jan 2018 at 10:28, Aki Tuomi wrote: On 22.01.2018 00:46, Jungersen, Danjel - Jungersen Grafisk ApS wrote: Hi there. I have read what I could find, but not enough apparently. I am about to migrate my server to a postfix / dovecot setup. I have stumbled on the mentio

Re: LAYOUT=fs

2018-01-23 Thread Aki Tuomi
On 22.01.2018 00:46, Jungersen, Danjel - Jungersen Grafisk ApS wrote: > Hi there. > > I have read what I could find, but not enough apparently. > > I am about to migrate my server to a postfix / dovecot setup. > > I have stumbled on the mentioned option and are wondering if I should > use it. > >

Re: Dovecot 2.3.0 TLS

2018-01-23 Thread Odhiambo Washington
On 23 January 2018 at 10:35, Aki Tuomi wrote: > > > On 22.01.2018 22:14, Odhiambo Washington wrote: > > > > On 22 January 2018 at 23:10, Matthias Fechner wrote: > >> Dear Odhiambo, >> >> Am 22.01.2018 um 19:58 schrieb Odhiambo Washington: >> >> ...and I am still unable to successfully compile 2.