From owner-freebsd-questions@FreeBSD.ORG Sun Apr 29 00:19:43 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AE93F16A401 for ; Sun, 29 Apr 2007 00:19:43 +0000 (UTC) (envelope-from bsilver@chrononomicon.com) Received: from trans-warp.net (hyperion.trans-warp.net [216.37.208.37]) by mx1.freebsd.org (Postfix) with ESMTP id 5BBC513C455 for ; Sun, 29 Apr 2007 00:19:43 +0000 (UTC) (envelope-from bsilver@chrononomicon.com) Received: from [127.0.0.1] (unverified [65.193.73.208]) by trans-warp.net (SurgeMail 3.8f2) with ESMTP id 114739081-1860479 for multiple; Sat, 28 Apr 2007 20:01:32 -0400 In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v752.3) X-Priority: 3 (Normal) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <4AF11324-1013-4C53-879D-55B709E257F2@chrononomicon.com> Content-Transfer-Encoding: 7bit From: Bart Silverstrim Date: Sat, 28 Apr 2007 20:00:56 -0400 To: Ted Mittelstaedt X-Mailer: Apple Mail (2.752.3) X-Authenticated-User: bsilver@chrononomicon.com Cc: Eric Crist , Grant Peel , Christopher Hilton , freebsd-questions@freebsd.org Subject: Re: Greylisting -- Was: Anti Spam X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Apr 2007 00:19:43 -0000 On Apr 28, 2007, at 5:25 AM, Ted Mittelstaedt wrote: > > >> -----Original Message----- >> From: Bart Silverstrim [mailto:bsilver@chrononomicon.com] >> Sent: Friday, April 27, 2007 1:58 PM >> To: Ted Mittelstaedt >> Cc: Christopher Hilton; Grant Peel; Eric Crist; >> freebsd-questions@freebsd.org >> Subject: Re: Greylisting -- Was: Anti Spam >> >> >> >> On Apr 26, 2007, at 12:15 AM, Ted Mittelstaedt wrote: >> >>> There are legitimate technical reasons that someone may want their >>> mail >>> to not be greylisted. For example, my cell phone's e-mail >>> address is >>> in our monitoring scripts to page me in the event of a server >>> failure. >>> I would be pretty pissed off if Sprint suddenly started >>> greylisting. It >>> isn't just dumb-ass users making stupid political decisions to >>> reject >>> it, although in your case it probably was. >> >> If it is a legitimate mail server, it would be promoted to the auto- >> whitelist. Not all mail is constantly greylisted by most intelligent >> greylist systems. Only the first few messages would be delayed, >> until it is established as legitimate. >> > > That won't work in my case since I generally only have a failure > that causes > a problem which results in paging about once every 3 months or so. > By the > time the pages got through the > greylist it would be at least an hour later after the system had gone > down. That isn't acceptable for a notification system. What? What do you mean, a failure that causes a problem which results in paging once every 3 months? If your mail server tries to contact another mail server and it can't reach it, you're saying your mail server doesn't retry for an hour? Even if it does take an hour, the fact that it retried the server on the other side doing the greylisting means it would be whitelisted after a couple mails. If you're doing something SO critical that three or four mails delayed an hour, until you're establishes as a legit user, means life or death, you definitely should be doing something that backs up how you communicate with other sites, or you're not such a big fish that the other sites have already added you manually to their whitelists like AOL or Amazon mail servers would most likely be already, or other local ISPs that are known legit and I just don't feel like waiting for the system to add them automatically.