|
|
|
|
|
|
|
|
Applies To: Models 1000, 2000, 3000
The deferred queue may accumulate email for several reasons, two common ones being:
Valid outbound email can't reach the target mail server(s). One would not expect this to cause an excessively large deferred queue in general, unless an email blast was perhaps targeting the same email server target.
Outbound "non-delivery notifications" produced by the "Reject on Unknown Recipient" feature (see below) are accumulating since there is no valid email server for the non-delivery notifications to be sent to. In other words, it is the side-effect of a spam attack where a valid "return address" does not exist. These "un-deliverables" will leave the queue in no more than 5 days. You may also go to Status/Reporting > Mail Queue and selectively remove deferred items if you wish.
Reject on Unknown Recipient — Rejects mail if the specified recipient does not exist. The system will perform an LDAP lookup on the recipient's address to ensure they exist before delivering the message.
The timing of ePrism resend attempts occur as follows:
ePrism will attempt to deliver a deferred message in 1000 seconds (16+ minutes).
If the above attempt fails, the interval doubles to 2000 seconds before the next attempt.
If the above attempt fails, the interval doubles to 4000 seconds before the next attempt, and is the maximum retry interval for a deferred message.
