This is an automated email from the ASF dual-hosted git repository.
humbedooh pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-ponymail-foal.git
The following commit(s) were added to refs/heads/master by this push:
new 07e9509 Reword some limitations
07e9509 is described below
commit 07e9509a0db042c9f5b7903319c3fa71621205e5
Author: Daniel Gruno <humbed...@apache.org>
AuthorDate: Fri Mar 18 13:45:25 2022 +0100
Reword some limitations
---
README.md | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/README.md b/README.md
index cfd140f..4ccfc52 100644
--- a/README.md
+++ b/README.md
@@ -47,14 +47,15 @@ Migration of the old database is required, and most of the
older ID generators h
been dropped in favor of collision-secure generators._
### Known Limitations:
-* If an email is re-imported or archived, entries are currently replaced.
- This can result in loss of attributes such as alternate Permalinks and
deleted status.
* emails are filed according to the Date: header, rather than arrival time.
This can cause emails to appear in the wrong month or year, or even be
future-dated.
* Whilst the underlying database can handle any number of emails in a month,
the UI and much of the API does not scale well beyond around 10,000 emails
per month per list.
+* Re-archiving/importing an email that was previously hidden will unhide it in
the archive.
#### Known limitations when migrating from older Pony Mail instances:
+* If an email is re-imported or re-archived after a migration, the database
entry is currently fully replaced.
+ This can result in loss of attributes such as alternate Permalinks.
* The migration tool can drop Permalinks if two existing entries point to a
sufficiently similar email
* The migration tool does not fix up badly-parsed message-ids etc
* There is no longer a 1-to-1 relationship between mbox and source entries.
