> > > it seems that md crashes (lock, software failure of reset!) when > > > fetching mails with a very large receiver list... if that happens i > > > have to log into my mailserver via web interface and delete those > > > messages manually... > > > > > any chance to see a fix? is this known or reproducable? > > > > Hm, I thought I fixed that one. Will have to look again. > > i'm not 100% sure if it is related to very long to: or cc: headers. i once > tried that: > > - md crashed when loading such an email > - i started simplemail, fetched that mail and stored it to disk > - i imported it with md2 and it worked ok > maybe importing does behave a little different? maye it is related to > filters as importing does not use filters? > > i'll have a closer look at such an mail and send it to you if this will > happen again. > of course it always are spam-mails which cause trouble.
I've also experienced this problem, but have to admit I'd not tried the import route. This seems to manifest itself in two ways. The first, and most common, way is that the message will start to open and then it will give a recoverable alert (yellow). You can click to okay the alert and it will flick back to MD2 then back to an alert. You can do this maybe two or three times and then it'll guru the machine. The other way, and this seems to be quite rare, is that it'll start to open the message as before, there's a delay and then the machine will guru without the alert. I've seen this with the amount of free memory displayed and the memory seems to get used up pretty quickly. Once you're out of memory it'll guru. While we're on memory issues and bug reports ;-) I've started noticing a few problems in recent months. My copy of MD2 has about 28000 messages stored in about 60 folders and I'm finding that when I reply to a message it'll start accessing the hard drive for maybe 10-15 seconds and start using up memory pretty quickly. If I ever find myself not having enough memory, the machine will freeze and I end up having to reset - the reply is normally saved okay in SPOOL though. I'm finding myself having to reply to mails with no other apps running and also having to close/reopen MD2 to free up memory after finishing my replies. Cleaning out some old mails in SPOOL, emptying trash and doing a cleanup db gives a slight improvement (a few hundred KB). This isn't happening with new messages, which don't make much of a dent in the memory usage, only replies. It *seems* to be caching something as I can usually make further replies to mails quickly and with little extra memory loss (though by this time, I'm down to about 1 MB chip and maybe 500k Fast from 2MB chip and 12-14MB fast). Finally, I also reported a bug a while back which may or may not be related to the issue with large To: or CC: lines. I've noticed a couple of other reports on this problem, but if the To: or CC: lines are particularly large (don't ask why you'd be foolish enough to do this *grin*) MD2 will send the mail to each recipient in a continuous loop until you kill the connection or MD2. Okay, bad netiquette to do that but you shouldn't expect to find yourself spamming people with a few hundred mails... Cheers :-) John -- | // John Chandler Kommunity Systems Limited Company Director | | \X/ Amiga A4000/030 Phoenix Developer Consortium Member | | AmigaOS / QNX RtP / NetBSD / Linux Suite101.com Amiga Editor | __________________________________________________________________ MicroDot-II Mailing List - http://www.vapor.com/md2/ MicroDot-II FAQ: http://faq.vapor.com/md2/ Listserver Help: mailto:[EMAIL PROTECTED]?Subject=HELP Unsubscribe....: mailto:[EMAIL PROTECTED]?Subject=UNSUBSCRIBE
