Hi Paul i would love a additional column in the message table containing the sha1 sum of the message before it get splitted in mime-parts or maybe better a own table with message-id and checksum and ignore that functionality if this table don't exist
that would offer a option for dbmail-util check reconstruction of current stored messages and by ignore old ones not having that value no compatibility break maybe that verification could go in a small new binary outside dbmail-util with a few options like limit the number of verified messages and specify a date range and produce a csv like output with userid, mailboxid, date and subject and last but not least integrity check of a specific message id that would greatly improve debugging / verification and in case of a complete raw message by a client that could also optionally calculated / verified and mismatch logged in the maillog to get some valuable Information in case of unpredictable bugs like the current reconstruction under load surely it needs resources on the server, hence the idea of a separate table to enable that behaviour but at the end of the day it gives us the opportunity to have an insight in overall integrity and early detection of regressions, their impact, easy confirmation of bugfixes by knowing the hash of the original message, and messages known to be broken before the proposed fix -- Reindl Harald (mobile) the lounge interactive design GmbH A-1060 Vienna, Hofmühlgasse 17 CTO / CISO / Software-Development +43 (676) 40 221 40 http://www.thelounge.net _______________________________________________ DBmail mailing list DBmail@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
