>Once in a while, in the middle of the night, incoming mail gets hung in the
>spool directory. Messages sent to another user on the same server get
>delivered, but incoming mail from the outside world starts filling up the
>spool directory. Before I know it I have 20,000 files in the spool
>directory and users aren't getting their mail.
I'm guessing a DNS issue. The SMTP32.EXE program (which takes care of
message delivery) is running fine for local deliveries.
>To fix the problem, I start to move files out to a hold directory and wait
>for the messages to start to start going through.
Still sounds like a DNS issue. That process just speeds up IMail's normal
slow delivery process when the queue is large. The easier way to deal with
it is click "Send All" about 20 times in IMail Administrator or the web
admin tools. That will start 20 SMTP32.EXE processes that will keep
sending out mail from the queue.
>This sounds like a corrupted message problem, but why would I just start
>having this problem all of a sudden?
I doubt it is a corrupted message problem. If that was the case, you would
likely see lots of SMTP32.EXE processes sitting idle in task manager.
You can check your SMTP log file at the time this starts to see what error
messages are showing up. If it is a DNS problem, you'll see lots of "MX
Connect Fail" and "Stack Connect Fail" messages.
-Scott
Declude: Anti-virus, Anti-spam and Anti-hijacking solutions for
IMail. http://www.declude.com
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/
