Answers below...
----- Original Message -----
From: "Michael Dinowitz" <[EMAIL PROTECTED]>
To: "inFusion Support List" <[EMAIL PROTECTED]>
Sent: Friday, August 29, 2003 5:03 PM
Subject: Re: [iMS] custom rejects
> I'm looking over the docs now to see the actual names of the headers but I'll be
> using something like this:
>
The header would be form.header_date
> <CFSET response="">
> <CFIF Not IsDefined('date_header') or Not Len(date_header)>
> <CFSET response=ListAppend(response, 'No date defined for email.')>
> </CFIF>
> <CFIF Not IsDefined('from_header') or Not Len(from_header)>
> <CFSET response=ListAppend(response, 'No from address defined for email.')>
> </CFIF>
> ...
> <CFIF Len(response)>
> result=abort
> <CFOUTPUT>customresponse="554 #response#"</CFOUTPUT>
> </CFIF>
> This will report all of the bad headers and reject the entire message. Do you
> think it would be better to gather them all or reject after the first bad one?
> I'm thinking of what would be the most legal looking.
>
You can group them together as long as your text does not exceed 512 characters
including the CRLF (effectively giving you a max of 506 characters of text if you
subtract the 3-digit command, space and CRLF).
HTH,
Howie
==^=======================================================
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/Support/
Need an iMS Developer license? Sign up for a free license here:
http://www.coolfusion.com/Developers/
List archives: http://wwwmail-archive.com/infusion-email%40eoscape.com/
Note: You are subscribed as [EMAIL PROTECTED]
==^=======================================================
