No archiving rules - not storing messages by default

[Veaceslav Grecea]

Hello,

We’ve got several piler instances which started to store messages only when we have added a default archiving rule (for required domains and we need to store all messages). Is it possible to get messages stored without any archiving rule ? Once having our domains listed sould messages come in by default ?

Thanks !

[Janos SUTO]

“started to store messages only when we have added a default archiving rule”

I doubt it. Piler needs no archiving rule to work properly. In fact archiving rules define what NOT to archive.

Do the following: remove all archiving rules (feel free to backup the archiving_rule table just in case), then restart all piler daemons. And finally check the mail log, and verify that emails are archived (look for ‘status=stored’ string), and not discarded.

[Veaceslav Grecea]

Hello Janos,

Thanks for your reply.

We did what you have suggested by default, during the initial configuration

No archiving rules, and a list of local domains, and we thought per documentation that piler configured like that should work.

But we have found missing messages in the archive and started to investigate and logs showed up that many messages have been discarded with “discarding: not on mydomains“ error. There is definitely something wrong in our configs that they don’t work like it should. So we have to add a rule which allows everything, restarted piler and all discarded messages went away.

[Janos SUTO]

Then you should either list all your missing domains in the administrator menu, or simply turn off this settings in piler.conf.

Anyway, the archiving rules don’t do what you think they do.

[Cristian Iconomu]

Hi Janos,
Cris here - working on this with Veaceslav, thanks for replying.
Both machines were duplicated and moved to new networks when this occurred, receiving new hostnames - then reconfigured for the new domains. We did this for faster implementation. Both stopped archiving, despite all configuration being done as needed (i.e. domains added in the admin list).

We just noticed after a while and compared the admin config to another (old) instance that was working fine which has this rule - which is why we assumed there is something about it.
I know the rules have nothing to do with archiving emails based on domainsbut the fact is, once the rule was added, archiving started to work (both inbound and outbound emails are archived, even though the rule is only for the From field…
I suspect something was triggered when we added the rule, which restored normal archiving.

We are going to remove the rule, restart services and see if it continues archiving.

If it does, it would be interesting to understand why it stopped to begin with…

[Janos SUTO]

That’s a new info. Anyway, whenever piler discards or rejects an email, be sure to check out the mail log, it should reveal why.

[Cristian Iconomu]

That’s the thing… we only got “not in mydomains” which was weird as the domains were added

[Janos SUTO]

Make sure you have archive_only_mydomains=0 in piler.conf

[Cristian Iconomu]

Thanks Janos, both machines seem ok now.

[Janos SUTO]

Then case is closed.