You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by Bounced mail <MA...@maven.apache.org> on 2014/10/21 13:17:36 UTC
Returned mail: see transcript for details
Spam detection software, running on the system "mx1-us-east.apache.org",
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
the administrator of that system for details.
Content preview: The original message was received at Tue, 21 Oct 2014 19:17:36
+0800 from maven.apache.org [71.164.21.147] ----- The following addresses
had permanent fatal errors ----- <co...@maven.apache.org> ----- Transcript
of session follows ----- while talking to maven.apache.org.: >>> MAIL From:"Bounced
mail" <MA...@maven.apache.org> <<< 501 "Bounced mail" <MA...@maven.apache.org>...
Refused [...]
Content analysis details: (16.9 points, 10.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
4.0 RCVD_IN_XBL RBL: Received via a relay in Spamhaus XBL
[222.66.83.44 listed in zen.spamhaus.org]
1.6 RCVD_IN_BRBL_LASTEXT RBL: No description available.
[222.66.83.44 listed in bb.barracudacentral.org]
0.0 SPF_HELO_FAIL SPF: HELO does not match SPF record (fail)
[SPF failed: Please see http://www.openspf.org/Why?s=helo;id=maven.apache.org;ip=222.66.83.44;r=mx1-us-east.apache.org]
0.9 SPF_FAIL SPF: sender does not match SPF record (fail)
[SPF failed: Please see http://www.openspf.org/Why?s=mfrom;id=mailer-daemon%40maven.apache.org;ip=222.66.83.44;r=mx1-us-east.apache.org]
2.0 BASE64_LENGTH_79_INF BODY: base64 encoded email part uses line length
greater than 79 characters
2.6 BASE64_LENGTH_78_79 BODY: No description available.
0.0 AXB_XMAILER_MIMEOLE_OL_024C2 Yet another X header trait
0.1 MISSING_MID Missing Message-Id: header
3.1 DOS_OE_TO_MX Delivered direct to MX with OE headers
0.0 TO_EQ_FM_DOM_SPF_FAIL To domain == From domain and external SPF
failed
2.5 TO_NO_BRKTS_MSFT To: misformatted and supposed Microsoft tool
The original message was not completely plain text, and may be unsafe to
open with some email clients; in particular, it may contain a virus,
or confirm that your address can receive spam. If you wish to view
it, it may be safer to save it to a file and open it with an editor.