francis picabia: > The tests have been done in both 2.6.6 and 3.0.2 > > We've been using canonical_maps for over a decade > without a hitch, but recently came across a situation > where an account is referenced in both mapping files. > > canonical_maps = > hash:/etc/postfix-internal/lowercase,hash:/etc/postfix-internal/genericstable > > We have student accounts beginning with a number and ending > with a letter. We'd like to map any uppercase to lowercase > so this appears uniform for all places this account is used. > So we have a lowercase mapping file: > > 123456A [email protected]
With few exceptions, table lookups are case-insensitive (it is configurable with regexp/pcre maps). This means that the above entry matches both 123456A and 123456a. > The account might also have an alias for a more personal name > we want to rewrite, so it is kept in genericstable: > > 123456a [email protected] This entry will not be found, because "123456A [email protected]" already matches the search key "123456a". Maybe you can swap the order of the maps (short name -> long name mapping before the casefolding mapping). Wietse
