I was simply replying to a gentlemen's post John. Read the thread.
HE asked if I found out whether Declude was the CAUSE of the problem or I switched to another AV product. > > Did you (or someone else) find a solution in the meantime, or did > > you > just > > switch to another AV ? I said it was NOT Declude. Hence my post. He specifically mentioned Peter Verzoni. I worked on that specific system. Again my reply. There was no need for further banter. He wanted to know if it was resolved. I agree Imail does not cooperate well with Intel NICs at extreme traffic. Your answer was GET A SERVER NIC. That is not the solution. The solution is Imail should fix their bug or use a NON intel NIC. Better yet you must use 3Com Nics to be sure since that seems to be all Imail tests. A NIC that we have found is prone to many other issues and is no longer the market leader. Back in 98-99 when Imail started it was and we all used them. No longer true today as Dell, HP and most white box servers use Intel NICs. But all that is irrelevant. The only issue I complained about was you were rude. Don't accept it, fine. But enjoy the world you create with responses like that. You must live with it, we must only read your posts. Deny Deny Deny .. Be like Bush....... To everyone else Again I apologize and promise I stop here no matter what the response (snappy or otherwise <G>)... Except Declude related... Regards Doug Doug -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Tolmachoff (Lists) Sent: Saturday, June 12, 2004 6:05 PM To: [EMAIL PROTECTED] Subject: FW: [Declude.Virus] BSOD and IMail-Server reboot Just realized this was originally posted on the Declude virus list, even though it has nothing to do with Declude Virus, and the person should have posted on the Imail list, since it is an Imail issue and a search of the Imail list archives shows this has been discussed many times. > The imail forum has not one post regarding an INTEL SERVER Board and > on board NICs. I recall some conversations about desktop boards but > none regarding SERVER BOARDs. I do not remember whether the board was a Server board or workstation board being part of the discussion on past problems. It was the Intel OB NIC that was discussed, and a search of the Imail archives shows 269 hits for "Intel OB NIC". > Furthermore what logic would you as a Networking Professional give to > an SMTP server running on the same platform and pushing sustained > traffic of three times that of the IMAIL server yet never causing any > issues and certainly not creating a BSOD. This is something I am very > interested in hearing. I am not an Ipswitch technician, so I have no idea of why this occurs, I just know from many others posting such that it does! > I have been building systems and maintaining data centers now for 16 years. Goody for you. Now back to the issue at hand. > I have brought this exact issue to Intel's and Microsoft's attention > and neither see any reason for the NIC to be the root cause of the issue. > > Microsoft has read the BSOD dumps and reports IMAIL as the culprit. Then take the next step and share that information with Ipswitch. From all the posts about Intel OB NICs and Imail over the years, it is my opinion there is a real problem with Imail and Intel OB NICs. To date, most have fixed the problem by using a server grade 3Com NIC and disabling the Intel OB NIC. If you have the time and resources to further pursue this issue with Ipswitch, many Imail admins will thank you. > This type of comment from you has little to no value. You act like > you are > participating in a forum but clearly you are using the forum simply > for your > own end. Sure it does. Just because you do not like the work around, and would rather spend time on finding the cause of the problem in hopes that Ipswitch will finally fix it, does not mean that my advice has no value. BTW, how does my posting advice on a subject that comes up again and again over time equal my using the forum for my own end? John Tolmachoff Engineer/Consultant/Owner eServices For You > > > ----- Original Message ----- > From: "John Tolmachoff (Lists)" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Friday, June 11, 2004 3:11 PM > Subject: RE: [Declude.Virus] BSOD and IMail-Server reboot > > > There has been much discussion concerning Intel OB NICs and Imail. > > Search the archives. > > Bottom line, get a solid Server designated NIC. > > John Tolmachoff > Engineer/Consultant/Owner > eServices For You > > > -----Original Message----- > > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > > On Behalf Of Douglas Cohn > > Sent: Friday, June 11, 2004 11:32 AM > > To: [EMAIL PROTECTED] > > Subject: RE: [Declude.Virus] BSOD and IMail-Server reboot > > > > This problem has not gone away. It occurs with very high traffic > > only > and > > is not related to declude. That is we tested iot without declude > > and > it > > still Blue Screens when there is extremely high traffic. > > > > Imail claims that when the server has extremely high traffic you > > need > to > use > > a SERVER NIC in the machine. One which does NOT offload processing > > to > the > > server but has it's own processor onboard the NIC. > > > > This has some logic but if true why on servers running only SMTP > passing > > double the amount of sustained traffic do we not also have the issue. > > > > Using Intel Based SE7501WV2 baseboards with on board nics on > > sevweral servers. Only Imail servers Blue Screen. We set them to > > auto reboot > and > it > > only happens in extremely high traffic times. > > > > DC > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of Uwe Degenhardt > > Sent: Thursday, June 10, 2004 5:05 AM > > To: [EMAIL PROTECTED] > > Subject: [Declude.Virus] BSOD and IMail-Server reboot > > > > Hi list and especially > > Peter Verzoni. > > > > Peter you mentioned a while ago > > the following problems you had on one of your servers: > > > > http://www.mail-archive.com/[EMAIL PROTECTED]/msg06418.html > > > > Did you (or someone else) find a solution in the meantime, or did > > you > just > > switch to another AV ? > > > > Would be great to get the link where you posted the info to F-Prot > > as > well. > > > > Thank you. > > > > Uwe > > > > --- > > [This E-mail was scanned for viruses by Declude Virus > > (http://www.declude.com)] > > > > --- > > This E-mail came from the Declude.Virus mailing list. To > > unsubscribe, > just > > send an E-mail to [EMAIL PROTECTED], and > > type "unsubscribe Declude.Virus". The archives can be found > > at http://www.mail-archive.com. > > --- > > [This E-mail scanned for viruses by Declude Virus] > > > > > > --- > > [This E-mail 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.Virus mailing list. To > > unsubscribe, just send an E-mail to [EMAIL PROTECTED], and > > type "unsubscribe Declude.Virus". 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.Virus mailing list. To unsubscribe, > just send an E-mail to [EMAIL PROTECTED], and > type "unsubscribe Declude.Virus". 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.Virus mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.Virus". The archives can be found at http://www.mail-archive.com. --- [This E-mail scanned for viruses by Declude Virus] --- [This E-mail 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.Virus mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.Virus". The archives can be found at http://www.mail-archive.com.
