Re: [iMS] Retry Bounces question

[David D Droddy]

I don't mean to imply that there is some huge compliance isssue here. But it does seem odd that if a receiving server reports something "temporary" that iMS would report otherwise.   When a message fails for ANY reason on an attempt less than max attempts, iMS reports this as accurately as possible (. . .I'm assuming based on the receiving server's response). However, once MaxAttempts has been reached, iMS changes this logic--instead of giving a failure "type", transient or fatal, it reports "fatal. . .because I'm giving up. . .not because the server I tried to send to advised that further attempts would be futile, but because I'm not going to try again."   What I'm wondering is why iMS changes it's reporting logic at MaxAttempts. Why is this necessary? So far, the answer is that it's a logical conclusion, or maybe the debate is one of semantics. I think the latter is true, in which case, perhaps iMS should not make it's own conclusion but rather leave that up to me. In my case, I don't need iMS to tell me that it won't be trying again, but rather what type of failure this is so I can give my paying users an accurate depiction of what happened.   Keith Ivey states "Even if an error is "temporary", the server isn't supposed to keep trying to deliver it forever, so it seems that iMS is following the spec." Does iMS need to report a permanent failure in order to quit trying?     I hope I'm not being terribly annoying. I appreciate you humoring me and giving good debate.   --David  ----- Original Message ----- From: Howie Hamlin To: inFusion Support List Sent: Monday, June 14, 2004 1:19 PM Subject: Re: [iMS] Retry Bounces question In what way?  iMS is providing you with a list of transient failures and then it's designating the failure as premanent if the mail cannot be delivered.  This doesn't really have much to do with the RFC and, as I mentioned, you can decipher the status code from the iMS vars.  If an email cannot be delivered for whatever reason then iMS considers that to be a permanent delivery failure for that particular email.  I mean - there's nothing to stop a remote server from permanently responding with a transient error....so, iMS is just telling you that it cannot deliver a particular mail and is giving up which means that the error for that mail is permanent.   Regards,   Howie ----- Original Message ----- From: David D Droddy To: inFusion Support List Sent: Monday, June 14, 2004 1:13 PM Subject: Re: [iMS] Retry Bounces question   So, I guess we CAN make our own conclusions from the detailed reason data, but it does seem to me that the interpretation of the code by iMS sort of steps away from the RFC 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]