The reason for running it through tmda twice is that we each have very different whitelists/blacklists. If my tmda blocks due to blacklist, will the message still go through to the second person?
I think this is a very bad idea, for the following reasons:
If you forward email to [EMAIL PROTECTED] to two internal accounts, and run TMDA at each destination account, then any time someone sends you email (and they aren't whitelisted) then they'll suddenly get TWO challenge messages (one from each forwarding destination). Some people hate challenge response, and others tolerate it, but will probably get a bit pissed being asked to confirm each message twice.
Also, if you're publishing [EMAIL PROTECTED] as a public email address, then that email address should have an identity of its own, and TMDA should be processed just for it. Much better would be to run TMDA as the webmaster user/virtual-user, with its own white/black list, then have all passed email forwarded to your two target users. Yes, this is a bit more admin work, but you can mitigate it by sharing the white/black-list files etc.
Alternatively, have the webmaster email delivered to its own directory, install an IMAP server, and have each person who reads webmaster's mail configure both their own personal account, and the webmaster account, into their email client, allowing full access to both data sets. This'll also let you reply to email as the webmaster user easily, which might help keep up the facade of the existence of a separate logical [EMAIL PROTECTED] entity.
-- Stephen Warren, Software Engineer, Parama Networks, San Jose, CA [EMAIL PROTECTED] http://www.wwwdotorg.org/pgp.html
signature.asc
Description: OpenPGP digital signature
_____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
