similar to: Dovecot 2.2.20 autoexpunge

> On Dec 22, 2015, at 9:49 AM, Dominik Breu <dominik at dominikbreu.de> wrote: > the autoexpunge feature only removes mails wich have the \Delete Flag so no deletion of mails wich doesn't have this Flag(see https://tools.ietf.org/html/rfc4315#section-2.1 or http://wiki2.dovecot.org/Tools/Doveadm/Expunge) > > you could run a cron job with a doveadm move comando to move the

On Dec 22, 2015, at 2:56 PM, Teemu Huovila <teemu.huovila at dovecot.fi> wrote: > > The autoexpunge feature does not check the \Deleted flag. > > Are any errors logged in "doveadm log errors"? Could you post your complete 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

Per RFC 8501 seciont 2.2 https://datatracker.ietf.org/doc/html/rfc8501 I have attempted to use a wildcard on a /64 boundary within a zonefile for NSD, but it doesn't not appear to work. PTR lookups fail... tested with, ie: $ORIGIN 1.1.0.0.8.5.1.b.2.2.5.2.ip6.arpa. * PTR my.fqdn.net. Did not work... or would you have to use? (not tested) *.*.*.*.*.*.*.*.*.*.*.* PTR .... --

We have the requirement to provide SSL on some IP addresses, but not others on our servers. Providing SSL is the easy part and we're able to use multiple SSL certificates now. (thanks Timo!) All is working ok, but we several IP hosts that do not require SSL and do not have valid certificates. While we can limit access via a firewall ACL to TLS connect ports (993/995) we can't do so on

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.

Samba organizers might want to look into this: [ns1:~] dig 150.73.70.66.relays.osirusoft.com ; <<>> DiG 9.2.2 <<>> 150.73.70.66.relays.osirusoft.com ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 28005 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 13 ;; QUESTION SECTION:

> 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

I have a rather busy Apache 2.2 server; tons of small & some large requests. It's a standard Dell 2650 server using the bge (broadcom) network driver. I seem to have a rather strange problem where after just a day or so Apache just stops processing new connections. You can connect to port 80, but trying to get Apache to process any data just hangs. There is nothing strange in

Currently pigeonhole supports reject which would generate a NDR for each message. (If I understand the current documentation) Using Dovecot LMTP it would be more optimal to kick a 5xx back to the primary MTA to reject the delivery rather than generating more back scatter NDRs. Anyone know if this is possible now (to forgo the NDR)'s or do we need to wait for ereject ? If so, how much work

In reading the Dovecot NFS WIKI entry: http://wiki2.dovecot.org/NFS It mentions a FreeBSD NFS client caching bug. I believe that bug only exists pre-8.x ? It seems that a patch in the PR notes was MFC'd and made it into 8.x at some point. (at least I checked the source in 8.3 and it was there). So I assume that FreeBSD 8.x mitigates the issue? Maybe not? So our deployment is multi

On Jan 13, 2015, at 8:30 PM, Reindl Harald <h.reindl at thelounge.net> wrote: > > so what you want in your OP is just DISCARD in a sieve script and there is no point in "Using Dovecot LMTP it would be more optimal to kick a 5xx back" when the desired result is DISCARD > > why do you want the burden of keep the SMTP session with the client open until the mail is

On 1/1/2015 4:17 PM, Robert Blayzor wrote: > On Jan 1, 2015, at 9:58 AM, Robert Blayzor <rblayzor.bulk at inoc.net> wrote: >>> Hmm. This smells like a bug. I notice that your modification times of >>> the .sieve and .svbin file are exactly the same (that is somewhat >>> unusual). I'm looking at a potential bug that would explain your problem. >>>

On Jan 13, 2015, at 7:34 PM, Reindl Harald <h.reindl at thelounge.net> wrote: > > and what would that change? > nothing if you think about how mail works! > > * the MTA receives the message > * the MTA confirms with 2xx status code > * later the delivery server rejects > * the MTA *must* create a bounce > > just don't reject mails after you confirmed you

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

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

On May 28, 2015, at 4:24 PM, list at airstreamcomm.net wrote: > > 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

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

On 02/05/16 16:51, Timo Sirainen wrote: > On 02 May 2016, at 03:47, Leon Kyneur <leon at f-m.fm> wrote: >> Was excited to see that wildcards are now possible on autoexpunge in the 2.2.24 release. >> >> However I'm trying to configure these from the userdb lookup and it doesn't appear to be working. >> >> if I set in 15-mailboxes.conf >> mailbox

Was excited to see that wildcards are now possible on autoexpunge in the 2.2.24 release. However I'm trying to configure these from the userdb lookup and it doesn't appear to be working. if I set in 15-mailboxes.conf mailbox Trash/* { ... autoexpunge = 10m } everything works.. however if I return =namespace/inbox/mailbox/Trash/*/autoexpunge=10m via userdb - it does not. Logs

Hello! I have the autoexpunge settings defined inside protocol imap thus (and it works): protocol imap { ? mail_plugins = quota notify replication imap_quota imap_sieve ? namespace inbox { ??? location = ??? mailbox Ham { ????? autoexpunge = 365 days ??? } ??? mailbox Spam { ????? autoexpunge = 365 days ??? } ??? mailbox Trash { ????? autoexpunge = 180 days ??? } ??? prefix = ? }