search for: 78bedce1

...estarting, logging in and out several times, I still see messages days/weeks past the autoexpunge setting. I checked the logs but never see any autoexpunge messages logged. Is there something else that needs to be set to trigger this? -- Robert inoc.net!rblayzor XMPP: rblayzor.AT.inoc.net PGP Key: 78BEDCE1 @ pgp.mit.edu

A bit off topic, but I was wondering if anyone here has a solution for centrally managing sieve for multiple users from a custom web application? We would like to implement pigeonhole sieve on our dovecot cluster, however we need to be able to access user?s sieve configurations from a central location for troubleshooting and support purposes.

> On August 5, 2016 at 6:47 PM "Michael A. Peters" <mpeters at domblogger.net> wrote: > > > On 08/05/2016 08:41 AM, Robert Blayzor wrote: > > Is there a way to configure Dovecot to perhaps filter/enforce which passwords are accepted before authenticating? > > > > Ie: Reject immediately (without a database lookup) if password is not X characters in

.../Tools/Doveadm/Move) Ok, but that?s not how the documentation for expire or this features reads. According to the docs it?s based off the ?saved timestamp?, not a deleted flag? So it?s based off ?saved timestamp? *and* deleted flag? -- Robert inoc.net!rblayzor XMPP: rblayzor.AT.inoc.net PGP Key: 78BEDCE1 @ pgp.mit.edu

...plete output of doveconf -n please. That?s what I thought. If I run expunge from doveadm manually, it will work as expected. I just never seem to get autoexpunge to fire. Looking in the logs, I see no errors: Below is the config? -- Robert inoc.net!rblayzor XMPP: rblayzor.AT.inoc.net PGP Key: 78BEDCE1 @ pgp.mit.edu # 2.2.21 (5345f22): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.9 (357ac0a0e68b+) # OS: FreeBSD 10.2-RELEASE-p8 amd64 doveconf: Warning: Dovecot was last started using /etc/dovecot/dovecot.conf, but this config is /usr/local/etc/dovecot/dovecot.conf auth_mechan...

...geonhole sieve on our dovecot cluster, however we need to be able to access user?s sieve configurations from a central location for troubleshooting and support purposes. Couldn?t this be done with ManageSieve and a master login? -- Robert inoc.net!rblayzor Jabber: rblayzor.AT.inoc.net PGP Key: 78BEDCE1 @ pgp.mit.edu

pid 31943 (dovecot), uid 0: exited on signal 11 (core dumped) dovecot --version 2.2.21 (5345f22) uname -a FreeBSD 10.3-BETA2 #0 r295966M: amd64 bt full #0 0x00000008008eb037 in t_push (marker=0x0) at data-stack.c:133 133 data-stack.c: No such file or directory. in data-stack.c (gdb) bt full #0 0x00000008008eb037 in t_push (marker=0x0) at data-stack.c:133 frame_block = (struct

Is there a way to configure Dovecot to perhaps filter/enforce which passwords are accepted before authenticating? Ie: Reject immediately (without a database lookup) if password is not X characters in length? ? -- Robert inoc.net!rblayzor XMPP: rblayzor.AT.inoc.net PGP Key: 78BEDCE1 @ pgp.mit.edu

dovecot --version 2.2.21 (5345f22) FreeBSD 10.2-RELEASE-p11 FreeBSD 10.2-RELEASE-p11 #0 r294908M: amd64 Core was generated by `dovecot'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/local/lib/dovecot/libdovecot.so.0...done. Loaded symbols for /usr/local/lib/dovecot/libdovecot.so.0 Reading symbols from /lib/libc.so.7...Reading symbols from