(manually fiddled together, since I am not on the tmda-users-list (just reading from the archive :-). I hope I don't break threading :-)
Drew Raines <[EMAIL PROTECTED]> wrote: > Thomas -Balu- Walter <[EMAIL PROTECTED]> writes: > > > $ cat .forward+test\=b-a-l-u.de > > "| /usr/bin/tmda-filter" > > > > but tmda will ask for a confirmation using the Reply-To: > > > > >[EMAIL PROTECTED] > > > > I've tried to change the USERNAME = "test" and HOSTNAME = "b-a-l-u.de" > > in my ~/.tmdarc, with no result at all. > > You didn't mention what version of TMDA you're using. Newer ones > can use > > http://tmda.net/config-vars.html#CONFIRM_ADDRESS I used the default debian-package (0.51-1), since I was about to play with it first - and that's easier by using apt-get :-) I've done a quick grep through tmda-rfilter for CONFIRM_ADDRESS with no result, so I guess it was not supported then. The newer packages require upgrade of python too, which I don't want to risk on a production machine... But I am quite sure, that it still won't work. As I stated, my addresses get mangled from [EMAIL PROTECTED] to balu+test=b-a-l-u.de@localhost. I wanted to use a .forward+test=b-a-l-u.de to filter mails through tmda. Mails sent by tmda that would look like (if CONFIRM_ADDRESS = "[EMAIL PROTECTED]"?): [EMAIL PROTECTED] My postfix would mangle that (for delivery) to balu+test+confirm+accept.1037718324.12857.c5713f=b-a-l-u.de@localhost Since postfix does not support "hierarchical" .forwards, it would look for .forward+test+confirm+accept.1037718324.12857.c5713f=b-a-l-u.de (not find it) and .forward. So my way to go would be to call tmda from .forward and not .forward+test=b-a-l-u.de as I wanted to do... But then again, all my mails would be filtered by tmda, which I wanted to avoid during my testing-phase... Balu _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
