LedHed wrote: > Are the multi-purpose email accounts you create Aliases to one > account? If so then you wont have to worry about maintaining 50+ > quarrantines because the mail ultimately goes to the primary (Non > Aliased) account which is what you will train/quarantine.
Yes - ultimately all those aliases all go to one account (although they're not always the same account). I would want one quarantine per ultimate destination. I just didn't see how dspam would know where the mail is actually going, since when postfix delivers it the To header remains intact. For example, this email was still addressed to [EMAIL PROTECTED], even though that isn't where it ended up. If dspam can somehow figure it out then that is great. Would I want to enable ParseToHeaders in this case? > I don't see > why you couldn't handle both local and virtual users, but if you were to > use dspam's domain scale (if you have multiple domains) then I'm not > sure how dspam would handle the local accounts. Postfix should allow > both local and virtual users. There are several ways to call dspam. > Typically with postfix its called via a content_filter, but it can also > be called via Local Transport, Virtual Transport, or in my case > Check_Client_Access. > I figured that a content filter would be the best approach, but I wasn't sure that this wouldn't cause confusion with all the aliases. If it will just magically figure everything out I can just give it a try.
