Tonni, Unfortunately our environment is not as centrally-controlled as yours, and we will be hosting domains for other groups who will independently-manage their end-users on a variety of different platforms. Hooking into all of these to perform smarthosting (getting ldap updates etc.) is not possible. Therefore, we will need postfix to continue to accept mail for [EMAIL PROTECTED] and transport what it except to the end mailserver after processing
Regarding the virtual file example I mentioned before, these are test we are doing now with a single domain trying to get the functionality we are looking for. In practical use, the virtual map will probably include some aliases for well-known spammer favorites (ceo, president, etc.) to point to one user (spamtrap perhaps) for that domain, and the rest will get forwarded to the end mailserver for the domain after processing via the transport map entry. I didn't include version numbers before because I was expecting more of a theoretical (best-practice) discussion about how to accomplish our goal and not so much specific syntax. If it helps, here is my info: postfix-2.3.7 dspam-3.6.8 mysql-5.0.32 If you have an alternative approach that would work better, please let me know. However, working with a controlled list of usernames will not be possible. Thank You, Sean
