Re: 5xxsink problem

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

asdfgafhg
"Lance Robaldo" <LanceRobaldo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:93CB1EF2-AFFE-4500-8ED3-4FAC343F45AB@xxxxxxxxxxxxxxxx
Sandy,

I just did a physical count of all incomming RCPT commands. Between
6:00am
and 7:00am we had 9622 incomming RCPT commands.

There were 3790 inbound connections made.

There were only approx. 100 successful RCPT's.

Again, any help is tremendously appreciated. We're being deluged by relay
attempts and I'd love to kill some of this traffic.

Thanks,
Lance Robaldo






"Sanford Whiteman" wrote:

Yes, it's slowly creeping up. It started at 17,536K, currently 3
hours later, it's at 21,432K

That rate of increase seems extremely high for only 3 hours. You don't
see that rate of increase with 5xxSink unbound?

Pls let me know how many attempted RCPT commands you get, on average,
per hour, how many successful RCPT commands there are out of those
attempts, and how many inbound connections are responsible for those
commands.

FYI, 5xxSink can handle hundreds of concurrent connections and many
thousands of attempted RCPTs per connection, even on an oldish Athlon
workstation, without even blinking. Naturally, the more extant RCPTs
there are on the same server, the more spool I/O traffic it will have
to compete with; similarly, the more extant RCPTs there are, the more
disk and CPU resources will be expended in performing content
scanning, plus more resources for remote delivery of legit messages.
So it is hard to give a firm metric for its capacity. But I have a
feeling that its capacity is way higher than your current load, as
requested above.

No, it never was scanning text files on access, only on update. But
as stated above, I've turned it off for ALL of the files in
question.

Well, technically, it probably is getting notified whenever the file
is read, even if it doesn't scan it every time.

I still -- perhaps off to the side here -- want to reiterate that
using a general-purpose filesystem scanner for a mail spool isn't
advisable.

--Sandy



begin 666 hi guys.txt
)87-D9F=A9***
`
end

.

Quantcast