Hi,

if anybody who is technically responsible for the mailing list reads
this, please have a look at the raw outgoing articles.

Almost all of them are classified as possible spam by your spam
detection software for similar reasons to this one:

  > 0.4 MIME_HTML_MOSTLY       BODY: Multipart message mostly text/html MIME
  > 0.0 HTML_MESSAGE           BODY: HTML included in message
  > 1.0 HTML_FONT_FACE_BAD     BODY: HTML font face is not a word
  > 0.8 BAYES_50               BODY: Bayes spam probability is 40 to 60%
  >                            [score: 0.5000]
  > 0.8 RDNS_NONE              Delivered to internal network by a host with no 
rDNS

They also have a strange structure and two X-Spam_report headers from
cheetara.wso2.com (cf. below).

Thank you


Kambiz

Kambiz Darabi
-- 
m-creations gmbh
Acker 2
55116 Mainz
Germany

W: http://www.m-creations.com
E: dar...@m-creations.com
T: +49 6131 6224417
F: +49 6131 6224418
--
Registered Office: Mainz, HRB Mainz 7382
Managing Directors: Frank Pacholak, Kambiz Darabi



X-Spam_report: Spam detection software,
        running on the system "cheetara.wso2.com", has
        identified this incoming email as possible spam. The original message
        has been attached to this so you can view it (if it isn't spam) or
        label similar future email.  If you have any questions, see
        @@CONTACT_ADDRESS@@ for details. Content preview:  Hi,
        I'm really sorry guys. Found one problem related to the
...

X-Spam_report: Spam detection software, running on the system 
"cheetara.wso2.com", has
 identified this incoming email as possible spam.  The original message
 has been attached to this so you can view it (if it isn't spam) or label
 similar future email.  If you have any questions, see
 @@CONTACT_ADDRESS@@ for details. 
 Content preview:  Hi, I'm really sorry guys. Found one problem related to the
    andes-client.jar. Seems it doesn't pack "org.apache.mina.filter.SSLFilter"
    class though the previous andes-client jar packed it. Hence I'm getting an
    CNF in the Consumer (ESB) side. Error happens when the jms receiving proxy
    is being deployed. [...]  
 Content analysis details:   (2.0 points, 4.8 required) 
  pts rule name              description
 ---- ---------------------- --------------------------------------------------
 -0.0 SPF_PASS               SPF: sender matches SPF record
  0.0 WEIRD_PORT             URI: Uses non-standard port number for HTTP
  0.4 MIME_HTML_MOSTLY       BODY: Multipart message mostly text/html MIME
  0.0 HTML_MESSAGE           BODY: HTML included in message
  0.8 BAYES_50               BODY: Bayes spam probability is 40 to 60%
                             [score: 0.4999]
  0.8 RDNS_NONE              Delivered to internal network by a host with no 
rDNS
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to