No, that's typical. We have a script scheduled to delete them every day. It
seems the sniffer script doesn't always delete them... probably Declude still
has a lock on the file, so it can be read, but not changed or deleted.
We monitor our spool and overflow directories, and when thresholds (b
I should add that in looking through my spool folder, I found a *lot* of
tmp*.tmp files, all generated by Armresearch for Sniffer and going way back.
Does this mean I have something misconfigured that these files are being left
over?
- Original Message -
From: Imail Admin
To: Decl
Hi,
I just looked in my declude.cfg and found these as the only non-commented lines:
THREADS 15
WAITFORMAIL 5000
INVITEFIXON
So it appears I've got 15 threads going. Unless there is some sort of
multiplier going? What happens if my thread count is too small?
Thanks,
Ben
- O
On 5/5/2011 4:28 PM, Bonno Bloksma wrote:
Hi,
Â
Even though I am running an Imail server
for a bachelor level education with about 2500 active
mailboxes and about 15.000 mails per day, I still have
Hi,
Even though I am running an Imail server for a bachelor level education with
about 2500 active mailboxes and about 15.000 mails per day, I still have
Declude set to max 150 THREADS. That is plenty to get the mail delivered in
time.
Declude itself can handle a lot more and using the bui
PS: I also upgraded Declude to use the integrated Sniffer and the integrated
Anti-Virus engine so that I could eliminate the number of command line
invocations.
From: IMail Admin [mailto:imailad...@bcwebhost.net]
Sent: Thursday, May 05, 2011 4:10 PM
To: Declude.JunkMail@declude.com
Subject: Re
In MY case it was not the number of threads, but eliminating one of the third
party command line applications. Although – I had never TRIED reducing the
number of threads to see if that would help the situation.
From: IMail Admin [mailto:imailad...@bcwebhost.net]
Sent: Thursday, May 05, 2011 4
That sounds like me. What’s the cure? Drop the number of threads in
declude.cfg? I haven’t looked at it yet to see what I have.
From: Andy Schmidt
Sent: Thursday, May 05, 2011 1:05 PM
To: Declude.JunkMail@declude.com
Subject: RE: [Declude.JunkMail] error 0xC142 smtp.exe
I had encountered
I had encountered the problem when I introduced another Declude add-on to the
mix (e.g., another command line program that Declude was launching). Eventually
there were too many command line processes using up too much heap…
Some of us were using the old command-line sniffer and 2 or 3 anti-vi
On 5/5/2011 2:21 PM, IMail Admin wrote:
> My business is so small any more than I could imagine using my smart
> phone to run the mail server. If it’s the smtp32.exe process causing
> the crash, then that would imply to me that I’ve got a lot of outbound
> messages all at once. I just don’t
With declude.cfg you can allocate the # of threads - but what do your logs
show? Are sending out a lot of email?
Maybe there are other issues like the box needs more physical ram/processing
power - does task mgr say all ik kool? Dunno the answer here - just giving you
some ideas for things to
HI Pete,
Thanks for the links. After reading all of those, and everything they link to,
I have a better idea of what’s happening. What Declude originally called the
“mystery heap” is apparently the desktop heap, which had a system wide limit of
48 mb (Win2k and Win2k3), allocated between inte
12 matches
Mail list logo
