We're using the CanonicalizeEmailAddress config options to deal with making sure [email protected] is the same as [email protected]. It works great, especially because nobody was ever supposed to create an email account as [email protected] and not create an equivalent one as [email protected].
Of course now someone in another unit has done that, and there is no matching [email protected] account. This goes against our own best practices, but there is nothing I can do about it right now. As a result, RT can not email [email protected] because RT keeps forcing the address to be [email protected] which does not exist. I tried manually changing the account for that user to use the real address, but CanonicalizeEmailAddress keeps kicking in and changing it. Any suggestions on how to work around it for this one email address? I wonder if I was to manually change the address in the database if that would help. I just do not want to mess with the database by hand... _______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [email protected] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
