Rules that move mails to Public Folders

WalterH

A long awaited feature has been added to grommunio. Rules that move mails to Public Folders.

1. Configure grommunio server

To make these rules work, modify the file /etc/gromox/exmdb_local.cfg and add this parameter
lda_twostep_ruleproc = 1
This can be done with one line of code, copy and paste this code into an ssh session an grommunio server:
echo "lda_twostep_ruleproc = 1" >> /etc/gromox/exmdb_local.cfg

To activate this change, restart 2 services:

systemctl restart gromox-delivery
systemctl restart gromox-delivery-queue

A limitation is, these rules are currently only configurable in grommunio-web. Outlook cannot save these rules at the moment.

2. Create a rule in grommunio-web

Select Settings - Rules - New to create a Rule

Give the rule a name
For When the message... select a appropriate action
For Do the following... select a sub folder in a Public Folder
An Exception is mostly not needed
Select Stop processing more rules
Click Save to store the rule

This screenshot shows a rule that responds to the words Test for PF in the subject and moves the mail to the sub folder TestPF in the Public Folder.

3. Prerequisites

The mailbox have write permissions in this sub folder in Public Folder.
All current patches (May 2023) applied to the grommunio server.

4. Test the rule

Send a message in this case with the words Test for PF in subject to this mailbox and watch the folder TestPF in Public Folder for the mail to appear.

5. Rules to forward mails to other recipients do not work

Please note, with this configuration inbox rules that forward mails to other recipients do not work. Okt. 31. 2023.

Enjoy grommunio

crpb

Hey Walter,

WalterH echo "lda_twostep_ruleproc = 1" >> /etc/gromox/delivery.cfg

Shouldn't that be /etc/gromox/exmdb_local.cfg?
https://github.com/grommunio/gromox/commit/7ec94fe3f7ef002d9f132594cc5b2bed0b70b059

WalterH

crpb Shouldn't that be /etc/gromox/exmdb_local.cfg?

Yes you are right, /etc/gromox/delivery.cfg is no longer used for this parameter.

weini

Sorry for initially replying in German....

Rules to public folders are not working for me unfortunately.
As soon as an email triggers a public folder forward, the gromox-delivery agent is killed.

Mai 08 14:47:03 systemd[1]: gromox-delivery.service: Main process exited, code=killed, status=11/SEGV
Mai 08 14:47:03 systemd[1]: gromox-delivery.service: Failed with result 'signal'.
Mai 08 14:47:03 systemd[1]: gromox-delivery.service: Scheduled restart job, restart counter is at 1.
Mai 08 14:47:03 systemd[1]: Stopped Gromox mail spooler.
Mai 08 14:47:03 systemd[1]: Started Gromox mail spooler.
Mai 08 14:47:03 delivery[2364343]: gromox-delivery 2.8 (pid 2364343 uid 0)
Mai 08 14:47:03 delivery[2364343]: system: host ID is "server"
Mai 08 14:47:03 delivery[2364343]: system: default domain is "domain.tld"
Mai 08 14:47:03 delivery[2364343]: Reexecing /usr/libexec/gromox/delivery
Mai 08 14:47:03 delivery[2364343]: gromox-delivery 2.8 (pid 2364343 uid 149)
Mai 08 14:47:03 delivery[2364343]: system: host ID is "server"
Mai 08 14:47:03 delivery[2364343]: system: default domain is "domain.tld"
Mai 08 14:47:03 delivery[2364343]: ldap_adaptor: default host <ldapi:///>, base <>, #conn=8, mailattr=mail
Mai 08 14:47:03 delivery[2364343]: alias_resolve: mysql [localhost]:3306, timeout=0, db=grommunio
Mai 08 14:47:03 delivery[2364343]: system: LDA is now running
Mai 08 14:47:03 systemd[1]: gromox-delivery.service: Main process exited, code=killed, status=11/SEGV
Mai 08 14:47:03 systemd[1]: gromox-delivery.service: Failed with result 'signal'.
Mai 08 14:47:03 systemd[1]: gromox-delivery.service: Scheduled restart job, restart counter is at 2.
Mai 08 14:47:03 systemd[1]: Stopped Gromox mail spooler.

My installation has the most up to date versions from the Debian community repository:

