On Fri, 4 Jan 2002, [Windows-1252] S�nke Ruempler wrote: > >Yep, like i said, account resolution happens after filtering :) > >You have to put filters even on aliases. > > so if i have 2000 aliases for one account (zB webmaster@*), i have to create > 2000 files in the filters directory? that is reallybad to handle, isn't it? > > and if i have an real account and some aliases for it, for what reason the > filter should not be executed for the aliases, too? > > sorry, but i see no logic in there :-).
I could describe my logic as "optimize for 99% of cases avoiding to bloat the source code to make happy the remaining 1%". Again, guess who's the only one that noticed it. 90% of XMail's users does not use filters. Of the remaining 10%, 95% of users use filtering with a simple .tab ( common filter for everyoone, like av, antispam, etc.. ). Of the remaining 5%, 98% uses filters with a domain granularity. Of the remaining 2%, 99% uses filters with account granularity and is happy with that. The remaining 1% ( basically you ) uses filters with account resolution, with accounts with 2000 aliases. Can you give me a valid reason why should i add another database lookup ( that will take place later ) to fit your case ? Solution : webmaster@* -alias-> [EMAIL PROTECTED] [EMAIL PROTECTED] -mproc-redirect-> realalias@whoever filter realalias@whoever - Davide - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
