|
Ah, OK, another thing that I have experienced when this
happens.
1. Check the number of current connections, you can use the
performance monitor, but I also use netstat because it shows stagnant
connections as well. If you have a whole lot of connections on the box (my
all time record was nearly 2000) It has been my experience that the smtp service
does not respond. It is most likely due to limited resorces on the TCP IP
protocol because I have plenty of memory and my CPU is ok as well.
To combat this I wrote a small exe that looks at the netstat
and counts the number of connections per IP address, then if a threashold is met
(I select 3) it puts the IP address in a text file that I merge with the one
that VOP mail uses to block IP addresses. Works great, but I have to run it
every 5 minutes so for 5 minutes they can flood me. It helps with spammers too,
becuase spammers have no regard, they want to blast as much email as possible,
so they will open as many connections as they can.
2. If there is any slowdown to the SQL server that is
servicing the VOP mail server. This is also been bad for us because I do error
logging to the SQL server, so it can get bogged down. If it gets too bogged down
or the database needs to be rebuilt VOP will sometimes studder waiting for
it.
That's a couple more of my experiences.
|
Title: Message
- [VOPmail Beta] SMTP failure Jaeme Adams
- [VOPmail Beta] SMTP failure Grapevine Staff
- [VOPmail Beta] SMTP failure Matthew J. Schwartz
- [VOPmail Beta] SMTP failure Robert Sinclair
- [VOPmail Beta] SMTP failure Matthew J. Schwartz
- [VOPmail Beta] SMTP failure David Payer
- [VOPmail Beta] SMTP failure Mike Herrera
- [VOPmail Beta] SMTP failure yehuda Glikman
- [VOPmail Beta] SMTP failure Salama hussein
- [VOPmail Beta] SMTP failure Matthew J. Schwartz
- [VOPmail Beta] SMTP failure Stephane Bismuth
- [VOPmail Beta] W32.Swen.A@mm Me
- [VOPmail Beta] SMTP failure Matthew J. Schwartz
- [VOPmail Beta] Incoming mail Marc Frega
