These are examples of SPF query responses that are not comprehended by ASSP:
Received-SPF: permerror -extension:foo (mybox.example.org: domain of
[EMAIL PROTECTED] uses mechanism not recognized by this client)
Received-SPF: temperror (mybox.example.org: error in processing during
lookup of [EMAIL PROTECTED]: DNS timeout)
Here's the ASSP log of an SPF permerror event. ASSP passed the message,
which is spam (not caught by the Bayesian test):
Jun-6-07 14:07:21 190.40.185.245 <[EMAIL PROTECTED]> accepting triplet:
(190.40.185.0,[EMAIL PROTECTED],
[EMAIL PROTECTED]) waited: 10m 3s
Jun-6-07 14:07:21 190.40.185.245 <[EMAIL PROTECTED]> to: [EMAIL PROTECTED]
recipient accepted:
[EMAIL PROTECTED]
Jun-6-07 14:07:24 190.40.185.245 <[EMAIL PROTECTED]> to: [EMAIL PROTECTED]
SPF: unknown
(mail.chewtoy.com: error in processing during lookup of
[EMAIL PROTECTED]) client-ip=190.40.
185.245; [EMAIL PROTECTED];
helo=client-190.40.185.245.speedy.net.pe;
Jun-6-07 14:07:24 Commencing DNSBL checks on 190.40.185.245
Jun-6-07 14:07:25 Completed DNSBL checks on 190.40.185.245
Jun-6-07 14:07:25 190.40.185.245 <[EMAIL PROTECTED]> to: [EMAIL PROTECTED]
deleting spamming
whitelisted tuplet: (190.40.185.0,clarity.ca) age: 4s
Jun-6-07 14:07:25 190.40.185.245 <[EMAIL PROTECTED]> to: [EMAIL PROTECTED]
RBL: Received-RBL: neutral
(cbl.abuseat.org->127.0.0.2;
zen.spamhaus.org->127.0.0.4; )
Jun-6-07 14:07:25 190.40.185.245 <[EMAIL PROTECTED]> to: [EMAIL PROTECTED]
Received-URIBL:
pass
Jun-6-07 14:07:26 190.40.185.245 <[EMAIL PROTECTED]> to: [EMAIL PROTECTED]
Bayesian Check Prob:
0.00000 => ham
Jun-6-07 14:07:26 190.40.185.245 <[EMAIL PROTECTED]> to: [EMAIL PROTECTED]
message ok
Here's what a dnsreport SPF test says:
SPF lookup of sender [EMAIL PROTECTED] from IP 190.40.185.245:
SPF string used: v=spf1 a mx ip4:mail.clarity.ca -all.
Processing SPF string: v=spf1 a mx ip4:mail.clarity.ca -all.
Testing 'a' on IP=190.40.185.245, target domain clarity.ca, CIDR 32,
default=PASS. No match.
Testing 'mx' on IP=190.40.185.245, target domain clarity.ca, CIDR 32,
default=PASS. No match.
Testing 'ip4:mail.clarity.ca' on IP=190.40.185.245, target domain
mail.clarity.ca, CIDR 32, default=PASS. ERROR: Bogus IP in ip4 mechanism.
Testing 'all' on IP=190.40.185.245, target domain clarity.ca, CIDR 32,
default=FAIL.
Result: PERMERROR
Possible Results:
a.. Pass - This IP is authorized to send E-mail from this domain.
b.. Fail - This IP is not authorized to send E-mail from this domain
c.. SoftFail - This IP probably is not authorized to send E-mail from this
domain, but the domain owners are not certain
d.. Neutral - The domain does not know if the IP is allowed to send E-mail
or not.
e.. TempError - A temporary error occurred. The E-mail should be retried
later.
f.. PermError - A permanent error was encountered. The E-mail should be
rejected.
g.. None - No SPF record was found. It cannot be determined if the IP is
allowed to send E-mail from this domain.
Developers, please consider adding appropriate processing of SPF temperror
and permerror results to the ASSP code.
Regards,
Dave
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Assp-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-user
