software:dailydata:archiveimap
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
software:dailydata:archiveimap [2019/09/17 02:48] – rodolico | software:dailydata:archiveimap [2019/09/19 01:53] – rodolico | ||
---|---|---|---|
Line 3: | Line 3: | ||
We run a small mail server for some of our clients, some of whom retain massive amounts of e-mail. A few never sort anything, but leave it all in the Inbox, which can cause programs like Outlook to become unstable. Additionally, | We run a small mail server for some of our clients, some of whom retain massive amounts of e-mail. A few never sort anything, but leave it all in the Inbox, which can cause programs like Outlook to become unstable. Additionally, | ||
- | Many programs allow auto-archiving of older mail. However, in the case of Outlook, this mail is stored in a local message store (.pst file), and while Thunderbird will move the mail around on the server, it is still creating a huge message store which can negatively impact resources on both the client machine and the mail server. | + | Many programs allow auto-archiving of older mail. However, in the case of Outlook, this mail is stored in a local message store (.pst file) which is difficult to back up. And while Thunderbird will move the mail around on the server, it is still creating a huge message store which can negatively impact resources on both the client machine and the mail server. |
The main solution we have found is to separate mail into an //active account// and an //archive account//. We create a separate mail account strictly for archival purposes, and keep the //active account// as small as possible for rapid response to the client and fewer resources used on both client and server. The //archive account// is used for permanent storage of old mail, and can be on older, slower hardware, and not automatically synchronized to the client' | The main solution we have found is to separate mail into an //active account// and an //archive account//. We create a separate mail account strictly for archival purposes, and keep the //active account// as small as possible for rapid response to the client and fewer resources used on both client and server. The //archive account// is used for permanent storage of old mail, and can be on older, slower hardware, and not automatically synchronized to the client' | ||
+ | |||
+ | In addition to traditional IMAP servers, archiveIMAP has been successfully used archiving mail from Microsoft Exchange and gmail. In theory, any mail server which supports an IMAP interface should be able to work. archiveIMAP queries the source and target servers for the delimiter. It is possible that one type of server may allow folders to contain characters not allowed on another, but we have not run into that yet. | ||
===== Client Perspective ===== | ===== Client Perspective ===== | ||
Line 45: | Line 47: | ||
This is released under Gnu 3. I thought about BSD or something else, but for now, it is Gnu gpl v3. | This is released under Gnu 3. I thought about BSD or something else, but for now, it is Gnu gpl v3. | ||
- | Uses the following | + | Uses the following |
<code perl> | <code perl> | ||
use Net:: | use Net:: |
software/dailydata/archiveimap.txt · Last modified: 2019/09/19 02:04 by rodolico