Thanks for the explanation. I understood that "officially" it can't be done (I would otherwise not have been digging through the data and resource forks), but I was hoping someone knew how.

The reason I am looking, is because I would like to lower the count threshold and increase the delay. In fact, I believe that, SIMS-PPC 1.8b9d14, these parameters are actually stricter. For instance, 5 failures seems to cause a tempban. I would like to institute a much longer delay like (like 15 minutes) after 2 or 3 failures on the premise that a legitimate server will keep trying periodically for several days and a legitimate sender will detect and correct the incorrect email address.

At 11:51 AM -0700 9/5/06, allan sent email regarding parameters for suspending suspected in address harvesting:
Can anyone explain this? I cannot find anything like this in either the data or resource fork of SIMS-PPC 1.8b9d14.

Since it's hard-coded, changing it would be difficult. Why are you looking for this?

[EMAIL PROTECTED] (Technical Support, Stalker Labs) said:

The parameters for suspending an SMTP session suspected in address harvesting are hardcoded as follows:

#define kRCPTFailShortCounter 3 // so many failures will cause short delay
#define kRCPTFailShortDelay 10 // 10 seconds
#define kRCPTFailLongCounter 10 // so many failures will cause long delay
#define kRCPTFailLongDelay 60 // 1 minute

Understand that the lines quoting the #defines are source code which has been compiled into the data fork. You will not find instances of those variable by those names in the compiled code.

If you are hoping to change those parameters, officially, you cannot -- being hard coded and all.

#############################################################
This message is sent to you because you are subscribed to
 the mailing list <[email protected]>.
To unsubscribe, E-mail to: <[EMAIL PROTECTED]>
To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]>
To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]>
Send administrative queries to  <[EMAIL PROTECTED]>

Reply via email to