Yep, that's on my RT annoyances list too. No easy way to work around
in the present product except to add the second email address to the
ticket, in which case the person associated with those addresses will
get 2 copies of RT correspondence, one to each address. This is
sub-optimal.
IMnsHO, the
On Thu, Apr 19, 2007 at 10:53:47AM -0600, Ole Craig wrote:
Yep, that's on my RT annoyances list too. No easy way to work around
in the present product except to add the second email address to the
ticket, in which case the person associated with those addresses will
get 2 copies of RT
Jesse -
Thanks! I hadn't seen that before. I'll give it a shot now that
I finally have hardware for an RT development system.
(Originally setup RT as a proof-of-concept, we needed it, started using
it, and then I was faced with the quandaries inherent in doing piecemeal
development work
We recently upgraded to 3.6.1 on fc5 and are now seeing these messages for
some correspondence. I'm not sure if this helps you at all but I spotted
that it is only happening when the original requestor replies using a
different e-mail address e.g. the ticket is created for user@domain,
we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Running RT 3.6.3 on Mac OS X 10.4.8
Everything has been working fine since upgrading to v3.6.3 from v3.6.1. We
added the
RT::LdapUserLocalOverlay to our installation shortly after doing the upgrade.
Since then we have had
intermittent issue with
