>After Thomas' last, it might not be so easy... maybe because there is no
>easy way to distinguish 'Subject' in the header. I'd think the parser
>could just count the bytes and when it reaches the max, skip to the body
>checks... but ianap, so may be totally off base...
It is realy easy to find the 'Subject'.
What has to be done to find it:
1. - find a line that begins with 'subject:'
2. - read all characters until the next header tag is found
that's all - you think - oooohhhhh no
3. unwrap all subject lines in to a single line removing all '\t' and ' '
in front of all lines
4. MIME-decode the subject
that's all - you think - ... - assp is doing all stuff in UTF-8
5. encode the subject to UTF-8
Now we know the contents, length - simply all about the subject. Any of
the steps above could make problems, if someone is able to produce very
dangerous header lines.
This is done the same way with all header tags and each of them or
combinations of them could lead in to a crash if someone knows how to do.
The subject was only the possible reason in this case.
Charles, throw away your thinking about the 'subject' - think big. Maybe
any other part (or parts) of the header caused assp to crash, nobody knows
- but it was realy easy to detect this single mail by a single line of the
subject - this was the part, that was the same every time and it was easy
to see.
Yes this subject was long - but compared to the body of an email it is
short - and we parse complete emails with attachments to scan the parts
for viruses and spam bombs - I don't think the length of the subject was
the reason - but this was the significant attribute of this mail for a
human.
Remember back (I think a year or so) - there where mails from
'emailserver3.com' - nothing significant to see - not even long - just
normal mails - and they caused assp to crash without any hint. Just luck
for us - the mails where all spam every time. So we could block the mails
by the domain name at the 'mail from:' command.
Thomas
Von: Charles Marcus <[email protected]>
An: [email protected]
Datum: 07.10.2010 17:10
Betreff: Re: [Assp-test] Antwort: Re: mail with too long subject
kills assp
On 2010-10-07 10:30 AM, K Post wrote:
> I think what we're suggesting is logical and I'm sure Thomas will too.
It's
> just a question of finding the time to code it!
After Thomas' last, it might not be so easy... maybe because there is no
easy way to distinguish 'Subject' in the header. I'd think the parser
could just count the bytes and when it reaches the max, skip to the body
checks... but ianap, so may be totally off base...
--
Best regards,
Charles
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Assp-test mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-test
DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally
privileged and protected in law and are intended solely for the use of the
individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no
known virus in this email!
*******************************************************
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Assp-test mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-test