Daryl C. W. O'Shea wrote:
Even after doing my best to fix the body wrap mangling of your sample, I can't get it to FP. It IS working as it should (ie. not hitting on the sample). That's why I asked for a copy sent as an attachment.

Oops, I overlooked that. You should have it by now. identifying info wasn't removed this time, so play nice :-)

Is there any part of this rule that might be affected by using Amavisd or testing via Milter? (I do both)

If whatever handled the message for scanning didn't fudge the "Received: from bigfootinteractive.com" header like it should be then this would happen.

Hm. Okay, the NO_RECEIVED and NO_RELAYS rules fired on this as well. Theory: perhaps Milter hands the message to Amavisd prior to adding the local Received line? That it only adds that header once Milter agrees?

I assume that we can check the current remote address in some form, yes? If I can figure this out, I'll provide an updated rule. If you know how to do this, clue me in.

I just provide the SARE rules as found on the SARE website (checked every few minutes) via sa-update channels. Beyond that, I have nothing to do with them.

Whoops. Sorry, I confused you and Ted because you responded. Apparently these are Ted's rules...

--
Jo Rhett
Network/Software Engineer
Net Consonance

Reply via email to