What is the difference between FailTo, Return-Path, and Errors-To?  Can you
show examples of how they should be coded (e.g. is capitalization important?
I assume hypens are, is the exact field name "Return-Path" and "Errors-To"?)

I realized that I have <insetheader Errors-To="errors.<:ID:>", and I think
this used to work, but now doesn't.

Which method would you recommend if you know that you want to process
bounce-backs and you need to have an exact ID or the exact address it was
sent to?  lyris codes the smtp address in the return path/errors-to/failto,
how can that same behavior be done in IMS?

Thx,

Tac

----- Original Message -----
From: "Howie Hamlin" <[EMAIL PROTECTED]>
To: "inFusion Support List" <[EMAIL PROTECTED]>
Sent: Saturday, March 23, 2002 1:22 PM
Subject: Re: [iMS] dynamic FailTo attribute


> FAILTO does not use tokens.  However, if FAILTO is blank then the server
looks at the return-path header.  So, you can make a
> dynamic return-path header and that should work.
>
> Howie
>
> ----- Original Message -----
> From: "Tac/Smokescreen" <[EMAIL PROTECTED]>
> To: "inFusion Support List" <[EMAIL PROTECTED]>
> Sent: Saturday, March 23, 2002 8:12 AM
> Subject: Re: [iMS] dynamic FailTo attribute
>
>
> > But if you're creating a dynamic FailTo, doesn't that prevent you from
using
> > the QUERY= tag?  Or is there a way to indicate a variable from the query
> > within it?  Alternatively, could you use the TOKEN system, which doesn
allow
> > this?   Howie?
> >
> > Tac
>
>
==^=======================================================
     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