Have you identiifed which process is causing the CUP to jump like that? I usuually watch Task Manager, and sort by CPU usage, to that the high usage items will always show at the top of the list and I can identify the process that is causing the CPU to jump.

BTW, you don't need to run the UI unless your doing maintenance or adding/managing users. Save some resources and run the UI only when needed.

I don't know if this will work for you, but it worked on my server. I just turned off the screen logging after I noticed a correlation between high CPU useage for serveral minutes after a client had downloaded his 900+ messages in his inbox and the slow extended screen logging. After turning screen logging off the server can now handle just about any amount of message access and the processor useage is negligible.

Here-Here with Dr Fission's post - turn off the UI!

Start it up and everything seems fine; leave it a few hours and yup - the CPU is at 100%. Close it down and - hey presto - things return to sensible.

We run it up when we need it, kill it off before we close the remote session on the server. My staff now fear for their kneecaps if they leave it running!

I'm having much the same problem - server runs great for about 2 hours with CPU usage very low then creeps up to 100%. Everything grinds to a halt, my users are calling me asking what's wrong with the mail and I get increasingly cranky! I'm really getting tired of rebooting every few hours.

I DO NOT have the GUI open and it is set to not log to screen anyway.

As CPU % usage goes up it is almost all in the AGMSService.exe and the amount of memory usage for that service also increases (to upwards of 60000K). The AGMSService.exe sits at 92-99% CPU usage!!

Machine is: CPU - AMD Athlon 64 1.5 GHz; 2Gb Ram; 40Gb windows hard drive, 300 Gb Raid running apps; 2 network cards with HTTP,SMTP routed through one and POP/IMAP through the other (Tried that as a possible fix - made no noticeable difference in performance over running everything through one card)
Software: Windows 2003 sp2, MS SQL Server 2008 express; Argosoft MailServer .NET ver. 1.0.5.9 (and webmail); latest versions of EWall and Paranoid

Running .NET mailserver with or without EWall makes no difference. Same setup on another machine behaves the same (worse, actually, since the other machine is considerably slower so it just locks up sooner).

This really acts like its leaking memory or handles somewhere. CPU usage is ok at this moment, but memory usage by AGMSService.exe has increased by 10000k while I've been writing this.

I know Archie loves the .NET thing, but the Pro version was working so well! I really don't want to go looking for new software, but I'm not very happy right now.

By the by, I'm also having the problem that the mail server does not start on machine startup. EWall and Paranoid start up fine, but Argo must be started manually. The services settings say that it is set to launch automatically, but it doesn't. This upsets EWall since it cannot deliver to the server. It upsets me because an unattended restart results in no mail service.

I hope there's a fix for this.

Thanks,Ross

I'm having much the same problem - server runs great for about 2 hours with CPU usage very low then creeps up to 100%. Everything grinds to a halt, my users are calling me asking what's wrong with the mail and I get increasingly cranky! I'm really getting tired of rebooting every few hours.

I DO NOT have the GUI open and it is set to not log to screen anyway.

As CPU % usage goes up it is almost all in the AGMSService.exe and the amount of memory usage for that service also increases (to upwards of 60000K). The AGMSService.exe sits at 92-99% CPU usage!!

Machine is: CPU - AMD Athlon 64 1.5 GHz; 2Gb Ram; 40Gb windows hard drive, 300 Gb Raid running apps; 2 network cards with HTTP,SMTP routed through one and POP/IMAP through the other (Tried that as a possible fix - made no noticeable difference in performance over running everything through one card)
Software: Windows 2003 sp2, MS SQL Server 2008 express; Argosoft MailServer .NET ver. 1.0.5.9 (and webmail); latest versions of EWall and Paranoid

Running .NET mailserver with or without EWall makes no difference. Same setup on another machine behaves the same (worse, actually, since the other machine is considerably slower so it just locks up sooner).

This really acts like its leaking memory or handles somewhere. CPU usage is ok at this moment, but memory usage by AGMSService.exe has increased by 10000k while I've been writing this.

I know Archie loves the .NET thing, but the Pro version was working so well! I really don't want to go looking for new software, but I'm not very happy right now.

By the by, I'm also having the problem that the mail server does not start on machine startup. EWall and Paranoid start up fine, but Argo must be started manually. The services settings say that it is set to launch automatically, but it doesn't. This upsets EWall since it cannot deliver to the server. It upsets me because an unattended restart results in no mail service.

I hope there's a fix for this.

Thanks,Ross

Hi all,

I also just upgraded from Pro to .Net, and have noticed a CPU spike as well. However, I have traced it to an issue with my antivirus software [McAfee] being too agressive on the .NET scripts that comprise the server. I have excluded the program directory from scanning, as well as the files which make up the web interface and all is well. Course I will keep watching to make sure this is truly resolved, as it has only been a few days.

Also, to combat the problem of the ArgoSoft Mail Server service not running automatically on startup, I have created a scheduled task, which simply runs a batch file with a single line:

@NET START ArgoSoftMailServerNet

Setting that task to run at system startup [not logon] does the trick for me!

Hope that helps,
Joe

There are several things you can do to solve the problem. I will be doing these settings default in next releases.

1. Make sure Use "Simple" Method when Receiving SMTP Data is checked at Options - Server options - Advanced;

2. Make sure Logging is unchecked for POP3 and IMAP at Options - Services. Logging of these protocols is very resource consuming, and it would be better not to keep them on, unless you are debugging something.

3. Use Hourly logging (Options - Server Options - General), possibly, the problem is with writing into large logs.

Archie

I did all the things Archie recommended and the server seemed to settle down, however, now the ASSP is freaking out.