Yes, but that still requires setting something (generic) in rcpt, then
calling that from within the tag. That's what I'm doing now, and it's a lot
of coding, and in some cases impossible. (For example, when I don't want to
set reply-to, rather than wanting to set it to something different).
I'd like to remove the rcpt insetheader's altogether, since the headers
different depending on what address it's being sent to, yet if it's going to
multiple addresses, you have to set it for everything. I want to process
list mail differently than individual mailboxes, so I'd prefer not to mangle
the emailfile in rcpt, since it's a shared file.
Overwriting the headers seems natural. I'm sure many of us have written
cfx_imsmail smtpto=... emailfile="xxx" header_from='"Test"
<address(at)domain.com>' header_subject="My New Subject">
and wondered why the from and subject didn't come out as expected. (At a
minimum, that tag should fail with the error messages that header_ is
incompatible with emailfile=, but again, overwriting the headers would be
more natural).
What logic would you suggest setting the headers for a mail received at the
same domain that's going to a discussion list, an announcement list, and to
an individual mailbox, with reply-to and subject different for each? It's a
lot of work to set up generic fields in rcpt and then process them. It
also requires that you re-process in the individual mail, otherwise you get
a subject that looks like <:generic_subject:>, since normally the raw
mailfile is put into the inbox table and sent as is it the client when it's
popped.
Does this all make sense?
Tac
>From your earlier email:
---
subject: <:prepend:> real subject
and dfine the "prepend" for the list member as the list name and for the
other recipient as a blank then that would
work.
In your RCPT template you can set the subject and in the call to the cfx you
can define the tokens.
This should work...
----- Original Message -----
From: "Howie Hamlin" <[EMAIL PROTECTED]>
To: "inFusion Support List" <[EMAIL PROTECTED]>
Sent: Saturday, June 22, 2002 12:06 PM
Subject: Re: [iMS] letting IMS tag override headers in emailfile
> I explained how you might be able to do this in a previous email. Have
you tried that yet?
>
> Howie
>
> ----- Original Message -----
> From: "Tac" <[EMAIL PROTECTED]>
> To: "inFusion Support List" <[EMAIL PROTECTED]>
> Sent: Saturday, June 22, 2002 11:58 AM
> Subject: [iMS] letting IMS tag override headers in emailfile
>
>
> > I've been coding up all sorts of logic in rcpt to send my messages
> > correctly, but I once again request that the imsmail tag header
attributes
> > override the ones in emailfile. Here's an example of something I'm
really
> > stuck with.
> >
> > Somebody sends a message to [EMAIL PROTECTED] and
> > [EMAIL PROTECTED] The internal logic is that discussion
lists
> > set the reply-to to the list, while announcements to back to the author.
So
> > I check for what kind of list it is and call <insetheader
> > Reply-To="<:list_code:>@domain.com> in the rcpt script.
> >
> > How do I set it up so that reply-to is set properly for each of the
lists?
> > (that is, set reply-to for the discussion list, but don't set anything
for
> > the announcement list, letting the user's settings for reply-to work)
> >
> > What I think I could do is set the reply-to header to some generic
field,
> > then set it in the cfx_imsmail call, but this starts to get more
complicated
> > than I'd like. Basically, I'd like to set the headers in cfx_imsmail,
since
> > that's where I know what I want them to be.
> >
> > Alternatively (though I don't really like this as much), is there a way
to
> > configure IMS so that each recpient gets its own emailfile, rather than
> > having all the recipients share it? I don't want to reject any mail
coming
> > to more than one recipient (putting the burden on the user to separate
each
> > list or individual email), but if there's a way to automate this, maybe
> > that's a solution.
> >
> > TIA,
> >
> > 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]
==^=======================================================
