Re: Feedback on first, i.e. novice-level, experiences with dovecot

2016-11-21 Thread James
On 20/11/2016 13:51, Michael Felt wrote: I built dovecot using --prefix=/opt (I abhor /usr/local these days - that is so 1984ish). The applications got installed in /opt/bin Well done but I urge you to go a step further. You should put your builds in a sub level of /opt/ to distinguish and a

Re: Exim still accepting emails to nonexistent users

2016-11-21 Thread Heiko Schlittermann
Hi Marti, (Please do not send CC to my private account) Marti Markov (Mo 21 Nov 2016 03:52:54 CET): > > Here is the router: > > virtual_aliases: … > hide data = CHECK_VIRTUAL_ALIASES > local_user: > debug_print = "R: local_user for $local_part@$domain" > driver = accept > do

Re: Exim still accepting emails to nonexistent users

2016-11-21 Thread Heiko Schlittermann
Hi, Heiko Schlittermann (Mo 21 Nov 2016 11:50:13 CET): > a) Routing stage > You need to interact with the user database dovecot uses. > Either you access the user database directory (flat file, LDAP, > whatever) or you use the ${readsocket…} feature of Exim to talk to > dovecot. The readsocket t

Index-cache sizes

2016-11-21 Thread Tom Sommer
I had a customer with an INBOX cache of 400MB+ (5.5GB maildir) which gave me "Error: mmap_anon(474165248) failed: Cannot allocate memory" errors, then I deleted the cache files and ran 'doveadm index -u x...@example.com "*"', now the INBOX cache is 7MB What is up with that? Is the cache now mi

Re: [PATCH] Manually cleanup OpenSSL from dovecot_openssl_common_global_unref()

2016-11-21 Thread Apollon Oikonomopoulos
Hi, On 22:59 Sun 20 Nov , Reuben Farrelly wrote: > Hi, > > This patch: > > > ... which was committed as c164f8afe58c8d83ef2a48aae629c72408dfea01 in > master-2.2, terminally breaks the build with LibreSSL. Obviously this > wasn't tested or considered ;) Yes, unfortunately LibreSSL fakes Op

nologin + reason -> logging reason

2016-11-21 Thread Arkadiusz Miśkiewicz
Hi. I'm using nologin with own reason [1]. That works fine. For example pop3 client gets nice message like "-ERR [AUTH] Account is locked. Please contact support." Unfortunately maillog lacks information details about why user was not allowed to log in. pop3-login: Disconnected (auth failed

Clients creating folders in root when using shared namespace

2016-11-21 Thread Jon Cutting
We have set up dovecot to use a shared namespace, and it works well. However, when a client attempts to create a folder in the namespace, although dovecot responds with permission denied, it still goes on to create a folder, but in the root of our virtual mailbox folder (more confusingly, even issu

Re: Implementing secondary quota w/ "Archive" namespace

2016-11-21 Thread Mark Moseley
On Sun, Nov 20, 2016 at 3:28 PM, Fred Turner wrote: > Hey Everybody— > > Posted this to the list a couple of months ago, but didn’t get any > responses. Is there a better place to ask this question about quota & > namespace configuration? Seems like a lot of the discussion here is a > little deep

Re: nologin + reason -> logging reason

2016-11-21 Thread @lbutlr
On Nov 21, 2016, at 7:39 AM, Arkadiusz Miśkiewicz wrote: > reason is the only thing in maillog that allows to distinguish why user was > not allowed to log in. Um… the only thing? How about where you set the reason in the first place? I think the assumption with nologin is that the admin knows

Re: nologin + reason -> logging reason

2016-11-21 Thread Arkadiusz Miśkiewicz
On Monday 21 of November 2016, @lbutlr wrote: > On Nov 21, 2016, at 7:39 AM, Arkadiusz Miśkiewicz wrote: > > reason is the only thing in maillog that allows to distinguish why user > > was not allowed to log in. > > Um… the only thing? How about where you set the reason in the first place? That

Re: nologin + reason -> logging reason

2016-11-21 Thread Timo Sirainen
On 21 Nov 2016, at 16.39, Arkadiusz Miśkiewicz wrote: > > > Hi. > > I'm using nologin with own reason [1]. That works fine. For example pop3 > client gets nice message like "-ERR [AUTH] Account is locked. Please contact > support." > > > Unfortunately maillog lacks information details about

Re: Implementing secondary quota w/ "Archive" namespace

2016-11-21 Thread Timo Sirainen
On 20 Sep 2016, at 21.28, Fred Turner wrote: > > Mac Pro Server 2012 > Mac OS X Server 10.6.8 > Dovecot 1.1.20apple0.5 That's an old one.. > quota = maildir:User quota:ns= > > quota2 = maildir:ns=testArchive/ > quota2_rule = *:storage=20G > > The first line is already in the default config, w

Re: nologin + reason -> logging reason

2016-11-21 Thread @lbutlr
On Nov 21, 2016, at 2:49 PM, Arkadiusz Miśkiewicz wrote: > On Monday 21 of November 2016, @lbutlr wrote: >> On Nov 21, 2016, at 7:39 AM, Arkadiusz Miśkiewicz wrote: >>> reason is the only thing in maillog that allows to distinguish why user >>> was not allowed to log in. >> >> Um… the only thing

Re: Implementing secondary quota w/ "Archive" namespace

2016-11-21 Thread @lbutlr
On Nov 20, 2016, at 4:28 PM, Fred Turner wrote: >> Mac Pro Server 2012 >> Mac OS X Server 10.6.8 >> Dovecot 1.1.20apple0.5 The 2012 Mac Pro Server shipped with 10.7.3. Did you seriously hack 10.6.8 onto it?

Re: Implementing secondary quota w/ "Archive" namespace

2016-11-21 Thread Fred Turner
Yeah, I gradually figured out it wouldn't work yesterday when delving back into this and testing. No separate quotas per namespaces until 2.1 or something, I think? So, got any suggestions on getting it to work with v2.x? I found an old thread from 2013 by Andreas (I think?) and he didn't seem

Re: Implementing secondary quota w/ "Archive" namespace

2016-11-21 Thread Fred Turner
Lol, may actually be a 2010...which is essentially no different than a 2012. Mac OS X 10.6.8 would work just fine on that hardware. And probably 10.5.8 as well! FT > On Nov 21, 2016, at 19:22, @lbutlr wrote: > > On Nov 20, 2016, at 4:28 PM, Fred Turner wrote: >>> Mac Pro Server 2012 >>> Mac

Re: nologin + reason -> logging reason

2016-11-21 Thread Arkadiusz Miśkiewicz
On Monday 21 of November 2016, Timo Sirainen wrote: > On 21 Nov 2016, at 16.39, Arkadiusz Miśkiewicz wrote: > > Hi. > > > > I'm using nologin with own reason [1]. That works fine. For example pop3 > > client gets nice message like "-ERR [AUTH] Account is locked. Please > > contact support." > >