I just installed the Sender Verification Extension for the first time, and I am looking at my inbox to see how it works. I have a question because I am not sure the behavior is correct. In at least two cases I see messages with a generic "SVE Verification Failed" message, and I know that the domains have SPF records because I am the host.

Case #1 My wife sent me an E-mail, the sending and receiving domains are the same.

From - Mon Nov 17 15:33:55 2008
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Return-path: <tammy@...>
Envelope-to: John@...
Delivery-date: Mon, 17 Nov 2008 16:33:09 -0600
Received: from [CENSORED FOR POST] by shelby.websitewelcome.com with local-bsmtp ([CENSORED FOR POST])
(envelope-from <tammy@...>)
id 1L2Cea-0002p1-T5
for John@...; Mon, 17 Nov 2008 16:33:09 -0600
X-Spam-Checker-Version: SpamAssassin 3.3.0-r613124 (2008-01-18) on
shelby.websitewelcome.com
X-Spam-Level: *
X-Spam-Status: No, score=1.4 required=5.0 tests=AWL,HTML_MESSAGE,RDNS_NONE,
SPF_SOFTFAIL shortcircuit=no autolearn=disabled version=3.3.0-r613124
Received: from [72.24.123.87] (port=1754 helo=freyr)
by shelby.websitewelcome.com with esmtp ([CENSORED FOR POST])
(envelope-from <tammy@...>)
id 1L2Cea-0002ov-Md
for John@...; Mon, 17 Nov 2008 16:33:08 -0600
From: "Tammery Reid" <tammy@...>
To: "'John C. Reid'" <John@...>
Subject: Chastain Law
Date: Mon, 17 Nov 2008 15:34:34 -0700
Message-ID: <000001c94904$aafd8cd0$1400a8c0@asgard>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0001_01C948C9.FE9EB4D0"
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AclJBKo3deUTkdHvQ4Oiayxs2O3Flw==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350

This is a multi-part message in MIME format.

------=_NextPart_000_0001_01C948C9.FE9EB4D0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit

SPF:

keeptechworking.com. IN TXT 14400 "v=spf1 a mx include:websitewelcome.com ~all"

Case #2 Send to me by a client whose domain I host.

Header:

From - Tue Nov 18 08:57:17 2008
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Return-path: <mta@...>
Envelope-to: John@...
Delivery-date: Tue, 18 Nov 2008 09:56:56 -0600
Received: from t313c0mm by shelby.websitewelcome.com with local-bsmtp ([CENSORED FOR POST])
(envelope-from <mta@...>)
id 1L2Swi-0004Me-2B
for John@...; Tue, 18 Nov 2008 09:56:56 -0600
X-Spam-Checker-Version: SpamAssassin 3.3.0-r613124 (2008-01-18) on
shelby.websitewelcome.com
X-Spam-Level:
X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED,AWL
shortcircuit=no autolearn=disabled version=3.3.0-r613124
Received: from [208.187.37.147] (port=2700 helo=[172.16.1.128])
by shelby.websitewelcome.com with esmtpa ([CENSORED FOR POST])
(envelope-from <mta@...>)
id 1L2Swh-0004MQ-Uo
for John@...; Tue, 18 Nov 2008 09:56:56 -0600
Message-ID: <4922E5C8.9000808@...>
Date: Tue, 18 Nov 2008 08:56:56 -0700
From: Terry Ambruster <mta@...>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: "John C. Reid" <John@...>
Subject: Re: [CENSORED FOR POST]
References: <492243AC.7090807@...>
In-Reply-To: <492243AC.7090807@...>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

SPF:

chastainlaw.net. IN TXT 14400 "v=spf1 a mx include:websitewelcome.com ~all"

Should these not pass verification? Is the error on my end? Is it a bug? Do I not have SPF setup correctly? I really don't know as I have never used your plug-in before, and it is what alerted me to the possibility that something might be wrong with my SPF record. Thank you for your help.