per-domain archive rules - no effect

Issue #617 resolved
Liam Retrams created an issue

I have just deployed the piler OVA template. I have several domains that I want to archive for. Some need to be retained for 30 days, others for 2557 days.

I have also enabled SaaS mode to give access to the owners of the domains.

I have added the domains under Administration > Domains then I have set retention rules (see attachment) but I am finding that piler is archiving e-mails for 2557 days and ignoring the retention rules (There are messages in there from when I first set up the system).

Here's what the mail.log says:

*#!Oct 11 14:33:56 piler piler[29000]: 400000005619bc8e350e7b3c001369bfb87b: from=e-mail@senderdomain.net, size=69637/27512, attachments=2, reference=, message-id=5022bb$ri7084@tmmta1.aus.sender.local, retention=2557, delay=0.02, delays=0.01/0.01/0.00/0.00/0.00/0.00, status=stored *

I tried running "pilerpurge" after sudo su to user "piler", and the log says this:

*#!Oct 11 17:13:58 piler pilerpurge[3066]: purged 0 messages, 0 bytes *

Am I doing something wrong or is this a bug?

Comments (5)

  1. Janos SUTO repo owner

    Did you restart piler after settings the retention rules? Also check a few messages with pilertest to verify that piler is aware of the proper rule, see the retention line in the output.

  2. Liam Retrams reporter

    Hi Justo, I rebooted the system and it's working -- perhaps the piler restart from web interface isn't working.

    Another question -- I'm finding that if a message is sent from a third party (e.g. someone@gmail.com) to one of my tenants and another person is CC'd in on this message, piler is retaining for 2557 days and ignoring the retention rules that I have set. How can I stop it from doing this?

  3. Janos SUTO repo owner

    You tell me, if it doesn't work. In that case it should provide an error message. For your another question, please provide meaningful, detailed description of the problem, ie. show me your rules, show me the recipients, and the sender.

  4. Log in to comment