User conversion tag

Question

Hi people,
I have following mapping rule in mappings file:
in-chan=*;out-chan=tcp_intranet;convert $C$:T$EYes,Channel=tcp_keeper
The $T is used to find user conversion tag, but it seem that it not working, at the same time it does work with mailDomainConversionTag.
I think user conversion tags don't get applied on "relaying" systems but instead get applied only on the final, mailhost system.
May you please tell me why it's not working in Front-End servers as it's working with the domain conversion tag?
Regards

Answer 1

Reply from Kristin Hubner:
In addition to what [email protected] wrote:
(manually forwarding from:
http://swforum.sun.com/jive/thread.jspa?forumID=15&threadID=21487)
Hi people,
I have following mapping rule in mappings file:
in-chan=*;out-chan=tcp_intranet;convert $C$:T$EYes,Channel=tcp_keeper
The $T is used to find user conversion tag,
Not exactly. $:T is used to test the $T flag, which is set by the
presence of conversion tags.
but it seem that it not
working, at the same time it does work with mailDomainConversionTag.
If it isn't working it is because the conversion tag for the user isn't
being read.
I think user conversion tags don't get applied on "relaying" systems
but instead get applied only on the final, mailhost system.
Correct. User conversion tags only apply if the mailhosts match. They're
not considered otherwise.Note that there is an RFE (# 4906355) to consider changing this (make user
conversion tags apply even on front end/relaying systems). The customer might
want to get themselves added to the interest list, as there's no customer
attached to it currently; having a real customer interested in this might
increase the chances we'll get around to doing it.
Regards,
Kristin
A special exception is made for domain conversion tags in this case so that
they can be applied.
May you please tell me why it's not working in Front-End servers as
it's working with the domain conversion tag?
See above.
                    Ned