X-Junk-Score: 0 [] X-Cloudmark-Score: 0 [] Return-Path: Received: from mail.allwebleads.com ([207.200.46.195] verified) by mail.stalker.com (CommuniGate Pro SMTP 5.2.7) with ESMTP id 47531624 for CGatePro@mail.stalker.com; Fri, 05 Sep 2008 16:18:04 -0700 Received-SPF: pass receiver=mail.stalker.com; client-ip=207.200.46.195; envelope-from=it@allwebleads.com X-Virus-Scanned: by cgpav Received: from [192.168.100.251] (account it HELO ix.allwebleads.com) by mail.allwebleads.com (CommuniGate Pro SMTP 5.2.7) with ESMTPSA id 10754538 for CGatePro@mail.stalker.com; Fri, 05 Sep 2008 18:17:46 -0500 Message-ID: <48C1BE1A.50609@allwebleads.com> Date: Fri, 05 Sep 2008 18:17:46 -0500 From: Mark Nipper User-Agent: Mozilla-Thunderbird 2.0.0.16 (X11/20080724) MIME-Version: 1.0 To: CommuniGate Pro Discussions Subject: Re: greylisting with CGPro References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit たまちゃん wrote: > Mark Nipper wrote: >> That's incorrect. Even RFC 821 (http://tools.ietf.org/html/rfc821) >> states that a client should retry after receiving a 400 level message. >> This might be ignored by much older clients of course, but there's >> nothing much to be done about substandard implementations. > > RFC 2821 states that the SMTP client is "encouraged" to try again. Hence the increased level of "severity" with the encouraged instead of just saying should as it did in 821. Essentially, to an implementor, you're really dumb if you don't follow this guideline, but hey, it's not necessarily a hard requirement. :) But yeah, greylisting is going to bounce legitimate messages occasionally. There are just too many crusty, old, broken mail systems out there still.