I also didn’t just move the old sambar install to the new win2k install. I downloaded the latest production version, installed it, and carefully moved my files from the old install, careful not to over-write any executables or dll files. In other words, I just moved the old data..
I tried just moving the Sambar install to another machine quite some time ago. That didn't help. The pop3 server was still crashing. When I re-bricked and re-installed Sambar fresh, the problem vanished. When I use the term "re-bricking", that just means re-formatting and re-installing everything.. That’s all I did... There must be some corrupt executable or dll file causing my problem. It sure is gone now. Paul Alger Ironclad Computer Services www.ironclad.net -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jim Hall Sent: Friday, June 18, 2004 5:55 PM To: sambar List Member Subject: [sambar] Mail server woes Thanks for the reply. I initially thought it was a hardware issue, so I put sambar on a different machine (and different OS, server A is win2k server, server B is win2k), but immediately saw the same issue. That's when I ruled out hardware as the culprit. Can you be a little more specific regarding "re-bricked" please? Thanks. ----- Original Message ----- From: "Paul Alger" <[EMAIL PROTECTED]> To: "sambar List Member" <[EMAIL PROTECTED]> Sent: Friday, June 18, 2004 7:41 PM Subject: [sambar] Mail server woes > I've seemed to fixed this Mail server issue with my server. The pop mail > server was going down almost once a day. I simply couldn't deal with it > anymore.. > > On the outside chance (I thought) that there was something wrong with the > OS, I reformatted and re-bricked my win2k server machine and haven't had one > mail server crash since. The mail server has now run flawlessly for about a > month.. It hasn't crashed once. > > I'm quite sure there is nothing wrong with Sambar's mail server now. If > re-bricking my computer helped my problem at all, it was the OS's fault at > the outset, not Sambar server.. > > My 2 cents worth.. > > Paul Alger > Ironclad Computer Services > www.ironclad.net > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of > Jim Hall > Sent: Friday, June 18, 2004 4:53 PM > To: sambar List Member > Subject: [sambar] Mail server woes > > This issue still exists in sambar 6. For the 5th or 6th day in row I have > had to leave the office to restart sambar because server threads are at 299, > and network connections the same. At this point this bug is costing me money > in lost time. > > While increasing the MTAs is a nice suggestion, it is NOT a solution. My MTA > settings are at 15. > > At this point, I need to know if Tod is addressing this issues, if so, what > is the timeframe for a real solution. And if not, can I get a refund for the > $100 I paid for software that works WORSE than the previous versions. > > This is unacceptable for production grade server software. > > ----- Original Message ----- > From: "Peter" <[EMAIL PROTECTED]> > To: "sambar List Member" <[EMAIL PROTECTED]> > Sent: Wednesday, February 11, 2004 12:12 PM > Subject: [sambar] Mail server woes > > > > Paul > > The default was 1 just like many of the other defaults you must change > > them to use the server in real life. > > > > When you run sambar as a service yes use the watcher and also use the > > service manager just in case. If you want the GUI in the try then run > > NTview.exe out of the bin, its a service GUI. The only draw back is it > > does not have pause and it must be started after the service. > > > > Peter > > > > -----Original Message----- > > From: "Paul Alger \(Ironclad\)" <[EMAIL PROTECTED]> > > To: "sambar List Member" <[EMAIL PROTECTED]> > > Date: Wed, 11 Feb 2004 08:54:23 -0800 > > Subject: [sambar] Mail server woes > > > > > Sambar defaults to mta = 1. If that is low, perhaps Todd should change > > > the > > > default? > > > > > > Peter, are you talking about the "Watcher Daemon"? Or running Sambar as > > > a > > > service? It seems like the watcher daemon doesn't check for a mail > > > server > > > failure. I am not running Sambar as a service but I can certainly give > > > that > > > a try and set the service manager to restart on failure. > > > > > > It says it is ok in the docs but is it advisable to run the watcher > > > daemon > > > when running Sambar as a service? In general, is it better to run > > > Sambar as > > > a service? For me, there is just something comforting in seeing the > > > icon in > > > the task bar tray... > > > > > > Paul > > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > > > Behalf Of > > > Peter > > > Sent: Wednesday, February 11, 2004 8:36 AM > > > To: sambar List Member > > > Subject: [sambar] Mail server woes > > > > > > Guys MTA's set to 1 or 2 is very low try increasing to 10 to 15, next > > > set > > > your service manager recovery to restart on failure and then there is > > > no > > > need to worry. > > > > > > Peter > > > > > > Jim it sopunds to me like the key you have is wrong or bad, get James > > > or Tod > > > to give you a new one. > > > > > > -----Original Message----- > > > From: "Jim H." <[EMAIL PROTECTED]> > > > To: "sambar List Member" <[EMAIL PROTECTED]> > > > Date: Wed, 11 Feb 2004 10:27:33 -0600 > > > Subject: [sambar] Mail server woes > > > > > > > I am seeing the same thing, but I also saw it in 5.3. > > > > > > > > Eventually the connections just keep growing, as if Sambar isn't > > > > killing idol connections. I recently increased MTAs [from 1 to 2] and > > > > am watching closely to see if that helps this issue. > > > > > > > > Between this problem and my restart/registration problem I damn near > > > > have to have someone babysitting the server 24/7. Gets expensive > > > fast. > > > > > > > > Not sure how much longer I can do this... > > > > > > > > -jim > > > > > > > > > > > > On 11/Feb/2004 08:14:11, Paul Alger \(Ironclad\) wrote: > > > > > I am experiencing random mail server crashes on Sambar 6. It > > > > > happens > > > > on the > > > > > average of once a week or so. > > > > > > > > > > The problem seems to be linked to this server log entry: > > > > > > > > > > [2004-02-11 07:56:54] WARN: POP3D event 'samples.dll:mail_connect' > > > > failed > > > > > > > > > > Or this one: > > > > > > > > > > [2004-02-11 07:44:02] ERROR: File openc of > > > > 'D:/sambar/config/mail.ini' > > > > > failed. > > > > > > > > > > After I reboot the server, things start working fine for another > > > > > week > > > > or > > > > > so.. > > > > > > > > > > > > > > > What happens is, the server will not accept any pop3 connections. > > > > They just > > > > > eventually time out. Sometimes the SMTP server just keeps working > > > > fine, > > > > > other times it crashes as well. > > > > > > > > > > As of now, I can't trust the server to run without babysitting it > > > > > all > > > > the > > > > > time. I am seriously considering rolling back to Sambar 5.x. It > > > > seems to > > > > > be much more stable than Sambar 6. > > > > > > > > > > Is anyone else experiencing these problems? Does anyone know what > > > > > "samples.dll" does? > > > > > > > > > > Paul Alger > > > > > > > > > > --- > > > > > Outgoing mail is certified Virus Free. > > > > > Checked by AVG anti-virus system (http://www.grisoft.com). > > > > > Version: 6.0.583 / Virus Database: 369 - Release Date: 2/10/2004 > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > To unsubscribe please go to http://www.sambar.ch/list/ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > To unsubscribe please go to http://www.sambar.ch/list/ > > > > > > > > > > > > > > ------------------------------------------------------- > > > To unsubscribe please go to http://www.sambar.ch/list/ > > > > > > > > > > > > > > > > > > --- > > > Incoming mail is certified Virus Free. > > > Checked by AVG anti-virus system (http://www.grisoft.com). > > > Version: 6.0.583 / Virus Database: 369 - Release Date: 2/10/2004 > > > > > > > > > --- > > > Outgoing mail is certified Virus Free. > > > Checked by AVG anti-virus system (http://www.grisoft.com). > > > Version: 6.0.583 / Virus Database: 369 - Release Date: 2/10/2004 > > > > > > > > > > > > > > > ------------------------------------------------------- > > > To unsubscribe please go to http://www.sambar.ch/list/ > > > > > > > > > > ------------------------------------------------------- > > To unsubscribe please go to http://www.sambar.ch/list/ > > > > > > > > > > > > > > ------------------------------------------------------- > To unsubscribe please go to http://www.sambar.ch/list/ > > > > > > --- > Incoming mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.705 / Virus Database: 461 - Release Date: 6/12/2004 > > > --- > Outgoing mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.705 / Virus Database: 461 - Release Date: 6/12/2004 > > > > > ------------------------------------------------------- > To unsubscribe please go to http://www.sambar.ch/list/ > > > > > ------------------------------------------------------- To unsubscribe please go to http://www.sambar.ch/list/ --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.705 / Virus Database: 461 - Release Date: 6/12/2004 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.705 / Virus Database: 461 - Release Date: 6/12/2004 ------------------------------------------------------- To unsubscribe please go to http://www.sambar.ch/list/
