Hi Paul,
Chipping in to the conversation. You said this Paul:
>What I've seen here recently is that the tokens are not evaluated in
>bounces, so the body has NO user-specific information.
Don't forget that there are two sorts of bounces, those that never leave
the server and those that bounce back from the distant server at some later
time.
The immediate bounces are as you say, nothing ever gets sent and are
therefore never evaluated, you have to rely on the info given to the
post-fail template for your error handling rather than what gets sent back
to the "sender". The later bounces have gone to the far end, and then been
rejected for whatever reason, so the message has been fully evaluated,
token-wise, and all the info you need is there.
Here at mbcomms we use the techniques already described, a unique
identifier of the "X-ListMember..." variety and a unique bounce eddress
then a processor template to handle the bounced stuff.
--
Yours,
Kym
==^=======================================================
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]
==^=======================================================
