all trusted when no received headers are found

[Ben Wylie <sa...@benwylie.co.uk>]

IS there a way to stop all trusted being triggered when no received 
headers are found at all?

Thanks
Ben

Re: all trusted when no received headers are found

[Matt Kettler <mk...@comcast.net>]

Ben Wylie wrote:
> IS there a way to stop all trusted being triggered when no received
> headers are found at all?
>
> Thanks
> Ben
>
>

That should not happen in recent versions of SA.. What version are you on?

SA 3.1.x will only fire ALL_TRUSTED if all of the following are met:
    1) there is at LEAST one trusted relay
    2) there are NO untrusted relays
    3) there are NO unparseable Received: headers.

A message with no Received: headers would not match the first criteria.

Early members of the SA 3.0 series and the 2.6 series suffer from bugs
where only criteria 2 applies, causing false-positives on messages with
no Received: headers, or malformed Received: headers.

--------------------------------------------
Code that implements this, from EvalTests.pm of SA 3.1.0:

sub check_all_trusted {
  my ($self) = @_;
  return $self->{num_relays_trusted}
        && !$self->{num_relays_untrusted}
        && !$self->{num_relays_unparseable};
}


And the buggy version from 3.0.0:

sub check_all_trusted {
  my ($self) = @_;
  if ($self->{num_relays_untrusted} > 0) {
    return 0;
  } else {
    return 1;
  }

}

Re: all trusted when no received headers are found

[Benny Pedersen <me...@junc.org>]

On Fri, July 28, 2006 13:56, Ben Wylie wrote:
> IS there a way to stop all trusted being triggered when no received
> headers are found at all?

that will be brokken if that happens, your own mta should be there no matter
how brokken the sending client is

what you can do is trust less to avoid it, and make sure you own mta do not
remove headers, last you can try to set your mta to force 7bit headers to see
if the problem goes away, if it does, then you know the problem

-- 
Benny