----- Original Message -----
From: Max Paperno <[EMAIL PROTECTED]>
To: inFusion Support List <[EMAIL PROTECTED]>
Sent: Monday, June 26, 2000 6:24 PM
Subject: Re: [iMS] 2 minor heads-up
>
> >
> >> 1. I had some code in rcpt.cfm that looked like so:
> >>
> >> result=relay
> >> mx="<CFOUTPUT>#CheckDomain.RelayToMX#</CFOUTPUT>"
> >>
> <snip>
>
> >That's something that can happen in a flexible system like iMS. You can
do
> >things that aren't exactly right (like the bad MX) but iMS will accept it
> >and try to deliver the message.
>
> Yea, I just thought it strange that data.cfm didn't just crash even though
CF threw an error...
>
> Actually, now that i think about it, what happened must have been that iMS
had already seen the "result=relay" response in the result stream, because
it came before the mx= response which threw the error. So! the lesson is
that you might not ever actually see a CF error that is thrown after your
"result=" response in a template because iMS will just see the result= and
ignore the rest.
>
Yes, that's what happened. You could always put the result=accept after
everything else to make sure...
> Questions... Should this behavior be changed? Or should the rule be that
outputting "result=" is the absolutely last thing your processing template
does? And, does the order of the response matter? For example, is it OK to
send mx= before the result=relay?
>
There will be yet another iMS beta today or tomorrow with all the recent
modifications and one new feature :-)
Regards,
Howie
> Thanks,
> -Max
>
========================================================================
This list server is Powered by iMS
'The Swiss Army Knife of Mail Servers'
--------------------------------------
To leave this list please complete the form at
http://www.CoolFusion.com/iMS.htm
List archives: http://www.mail-archive.com/infusion-email%40eoscape.com/
========================================================================
