Because what to you is 'just working' is to a bunch of other people 'hiding
an import error'.
If you have CFMX 6.1 mail spooling problems, I would look to your mail
server. I would also report a problem through technical support and maybe
we can fix it for you.
By the way, there is very little functional difference between cfmail
qeuery= and cfloop/cfmail. If you believe your DB has bad Email addresses
in it, use the loop and validate the addresses. If you have verified your
data's integrity on entry, use the query= syntax.
I do have an enhancement on my plate to batch bad addresses when running
cfmail over a query. We know this is a problem many users encounter. We
just have to figure out how the interface would work. Suggestions?
--
Tom Jordahl
Macromedia Server Development
-----Original Message-----
From: Tyler Clendenin [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 21, 2004 12:11 PM
To: CF-Talk
Subject: RE: CFMX 'bug'? Easy to crash CFMAIL.
Well overall better then crashing is spending more money on something like
cfx_activmail that just works. That is my major gripe, why can't these
things just work. Even still with this new version of CFMX I have a problem
after i get more then 2000 e-mails in my spool. If anyone wants the link
ActivMail is at http://www.cfdev.com . It just works.
Tyler Clendenin
GSL Solutions
_____
From: Deanna Schneider [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 21, 2004 11:59 AM
To: CF-Talk
Subject: Re: CFMX 'bug'? Easy to crash CFMAIL.
I've handled this by looping over my query, doing the validation, and
re-building the query for the cfmail tag, minus the bad records. Total
hassle, but better than crashing.
-d
----- Original Message -----
From: "Dave Watts" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Wednesday, January 21, 2004 9:44 AM
Subject: RE: CFMX 'bug'? Easy to crash CFMAIL.
> > Re #1: Doesn't putting a try/catch around the cfmail do the
> > trick? That way you don't have to validate the email yourself...
> > just let cfmail fail if it wants to.
> >
> > If you put the try/catch around the entire cfloop (or cfoutput)
> > of a query then Yes, it will abort the whole job. But if you put
> > the cftry/cfcatch around only the cfmail then you can do whatever
> > error recovery you want. One easy way is to set
> > variables.DidEmailWork = true above the cftry/cfmail and set
> > variables.DidEmailWork = false in the cfcatch. Then do any good/no
> > good handling outside of the cfttry using that variable to decide
> > what happened.
>
> Unfortunately, this approach isn't as clear when you're using a query with
> your CFMAIL tag itself; when you do that, it automatically loops over your
> recordset, and if any record within that recordset has an invalid address,
> the whole thing will fail at that point.
>
> Dave Watts, CTO, Fig Leaf Software
> http://www.figleaf.com/
> voice: (202) 797-5496
> fax: (202) 797-5444
>
>
_____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
