We're using the CanonicalizeEmailAddress config options to deal with making sure usern...@somemachine.server.edu is the same as usern...@server.edu. It works great, especially because nobody was ever supposed to create an email account as someth...@somemachine.server.edu and not create an equivalent one as someth...@server.edu.
Of course now someone in another unit has done that, and there is no matching someth...@server.edu 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 someth...@somemachine.server.edu because RT keeps forcing the address to be someth...@server.edu 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: sa...@bestpractical.com Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
