Re: : [dspam-users] dspam as mailbox_command or how I learned to ...

Sorry, I wasn't being clear.

My issue with aliases is when dspam is running as a content-filter.
postfix hasn't / doesn't process / determine the final reciepient and
it generates multiple targets (unless I play with a postfix
virtual_alias tables. (I'm not ready yet.)) And spreads the tokens
across multiple users. (So new users (i.e. a new full email address)
do not have access to the "real" users token set)

<chaim>

On 10/7/05, kjohnson@hanoveruniform.com <kjohnson@hanoveruniform.com> wrote:
> If you are worried about the aliases, you could use the
> "MySQLUIDInSignature on" option. This makes it so that there are only two
> training aliases -- spam@ and notspam@, and dspam figures out the user
> based on a string in the dspam signature.
> This also works for the other DB, psomething
>
> --Kyle
>
>
> !DSPAM:2102,43467253230908792415415!
>
>
>
>
Received on Fri Oct 7 10:30:58 2005