Can we talk sometime early today about this? I am not sure you and I are on the same page unless I am miss reading all of these threads. I am 99% sure it is blowing up in HijackGetIp() and 95% sure is it this line...
c = *env.databodystart; To work this out, I really need to speak with you rather than email pls. It would be much faster and I can pick your brain... Thanks r -- -----Original Message----- -- From: [EMAIL PROTECTED] [mailto:Declude.JunkMail- -- [EMAIL PROTECTED] On Behalf Of R. Scott Perry -- Sent: Friday, February 11, 2005 7:43 PM -- To: [email protected] -- Subject: RE: [Declude.JunkMail] Declude 2.0 -> crash -- -- -- >We've gone back to 1.82 as well. -- > -- >We'll wait again until 2.0 is proven stable. Declude hasn't been like -- what -- >has been in the past. -- -- Just to let people know a bit about this -- the source of the crash was -- identified pretty quickly. And a change could have been made almost as -- quickly to prevent the crash. -- -- However, in this case, the D*.SMD files (the ones containing the E-mail -- body) were disappearing -- a situation that should (in theory) never -- happen. There are causes for this (such as an on-access virus scanner), -- but they aren't very common. So my advice was that rather than just fix -- the crash, further investigation should be done to determine why those -- files were disappearing. That way, we can have a new release that fixes -- the crash without running the risk of people noticing a new problem (that -- they weren't seeing simply because the crash occurred). -- -- With software, there are often minor issues that come up that don't get -- addressed because they seem so minor or aren't being reported. Yet many -- times when this happens, a bigger bug appears later that would have been -- fixed if the minor issue had been dealt with right away. I've seen this -- a -- number of times with software I've worked on that nobody but myself -- runs. One out of a hundred times, something that isn't quite right will -- appear. The thought process is "Gee, it would be a good idea to look -- into -- that to see why it happened, but it would be a lot of work tracking it -- down; I'll deal with that later." With a program that only I run, that's -- fine. But for software that 1,000s of people are running, most of whom -- consider E-mail to be mission critical, I think it is best to wait and -- have -- it done right. -- -- And, to take credit away from where it should be taken (or whatever the -- opposite of "giving credit where it is due" is), the crash is occurring -- in -- code that I wrote. -- -- -Scott -- --- -- Declude JunkMail: The advanced anti-spam solution for IMail mailservers -- since 2000. -- Declude Virus: Ultra reliable virus detection and the leader in -- mailserver -- vulnerability detection. -- Find out what you've been missing: Ask for a free 30-day evaluation. -- -- --- -- [This E-mail was scanned for viruses by Declude Virus -- (http://www.declude.com)] -- -- --- -- This E-mail came from the Declude.JunkMail mailing list. To -- unsubscribe, just send an E-mail to [EMAIL PROTECTED], and -- type "unsubscribe Declude.JunkMail". The archives can be found -- at http://www.mail-archive.com. --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
