[PR #633] [MERGED] Add Open Archiver to Backups #615

New Issue

GiteaMirror · 2025-11-06T17:04:42-06:00

GiteaMirror commented

2025-11-06 17:04:42 -06:00

📋 Pull Request Information

Original PR: https://github.com/awesome-foss/awesome-sysadmin/pull/633
Author: @wayneshn
Created: 7/28/2025
Status: ✅ Merged
Merged: 10/16/2025
Merged by: @Technetium1

Base: master ← Head: add-open-archiver

📝 Commits (5)

e63fc5f Add Open Archiver to Backups
dd8c036 Remove source code link
75610be Add website and source code link
a2c8ad0 Apply suggestion from @nodiscc
a9b36b2 Merge branch 'master' into add-open-archiver

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 README.md (+1 -0)

📄 Description

Thank you for taking the time to work on a PR for Awesome-Sysadmin!

To ensure your PR is dealt with swiftly please check the following:

Your additions are Free software
Software you are submitting is not your own, unless you have a healthy ecosystem with a few contributors (which aren't your sock puppet accounts).
Submit one item per pull request. This eases reviewing and speeds up inclusion.
Format your submission as follows, where Demo and Clients are optional.
Do not add a duplicate Source code link if it is the same as the main link.
Keep the short description under 80 characters and use sentence case
for it, even if the project's webpage or readme uses another capitalisation.
Demo links should only be used for interactive demos, i.e. not video demonstrations.
- [Name](http://homepage/) - Short description, under 250 characters, sentence case. ([Demo](http://url.to/demo), [Source Code](http://url.of/source/code), [Clients](https://url.to/list/of/related/clients-or-apps)) `License` `Language`
Additions are inserted preserving alphabetical order.
Additions are not already listed at awesome-selfhosted
The Language tag is the main server-side requirement for the software. Don't include frameworks or specific dialects.
You have searched the repository for any relevant issues or PRs, including closed ones.
Any category you are creating has the minimum requirement of 3 items.
Any software project you are adding to the list is actively maintained.
The pull request title is informative, unlike "Update README.md".
Suggested titles: "Add aaa to bbb" for adding software aaa to section bbb,
"Remove aaa from bbb" for removing, "Fix license for aaa", etc.

Please take some time to answer the following questions as best you can:

Why is it awesome?

Open Archiver is awesome because it provides a comprehensive, self-hosted solution for email archiving that gives sysadmins full control over their organizations' data. It supports major email platforms, such as Google Workspace and Microsoft 365, and is built with a modern tech stack. Its focus on data sovereignty, security (encryption at rest), and efficient storage makes it a valuable tool for organizations needing to maintain a long-term, searchable record of their email communications without vendor lock-in.

Have you used it? For how long?

As the primary developer and maintainer of Open Archiver, I have been using it continuously since its inception. It is the core project I work on. My company, an Estonia-based tech company, also uses it to back up our email inboxes for compliance purposes.

Is this in a personal or professional setup?

Open Archiver is designed for both personal and professional setups. It can be used by individuals who want to keep a personal archive of their emails (Gmail, Outlook etc), as well as by businesses that want to back up their organizations' emails (Google Workspace, MS 365 etc). We use it for development and testing in a professional context.

How many devices/users/services/... do you manage with it?

In our development and testing environments, we manage multiple ingestion sources from Google Workspace, Microsoft 365, and various IMAP accounts, archiving thousands of emails for testing purposes. Our company uses it in production to archive all of our email inboxes with more than 100,000 emails with continuous syncing.

Biggest pros/cons compared to other solutions?

Pros: The biggest advantage of Open Archiver is that it is a fully open-source and self-hosted solution, which guarantees data sovereignty and avoids vendor lock-in. It offers universal email ingestion, powerful full-text search across emails and attachments, and flexible storage options (local or S3-compatible). Its modern tech stack makes it maintainable and scalable.

Cons: Some advanced compliance features, such as legal holds, are still under development.

Any other comments about your use case, things you've found excellent, limitations you've encountered... ?

As the maintainer, I want to highlight that the search capability, powered by Meilisearch, is exceptionally fast and efficient, even with large volumes of emails and attachments. The pluggable storage architecture has also been a key design choice, allowing users to choose the most cost-effective storage solution for their needs.

Limitations: Currently, we don't support enterprise-specific features like SSO and role-based access, which will be added in our next update. But currentl,y the email archiving solution is solid and works in production environments.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/awesome-foss/awesome-sysadmin/pull/633 **Author:** [@wayneshn](https://github.com/wayneshn) **Created:** 7/28/2025 **Status:** ✅ Merged **Merged:** 10/16/2025 **Merged by:** [@Technetium1](https://github.com/Technetium1) **Base:** `master` ← **Head:** `add-open-archiver` --- ### 📝 Commits (5) - [`e63fc5f`](https://github.com/awesome-foss/awesome-sysadmin/commit/e63fc5f3841a7757db5de6953a90d1a3d8f49e16) Add Open Archiver to Backups - [`dd8c036`](https://github.com/awesome-foss/awesome-sysadmin/commit/dd8c036b467e6d23a9ffdbacb392916b3ff2d300) Remove source code link - [`75610be`](https://github.com/awesome-foss/awesome-sysadmin/commit/75610be85d09e269cad2555e7a26f8642ddcecc7) Add website and source code link - [`a2c8ad0`](https://github.com/awesome-foss/awesome-sysadmin/commit/a2c8ad0917dd19e16ddf022593c4bab30450f2d9) Apply suggestion from @nodiscc - [`a9b36b2`](https://github.com/awesome-foss/awesome-sysadmin/commit/a9b36b2ec235c37a10afae0a5b46c9b017920298) Merge branch 'master' into add-open-archiver ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+1 -0) </details> ### 📄 Description  Thank you for taking the time to work on a PR for Awesome-Sysadmin! To ensure your PR is dealt with swiftly please check the following: - [x] Your additions are [Free software](https://en.wikipedia.org/wiki/Free_software) - [x] Software you are submitting is not your own, unless you have a healthy ecosystem with a few contributors (which aren't your sock puppet accounts). - [x] Submit one item per pull request. This eases reviewing and speeds up inclusion. - [x] Format your submission as follows, where `Demo` and `Clients` are optional. Do not add a duplicate `Source code` link if it is the same as the main link. Keep the short description under 80 characters and use [sentence case](https://en.wikipedia.org/wiki/Letter_case#Sentence_case) for it, even if the project's webpage or readme uses another capitalisation. `Demo` links should only be used for interactive demos, i.e. not video demonstrations. ``- [Name](http://homepage/) - Short description, under 250 characters, sentence case. ([Demo](http://url.to/demo), [Source Code](http://url.of/source/code), [Clients](https://url.to/list/of/related/clients-or-apps)) `License` `Language` `` - [x] Additions are inserted preserving alphabetical order. - [x] Additions are not already listed at [awesome-selfhosted](https://awesome-selfhosted.net) - [x] The `Language` tag is the main **server-side** requirement for the software. Don't include frameworks or specific dialects. - [x] You have searched the repository for any relevant [issues](https://github.com/awesome-foss/awesome-sysadmin/issues) or [PRs](https://github.com/awesome-foss/awesome-sysadmin/pulls), including closed ones. - [x] Any category you are creating has the minimum requirement of 3 items. - [x] Any software project you are adding to the list is actively maintained. - [x] The pull request title is informative, unlike "Update README.md". Suggested titles: "Add aaa to bbb" for adding software aaa to section bbb, "Remove aaa from bbb" for removing, "Fix license for aaa", etc. -------------- Please take some time to answer the following questions as best you can:  - **Why is it awesome?** Open Archiver is awesome because it provides a comprehensive, self-hosted solution for email archiving that gives sysadmins full control over their organizations' data. It supports major email platforms, such as Google Workspace and Microsoft 365, and is built with a modern tech stack. Its focus on data sovereignty, security (encryption at rest), and efficient storage makes it a valuable tool for organizations needing to maintain a long-term, searchable record of their email communications without vendor lock-in. - **Have you used it? For how long?** As the primary developer and maintainer of Open Archiver, I have been using it continuously since its inception. It is the core project I work on. My company, an Estonia-based tech company, also uses it to back up our email inboxes for compliance purposes. - **Is this in a personal or professional setup?** Open Archiver is designed for both personal and professional setups. It can be used by individuals who want to keep a personal archive of their emails (Gmail, Outlook etc), as well as by businesses that want to back up their organizations' emails (Google Workspace, MS 365 etc). We use it for development and testing in a professional context. - **How many devices/users/services/... do you manage with it?** In our development and testing environments, we manage multiple ingestion sources from Google Workspace, Microsoft 365, and various IMAP accounts, archiving thousands of emails for testing purposes. Our company uses it in production to archive all of our email inboxes with more than 100,000 emails with continuous syncing. - **Biggest pros/cons compared to other solutions?** **Pros**: The biggest advantage of Open Archiver is that it is a fully open-source and self-hosted solution, which guarantees data sovereignty and avoids vendor lock-in. It offers universal email ingestion, powerful full-text search across emails and attachments, and flexible storage options (local or S3-compatible). Its modern tech stack makes it maintainable and scalable. **Cons**: Some advanced compliance features, such as legal holds, are still under development. - **Any other comments about your use case, things you've found excellent, limitations you've encountered... ?** - As the maintainer, I want to highlight that the search capability, powered by Meilisearch, is exceptionally fast and efficient, even with large volumes of emails and attachments. The pluggable storage architecture has also been a key design choice, allowing users to choose the most cost-effective storage solution for their needs. Limitations: Currently, we don't support enterprise-specific features like SSO and role-based access, which will be added in our next update. But currentl,y the email archiving solution is solid and works in production environments. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2025-11-06 17:04:42 -06:00

GiteaMirror closed this issue

2025-11-06 17:04:42 -06:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/awesome-sysadmin#615