[ingo] case sensitive user names and ingo mailfilter
Jan Schneider
jan at horde.org
Fri Feb 6 17:50:28 UTC 2009
Zitat von dev at stean.ch:
> hello all,
>
> i am using maildrop as mail filtering backend for ingo, the path
> for the filenames of these filters is build with the user its
> name (%u placeholder).
>
> recently some user complained about that even if the spam filter
> was activated (and so it is according horde preferences) but not
> working at all. the maildrop filter file was missing where it
> should have been.
>
> soon i found out that the user is logging in by typing the user
> name with uppercase letters, so for example instead of
> tom at somewhere.com typed Tom at somewhere.com
>
> what ingo then did is writing the mailfilter file to a sub
> directory named Tom instead of tom. looks like horde itself uses
> as user id what ever comes but handles it case insensitive,
> however running a unix system behind, this will of course not work
> for files.
>
> should there be a correction made in the backend handler of ingo
> to use always lowercase?
No, you should use an authentication hook to normalize user names, if
your authentication backend is case insensitive.
Jan.
--
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/
More information about the ingo
mailing list