Re: [Assp-user] Mailhop Backup MX?

[Charles M. <CM...@Me...>]

On 10/6/2008 11:07 AM, Micheal Espinola Jr wrote:
> Jeroen van Aart wrote:
>> The server doesn't HAVE to retry for any set amount of time, it's just 
>> that it is generally understood 5 days is acceptable. Be that as it may, 
>>   absolutely nothing prevents your users from resending it anyways. It's 
>> not like a delivery failure disallows them the privilege of using email.
> 
> Generally understood by whom?  I am aware of no data to support this. 5
> days may be a software default, but that does not imply being acceptable
> in my mind.

RFC 2821 - http://www.faqs.org/rfcs/rfc2821.html

4.5.4.1 Sending Strategy

   The general model for an SMTP client is one or more processes that
   periodically attempt to transmit outgoing mail.  In a typical system,
   the program that composes a message has some method for requesting
   immediate attention for a new piece of outgoing mail, while mail that
   cannot be transmitted immediately MUST be queued and periodically
   retried by the sender.  A mail queue entry will include not only the
   message itself but also the envelope information.

   The sender MUST delay retrying a particular destination after one
   attempt has failed.  In general, the retry interval SHOULD be at
   least 30 minutes; however, more sophisticated and variable strategies
   will be beneficial when the SMTP client can determine the reason for
   non-delivery.

   Retries continue until the message is transmitted or the sender gives
   up; the give-up time generally needs to be at least 4-5 days.  The
   parameters to the retry algorithm MUST be configurable.


-- 

Best regards,

Charles