On Mon, Jun 21, 2004 at 08:38:55PM +0200, Grzegorz Janoszka wrote: > On Thu, 17 Jun 2004, Grzegorz Janoszka wrote: > > > 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 > > > > I would like to use opt BOFHCHECKHELO=14. > > So? Any feedback? > > Should I write a patch for some new variables? For example > BLOCKNOTFQDNHELO, BLOCKMYHELO, BLOCKNOTRESOLVABLEHELO, > BLOCKOTHERDOMAINHELO and so on?
I'd like to see it. I have one further thing to add: Some spam coming in starts with (literally) 'HELO foo'. I would like to have an option to at least check the syntax of the host/domain name. Anything that isn't a properly formatted FQDN or at least a domain name should be rejected. Thanks, James Graves Delta Mobile Software http://www.deltamobile.com ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
