Project

General

Profile

Bug #50027

Spam Assassin gives a score to Outlook and SWA emails marked as 'important' or 'urgent'.

Added by Richard Hall over 4 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Richard Hall
Category:
Scalix Server
Target version:
Start date:
10/21/2015
Due date:
10/21/2015
% Done:

100%

Estimated time:
Operation System:
--

Description

Outlook and SWA emails marked as 'important' or 'urgent' are given a positive score by Spam Assassin indicating that the email may be spam.
Originally reported some time ago:
http://old.bugzilla.scalix.com/show_bug.cgi?id=14920

The issue here is that if the x-msmail-priority field is used then the x-mimeole header field should also be present (Scalix does not generate x-mimeole header). If not both present then Spam Assassin is unhappy: "This suggests that the sender is using badly-written mailout software, rather than a genuine Microsoft email program.":
https://wiki.apache.org/spamassassin/Rules/MISSING_MIMEOLE

Scalix should generate a consistent set of internet header lines when a message is marked as 'important'.

History

#1

Updated by Richard Hall over 4 years ago

For this specific problem I think that the Scalix server should stop generating the X-MSMail-Priority header line (rather than adding the X-MimeOLE line). I believe the X-msmail-priority can be safely omitted as priority, x-priority and importance lines are also currently added when the user selects "high priority" or "important" for an outgoing message.

I was going to add a separate bug for SWA, but the server actually rewrites the internet header lines before the message leaves Scalix even if submitted by SWA.

Here's an example of the header line submitted by SWA:
------------------------------------------------------
.
.
Date: Mon, 28 Jul 2014 06:32:37 0400 (EDT)
From: <>
To: <>
Message-ID: <>
Subject: SWA msg: Importance - High
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="---
=_Part_2_1594851800.1406543557043"
X-Mailer: Scalix 12.1.0.14474
X-MSMail-Priority: high
Importance: high
.
.

and what is actually sent by Scalix:
------------------------------------
.
.
Date: Mon, 28 Jul 2014 06:32:37 -0400
From: Richard Hall <>
To: <>
Message-ID: <>
Subject: SWA msg: Importance - High
Importance: High
Priority: Urgent
X-MSMail-Priority: High
X-Priority: 1
x-scalix-Hops: 1
X-Mailer: Scalix 12.1.0.14474
.

And her's an example of the header lines for a msg fro MAPI connector:
----------------------------------------------------------------------
.
.
From: Richard Hall <>
To: "r.m.hall" <>
Message-ID: <H000009200168491.1406543081.mail.scalix.com@MHS>
Subject: OL msg - high importance
Importance: High
Priority: Urgent
X-MSMail-Priority: High
X-Priority: 1
x-scalix-Hops: 1
.

#2

Updated by Danny T over 4 years ago

Reassign.

#3

Updated by Richard Hall over 4 years ago

Change is to stop adding X-MSMail-Priority header for urgent/important and non-rgent/non-important messages.
If the message being processed already has a X-msmail-priority header then this will be propagated.

Bluenose (12.2) change:

svn commit

Sending msl_readcont.c
Sending msl_readqmsg.c
Transmitting file data ..
Committed revision 14613.

trunk:

svn commit

Sending msl_readcont.c
Sending msl_readqmsg.c
Transmitting file data ..
Committed revision 14614.

#4

Updated by Alexey Bobyr over 4 years ago

removed setting X-MSMail-Priority header in SWA

#5

Updated by Richard Hall over 4 years ago

Marking as 'resolved/fixed'. These changes are in the Scalix 12.5 release.

#6

Updated by Volodymyr Tomash over 4 years ago

  • Due date set to 10/21/2015
  • Status changed from Answered to Resolved
  • % Done changed from 0 to 100
#7

Updated by Volodymyr Tomash over 4 years ago

  • Subject changed from https://bugzilla.scalix.com/show_bug.cgi?id=50027 to Spam Assassin gives a score to Outlook and SWA emails marked as 'important' or 'urgent'.

Also available in: Atom PDF