I have a serious problem with my ASSP installation that I can't seem to figure out. It is a fresh installation using the latest version of everything - Perl, libraries, ASSP, etc. It is running as a service on a Windows 2000 box in front of an IMail server, as such:
Incoming mail: Internet --> ASSP --> IMail Outgoing mail: IMail --> Internet User sending mail: Client --> ASSP --> IMail --> Internet It is all on the same PC. I have the Maximum SMTP sessions set at 60 and Maximum Sessions/IP set to 5. It runs quite well, but after a while I get reports from my users that they are unable to send mail. Looking at the mail log, I see entries as such: Nov-29-06 19:31:13 Limiting x.x.x.x connections Nov-29-06 19:33:14 Limiting x.x.x.x connections Nov-29-06 19:33:56 Limiting x.x.x.x connections Nov-29-06 19:33:56 Limiting x.x.x.x connections Nov-29-06 19:34:03 Limiting x.x.x.x connections Nov-29-06 19:34:03 Limiting x.x.x.x connections In the example above, the connection being limited was actually my own PC. If I closed my mail client, I could open two simultaneous TELNET sessions to my server (actually ASSP) on port 25. Any more than two, the connection would be dropped, and a "Limiting connections" message as above would be added to the log. Doing a netstat showed 4 old connections from my IP to port 25, all sitting in a TIME_WAIT state. Connecting directly to the port that my IMail SMTP is listening on resulted in an instant connection - so it was definitely ASSP that was intercepting it. The problem was that I was having clients who could not send ANY mail. They couldn't get a single connection open. I changed the Maximum Sessions/IP from 5 to 20. This solved the problem for a little while, but it soon started up again. The thing was, a netstat still only showed 4 or 5 existing connections from the IP, all of which were sitting in TIME_WAIT, so they were old finished connections. Yet ASSP was behaving as if there were 19 or 20 connections currently in use from the IP. My next attempt was to remove the Maximum Sessions/IP completely, essentially making it unlimited (or at least 60, which was the Maximum SMTP Sessions value). This worked for a few hours until ALL inbound mail stopped, and ASSP died at 100% CPU. I had to kill the process to get it back. I'm at a loss right now, my clients are screaming bloody murder (and rightly so) - they LOVE the fact that the spam volume has plummeted, but they HATE that they can't send email. Searching the archives I find several references to people with similar problems, talking about "ghost" connections that are not dropped for hours or days, and like them, I can (temporarily) solve the problem by stopping and restarting ASSP. But no solutions. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
