Sorry for the long delay in response. It appears that this is only the case with TMDA 1.0.x. Looks like I changed this behavior in 1.1.x, so that if you include 'Received' in PURGED_HEADERS_CLIENT, that header will be removed.
So, you might upgrade your TMDA to the 'unstable' branch, which actually isn't that unstable since it doesn't differ greatly from 'stable' at this point. On Jan 28, 2006, at 2:05 PM, Alfred Ganz wrote: > Jason, > Subject: Re: Received: header from tmda-inject > Date: Wed, 25 Jan 2006 20:57:45 -0700 > > Have you tried adding 'received' to your PURGED_HEADERS_CLIENT > setting? I forget whether these headers are purged before of after > the custom Received headers are added, but it's worth looking into I > think. > Sadly, the purge takes place just before the addition of the Received: > line in tmda-inject. > > BTW, I have modified tmda-inject locally to use Util.gethostname() > instead of socket.getfqdn() for the moment, but I don't like to run > with > non-vanilla stuff. > > Thanks for the suggestion anyhow, AG > > -- > > ---------------------------------------------------------------------- > Alfred Ganz alfred-ganz:at:agci.com > AG Consulting, Inc. (203) 624-9667 > 440 Prospect Street # 11 > New Haven, CT 06511 > > ---------------------------------------------------------------------- > _____________________________________________ > tmda-users mailing list (tmda-users@tmda.net) > http://tmda.net/lists/listinfo/tmda-users _____________________________________________ tmda-users mailing list (tmda-users@tmda.net) http://tmda.net/lists/listinfo/tmda-users
