No. the issue with CFMAIL is that if you have a syntax error in just about any other place in ColdFusion, it throws an error and you can deal with it. IF you have a syntax error in the content of a CFMAIL message, nothing happens. Since you dont usually get to see your email going anyway, the only way you know there was a problem with your CFMAIL is that after 20 minutes or half an hour you haven't got your test message yet.
IF you have an error in the attributes of the cfmail tag, or if you have a server name missing for example or a setting wrong, incorrect password, or a syntax error in the body of the mail message, the result is the same - nothing. But a valid email can take up to 20 minutes to be sent, go through the mail system and find its way into your MS Outlook, so you dont really know that your mail has failed until a reasonable period has elapsed and you can be sure that had an email been sent you would have received it by now. IN a shared environment you normally have no access to the Undelivr folder so you can't see if your mail failed and is sitting there. There can be any of a dozen reasons why your mail has failed, not all of which are in your code. And there is no way to debug it. You just have to keep trying things until you get it working. And as I have said, some of the reasons why it doesnt work might be related to something completely out of your control. Or it might indeed BE working but just taking its time to get to you. For example it can take 8 hours sometimes for my posts to CFTALK to appear in my gmail box. So every time i post my trial email from a form, do i have to wait 8 hours before I conclude that it's not going to work? Thats why I think ColdFusion ought to offer a better degree of debugging. Not everyone works in a controlled local environment all the time. This week i've had a terrible time trying to figure out why three of my clients would have customer order forms that dont send emails to them as required. Was there a code problem suddenly introduced? Was a system setting different ? was there a problem with the mail server? It took ages. And even then when the emails suddenly started working again - why? was it something i fixed? or was the whole problem something beyond our system that went away? It's all far to hit and miss for my liking. I think the CFMAIL part of coldfusion is the worst part of the whole language/server/application. Cheers Mike Kear Windsor, NSW, Australia Certified Advanced ColdFusion Developer AFP Webworks http://afpwebworks.com ColdFusion, PHP, ASP, ASP.NET hosting from AUD$15/month On 7/29/06, Ryan, Terrence <[EMAIL PROTECTED]> wrote: > Can't this particular issue be resolved if you use the existing "failto" > attribute of CFMAIL? > > As this would route failed mail to a specific email address instead of > the Undelivr folder. > > Granted it's sub optimal, in that you have to look someplace else for > the messages. > > > > Terrence Ryan > Senior Systems Programmer > Wharton Computing and Information Technology > > E-mail: [EMAIL PROTECTED] > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:248124 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4