Re: RE: ASK confirmation code, wrapped lines etc.

On Sun, 18 Jul 2004, Rob Nielson wrote:

> > * Big Emails: What do do with big emails? Do we scan the entire email
> > for the key or just, say, the first 100 lines? Scanning the entire email
> > means more CPU use, which is bad.

> With today's CPU speeds, we're talking about nanoseconds to scan an Email.

I don't agree: I suspect some people are already using ASK on servers,
which may be already tight on power due to a huge number of messages
per second processed. Once you gave some performance to users, you can
never take it back :-)

Moreover, you can imagine some kind of very easy DoS attack, sending
huge messages to some ASK server...


> If, for the odd event, the Email is exessively huge, then just include the
> first 20, 30, 50... or whatever... number of lines.

Preferred.


Even if moving the confirmation code to the body of the message may
seem a better solution in the long term, finding out why the subject
line gets wrapped would fix the issue much sooner. I really feel like
it's ASK's fault here, as I never saw any wrapped subject line before
using ASK. From RFC 2822 <http://www.faqs.org/rfcs/rfc2822.html>
section 2.2.1, I even understand that wrapped subject lines are
"forbidden". I wonder how most mail software would handle such broken
messages; they would probably seldom come to the recipient.

Cheers,

Marc.



-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_idG21&alloc_id040&op=click