GitHub user sebbASF opened an issue:
https://github.com/apache/incubator-ponymail/issues/373
Bug: import --dedup does not cater for messages sent to multiple lists
The import-mbox --dedup option checks for an existing email with the same
Message-Id. If one is found, then the message is not imported.
This does not work properly for messages that have been sent to multiple
lists, as they will all have the same Message-Id.
For example:
Message-Id: <[email protected]>
was sent to dev@ commits@ and issues@ ponymail.incubator.apache.org in Jan
2017:
https://lists.apache.org/thread.html/f2eaff06618e9c4b400bf52198285036268fa9461b9db51c3c69c8b9@%3Cdev.ponymail.apache.org%3E
https://lists.apache.org/thread.html/afbdb3ea514df49a21e9eca9795bdbd001c92cffb0fb6aded73c0103@%3Ccommits.ponymail.apache.org%3E
https://lists.apache.org/thread.html/d4e5c40af9a0a07142e6158b00a1a408111b8f2392d80a5f896673b3@%3Cissues.ponymail.apache.org%3E
(It was also sent to private@; not shown here)
If the Jan 2017 mailboxes for those lists are imported into a new database
using the --dedup option, the email will only appear on one of the lists
instead of all of them.
The dedup option needs to take account of the mailing list.
----
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
