Re: Re: Case-sensitive status
Alessandro Vesely <[email protected]>
| Newsgroups | gmane.mail.spam.spf.discuss |
|---|---|
| Message-ID | <[email protected]> |
Hi Frank! On 13.08.2011 20:44, Frank Ellermann wrote: > On 13 August 2011 20:07, Alessandro Vesely wrote: > >> I'd be even more conservative. > > Good point, Authentication-Results in conflict with Received-SPF > would indicate that something might be not as it should be. Lack of inter-agent communication, unless Received-SPF had a TempError. For an example, Courier-MTA doesn't put an A-R field, but puts Received-SPF if properly configured; a filter that implements RFC 5451 can ease its job by reading any existing Received-SPF. E.g., zdkimfilter operates this way, without implementing check_host, but possibly adding other results. Implementing RFC 5451 requires to choose an "authserv-id" and to filter any existing, possibly spurious A-R fields that bear the same token. It is no rocket science, but may need to be coordinated with any existing agent that already sets A-R fields (most commonly, for DKIM / DomainKeys checks.)