On Wed, 16 Jun 2004, Sander Holthaus - Orange XL wrote: > Same here :-( Wouldn't it be possible to make a BOFHCHECKHELO = hard and > BOFHCHECKHELO = soft or some sort, in which the first act as BORHCHECKHELO > does now and the latter only rejects HELO's that are totally bogus? Blocking > things like hotmail is just not acceptable for ANY system-administrator. > There has to be a middleway here.
I agree - we have several possibilities: 1. remote host uses unresolved name such as h45h34h5345.df.3r34.rt 2. remote host uses resolved name but in some other domain or IP class C 3. remote host uses resolved name in the same domain or IP class C 4. remote host uses MY name or MY IP in its HELO I wish to filter 1, 2 and 4 out and let 3 in, but its now impossible :( -- Grzegorz Janoszka ------------------------------------------------------- This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
