Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[Dltk-dev] failed deliveries


  every now and again i get these types of messages when posting to the list.

  thx!

---------- Forwarded message ----------
From: Mail Delivery Subsystem <mailer-daemon@xxxxxxxxxxxxxx>
Date: Jul 8, 2007 9:53 PM
Subject: Delivery Status Notification (Failure)
To: jgangemi@xxxxxxxxx

This is an automatically generated Delivery Status Notification

Delivery to the following recipient failed permanently:

     dltk-dev@xxxxxxxxxxx

Technical details of permanent failure:
PERM_FAILURE: SMTP Error (state 13): 554 Service unavailable; Client host [64.233.166.181] blocked using multihop.dsbl.org; http://dsbl.org/listing?64.233.166.181

   ----- Original message -----

Received: by 10.35.32.3 with SMTP id k3mr5774318pyj.1183946036394;
        Sun, 08 Jul 2007 18:53:56 -0700 (PDT)
Received: by 10.35.117.14 with HTTP; Sun, 8 Jul 2007 18:53:56 -0700 (PDT)
Message-ID: < f8e1c5150707081853r77f1410dg5392c3c529836830@xxxxxxxxxxxxxx>
Date: Sun, 8 Jul 2007 21:53:56 -0400
From: "Jae Gangemi" <jgangemi@xxxxxxxxx>
To: "DLTK Developer Discussions" < dltk-dev@xxxxxxxxxxx>
Subject: Re: [Dltk-dev] Documentation?
In-Reply-To: <4153ee230707081847i63952c6an2c8710046df1fa0@xxxxxxxxxxxxxx >
MIME-Version: 1.0
Content-Type: multipart/alternative;
        boundary="----=_Part_67442_3095104.1183946036343"
References: < 4153ee230707080039u58da5266w87dbb28c470e03f2@xxxxxxxxxxxxxx>
         <f8e1c5150707080949q3c0941c3m3ee3ee80bd0a791e@xxxxxxxxxxxxxx >
         <4153ee230707081612i37b2598cr9e90f1daa08cd0@xxxxxxxxxxxxxx>
         < f8e1c5150707081820wfba818cr178055b3fe9c9214@xxxxxxxxxxxxxx>
         <4153ee230707081829p3549e038i8ce3ccc6c4f08d48@xxxxxxxxxxxxxx >
         <f8e1c5150707081838u71b2e0c7sf3c1f4cf6c59b749@xxxxxxxxxxxxxx>
         < 4153ee230707081847i63952c6an2c8710046df1fa0@xxxxxxxxxxxxxx>

------=_Part_67442_3095104.1183946036343
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

  well - antlr is going to build tokens, and those tokens get turned into
larger AST type objects.

  i guess for now, think about how you would handle things if you just had a
the lexer - you'd need to look at each token individually and know based

   ----- Message truncated -----



--
-jae

Back to the top