[ 
https://issues.apache.org/jira/browse/JAMES-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Norman Maurer updated JAMES-1010:
---------------------------------

    Fix Version/s: 3.0-M1

Need to get fixed if its still there..

> MSGID_FROM_MTA_HEADER
> ---------------------
>
>                 Key: JAMES-1010
>                 URL: https://issues.apache.org/jira/browse/JAMES-1010
>             Project: JAMES Server
>          Issue Type: Bug
>          Components: James Core
>    Affects Versions: 2.3.2
>         Environment: Ubuntu Linux 9.0.3
>            Reporter: Gavin Chiu
>             Fix For: 3.0-M1
>
>
> Hi, 
> I thought this was fixed from 
> https://issues.apache.org/jira/browse/JAMES-875, but:
> I have the latest JAMES 2.3.2 running and I am getting this error in the 
> Barracuda header report from all the email I send from this JAMES mail 
> server: 
> X-Barracuda-Spam-Score: 1.50 
> X-Barracuda-Spam-Status: No, SCORE=1.50 using global scores of TAG_LEVEL=3.5 
> QUARANTINE_LEVEL=1000.0 KILL_LEVEL=5.0 tests=DKIM_SIGNED, DKIM_VERIFIED, 
> HTML_MESSAGE, MSGID_FROM_MTA_HEADER, MSGID_FROM_MTA_HEADER_2 
> X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.2.30982 
> Rule breakdown below 
> pts rule name description 
> ---- ---------------------- 
> -------------------------------------------------- 
> -0.00 DKIM_VERIFIED Domain Keys Identified Mail: signature passes 
> verification 
> 0.00 DKIM_SIGNED Domain Keys Identified Mail: message has a signature 
> 0.00 HTML_MESSAGE BODY: HTML included in message 
> 0.00 MSGID_FROM_MTA_HEADER Message-Id was added by a relay 
> 1.50 MSGID_FROM_MTA_HEADER_2 Message-Id was added by a relay 
> Have I implement the new version incorrectly? Please advise. 
> Thanks 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to