> I first want to thank everyone who replied to me with help on an ISP > configuration... > > > My next question has to do with the way IMGate and IMail are talking.. Mail > is getting delayed from IMGate to IMail. IMgate log below... > > Mar 31 16:46:28 mx1 postfix/smtp[4943]: connect to > 24.117.109.196[24.117.109.196]: Connection refused (port 25) > Mar 31 16:46:28 mx1 postfix/smtp[4683]: connect to > 24.117.109.196[24.117.109.196]: Connection refused (port 25) > Mar 31 16:46:28 mx1 postfix/smtp[4943]: 65886188B8:to=<[EMAIL PROTECTED]>, > relay=none, delay=3719, status=deferred > (connect to 24.117.109.196[24.117.109.196]: Connection refused)
There is an IMail setting, Auto-deny possible hack attempts, which can block mail from a single source. It is the IMail way of cutting down a thundering heard attack. Try un checking it. > The delay between receiving in IMgate and successfully forwarding it to > IMail can be quite long.... The IMGate machine is taking the brunt of the > spam hits but the IMail machine is still getting hit by spammers even though > its been removed from the MX records... Could these delays be because the > IMail machine is getting too many connections? Or am I on the wrong track > here? Yes, see above. Also, you can now be more strict with your IMail relaying rules and block list. Start slamming entire blocks that send you junk. That way they must go to the MX or not send you mail. Many UCE servers have lists of detected mail servers, or try sending to mail.whatever.ext, which can bypass the MX. By blocking more at the IMail machine you clean up this issue, and because all valid mail routes through the MX you do not lose anything. --Eric
