Aaron Stone wrote: > On Mon, Jun 18, 2007, Paul J Stevens <[EMAIL PROTECTED]> said: > >> Aleksander Kamenik wrote: >>> Michael Monnerie wrote: > >>> It would be cool to find out which messages this affects. In the level 3 >>> trace maybe "message with ID blah is a duplicate"? >> That message is currently at TRACE_DEBUG, but I'll make sure it's issued >> at TRACE_INFO > > Perhaps TRACE_MESSAGE would be better? I'm on the fence about this one, > but leaning towards it being fairly important in case there is an improper > repetition of message-id and the mail admin wants to know why something > appears to have been delivered (looking at TRACE_MESSAGE indications) but > did not actually show up in the database (therefore suppression should be > also indicated at TRACE_MESSAGE).
Done. suppress_duplicate added to config, defaults to 'no', checks for resent-message-id or message-id in mailbox using a 3day timewindow, and skips final copying into mailbox if a match is found. I've pushed this new feature onto dbmail_2_2_branch. -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
