Michael Monnerie wrote:
Sounds good, but a config option could be of value for some
environments, i.e. some people must receive even duplicate messages
(for automated e-mails).
What automated messages with different content do NOT differ by message-id?
Also, if you do get the same message (with the same message id) in case
of automated mail, wouldn't this be the perfect case to skip the duplicate?
Anyway, I would say it's more of a user setting than system setting. And
in dbmail's case a sieve thing and I don't think there's something like
that implemented in sieve.
Also, is checking the message-id header secure enough? Maybe the cyrus
community has seen some problems with this? I'm just naturally paranoid
about ignoring messages based on a header.
It would be cool to find out which messages this affects. In the level 3
trace maybe "message with ID blah is a duplicate"?
Just some thoughts,
--
Aleksander Kamenik
system administrator
+372 6659 649
[EMAIL PROTECTED]
Krediidiinfo AS
http://www.krediidiinfo.ee/
_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
