http://bugzilla.spamassassin.org/show_bug.cgi?id=3358
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From [EMAIL PROTECTED] 2004-05-11 23:38 -------
OK, now working fine in 3.0.0-svn:
debug: looking up A records for 'chemistry.chem.utah.edu'
debug: A records for 'chemistry.chem.utah.edu': 128.110.196.114
debug: received-header: 'from' 128.110.197.97 is near to first 'by'
debug: received-header: relay 128.110.197.97 trusted? yes internal? no
debug: metadata: X-Spam-Relays-Trusted: [ ip=128.110.197.97
rdns=sharklvr.chem.utah.edu helo=sharklvr by=chemistry.chem.utah.edu ident=
envfrom= intl=0 id=i47Lw3HH012625 ]
debug: metadata: X-Spam-Relays-Untrusted:
...
debug: tests=ALL_TRUSTED,BAYES_00
debug:
subtests=__CT,__CTYPE_HAS_BOUNDARY,__CTYPE_MULTIPART_ALT,__HAS_MIMEOLE,__HAS_MSGID,__HAS_OUTLOOK_IN_MAILER,__HAS_SUBJECT,__HAS_X_MAILER,__MIME_VERSION,__MSGID_OK_DIGITS,__MSGID_OK_HOST,__NEXTPART_ALL,__NEXTPART_NORMAL,__SANE_MSGID
note that (obviously) you have to either have specified that 128.110.196.114 is
trusted in your config; or *no* trusted_networks or internal_networks lines at
all for the trust to be inferred, for this test to be accurate.
(If you have any trusted_networks lines the inferrence is switched off.)
I did find a bug in the DNS lookup code in Received, though, now fixed.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
