Jim Ramsay <[EMAIL PROTECTED]> writes: > pass - The client mailserver matches the published SPF record for the > email address domain. You can be reasonably sure that the address is > not forged. In my case, I'm going to let this through unchallenged. > > fail - The client mailserver did NOT match the published SPF record > for the domain, so we know the address is forged. (Some SMTP servers > will drop these and not tag them). In my case I'll drop it, maybe > even at the SMTP level. I'll probably wait and see how this works, > though. > > unknown - There was no SPF record for the email domain, so no check > was made. > > error - Something went wrong.
It also says that when an SPF query returns "fail", the MTA should reject the connection, so it isn't likely that you'll see this in Received-SPF. "unknown" and "error" should be challenged as usual which means no incoming filter entry. This leaves "pass" which we will accept. This is the only case where I see Received-SPF being useful to the TMDA user. _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
