However the search is performed in case sensitive mode but rfc822
describe mail addresses in case unsensitive mode.
So, the following modification in /opt/rt3/lib/RT/EmailParser.pm file
would be quite reasonable
However the search is performed in case sensitive mode but rfc822
describe mail addresses in case unsensitive mode.
while I agree that it’s probably more useful to do the search-replace
case-insensitively, that’s not what the rfc says. The host portion of
an email address is case-insensitive, but there’s nothing in the RFCs
that mandate the username portion (to the left of the @) be
case-insensitive. I believe in a couple MTAs it’s not.
However the search is performed in case sensitive mode but rfc822
describe mail addresses in case unsensitive mode.
RFC 822 requires the email address local-part to be case sensitive, see
section 6.1. RFC 2822 has this to say in section 3.4.1:
The local-part portion is a domain dependent string. In addresses, it
is simply interpreted on the particular host as a name of a particular
mailbox.
On Unix systems, the local-part traditionally has been case sensitive,
and still is on a lot of systems.
many (most?) mail systems accept email addresses regardless of case.
The right answer here would appear to be default to case insensitive and
an option to return to case sensitive when needed. Most mail daemons
handle this properly so only those stuck with truly old systems are an
issue here.
However the search is performed in case sensitive mode but rfc822
describe mail addresses in case unsensitive mode.
So, the following modification in /opt/rt3/lib/RT/EmailParser.pm file
would be quite reasonable
645c645
< $address =~ /$RT::RTAddressRegexp/ ) {
$address =~ m/$RT::RTAddressRegexp/i ) {
I have not tested this, but you should be able to write the regular
expression to be case-insensitive without changing the RT core code,
using the “(?i)” construct:
The right answer here would appear to be default to case insensitive
and an option to return to case sensitive when needed. Most mail
daemons handle this properly so only those stuck with truly old
systems are an issue here.
Well, as it stands, you can overlay the function that does the search
and replace with sort of logic you like.