||/ Name                                      Version                Architektur  Beschreibung
+++-=========================================-======================-============-=================================================================
ii  grommunio-admin-api                       1.11.17.482afbb-1+65.2 all          Backend for grommunio management
ii  grommunio-admin-common                    6.cb985db-1+2.4        amd64        Common files for grommunio management
ii  grommunio-admin-web                       2.7.0.6.7b082a2-1+49.2 all          Frontend for grommunio management
ii  grommunio-common                          14.dfc18e0-1+19.2      amd64        Common configuration package for grommunio
ii  grommunio-dav                             1.3.11.2b59b5d-1       all          grommunio-dav is CalDAV and CardDAV implementation for grommunio.
ii  grommunio-error-pages                     1.0.6.9c50afb-1+3.3    all          Grommunio-branded error pages for webservers
ii  grommunio-index                           0.1.36.4ebe9ad-1+39.2  amd64        Generator for grommunio-web search indexes
ii  grommunio-sync                            2.0.15.cba7b39-0       all          an implementation of the ActiveSync protocol which is
ii  grommunio-web                             3.2.44.682819a-1+219.1 all          Web access for grommunio
ii  gromox                                    2.8.97.9dcd0b1-1+63.1  amd64        Groupware server (backend) with RPCH, IMAP and Z-MAPI support

But I really love to see that this feature is getting implemented now!

crpb

hmm.. still works here on my test-debian with the same gromox build.
i didn't even configure any permissions on IPM_SUBTREE (0x2) or my Test-Folder
maybe there is more output with /etc/gromox/delivery.cfg:lda_log_level=6 ?

weini

Thanks for the hint, but if I interpret the logs correctly, then this is only the restart of the service. Nothing is written at the time when the rule is processed.

May  8 21:09:34 server systemd[1]: Stopping Gromox local delivery agent frontend...
May  8 21:09:34 server systemd[1]: Stopping Gromox mail spooler...
May  8 21:09:34 server delivery[2478702]: transporter: unloading libgxm_remote_delivery.so
May  8 21:09:34 server delivery[2478702]: transporter: unloading libgxm_mlist_expand.so
May  8 21:09:34 server delivery[2478702]: transporter: unloading libgxm_exmdb_local.so
May  8 21:09:34 server delivery[2478702]: transporter: unloading libgxm_alias_resolve.so
May  8 21:09:34 server delivery[2478702]: service: unloading libgxs_authmgr.so
May  8 21:09:34 server delivery[2478702]: service: unloading libgxs_mysql_adaptor.so
May  8 21:09:34 server delivery[2478702]: service: unloading libgxs_ldap_adaptor.so
May  8 21:09:34 server systemd[1]: gromox-delivery-queue.service: Succeeded.
May  8 21:09:34 server systemd[1]: Stopped Gromox local delivery agent frontend.
May  8 21:09:34 server systemd[1]: gromox-delivery.service: Succeeded.
May  8 21:09:34 server systemd[1]: Stopped Gromox mail spooler.
May  8 21:09:34 server systemd[1]: Started Gromox local delivery agent frontend.
May  8 21:09:34 server systemd[1]: Started Gromox mail spooler.
May  8 21:09:34 server delivery[2478755]: gromox-delivery 2.8 (pid 2478755 uid 0)
May  8 21:09:34 server delivery[2478755]: system: host ID is "server"
May  8 21:09:34 server delivery[2478755]: system: default domain is "domain.tld"
May  8 21:09:34 server delivery[2478755]: system: worker threads: between 1 and 5
May  8 21:09:34 server delivery[2478755]: system: free contexts number is 5
May  8 21:09:34 server delivery[2478755]: system: average mimes number for one context is 8
May  8 21:09:34 server delivery[2478755]: message_dequeue: maximum allocated memory is 1024M
May  8 21:09:34 server delivery[2478755]: Reexecing /usr/libexec/gromox/delivery
May  8 21:09:34 server delivery-queue[2478754]: gromox-delivery-queue 2.8 (pid 2478754 uid 0)
May  8 21:09:34 server delivery-queue[2478754]: system: host ID is "server"
May  8 21:09:34 server delivery-queue[2478754]: system: default domain is "domain.tld"
May  8 21:09:34 server delivery-queue[2478754]: system: rectified contexts number to 400
May  8 21:09:34 server delivery-queue[2478754]: dq: STARTTLS support is off
May  8 21:09:34 server delivery-queue[2478754]: dq: maximum mail length is 64M
May  8 21:09:34 server delivery[2478755]: gromox-delivery 2.8 (pid 2478755 uid 149)
May  8 21:09:34 server delivery[2478755]: system: host ID is "server"
May  8 21:09:34 server delivery[2478755]: system: default domain is "domain.tld"
May  8 21:09:34 server delivery[2478755]: system: worker threads: between 1 and 5
May  8 21:09:34 server delivery[2478755]: system: free contexts number is 5
May  8 21:09:34 server delivery[2478755]: system: average mimes number for one context is 8
May  8 21:09:34 server delivery[2478755]: message_dequeue: maximum allocated memory is 1024M
May  8 21:09:34 server delivery[2478755]: ldap_adaptor: default host <ldapi:///>, base <>, #conn=8, mailattr=mail
May  8 21:09:34 server delivery[2478755]: mysql_adaptor: host [localhost]:3306, #conn=8 timeout=0, db=grommunio
May  8 21:09:34 server delivery[2478755]: mysql_adaptor: Current schema n117. Update available: n122.
May  8 21:09:34 server delivery[2478755]: alias_resolve: mysql [localhost]:3306, timeout=0, db=grommunio
May  8 21:09:34 server delivery[2478755]: I-1612: refreshed alias map (2 entries)
May  8 21:09:34 server delivery[2478755]: textmaps: cpid: 140 IDs, 139 names
May  8 21:09:34 server delivery[2478755]: textmaps: lcid: 412 IDs, 807 names
May  8 21:09:34 server delivery[2478755]: textmaps: lang_charset: 3 mappings
May  8 21:09:34 server delivery[2478755]: textmaps: mime_extension: 190 exts, 125 mimetypes
May  8 21:09:34 server delivery[2478755]: textmaps: 91 translations in folder namedb
May  8 21:09:34 server delivery[2478755]: exmdb_local: x500 org name is "i630355aa"
May  8 21:09:34 server delivery[2478755]: exmdb_local: default charset is "windows-1252"
May  8 21:09:34 server delivery[2478755]: exmdb_local: exmdb connection number is 5
May  8 21:09:34 server delivery[2478755]: exmdb_local: cache scanning interval is 3min
May  8 21:09:34 server delivery[2478755]: exmdb_local: retrying times on temporary failure is 30
May  8 21:09:34 server delivery[2478755]: exmdb_local: failure count for alarm is 10
May  8 21:09:34 server delivery[2478755]: exmdb_local: interval for failure alarm is 1h
May  8 21:09:34 server delivery[2478755]: exmdb_local: alarms interval is 30min
May  8 21:09:34 server delivery[2478755]: exmdb_local: auto response audit capacity is 1000
May  8 21:09:34 server delivery[2478755]: exmdb_local: auto response interval is 3min
May  8 21:09:34 server delivery[2478755]: bounce_gen: postmaster set to <postmaster@server.domain.lan>
May  8 21:09:34 server delivery-queue[2478754]: Reexecing /usr/libexec/gromox/delivery-queue
May  8 21:09:34 server delivery[2478755]: bounce_gen: postmaster set to <postmaster@server.weinberger.lan>
May  8 21:09:34 server delivery[2478755]: system: LDA is now running
May  8 21:09:34 server delivery-queue[2478754]: gromox-delivery-queue 2.8 (pid 2478754 uid 149)
May  8 21:09:34 server delivery-queue[2478754]: system: host ID is "server"
May  8 21:09:34 server delivery-queue[2478754]: system: default domain is "domain.tld"
May  8 21:09:34 server delivery-queue[2478754]: system: rectified contexts number to 400
May  8 21:09:34 server delivery-queue[2478754]: dq: STARTTLS support is off
May  8 21:09:34 server delivery-queue[2478754]: dq: maximum mail length is 64M
May  8 21:09:34 server delivery-queue[2478754]: ldap_adaptor: default host <ldapi:///>, base <>, #conn=8, mailattr=mail
May  8 21:09:34 server delivery-queue[2478754]: system: delivery-queue / SMTP daemon is now running

