Spam detection software, running on the system "mailcrunch1.panix.com", has identified this incoming email as possible spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see support@panix.com for details.

Content preview: [Cyrus’s recent patches for ABCL-ASDF to use alternate Maven repositories and other fixes][1] have been merged [into the ABCL trunk][2,3,4,5]. [I made the following deviation from the patches][6]: The codes seems to intend to record, buts fails to actually set, the repository an artifact is download from as part of the path. I changed the ineffective code as a comment, mainly as the MVN path is intended to follow the [MVN URI scheme][7] for which the repository definitely doesn’t belong at the end but rather at the beginning. [...]

Content analysis details: (5.9 points, 5.0 required)

pts rule name description ---- ---------------------- -------------------------------------------------- 2.4 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net [Blocked - see http://www.spamcop.net/bl.shtml?109.126.64.2] 3.6 RCVD_IN_SBL_CSS RBL: Received via a relay in Spamhaus SBL-CSS [109.126.64.2 listed in pgwm4qf5v2mbif3ei5nmvnmsve.zen.dq.spamhaus.net] 0.0 HEADER_FROM_DIFFERENT_DOMAINS From and EnvelopeFrom 2nd level mail domains are different -0.0 SPF_HELO_PASS SPF: HELO matches SPF record -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature