How does Email Engine failover for incoming email with MBOX on Linux keep from processing emails already processed by the primary server

Version 2

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    Remedy AR System Server


    Remedy AR System Server


    AR System Email Engine 7.x and above



    We have 2 Linux servers where incoming email is sent to for high availability. While the primary incoming email server is running, it processes the email from its MBOX file then deletes each message. Should a failover event occur and the system start using the secondary incoming email server, how does it handle the email messages in that file that were purged from the primary? There will potentially be messages in that new file for previous days/weeks/months that were already processed by the primary server.



    The processing of duplicate emails in a failover is the same for any protocol, not just MBOX.  

    The EE checks for duplicates based on the Message-ID. Message-ID is a unique identifier for a digital message, most commonly a globally unique identifier used in email and Usenet newsgroups. Message-IDs are required to have a specific format which is a subset of an email address and to be globally unique. The AR System Email Engine checks the Message-ID for an incoming email to make sure that Message-ID doesn't already exist in the AR System Email Messages form. This way it will not process a duplicate message or as in the above scenario, one that was already processed by the primary before the failover.  


    Article Number:


    Article Type:

    Product/Service Description

      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles