Ah. I didn't even think of that. Thanks.
Please forgive the evil thoughts, but I'm sure someone here has realized
that this is a very powerful and dangerous tool for those who spam. You
could send out email with really controlled headers and have a really hard
time tracking them down.


> I don't know what causes the word wrap issue, but as for the header_CC, it
> would properly display CC data (at least it does in outlook) however it
> won't send an e-mail. For the mail to be CC'd, you would need to include
the
> CC address in the SMTPTO field.
>
>
>
>
> -----Original Message-----
> From: Michael Dinowitz [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, July 18, 2001 11:07 AM
> To: inFusion Support List
> Subject: [iMS] Re: word wrap
>
>
> I've implemented the CFX_iMSMail tag on the HoF box to work with the
system
> I have in place now and I found a slight problem. I'm using the beta that
> howie sent that allows for plain text messages. It seems the word wrap on
> that is slightly off. Its set to 66 characters and wouldn't change. Here's
> an example:
> ----------------------------
> I got into work and had a few phone messages from my wife who was
> quite
> concerned. It seems that the secret service called her about the
> thread.
> That's all I need. Macromedia AND the US government upset with me. :)
> Actually, they just wanted the headers from the post. I sent them the
> posters apology as well. Hope it's all ok.
> --------------------------
> Oh, and the header_cc doesn't seem to CC.
>
>
>
>
>
==^======================================================================
     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/iMSSupport.cfm
Need an iMS Developer license?  Sign up for a free license here:
http://www.coolfusion.com/iMSDevelopers.cfm
List archives: http://www.mail-archive.com/infusion-email%40eoscape.com/
Note: You are subscribed as [email protected]
==^======================================================================


Reply via email to