1
0
mirror of https://github.com/imapsync/imapsync.git synced 2024-11-16 15:52:47 +01:00
imapsync/FAQ.d/FAQ.Principles.txt

49 lines
1.4 KiB
Plaintext
Raw Permalink Normal View History

2020-04-11 01:15:57 +02:00
2021-05-01 17:46:04 +02:00
$Id: FAQ.Principles.txt,v 1.10 2021/04/18 13:00:00 gilles Exp gilles $
2020-04-11 01:15:57 +02:00
This documentation is also available online at
https://imapsync.lamiral.info/FAQ.d/
https://imapsync.lamiral.info/FAQ.d/FAQ.Principles.txt
=======================================================================
Imapsync principles and design ideas
=======================================================================
Questions answered in this FAQ are:
2021-05-01 17:46:04 +02:00
Q. Give me some design ideas of imapsync
2020-04-11 01:15:57 +02:00
Now the questions again with their answers.
=======================================================================
2021-05-01 17:46:04 +02:00
Q. Give me some design ideas of imapsync
R.
* No configuration file
* Stateless
* Rsync in mind
* Reliable
* Robuste
* The user is not an expert, help him with:
* Good behavior by default.
* No harm by default.
* Prefer fixing an issue in the code than documenting the issue
* Inline help suggestions
Consequences of those design ideas:
* Stateless:
* A sync can be done by another tool before or after imapsync, it is
safe as long as the other tools don't modify the messages' headers
"Message-Id:" and "Received:", or at least "Message-Id:".
* Ready to run in a container.
2020-04-11 01:15:57 +02:00
=======================================================================
=======================================================================