Hello,
(For those short one time, the actual question is at the bottom...) I'm on a mission to replace an outdated Barracuda with a shiny new DSPAM installation. We are hosting a half dozen domains or so, and have a number of people with multiple email aliases. All users are on Exchange, and so the DSPAM box will function as a mail relay (it is not in production yet). I have a running installation of DSPAM 3.6.8 on Debian Etch, with a MySQL 5.0 backend, Postfix 2.3.8 and Apache 2.2.3. The basics are working, I can control through Postfix which domains go through DSPAM, and filtering/web front-end etc. works, the latter with LDAP authentication against the domain even. My goal is to polish this into something that works as transparently as possible, with as little disruption to the end-user as possible. Because I obviously want the end-users to take part in training DSPAM for themselves, it is also important that this process be as simple and uninvolved as possible (Outlook plugin has my preference). Aside from the now horrendous filtering performance (accuracy wise) and ridiculous cost of the annual subscription service, we were pretty satisfied with the way the Barracuda functions and interfaces with the end-user. There are some issues I need to work out before I can put DSPAM in production however. The hurdle I'm trying to get over at the moment is the challenge of DSPAM and email aliases. I'm aware of the localStore option where uid's are re-used for email aliases, and that would be fine. The part that I was trying to figure out is how to get DSPAM to be aware of what's an alias - an LDAP lookup to Active Directory would've been ideal, but that doesn't seem to be implemented by DSPAM (yet?), at least not with this functionality. Periodically running some kind of script to maintain an alias database would be acceptable, but I'd prefer some way to do "live" lookups. Then, while searching this list, several people mentioned handling this with Postfix instead so that the recipient is replaced with the primary email address which DSPAM will recognize, and that makes a lot of sense to me. So this is my question today: how can I get Postfix to perform LDAP lookups to Active Directory and substitute any email alias with its primary email address in the envelope before passing the message to DSPAM? I have found some documentation on some aspects of this, but nothing that specifically does this with AD in particular. And on the same subject, what about distribution groups? Should they also be expanded, or treated as a single entity? Thanks in advance for any help. Anton Tilstra
