We're going to gather up a list of feature requests for iMS 2.6 of 3.0.
Regards,
Howie
----- Original Message -----
From: "Tac" <[EMAIL PROTECTED]>
To: "inFusion Support List" <[EMAIL PROTECTED]>
Sent: Thursday, January 23, 2003 11:38 AM
Subject: [iMS] feature request: subjectprepend
> I have a feature request to modify the behavior of subjectprepend.
> Specifically, I'd like the tokenization happen before the subject check, so
> that when a token is being used, it is not prepended if that value already
> exists in the subject.
>
> An example: message sent to list_1 and list_2. The rcpt script prepends
> the <:list_code:>, which of course is not yet expanded, it is the literal
> token.
>
> inset_header('subjectprepend','[<:list_code:>]'); //
>
> When Post is delivering the message, I believe that it checks for the
> literal <:list_code:> in the subject, doesn't see it, so prepends
> <:list_code:> to the front of the subject, then tokenizes it. This, of
> course, does exactly what I don't want it to do, leaves the subject with a
> bunch of repeated list codes.
>
> I can't expand out the token in rcpt, because it might be going to multiple
> lists.
>
> Thank you for your consideration of this request. I believe it will be a
> matter of applying the tokenization to the subject prepend pattern before
> the check, not sure how difficult this is.
>
> 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]
==^=======================================================
