On Mon, May 05, 2008 at 03:21:50PM +0100, Marcin Owsiany <[EMAIL PROTECTED]> wrote: > My guess would be that the API does not work like spfmilter assumes it > does. I don't know where the bug lies, though. > > Yes, I am using etch, postfix 2.3.8-2
My understanding from talking to other Postfix folks is that the Milter API in Postfix 2.3.x is rather immature. The API documentation reflects exactly what spfmilter is attempting to do: https://www.milter.org/developers/api/smfi_chgheader There are only two lines of code making this call, the first used when there are more than 10 Received-SPF headers and the second when there are Received-SPF headers purporting to be from the local host: smfi_chgheader( ctx, HEADER_NAME, i, (char*) 0 ); and smfi_chgheader( ctx, HEADER_NAME, cd->del_header_list[i], (char*) 0 ); Which is why I mentioned HEADER_NAME: #define HEADER_NAME "Received-SPF" If this header is actually being eaten by the smfi_chgheader() then it is a bug in the Postfix Milter implementation. The code for deleting this header should only be triggered if there's an existing Received-SPF: header. You can check for yourself; smfi_chgheader() is called at no other times :). -- Mike Markley <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
