Re: [iMS] Retry Bounces question

[David D Droddy]

Howie,   Here's our thinking on the deliverability reporting:   If we report that a message failed for transient reasons, the sender may attempt send to the recipient again in the future. If we report that a message failed for more fatal reasons, the sender may consider contacting the recipient to correct the email address or we may try to find out if a spam filter or firewall is blocking the message in which case we will attempt to assist the sender in resolving the issue.   So, I guess the real difference here is the perspective when reporting the failure "type." We report the failure from the perspective of the receiving server. iMS reports the failure based on whether it will ever attempt to send the message again.   Is there some way to tap into the way iMS analizes SMTP receiving server responses? We do intend to eventually build our own code for more specific analysis of failure reasons, but right now we're trying to figure out a more timely way to plug iMS into our current system.   Thanks and kind regards,   David Droddy Application Developer Real Magnet 202-244-2337 ----- Original Message ----- From: Howie Hamlin To: inFusion Support List Sent: Monday, June 14, 2004 11:49 AM Subject: Re: [iMS] Retry Bounces question   ----- Original Message ----- From: David D Droddy To: inFusion Support List Sent: Monday, June 14, 2004 11:37 AM Subject: Re: [iMS] Retry Bounces question Howie,   Thanks.   The ReportPostStatus.cfm template will be run when one of the following three things happens:       A message send attempt resulted in Temporary Failure     A message send attempt resulted in Permanent Failure     A message send attempt resulted in Success   Is this correct?   Yes.    Is there anything else that will prompt ReportPostStatus.cfm to run?   No.   Lastly, as you say, once MaxAttempts is reached, a recipient who was in tempfailedlist for all attempts will now be in permfailedlist? So, at that point we don't know if the final attempt/failure was for a "transient" reason like "mailbox full?"   It's likely that the last attempt was a transient failure since those before it were transient.  The server also gives you the response from the other server so you can see exactly what the status was.   I ask this because we provide general statistics on deliverability to our senders (% Hard (permanent) failures and % Soft (temporary/transient) failures). But as you have described it, eventually all failures will show up as non-transient. Is there some other way I should deal with this?   Well, if the mail cannot be delivered because there are transient errors over and over then I would consider that to be a permanent delivery failure.  You can use the aforementioned information to provide details if that helps.   Regards., Howie   Thanks,   This list server is Powered by iMS "The Swiss Army Knife of Mail Servers" This list is provided as a free service. Although we will try to address issues in a timely manner, support via this list is not guaranteed. If you require expedited support then a support contract is required. Support may be purchased from http://www.coolfusion.com/commerce. Details regarding support options may be reviewed at: http://www.coolfusion.com/SupportOptions.cfm. To leave this list please complete the form at http://www.coolfusion.com/Support/ Need an iMS Developer license? Sign up for a free license here: http://www.coolfusion.com/Developers/ List archives: http://www.mail-archive.com/infusion-email%40eoscape.com/ Note: You are subscribed as [EMAIL PROTECTED]