> Maybe can we use the bits of BOFHCHECKHELO? > Bit 0 (value of 1) - the same as today - all bad HELO is bloked. > (this gives us backward compatibility) > Bit 1 (2) - hosts presenting with our names or our IP's are blocked. > Bit 2 (4) - non resolvable HELO's are blocked Bit 3 (8) - bad > HELO is blocked but we pass through HELO 'hotmail.com' > from host 'out2.mail.hotmail.com' (from the same domain) > or from the same IP class C
Should't option 2 (bit 1) be blocked under any circumstance (if it does not resolve of course)? Basically, using bits doesn't seem like a good idea (no offence). It's just not user-friendly and I've neever seen it before in Courier's config-files. Using numbers like 0, 1, 2, (, 3?), 4 or things like strict, loose, soft, hard are more user-friendly and descriptive. > > I would like to use opt BOFHCHECKHELO=14. > > -- > Grzegorz Janoszka Kind Regards, Sander Holthaus ------------------------------------------------------- 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
