RE: [Declude.JunkMail] Declude 2.0 -> crash
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: Declude.JunkMail@declude.com -- 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.
RE: [Declude.JunkMail] Declude 2.0 -> crash
> One other thing that also still concerns me is the new licensing > scheme. It seems like this might have been one of the issues, any while > you might be confident that it is working fine now and is supportable, I > really want to know how it works from a flow-chart perspective. For > instance, I don't want to run into issues during an outage where I am > recovering from a backup onto a different server only to find that > things aren't working because of some licensing mechanism. I know that > this might trip Windows Server 2003 to require re-register with them, > but it will work for 30 days without that. I have no idea if Declude > needs to be immediately re-registered, how you might choose to block > such things, and otherwise what ever else I might have to look out for > such as server outages on your end. A recent experience of my own with > BackupExec doubled the time of an outage because of a simple default > setting in their software that didn't allow me to catalog imported > backup media properly without changing. Something as simple as that is > such a big deal that I decided that I can no longer trust BackupExec as > a disaster recovery solution since this is definitely not the only quirk > that I have come across and I don't have the time to be any more > proactive in identifying these things ahead of time. I also really, > really hope that you created a backdoor registration work-around so that > in the event of something happening to Declude that this information > could be distributed in order for us to continue using the software. > Even TiVo is reported to have a backdoor that is closely held and so far > secure that they can distribute to keep their units from becoming > completely useless without the required updates (otherwise they could > only be used to play previously recorded content). FYI, while I was one of the ones having licensing issues, I will clearly state that the software kept working, with the exception of what I called 2.0_releaseB, which apparently had a major bug. That means that even though the Declude license check was having problems, declude.exe was still firing and processing mail. In fact, I will state something here: On one of the servers I actively work on, I went by knowledge that the SA was up to date, in that it should have been renewed in September of last year. I went and installed versions 2.0.x on there and it was working, even though the license was not verifying. In working with Declude on the problem, Barry gave me a call to let me know that there was no SA for that server. Turns out the SA was renewed, but the person that did it put down different information and it did not match. That has now been corrected. Anyway, point is as far as Declude was concerned at the time, there was no SA and no legal way version 2.0.x should have been used on that server, yet it was working. In other words, the program will work, but Declude will actively know that something is running that should not be and they can take action. John Tolmachoff Engineer/Consultant/Owner eServices For You --- [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.
Re: [Declude.JunkMail] Declude 2.0 -> crash
Scott, Barry, et al., Just a few comments. First, I am very happy to see the return of the minor version release. While this might not have been intentional, it is a welcome site since that means that smaller issues are being addressed outside of the more major releases. I hope that following the bumps in the road on the way to getting a broadly stable 2.0.x release out the door that this can continue for the purpose of fixing bugs (leaving new non-emergency functionality for major version releases. I also greatly appreciate knowing what the issues are. This was something that was nice about the old way that Declude worked. While Scott wasn't necessarily forthcoming with documentation and disclosure, with prodding and by communicating with others on this list, that information seemed to surface when it was vital to know. That has changed. It would still be nice to know about all of the issues in slightly more detail. The release notes for IMail for instance are a good example of this. I learn a lot about the issues with IMail by reading them and it allows me to be more proactive in managing my software. Even if they don't affect me, it does disclose information that may help me down the line. As far as I am concerned, knowing about fixed bugs, even minor ones, is as important as knowing about new features. I can understand that from a marketing perspective new features are perceived as the most important by non-administrators, but truth be told, many of us are more concerned about avoiding and fixing bugs so marketing that information to us is just as important if not more. It would also be nice to know what the major changes were even if they are supposed to be transparent. For instance, this release obviously re-worked some facets of the software, and I would really like to know how extensive that work was so that I can better determine when I am comfortable in upgrading. Personally, I'm still not comfortable, and I probably won't be at least until there is a determination as to what was deleting the files on Andy's system along with the memory leak obviously being addressed that was exposed by this condition. One other thing that also still concerns me is the new licensing scheme. It seems like this might have been one of the issues, any while you might be confident that it is working fine now and is supportable, I really want to know how it works from a flow-chart perspective. For instance, I don't want to run into issues during an outage where I am recovering from a backup onto a different server only to find that things aren't working because of some licensing mechanism. I know that this might trip Windows Server 2003 to require re-register with them, but it will work for 30 days without that. I have no idea if Declude needs to be immediately re-registered, how you might choose to block such things, and otherwise what ever else I might have to look out for such as server outages on your end. A recent experience of my own with BackupExec doubled the time of an outage because of a simple default setting in their software that didn't allow me to catalog imported backup media properly without changing. Something as simple as that is such a big deal that I decided that I can no longer trust BackupExec as a disaster recovery solution since this is definitely not the only quirk that I have come across and I don't have the time to be any more proactive in identifying these things ahead of time. I also really, really hope that you created a backdoor registration work-around so that in the event of something happening to Declude that this information could be distributed in order for us to continue using the software. Even TiVo is reported to have a backdoor that is closely held and so far secure that they can distribute to keep their units from becoming completely useless without the required updates (otherwise they could only be used to play previously recorded content). So please don't be fearful in releasing minor revisions, in fact this is greatly desired and a sign of what I would consider to be responsible development of an app that is involved in a highly important service (E-mail). And please do start more fully documenting every release by identifying all changes, whether or not they were intended to be transparent. Thanks, Matt R. Scott Perry wrote: 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 t
RE: [Declude.JunkMail] Declude 2.0 -> crash
Yes, it's occurring with 2.04. I agree with Scott in principle - it is better to determine the underlying cause of a problem, than to quick-fix the symptom. Too often have I seen short-term solutions cover up big issues that ended up having a much bigger impact later. Best Regards Andy Schmidt Phone: +1 201 934-3414 x20 (Business) Fax:+1 201 934-9206 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Darin Cox Sent: Saturday, February 12, 2005 12:40 AM To: Declude.JunkMail@declude.com Subject: Re: [Declude.JunkMail] Declude 2.0 -> crash Hi Scott, Just to clarify...is this problem occurring with 2.04? Just wanted to check before I updated. Thanks, Darin. --- [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.
Re: [Declude.JunkMail] Declude 2.0 -> crash
Hi Scott, Just to clarify...is this problem occurring with 2.04? Just wanted to check before I updated. Thanks, Darin. - Original Message - From: "R. Scott Perry" <[EMAIL PROTECTED]> To: Sent: Friday, February 11, 2005 7:43 PM 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.
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.
RE: [Declude.JunkMail] Declude 2.0 -> crash
Good reminder for me - Nothing will ever be like it was. Software development is an insane business. One of the reasons I got out of it. I've value the support I get from Declude and Sniffer folks. I would rather pay these guys money to help me fight the bad guys by listening and trying to provide some code that works in the end versus paying a bazillion bucks for Microsoft products that they think will save me. After the last couple years I've learned to be able to back out an upgrade within a few minutes. I always expect something to happen. Not all the time mind you but right now I know the company needs some more time to settle down. Keep the heat on since I have no desire to rob a bank to replace the support and functionality these products give me. And gotta add the list participants are equally excellent assets to the battle. Gotta run ... Imail web service just went down. Michael Jaworski Puget Sound Network, Inc. (206) 217-0400 (800) 599-9485 --- [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.
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. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andy Schmidt Sent: Saturday, February 12, 2005 12:12 AM To: Declude.JunkMail@declude.com Subject: RE: [Declude.JunkMail] Declude 2.0 -> crash Well, about an hour ago they had to leave for the weekend. I watched my system a little longer - and eventually seeing a crash every few minutes (due to high load), I had to go back to 1.82. Best Regards Andy -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Tolmachoff (Lists) Sent: Friday, February 11, 2005 11:30 AM To: Declude.JunkMail@declude.com Subject: RE: [Declude.JunkMail] Declude 2.0 -> crash Andy, just for kicks, can you exclude any scanning of smd, _md, ~md files and such. John Tolmachoff Engineer/Consultant/Owner eServices For You --- [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.
RE: [Declude.JunkMail] Declude 2.0 -> crash
Well, about an hour ago they had to leave for the weekend. I watched my system a little longer - and eventually seeing a crash every few minutes (due to high load), I had to go back to 1.82. Best Regards Andy -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Tolmachoff (Lists) Sent: Friday, February 11, 2005 11:30 AM To: Declude.JunkMail@declude.com Subject: RE: [Declude.JunkMail] Declude 2.0 -> crash Andy, just for kicks, can you exclude any scanning of smd, _md, ~md files and such. John Tolmachoff Engineer/Consultant/Owner eServices For You --- [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.
RE: [Declude.JunkMail] Declude 2.0 -> crash
Andy, just for kicks, can you exclude any scanning of smd, _md, ~md files and such. John Tolmachoff Engineer/Consultant/Owner eServices For You > -Original Message- > From: [EMAIL PROTECTED] [mailto:Declude.JunkMail- > [EMAIL PROTECTED] On Behalf Of Andy Schmidt > Sent: Friday, February 11, 2005 6:23 AM > To: Declude.JunkMail@declude.com > Subject: RE: [Declude.JunkMail] Declude 2.0 -> crash > > Hi, > > Nope, this is 2.0.4 - just checked my root, this was not the only > occurrence. They contacted me, so I'm in the process to collect logs and > configs to send it off. > > My Declude.GP1 states: > > (Error 5 at 414c99 v2.0.4) > (attempt to read at 0) > (00414C99 0012FF80 (0002 007A0AB0) D:\IMAIL\Declude.exe) > (0042D781 0012FFC0 ( 00135F6C) D:\IMAIL\Declude.exe) > (7C59893D 0012FFF0 (0042D6CD ) D:\WINNT\system32\KERNEL32.dll) > Qb23f0f4c05a2 Couldn't open headers datafile (are you running an > on-access virus scanner?) > > Yes - I've always had an 'on-access scanner' - but I have the Imail\Spool > tree excluded. > > Best Regards > Andy Schmidt > > Phone: +1 201 934-3414 x20 (Business) > Fax:+1 201 934-9206 > > > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Franco Celli > Sent: Friday, February 11, 2005 08:28 AM > To: Declude.JunkMail@declude.com > Subject: Re: [Declude.JunkMail] Declude 2.0 > > > I had the same problem with version 2.0.? (declude executable date = feb. > 1st). > > While no apparent problem with 2.0.4 so far. > > --- > Franco Celli > > > > - Original Message - > From: "Andy Schmidt" <[EMAIL PROTECTED]> > To: > Sent: Friday, February 11, 2005 5:28 AM > Subject: [Declude.JunkMail] Declude 2.0 > > > > Well - I tried... > > > > Minutes after install my mail server became unresponsive - after a few > > minutes, I saw Dr. Watson in the task list - and then found these in > > the root. > > > > Best Regards > > Andy Schmidt > > > > Phone: +1 201 934-3414 x20 (Business) > > Fax:+1 201 934-9206 > > > > > > > > --- > [Quipo ISP - Questa E-mail e' stata controllata dal programma Declude Virus] > [Quipo ISP - This E-mail was scanned for viruses by Declude Virus] > > --- > [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. --- [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.
RE: [Declude.JunkMail] Declude 2.0 -> crash
Hi, Nope, this is 2.0.4 - just checked my root, this was not the only occurrence. They contacted me, so I'm in the process to collect logs and configs to send it off. My Declude.GP1 states: (Error 5 at 414c99 v2.0.4) (attempt to read at 0) (00414C99 0012FF80 (0002 007A0AB0) D:\IMAIL\Declude.exe) (0042D781 0012FFC0 ( 00135F6C) D:\IMAIL\Declude.exe) (7C59893D 0012FFF0 (0042D6CD ) D:\WINNT\system32\KERNEL32.dll) Qb23f0f4c05a2 Couldn't open headers datafile (are you running an on-access virus scanner?) Yes - I've always had an 'on-access scanner' - but I have the Imail\Spool tree excluded. Best Regards Andy Schmidt Phone: +1 201 934-3414 x20 (Business) Fax:+1 201 934-9206 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Franco Celli Sent: Friday, February 11, 2005 08:28 AM To: Declude.JunkMail@declude.com Subject: Re: [Declude.JunkMail] Declude 2.0 I had the same problem with version 2.0.? (declude executable date = feb. 1st). While no apparent problem with 2.0.4 so far. --- Franco Celli - Original Message - From: "Andy Schmidt" <[EMAIL PROTECTED]> To: Sent: Friday, February 11, 2005 5:28 AM Subject: [Declude.JunkMail] Declude 2.0 > Well - I tried... > > Minutes after install my mail server became unresponsive - after a few > minutes, I saw Dr. Watson in the task list - and then found these in > the root. > > Best Regards > Andy Schmidt > > Phone: +1 201 934-3414 x20 (Business) > Fax:+1 201 934-9206 > > > --- [Quipo ISP - Questa E-mail e' stata controllata dal programma Declude Virus] [Quipo ISP - This E-mail was scanned for viruses by Declude Virus] --- [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.
