Handling Email Fallback Scenarios

Overview

When email correspondence fails to deliver, QFD implements a fallback workflow to ensure messages reach their intended recipients. In the event a retry cannot be completed, QFD will either route to a user with or send the communication via paper mail. This guide outlines various failure scenarios and how to handle them.

Initial Email Failure Scenarios

Connection Failures

When QFD cannot connect to the mail exchange:

1. A failure task is created in PendingEmailRetry where QFD will attempt one retry after one hour

2. If the retry fails, the Letter Failed to Send assignment is generated
   
   

Delivery Failures (Bouncebacks)

Rate Limited Failures

1. Creates failure task in PendingEmailRetry where QFD will attempt one retry after one hour

2. If the retry fails, the Email Exchange Failure assignment is generated

Transient Failures

Includes failures such as: 4.4.7 - Delivery Time Expired and 5.4.5 - Network congestion

1. A failure task is created in PendingEmailRetry where QFD will attempt one retry after one hour

2. If the retry fails, the Letter Failed to Send assignment is generated

Permanent Failures

Includes failures such as: 5.3.4 - Message too big for system and 5.1.1 - Bad destination mailbox address

1. No retry is attempted

Undefined Failures

For any failure type not specifically defined:

1. No retry attempted

2. Communication channel updated to Mail

3. Failed email resent via physical mail

4. All future correspondence defaulted to physical mail until manually updated