Unfortunately that approach won't work, since it means that TMDA wouldn't see any incoming spam messages. I'm a bit confused as to why TMDA doesn't preserve the original address if there's no tmda specific tokens. This seems v. broken.
- Silowyi -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nils Vogels Sent: Friday, September 07, 2007 13:10 To: [email protected] Subject: Re: Munging hyphenated addresses. Hi Silowyi, Silowyi Dracotiri wrote on 7-9-2007 17:56: > TMDA appears to be munging addresses with hyphens in them even when they > don't contain tmda tokens. For example: > > 9 Sep 5 16:56:14 mail postfix/pipe[8679]: CE90C9395C0: > to=<[EMAIL PROTECTED]>, ***relay=tmda***, delay=1, status=sent > (mail.some_domain.com) > 10 Sep 5 16:56:14 mail postfix/qmgr[3235]: CE90C9395C0: removed > 11 Sep 5 16:56:17 mail postfix/smtp[10432]: 4A6EA9398EC: > to=<[EMAIL PROTECTED]>, ***relay=mail.other_domain.com[<removed>]***, > delay=3, status=sent (250 OK <S860D>) > 12 Sep 5 16:56:17 mail postfix/qmgr[3235]: 4A6EA9398EC: removed > For one, this is why I personally use the + as a seperator :-) When looking at your logfiles, your postfix decides to treat mail differently between line 9 and line 11 (look at the relay= entries). I'd start by telling postfix that it only needs to do that in case of multiple seperators, since TMDA usually uses more than one seperator. Maybe you could even specify your filter so that only real TMDA-generated addresses are sent through TMDA for verification. Greets, Nils _____________________________________________ tmda-users mailing list ([email protected]) http://tmda.net/lists/listinfo/tmda-users
