On my system I set up internal only keyword aliases and have support forwarded to them...
ex: support .forward file [EMAIL PROTECTED], [EMAIL PROTECTED] tom > I ended up doing this. > > 1) installed TMDA on user "support" > 2) set DELIVERY = "[EMAIL PROTECTED]" > 3) tmda_tagged_support = alias to 3 user accounts. > > Now, it half works. When you email support for the first time it asks > you to please reply and authorize, as it should. When you do so, it > forwards to tmda_tagged_support@ and everything is fine. But, if you > send a second email, one of the users from the alias (me) also has TMDA > installed, and it will ask you to authorized to him as well. In my > whitelist I have @ourdomain.com. Shouldn't the email being sent from > support@ to tmda_tagged_support match the @ourdomain.com and there for > by pass TMDA? > > What other steps am I missing? Can I make a rule to match > X-Original-To? That way if TMDA sees the email header with > "X-Original-To: [EMAIL PROTECTED]" it will whitelist it, or just > let it pass through? > > _____________________________________________ > tmda-users mailing list ([EMAIL PROTECTED]) > http://tmda.net/lists/listinfo/tmda-users _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
