Or make the matching work (a bit) like in the alias table...
login,userid
[EMAIL PROTECTED] [EMAIL PROTECTED]
ANY [EMAIL PROTECTED]
where the match first tries to match the largest and than reduces.
%s is replaced by ANY.
I'm not sure this is possible at all, just a su
Marc Dirix wrote:
>>
>> login,sock_allow,userid
>> userA,inet:10.0.0.1:110,[EMAIL PROTECTED]
>> userB,inet:10.0.0.1:110,[EMAIL PROTECTED]
>> userC,inet:10.0.0.1:110,[EMAIL PROTECTED]
>>
>> that way your users can login with both userA, and with [EMAIL PROTECTED]
>>
>
> Does this work with 100.00
login,sock_allow,userid
userA,inet:10.0.0.1:110,[EMAIL PROTECTED]
userB,inet:10.0.0.1:110,[EMAIL PROTECTED]
userC,inet:10.0.0.1:110,[EMAIL PROTECTED]
that way your users can login with both userA, and with [EMAIL PROTECTED]
Does this work with 100.000 accounts per domain?
Marc
Marc Dirix wrote:
> is it also possible to have 2 tests in dbmail_usermap?
>
> I'd like to reduce helpdesk traffic by both allowing users to logon with
> 1) userid
> 2) [EMAIL PROTECTED]
>
> the users are in the database in the form "[EMAIL PROTECTED]"
>
> i.e. would this work?:
>
> | login
is it also possible to have 2 tests in dbmail_usermap?
I'd like to reduce helpdesk traffic by both allowing users to logon with
1) userid
2) [EMAIL PROTECTED]
the users are in the database in the form "[EMAIL PROTECTED]"
i.e. would this work?:
| login | sock_allow | sock_d
Marc Dirix wrote:
> Hi
>
>
> The dbmail_usermap is not working as I expected. Somehow I'm doing
> something wrong here
> or dbmail behaves wrong.
>
> This is my dbmail_usermap:
>
> | login | sock_allow | sock_deny| userid
> --++--
Hi
The dbmail_usermap is not working as I expected. Somehow I'm doing
something wrong here
or dbmail behaves wrong.
This is my dbmail_usermap:
| login | sock_allow | sock_deny| userid
--+++--
+--
