Received: from feferman.megacz.com. (feferman.megacz.com [65.23.154.28]) by krbdev.mit.edu (8.12.9) with ESMTP id m2HDdoHW024510; Mon, 17 Mar 2008 09:39:50 -0400 (EDT)
Date: Mon, 17 Mar 2008 09:39:50 -0400 (EDT)
Envelope-To: rt@krbdev.mit.edu
X-Originally-Received: from unreliable0.EECS.Berkeley.EDU (UNRELIABLE0.EECS.BERKELEY.EDU) by megacz.com (org.ibex.mail.SMTP) with ESMTP for ; Mon, 17 Mar 2008 06:39:42 -0700 from mx1.EECS.Berkeley.EDU (mx1.EECS.Berkeley.EDU [169.229.60.161]) by unreliable0.EECS.Berkeley.EDU (8.14.2/8.13.3) with ESMTP id m2HDdfLD027526 for <megacz@unreliable0.EECS.Berkeley.EDU>; Mon, 17 Mar 2008 06:39:41 -0700 (PDT) from bc3.EECS.Berkeley.EDU (bc3.EECS.Berkeley.EDU [169.229.60.70]) by mx1.EECS.Berkeley.EDU (8.14.2/8.12.10) with ESMTP id m2HDdefH019994 for <megacz@cs.berkeley.edu>; Mon, 17 Mar 2008 06:39:40 -0700 (PDT) from krbdev.mit.edu (localhost [127.0.0.1]) by bc3.EECS.Berkeley.EDU (Spam Firewall) with ESMTP id 55E22CDA1F for <megacz@cs.berkeley.edu>; Mon, 17 Mar 2008 06:39:03 -0700 (PDT) from krbdev.mit.edu (KRBDEV.MIT.EDU [18.7.14.135]) by bc3.EECS.Berkeley.EDU with ESMTP id rP7hYzgCEkZ5ChuB for <megacz@cs.berkeley.edu>; Mon, 17 Mar 2008 06:38:53 -0700 (PDT) (from daemon@localhost) by krbdev.mit.edu (8.12.9) id m2HDcqlc024498; Mon, 17 Mar 2008 09:38:52 -0400 (EDT)
To: rt@krbdev.mit.edu
From: adam@megacz.com
Subject: Re: [krbdev.mit.edu #5916] AutoReply: Re: Reading kerberos-adm from DNS: when will MIT-krb support this?
Message-ID: <3IV23XDF.@feferman.megacz.com>
RT-Send-Cc: 
X-RT-Original-Encoding: iso-8859-1
Content-Length: 1573

Hi, I've never sent a message to you before, so my spam filter trapped
your email.  If you're really a human being and not an evil spammer,
please click the link below or paste it into a web browser; doing so will
add you to my list of non-spammers (so you won't get this email in the future)
and it will move your message from my spam folder to my incoming mail folder.

Thanks!

  - Adam

http://www.megacz.com:8025/whitelist/xrt-5916-26183.5.2518976017344%40krbdev.mit.edu.txt


About this message:

NOTE: SPAMCOP DOES NOT CONSIDER THIS TO BE SPAM; see this:

         http://www.spamcop.net/fom-serve/cache/369.html

      and examine the "x-originally-received" header on this message 
      for the required "chain of custody" information.

      Only one of these challenge messages is ever generated in response to 
      a given inbound SMTP connection; it cannot be used to amplify spam    
      attacks, and in fact actually retards them while also stripping the   
      advertisement they were meant to convey.

      Only one delivery attempt for this challenge is ever made, and it is made
      DURING the SMTP delivery of the message being challenged (that is, 
      between C:DATA and S:250); the deliverer of the possibly-spam message
      must remain SMTP connected to my server during the entire process or else
      the delivery will immediately abort.  These challenge messages are NEVER,
      EVER queued for multiple delivery attempts
      
      For more information, please see:
      
      http://www.templetons.com/brad/spam/crgood.html