> [...\Services\InetInfo\Parameters\ThreadTimeout] seemed to make
> sense, though I'm not sure that it solves anything and I'm not sure
> if it has any consequences yet.
This tweak would apparently hinder, rather than help, the issues under
consideration. This setting allows already-allo
I'm just going to cross-post this from the o.e.support newsgroup, but
unless there is interest here in more of this, I'm just going to avoid
updating this thread.
-
Sandy,
I started testing by using the following:
...\Services\InetInfo\Parameters\PoolThreadLimit 200
> I have not yet tested out any changes to the threads. It seems that
> people don't want to discuss it.
Oh, I'll discuss it. . . but I don't really don't know why the burden
of proof fell my way, rather than this stuff being investigated
_before_ declaring without real testing that MS SM
Right now I am not using any tarpitting. As I indicated many times
before, using the MS SMTP tarpitting is not recommended, though it
would probably work fine if you had no size limit in MS SMTP since it
is the oversized messages that created the issues. I have not yet
tested out any changes
Matt -
So Are you using ORF to tarpit or MS SMTP and if the latter besides the
2 reg tweaks below do you make any other changes? The threads thing is
ok?
Thanks
-Nick
Matt wrote:
I just confirmed that this works properly. If the size limit is
exceeded for the DSN, it strips all a
Sweet. Thanks for the testing and follow up on this,
Matt.
Andrew
8)
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
MattSent: Wednesday, January 11, 2006 6:52 AMTo:
Declude.JunkMail@declude.comSubject: Re: [Declude.JunkMail] OT:
MaxDSNSize
I just
I just confirmed that this works properly. If the size limit is
exceeded for the DSN, it strips all attachments out and only sends back
the original headers and the top 20 lines of the original message
body. I set the MaxDSNSize to 100 KB, removed the MS SMTP size
limitation, and let IMail re
