Usually in situations like this you ran into a killer message. When
Declude restarts it will copy all of the files from the work directory
into the review directory. You can slowly copy those messages to track
down the killer message and than when you find the message submit it to
Declude for review.
Darrel
----------------------------------
Check out http://www.invariantsystems.com for utilities for Declude,
Imail, mxGuard, and ORF. IMail/Declude Overflow Queue Monitoring,
SURBL/URI integration, MRTG Integration, and Log Parsers.
Ferrell Ard wrote:
We are running Declude 4.4.0 with IMail 9.10
Yesterday, Declude "hung" using just of 1 GB Memory processing 501
4 times.
Is there anthing that we can do to help identify what email (out of the
501)
that caused the "hang"?
Our recovery was to kill the Declude PID and restart the service.
Thanks very much
Ferrell Ard
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail". The archives can be found
at http://www.mail-archive.com.
--
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail". The archives can be found
at http://www.mail-archive.com.
