Ashik, > For example when I send a mail to hotmail acocunt, its been recvd > within 2 to 5 minutes time.
Which means that Imail is having no trouble allocating a SMTP32.EXE process for your outgoing mail after the SMTP conversation ends. This is the same resource it must allocate for local mail at that point, so it's not simply starved for that resource. > I have been running smtp32 exe the whole day for 2 to 3 days to > clear my spool. In an endless loop, or with what interval? If Imail is allocating all remote mail an SMTP32.EXE worker in a timely fashion, but can't deliver local mail with the same average number of recipients in a similar time frame, that's likely due to an inadequate/malfunctioning disk subsystem and/or user database. It also may be due to problems experienced by all NTFS systems such as a large number of subdirectories under a single TopDir, excessive fragmentation, or real-time virus scanning. Under such circumstances, running queue runs isn't the solution, except insofar as they accelerate the retry interval. What are the kind of errors you see in your logs? Looking at some of your other mail to the list, I see that you tried to get Declude Queue up and running but couldn't--this would be a great help in isolating your problems. I also saw that you were trying to send mail to an 80,000-member list at one point--if you are still burdening a single Imail server with tasks like this, alongside normal mail for 200K accounts, and you don't have IMGate or anything else to offload SMTP sending, you just have to get realistic. Rome wasn't scaled up in a day, it was scaled out. Sandy Please visit http://www.ipswitch.com/support/mailing-lists.html to be removed from this list. An Archive of this list is available at: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
