Hector Santos wrote:
Then how are you expecting this to be read?
NEUTRAL --> default neutral, no match, continue
NEUTRAL --> default neutral, no match, continue
FAIL --> FAIL? Or use previous default?
The above doesn't match sense. No?
No, I expect it to match the Neutral mechanism and return a Neutral
result. The message is sent via a shared MTA that does not have
cross-user forgery protections in place, so Neutral is an appropriate
qualifier for the mechanism.
The message that your MTA rejected was sent from:
relay01.pair.com (relay01.pair.com [209.68.5.15])
The relevant mechanism in my record is ?a:relay.pair.com.
% dig relay.pair.com A
; <<>> DiG 9.2.3rc4 <<>> relay.pair.com A
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16657
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 2, ADDITIONAL: 2
;; QUESTION SECTION:
;relay.pair.com. IN A
;; ANSWER SECTION:
relay.pair.com. 7200 IN A 209.68.5.15
relay.pair.com. 7200 IN A 209.68.5.16
relay.pair.com. 7200 IN A 209.68.5.17
relay.pair.com. 7200 IN A 209.68.1.20
;; AUTHORITY SECTION:
pair.com. 4159 IN NS ns1.pair.com.
pair.com. 4159 IN NS ns0.ns0.com.
;; ADDITIONAL SECTION:
ns0.ns0.com. 4215 IN A 209.197.64.1
ns1.pair.com. 4215 IN A 209.68.1.11
;; Query time: 12 msec
;; SERVER: 209.68.4.105#53(209.68.4.105)
;; WHEN: Thu Aug 25 11:55:52 2005
;; MSG SIZE rcvd: 168
So the mechanism matches and Neutral should be the result.
Scott K