On Sat, May 03, 2008 at 07:39:17PM -0700, Mike Markley wrote: > It seems more likely to me that the Received header is somehow being > suppressed (it should be inserted by the host that's running spfmilter, > right?)
No. It is removing the most recent Received header which is _already_ in the received message (i.e. the header added by the MTA which directly preceded the problematic one on the message's path). > I still don't understand how spfmilter could be causing this, so I plan > to take it to postfix-users or similar. Based on the spfmilter package > version, I'm guessing you're running etch, and therefore Postfix 2.3.8; > can you confirm that? 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 -- Marcin Owsiany <[EMAIL PROTECTED]> http://marcin.owsiany.pl/ GnuPG: 1024D/60F41216 FE67 DA2D 0ACA FC5E 3F75 D6F6 3A0D 8AA0 60F4 1216 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
