Contrary to modern APIs, email delivery is not a real-time protocol and delays can (and will) sometimes happen. We picked the most reliable and respected inbound delivery partner we could find (hello Postmark), but even with them, there could be delays.

If your business depends on real-time delivery and processing of emails, you should know about those possible delays and have a backup plan ready for when they occur.

Parseur is the only email parser on the market that offers a free and optional redundant email processing pipeline. Here is how it works.

How can I setup the dual email inbound system?

To use a redundant delivery pipeline, you will send your emails to two inbound delivery processor companies at once. Parseur will take the email it receives first and discard the other one (i.e. Parseur will reduplicate the requests so that you don't get twice your emails).

All you have to do is to send your emails to two addresses in a single email: and


That's all!

Limitations and disclaimer

Our deduplication system works based on email MessageIDs. Consequently, it will only work if both email addresses are present in the same email.

The following setups will work:

  • Set both email addresses in the TO field of the emails

  • Set one email address in the TO field and the second one in the CC or BCC fields

The following setup WILL NOT work (you will receive emails twice, using twice the credits and triggering twice your webhooks):

  • Send one email to and another to even if it has the same subject and content

Alternative solutions to manage email delivery issues

There are other solutions that you can implement that can reduce the impact of delivery delays:

  1. Use our API to send us documents directly without relying on email delivery

  2. Have a backup plan ready in your organization to deal with the situation in a degraded way for when email delays occur (e.g. have access to the source mailboxes, or CC request to a mailbox you control).

How can I monitor email delivery delays?

You can also check for incidents on our partners' status pages:

Did this answer your question?