Fabrice, I do not have Delphi available at this moment, so could you test
the code below to see if it is treated as spam by SpamAssassin?
Checking against SpamAssassin is required, but checking against most common
mail readers (either standalone mail client or webmail applications) is also
mandatory.
--
francois.pie...@overbyte.be
The author of the freeware multi-tier middleware MidWare
The author of the freeware Internet Component Suite (ICS)
http://www.overbyte.be
----- Original Message -----
From: "DZ-Jay" <d...@caribe.net>
To: "ICS support mailing" <twsocket@elists.org>
Sent: Friday, September 03, 2010 11:03 PM
Subject: Re: [twsocket] TSmtpCli and bad spam score
On 09/03/2010 15:09, Arno Garrels wrote:
Does that mean that you or DZ-Jay will check in this change?
I'm currently not up to date with the SMTP RFCs.
But I wonder why "Priority" and "X-MSMail-Priority" are no
longer required?
Arno,
I did a little more research (I haven't kept up with these RFCs for a
while) and I found the following:
The "Priority" header is defined in RFC #2156 (MIXER) for MIME headers,
which extends RFC #822. However, it appears that nobody is using that
header.
There was a time, as you may know, that most every mail client implemented
their own set of "standards" for things like Priority and Return Receipt,
and they were all different. Nowadays, these have standardize a bit, but
they are still conventions, not "standards". This is the reason why ICS
and other libraries and applications typically include more than one
variation of a header, to please the most popular clients out there and
their idiosyncrasies.
The "X-MSMail-Priority" header was introduced in old versions of MS
Outlook Express client, but it has been superseded by "X-Priority" since
then. It was always MS-specific and non-standard.
"X-Priority" was originally introduced by Eudora in the 1980s, but since
it was so popular, many other clients followed suit. (The "X-" prefix
indicates that it is a custom field.)
RFC #2156 seems to try to formalize this with "Priority" as a bona fide
header, but perhaps it came too late and nobody paid attention.
I guess we should include it too, for the sake of following standards.
After all, it is the only one of those which appears on an actual RFC. And
if SpamAssassin treats it as "spam", well then it is SpamAssassin who is
wrong.
Fabrice, I do not have Delphi available at this moment, so could you test
the code below to see if it is treated as spam by SpamAssassin?
procedure TCustomSmtpClient.Data;
...
if FHdrPriority < smtpPriorityNormal then begin
FHdrLines.Add('Importance: high');
FHdrLines.Add('Priority: urgent');
FHdrLines.Add('X-Priority: 1');
end
{
else if FHdrPriority = smtpPriorityNormal then begin
FHdrLines.Add('Importance: normal');
FHdrLines.Add('Priority: normal');
FHdrLines.Add('X-Priority: 3');
end
}
else begin
FHdrLines.Add('Importance: low');
FHdrLines.Add('Priority: non-urgent');
FHdrLines.Add('X-Priority: 5');
end;
...
Thanks,
-dZ.
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
