1997-02-13 - Re: Cypherpunks Distributed Remailer (fwd)

Header Data

From: Jim Choate <ravage@EINSTEIN.ssz.com>
To: cypherpunks@toad.com
Message Hash: b52a9e9a314d934a24a16958cb28773783431c669de3187fed66d2fbc72b0906
Message ID: <199702130059.SAA02356@einstein>
Reply To: N/A
UTC Datetime: 1997-02-13 00:52:51 UTC
Raw Date: Wed, 12 Feb 1997 16:52:51 -0800 (PST)

Raw message

From: Jim Choate <ravage@EINSTEIN.ssz.com>
Date: Wed, 12 Feb 1997 16:52:51 -0800 (PST)
To: cypherpunks@toad.com
Subject: Re: Cypherpunks Distributed Remailer (fwd)
Message-ID: <199702130059.SAA02356@einstein>
MIME-Version: 1.0
Content-Type: text



Forwarded message:

> Date: Wed, 12 Feb 1997 18:47 EDT
> From: "E. Allen Smith" <EALLENSMITH@ocelot.rutgers.edu>
> Subject: Re: Cypherpunks Distributed Remailer (fwd)
> 
> 	Someone with more experience correct me if I'm wrong (I'm just
> starting to learn about mailing list management), but isn't saving
> at least the first bounce from a given address good in order to check
> what address is the one that's actually bouncing? Admittedly, this only
> applies to badly-formed bounces. The rest can just have the address
> noted.

Hmmm, I can see saving the address causing the bounce in some sort of array
that is indexed to the majordomo subscription list for a given remailer. It
would not cost anything but overhead to save the entire message. I guess my
motivation was not that I cared their mailbox was full or it was a invalid
address but that I wouldn't be able to deliver at this time. I just don't
see any reason that it helps me to know why they can't receive mail only that
they can't.

> >Want to volunteer?
> 
> 	Give me some idea of how much programming knowledge, time, etcetera
> is required, please, before I can answer. I'd be renting space on some other
> computer (e.g., an account on cyberpass.net) to do it in; the only higher-level
> programming language (i.e., beyond Applesoft Basic) that I know anything of
> is Perl (and I don't know that all that well); and I am somewhat busy with
> other stuff. In other words, it depends.

Hmmm, not shure how much programming it would take - never done it myself.
I think Perl would be an acceptable language. I certainly hope to do the
majority of the scripts on the CDR in Perl myself. Perhaps there is somebody
who knows the fine points of how INN cache's messages. Redbeard and I had a
short discussion about this issue today relating to tracking messages to
reduce mail-loops. I will discuss it with him and see what happens.

I know exactly what you mean. I have two full-time jobs and hadn't really
thought of taking on the cpunks list in any manner. But hey, that is the
spice in life...

Give me a couple of days to look at the situation and if somebody don't beat
me to it I'll post what I find out. Cool?

                                                     Jim Choate
                                                     CyberTects
                                                     ravage@ssz.com







Thread