crpb

that log is only from the restart, try to "break" it again( send a mail matching the rule ).

weini

@crbp: This is exactly what I did and what I worte in my last post. It looks to me that there is no logging triggert by the rule execution. Or is there another log level that I need to increase?

WalterH

Try to remove all rules with this documentation: https://learn.microsoft.com/en-us/outlook/troubleshoot/data-files/delete-corrupted-public-folder-rule . I assume there is one damaged rule. Recreate the rule and test again.

WalterH

We see this issue with an other customer, development investigate in this issue.

weini

@"WalterH"
Thank you! Does it still make sense to test the deletion of the rules? I planned to do this this evening. Is ti necessary to follow the approach described by M$ or would a simple deletion & re-creation also be sufficint, in case that deletion via Outlook or Web UI is feasible?

One of my rules is not triggert by a subject line text match, but by "wurde empfangen (alle Nachrichten)", so it is scanning for all messages that arrive as I want them all to be moved in a public folder. I´ll do a test if modifying the condition will change the behaviour.

weini

Just did a test and adjusted the filter from "wurde empfangen (alle Nachrichten)" to a subject line text matching condition.
Result is the same, gromox-delivery is crashing again. So it is very likely not the specific filter condition.

WalterH

I tested the functionality and did not find any issues, but at customer site in production we see the issues.

WalterH

Was solved with current update: gromox-2.9-18-g538f50343 or newer.

weini

Looks very promissing, a first quick test was successful!
Many thanks to all of you!

WalterH

I assume it was this fix: https://github.com/grommunio/gromox/commit/538f50343b85dbc50f9fbf20b60a9069b1ff455e