1

Topic: 3rd party email archiving required

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.6.2
- Deployed with iRedMail Easy or the downloadable installer? downloadable
- Linux/BSD distribution name and version: Rocky Linux 8
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL/Mariadb
- Web server (Apache or Nginx):nginx
- Manage mail accounts with iRedAdmin-Pro? No
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

I have an account, a single email address, that is required by law to have all ingoing and outgoing emails archived to an outside/3rd party email archiver.

It looks like I can do this through Postfix's inherent sender_bcc_maps and recipient_bcc_maps and postmap but if this "should" be done through iRedmails sql framework, I'd rather do it there.

Any feedback on this is greatly appreciated.

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: 3rd party email archiving required

In the support documents, the words tripping me up are:

"Important notes:

    the destination email address used to store emails must exist. In this tutorial, they're outbound@example.com and inboud@example.com."

And I am wondering if that means "emails must exist" ON THIS SERVER.

I'm going to test case to see if that is true or false.





montanelli wrote:

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.6.2
- Deployed with iRedMail Easy or the downloadable installer? downloadable
- Linux/BSD distribution name and version: Rocky Linux 8
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL/Mariadb
- Web server (Apache or Nginx):nginx
- Manage mail accounts with iRedAdmin-Pro? No
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

I have an account, a single email address, that is required by law to have all ingoing and outgoing emails archived to an outside/3rd party email archiver.

It looks like I can do this through Postfix's inherent sender_bcc_maps and recipient_bcc_maps and postmap but if this "should" be done through iRedmails sql framework, I'd rather do it there.

Any feedback on this is greatly appreciated.

3

Re: 3rd party email archiving required

For those of you interested, the directions provided on:
https://docs.iredmail.org/monitor.incom … h.bcc.html
appear be compliant with SEC requirements (e.g. licensed financial services agents) and provide "silent" server side BCC on outgoing and incoming emails for either domain based or single user accounts. It is completely SQL based, postmap not needed.

4

Re: 3rd party email archiving required

If you need to view or search archived emails later, BCC might be not enough. Take a look at our  lightweight, on-premises Spider Email Archiver: https://spiderd.io/

Free for 10 mailboxes.

5

Re: 3rd party email archiving required

Thank you. But these are leaving our server to a government approved archive server.

However I noticed your archiver and maybe I'll give it a spin to see what it does. Right now I have to build out a new iRedmail on on Rocky Linux 9 and move the exisiting accounts on Rocky Linux 8 to it once I've polished it out to work with SELinux enabled.