Mark Martinec wrote:
On Wednesday February 10 2010 10:45:37 Mike Cardwell wrote:
On 10/02/2010 00:31, Kai Schaetzl wrote:
MISSING_SUBJECT,
Now, why the message that SA is creating is getting TWO Subject: lines
is a different question.
because SA thinks it's got no subject, so it adds one as it is instructed
to tag the subject. Obviously, it wants to see at least a whitespace
after the colon to accept it as a header.
I don't think so. At least, in my tests here, v3.3.0 doesn't. Both of
these commands lead to SpamAssassin outputting a single "Subject:
*****SPAM*****" header:
echo -ne "Subject: \nX-Foo: bar\n\nviagra CIALIS\n"|spamassassin
echo -ne "Subject:\nX-Foo: bar\n\nviagra CIALIS\n"|spamassassin
Indeed, the bug was fixed with v3.3.0 (Bug 6016).
Kai Schaetzl wrote:
I did some research on this matter some
time ago and if I remember correctly the latest RFCs (5322, maybe 2822)
indeed require a whitespace while older RFCs (822) were not 100% clear
about this.
This is incorrect. A space is not required after a colon.
Both the RFC 5322 and RFC 2822 are perfectly clear on this.
Ted Mittelstaedt wrote:
So Thunderbird displays the last Subject line header it comes across.
Is that incorrect behaviour for an MUA?
I think it is. Setting aside the question of whether they are supposed
to be there or not, the purpose of an MUA is to make it easier for
the user to interact with a mail message. Multiple Subject: lines
can contain multiple amounts of information, and only displaying the
last Subject line is denying the user information that they are
supposed to be able to see see.
The RFC 5322 (and RFC 2822) require that a Subject header field
appears zero or one time. Multiple Subject header fields are not allowed.
A MUA can do whatever it pleases with syntactically invalid mail messages:
garbage-in, garbage-out.
Mark
The intent of the people who wrote the MUA under question was to assist
users to read mail, it was NOT to advance an agenda on the
Internet. If you want to use MUA's which attempt to enforce agendas
then there are plenty of those out there - you can start with Outlook.
I would assume that by definition any MUA written to help users has
a flaw in it if it does something that makes it harder for the user
to read mail. That is why I consider this incorrect behavior. An
MUA that's goal was to assist should at least make an effort to notify
the user that there's a problem with the message. And as a matter
of fact, Thunderbird DOES do this quite a lot with other types of errors
on e-mail messages.
Ted
