Uploaded image for project: 'James Server'
  1. James Server
  2. JAMES-1010

MSGID_FROM_MTA_HEADER

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.3.2
    • 3.0-M1
    • James Core
    • None
    • Ubuntu Linux 9.0.3

    Description

      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

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            norman Norman Maurer
            gavinchiu Gavin Chiu
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment