Re: v2.3.0 release candidate released

What am I missing here: OS = FreeBSD 8.4 Here is how it fails during `gmake`: mv -f .deps/test_auth_cache-test-auth-cache.Tpo .deps/test_auth_cache-test-auth-cache.Po gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-auth -I../../src/lib-test -I../../src/lib-dict

Re: POP3 lock

Am 19.12.2017 um 21:32 schrieb The Doctor: > This might be trivial or not. > > I have a customer access his e-mail via POP3 using multiple devs. > > I recommend they switch to IMAP , however, > > How can the POP3 locking be made into a non-issue? > > -- > Member - Liberal International This is

POP3 lock

This might be trivial or not. I have a customer access his e-mail via POP3 using multiple devs. I recommend they switch to IMAP , however, How can the POP3 locking be made into a non-issue? -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca Yahweh, Queen &

Re: IMAP proxy

2017-12-15 18:21 GMT+01:00 Aki Tuomi : > Return from passdb, 'proxy host=your-new-host port=143 ssl=starttls' So, instead of returning the current db output: "user, password, userdb_mail, userdb_sieve, .." is enough to only return "proxy host=your-new-host port=143

detect suspicious logins

does anyone know of a linux module (maybe similar to fail2ban) that could be installed which would monitor email logs (sign ins) and alert the user to any suspicious activity on their account? i suspect it would need to log geo location, device type and ip address to a database. it seems

Panic: file-lock.c

Today we had an unclean shutdown of our NFS filler and have had lots of issues with mailboxes being re-synced, mostly all the issues are now resolved but we are seeing the following appear for one user on our system. Dec 19 16:15:29 imap(xxx@xxx.com)(xxx@xxx.com): Panic: file

Re: sieve_pipe_socket_dir not created at startup for configured pipe service

> On December 19, 2017 at 5:06 AM Garth Corral wrote: > > > In looking at this further, I’m not seeing how this can be configured as > documented and still work. > > The sieve_pipe_socket_dir setting, as the documentation suggests, appears to > be used by the plugin to

Re: Released Pigeonhole v0.5.0.rc1 for Dovecot v2.3.0.rc1.

On 19 Dec 2017, at 03:24, Larry Rosenman wrote: > As soon as possible after release. I'm the maintainer for pigeonhole, and > Adam Weinberger is the maintainer for dovecot (I'm AKA l...@freebsd.org). Oh good. Time to start diving in to pigeonhole :) -- Apple broke

Re: Released Pigeonhole v0.5.0.rc1 for Dovecot v2.3.0.rc1.

As soon as possible after release.  I'm the maintainer for pigeonhole, and Adam Weinberger is the maintainer for dovecot (I'm AKA l...@freebsd.org). Sent from my T-Mobile 4G LTE Device Original message From: "@lbutlr" Date: 12/19/17 4:19 AM (GMT-06:00)

Re: Released Pigeonhole v0.5.0.rc1 for Dovecot v2.3.0.rc1.

> On 18 Dec 2017, at 14:58, Stephan Bosch wrote: > > Here is the Pigeonhole release candidate that goes with the Dovecot > v2.3 release candidate. Of course, a large part of this release consists > of compatibility changes for Dovecot v2.3. Apart from that, not much >

Re: v2.3.0 release candidate released

On Mon, Dec 18, 2017 at 05:23:28PM +0200, Timo Sirainen wrote: > https://dovecot.org/releases/2.3/rc/dovecot-2.3.0.rc1.tar.gz > https://dovecot.org/releases/2.3/rc/dovecot-2.3.0.rc1.tar.gz.sig Please do not feed libraries into LDFLAGS. It is wrong and breaks with --as-needed: [...] checking

Re: v2.3.0 release candidate released

On Mon, Dec 18, 2017 at 05:23:28PM +0200, Timo Sirainen wrote: > https://dovecot.org/releases/2.3/rc/dovecot-2.3.0.rc1.tar.gz > https://dovecot.org/releases/2.3/rc/dovecot-2.3.0.rc1.tar.gz.sig Some source based distros like Gentoo already enable -D_FORTIFY_SOURCE=2 by default resulting in the