Don't know if you tried (from very old forum post) but answering this with sieve in mind or whatever they are using.For recent versions, there is this link: https://wiki.zimbra.com/wiki/Log4j2 which still has filter listed but different syntax.
Provided I am reading the above wiki documentation correctly, it might be this for more modern versions of zimbra.Never tried it myself but from wiki looks like it might do what you are asking. Another option since user filters are stored in ldap is to either dump the contents to stdout or to dump the specific user via zmprov to stdout.
I add a tag when I create any filter with the same name as the filter so I can tell which fired when I don't see email in folders I expect and want to know how it got there.![;-)]( "Wink")
... but that strategy would not help with discard.
HTH,
Jim
Code:
log4j.logger.zimbra.filter=DEBUGProvided I am reading the above wiki documentation correctly, it might be this for more modern versions of zimbra.
Code:
logger.zimbra.name = zimbra.filter logger.zimbra.level = DEBUG I add a tag when I create any filter with the same name as the filter so I can tell which fired when I don't see email in folders I expect and want to know how it got there.
... but that strategy would not help with discard. HTH,
Jim
Statistics: Posted by JDunphy — Tue Aug 13, 2024 8:20 pm