On 13/09/2003 at 13:34:49, SWIT wrote: >> I repeat there is no *technical* restriction. This is also >> NO RFC that says you SHOULD / MUST send mail by any means >> other than direct.
He's right, there's no technical restriction. That doesn't change the fact that dynamic IP pools are major abuse sources. The restrictions you put in place should be whatever works for you. If blocking dynamic IP ranges works for you, do it and whitelist the exceptions. If it doesn't (like here, where we get very particular types of spam and work with a lot of clueless companies - 80% of mail here which matches Len's recent IP HELO regexp is stuff we want) then don't do it, just blacklist specific problems. That's the great thing about managing your own incoming MX - you have control over what you do and don't accept. Provided you keep an eye on your server and are prepared to deal with (whitelist) problems that your blocks create, I don't think it's the lazy way out. It's the efficient way out. Evan
