1 Topic by baghamojtaba (edited by baghamojtaba 2020-03-25 06:00:23)

  • baghamojtaba
  • Member
  • Offline
  • Registered: 2020-03-23
  • Posts: 1

Topic: Manually transfer emails

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.1
- Deployed with iRedMail Easy or the downloadable installer? downloadable installer
- Linux/BSD distribution name and version: Ubuntu 18.04
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- 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.
====

We have two servers with domains aaa.com and bbb.com
This is how the process works:
1- every user in aaa.com who sends an email, the email server, places a file corresponding to it in a path.
2- Files copied along that path are exported to bbb.com with a device such as a hard drive or flash
3- Bbb.com should read them and place them at user1@bbb.com.

This process should be done so that users on both sides see the normal process of sending emails and what is happening along the way should not change their functioning with the system.
Users can connect to any server from any Email Client email client such as Outlook, SoGo and send and receive emails.

Can anyone help me or give me an idea?
Is this workable or is it better to develop a separate mail server?

----

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

2 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,090

Re: Manually transfer emails

PERSONAL suggestions, in order:

1) Use a mail archiving software.

- There're many commercial archiving products, many of them offer cloud edition too.
- Deploy an open source mail archiving software. for exampler, MailPiler: http://www.mailpiler.org

2) Another solution is: Postfix "always_bcc".

Update Postfix "always_bcc" option (in /etc/postfix/main.cf) on your iRedMail server, it will BCC all inbound and outbound to the specified email address.

It could be an email address hosted on your 2nd server, then write some simple sieve rules to forward or place them into another mailbox on 2nd server. This 2nd server doesn't need to be an iRedMail server, you can run Postfix+Dovecot with any other softwares you like for 2nd server.

3) Replicate mailboxes in real-time.

Setup 2nd server with iRedMail, then setup Dovecot replication to sync mailboxes on both servers in real-time.
FYI: https://wiki.dovecot.org/Replication

Notes:

- this replication requires Dovecot on both servers, and BETTER (but not forced) same Dovecot version.
- you should setup MySQL replication on both servers too, so that Dovecot gets same mail accounts.

I think option #1 is the best and easily, doesn't impact your iRedMail setup and further upgrade.
#2 and #3 are both technically achievable, the concern is workload of further maintenance and upgrade of iRedMail itself.