Il 15/07/2016 04:05, Rick King via Users ha scritto:
Is there a way to NOT track read-receipt messages in the cbpolicyd service?Apparently if a sender requests a read-receipt, and the recipient clicks OK to accept the read-receipt, this could be problematic as this can drive up the messageCount resulting in exceeding the sending limit. Looking at the accounting_tracking table during the read-receipt transaction, the address logged is "Sender:<>". e.g. accounting_tracking ("AccountingID", "TrackKey", "PeriodKey", "LastUpdate", "MessageCount", "MessageCumulativeSize") VALUES (1, 'Sender:<>', '2016-06-22', 1466632683, 140, 3518), (2, 'Sender:<>', '2016/25', 1466761564, 670, 27584), (3, 'Sender:<>', '2016-06', 1466761564, 670, 27584); Is there anyway to prevent tracking of read-receipt messages in cbpolicyd? If there is a rule that can be created that does not drive up the messageCount from read-receipt messages, that would be helpful. Best Regards, -- Rick King _______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users_lists.policyd.org
i have the same problem.. the "temporary solution" is to make a job that delete the value in the db.. 'DELETE FROM accounting_trackinG WHERE TrackKey LIKE "Sender:<>"' -- Dr. Andrea Cavaletti System & Technology Department e-mail: [email protected] ph. +39 02 26995374 - mob. +39 348 2905648 - fax +39 02 2135520 CINECA - Consorzio Interuniversitario skype andrea.cavaletti _______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users_lists.policyd.org
