>It looks like these two lines will do what I want for a start: > >#Set($CanonicalizeEmailAddressMatch , '@subdomain\.example\.com$'); >#Set($CanonicalizeEmailAddressReplace , '@example.com'); > >To handle multiple email servers would I do something like this? My >regexp knowledge is not that great. > >#Set($CanonicalizeEmailAddressMatch , >'@(subdomain1.\.dept|subdomain2\.something|subdomain3)\.example\.com$');
Yes, but I'd be leary of the @ signs, which you don't need in this case. My file is: Set($CanonicalizeEmailAddressMatch , '(tigger|icarus|mailserv)\.(cc\.)?uic\.edu$'); Set($CanonicalizeEmailAddressReplace , 'uic.edu'); bobg > >Bob Goldstein wrote: >>> Do you all have any creative solutions for dealing with multiple email >>> addresses from the same person so you don't end up with two user >>> accounts per person? I see situations where someone has their email >>> client misconfigured so they send mail out as >>> [EMAIL PROTECTED] when most of the time they are >>> [EMAIL PROTECTED] >> >> in RT_SiteConfig.pm see: >> >> CanonicalizeEmailAddressMatch >> CanonicalizeEmailAddressReplace >> CanonicalizeOnCreate >> >> That at least lets you map various email addresses to one address, >> if you can do it with generic regexps. >> >> In my case, this would squeeze [EMAIL PROTECTED], [EMAIL PROTECTED], >> [EMAIL PROTECTED] >rus.cc.uic.edu, etc. >> But no relation to [EMAIL PROTECTED] And of course, an append to a ticket >> only goes to a single address. >> >> In my case, we go a small step further, becuase the cannonical mail address > here >> is related to the web logon, so when an account gets created, >> either by web or email, both web and email parts of the account are done ri >ght. >> >> bobg >> >>> We can probably use procmail examine and sometimes re-write email >>> addresses before they go into RT, but I was curious what others have >>> done. Part of my problem is there are many machines email may come from >>> [EMAIL PROTECTED], [EMAIL PROTECTED], etc >>> _______________________________________________ >>> 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 >>> > _______________________________________________ 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
