Hastymail2

Hastymail2 is an Open Source IMAP webmail client written in PHP. Our focus is compliance, usability, security, and speed.

Hastymail 2

avatar
"Maximum read length exceded, the message was truncated"

First (small) problem:  Spelling error:  exceded should be exceeded.

Main problem:  How do I fix this error?

There's also a "Fatal error.  Maximum execution time of 30 seconds exceeded [spelled right! -ed] in /var/www/html/hastymail2_beta_3/lib/htmlfilter.inc on line 312."

The email in question is a weekly email I get from a local computer store, listing their weekly specials.  It's usually a long list, with small graphics for many items.  Maybe a 600K email, on average?

Hastymail 1 didn't have a problem with these.

Reply /Quote
avatar
Re: "Maximum read length exceded, the message was truncated"

Thanks for the feedback. I will correct the spelling error. As for the other 2 issues:

The maximum read length is set in the imap class and is intended to avoid causing an error on messages that are too long to display via a web interface (Most browsers will choke on too much HTML).  I can however move this setting into the confg file so that it can be adjusted on a site basis which will allow you to set it to a higher value for your environment.

The fatal error you are getting is from PHP and is happening because its an HTML message and needs to be sanitized in order to be safely viewed. hm2 uses the same filter as hm1 so I am surprised that there is a difference. If you could send me a copy of the message in question that would help track down the situation. You can send it to jason@hastymail.org.

Thanks again for the feedback,

Jason

Reply /Quote
avatar
This might help

I just sent the email to you so you could check it.  I mentioned it in the email, but forgot to in my original request, that HM1 doesn't display *all* of the email in question.  It truncates it as well, after some number of screenfuls.  I never get an error message though, HM1 just does the truncation and shows me what it can.  I suppose it's possible that it's getting to the same state though.

So it's possible that the *displaying* of the message is what's failing, for some reason the HTML filter is allowing display of what it's parsed up to the truncation point in HM1, but in HM2 when it fails it cans the HTML parsing and stops *all* display?

Just thinking out loud.  Hope it helps!

 

Reply /Quote


 SourceForge.net Logo