Inbound mail is queued while your own mail server is offline and delivered when it is back. This is not an archive or a full backup. It does not remove the risk of loss. Queue time and capacity are written in the contract.
End to Lost Emails!
With the ETRN service, all your incoming emails are redirected to our ETRN servers in the event of any interruption on your server or internet line. From the moment the problem is resolved, your mails, which wait safely on our servers during this period, are sent to you again.
As a working principle, it operates as a backup or "recovery" system.
In normal operation, emails reach the main email server on the user's side directly, without ever passing through OwnHost. When a problem occurs on the user's email server or internet line for any reason (server crash, power outage, etc.), the mails sent to you do not bounce back (they do not return an error). Instead, the emails begin to accumulate on the OwnHost ETRN server.
When the customer’s mail server is back, queued messages are offered to it. Delivery is limited by queue time and capacity. This does not remove the risk of loss.
The ETRN service kicks in when your main mail server goes down or your internet connection is lost. Instead of incoming mails bouncing back to your customers or senders with a 'delivery failed' error, they are safely queued on OwnHost servers. When your server comes back online, all queued mails are automatically delivered to your server.
During downtime or hardware interruption on your server, your incoming emails are, as standard, queued on our ETRN servers up to 7 days are stored safely. If your server does not come online within 7 days, a delivery-failed notice reaches the sender.
No. It does not remove the risk of loss. Queued messages are offered when the server is back. When the time or capacity limit is reached, the sender may get a delivery-failure notice. ETRN is not an archive or a full backup.
No, you do not need to make any physical changes to your own server configuration or hardware. It is sufficient to simply add the OwnHost ETRN servers as secondary (low priority, such as MX 20, MX 30) to the MX records in your domain's DNS panel.
No quota or limit is applied for standard usage and daily mail traffic. Your company's critical communication traffic can be stored on OwnHost servers without hitting capacity limits.
For all our packages User Agreement ve General Terms of Use, in addition, the usage terms listed below apply.
