SV> Correct. To prevent denial-of-service attacks against the RFC 822 SV> parser, the maximum number of parsed MIME entities has a hard upper SV> limit.
SV> Not a bug, but perhaps the maximum upper limit should be raised. You have sunk my http://jidanni.org/comp/spam/spamdealer.html project, at least when I am on the road and must use Dreamhost's squirrelmail which I suppose I must now ask somebody to hack to deal with your hacked RFC822.SIZE, which I'm not sure why you are peering into the message so deeply to find vs. e.g., dovecot. Anyway, from a Debian user's view this deeply laid undocumented except perhaps in the source code landmine is a certain violation of RFCs and... And well why don't you just stop feeding the message in its tracks if the goal is to protect whatever is connected? Anyway, more and more clients will have to be hacked to deal with your hack. Originally I can have Oh, 700 spams headers ordered by score in one message. Now I must have a cronjob set for about when 130 spams should have accumulated, and instead read 5 separate spam reports. Anyway, OK thanks for protecting whatever from whatever. I thought I finally came up with a ideal spam reviewing solution for low bandwidth offline users. But... Dreamhost uses courier-imap. Anyway, go ahead and raise the upper limit. I'll only be back again saying that it's too small. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
