The -d29.4 debugging switchcauses the
process of fuzzy matching to be traced:
finduser(name)
Here, name is an address in the form of a local user address, without the host part. The
name is first looked up in the passwd(5) file on the assumption that it is a login name. If it is
found, sendmail prints:
found (non-fuzzy)
If sendmail was compiled with hesiod support, all numeric login names will not work properly,
resulting in the following:
failed (numeric input)
If the name is looked up and not found, the entire passwd(5) is searched to see whether
name appears in any of the GECOS fields. This search is done only if MATCHGECOS
(?§3.4.21 on page 120) was defined when sendmail was compiled and if the MatchGECOS
option (?§24.9.63 on page 1043) is true. If MATCHGECOS was undefined, the search ends
and the not-found name causes the mail to bounce. If the MatchGECOS option is false, sendmail
bounces the message and prints the following:
not found (fuzzy disabled)
If the MatchGECOS option is true, the GECOS fields are searched. But before the search starts,
any underscore characters (and the character defined by the BlankSub option, ?§24.9.10 on
page 980) that appear in name are converted to spaces. Then, in turn, each GECOS field
has the full name extracted (everything following the first comma, semicolon, or percent is
truncated off, including that character), and any "&" (ampersand) characters found are
converted to the login name.
Pages:
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997