Re: Mail delivery failed: returning message to sender

[Greg Cope <gj...@rubberplant.freeserve.co.uk>]

Mail Delivery System wrote:
> 
> This message was created automatically by mail delivery software.
> 
> A message that you sent could not be delivered to one or more of its
> recipients. The following address(es) failed:
> 
>   modperl@apache.org:
>     SMTP error from remote mailer after RCPT TO:<mo...@apache.org>:
>     host mail.apache.org [63.211.145.10]:
>     553 Open relay problem - see <URL:http://www.mail-abuse.org/cgi-bin/nph-rss?195.102.240.129>
> 
> ------ This is a copy of the message, including all the headers. ------
> 
> Return-path: <gj...@rubberplant.freeserve.co.uk>
> Received: from [212.134.215.254] (helo=rubberplant.freeserve.co.uk)
>         by serv1.is1.u-net.net with esmtp (Exim 3.12 #1)
>         id 13Gf2m-0004W7-00; Mon, 24 Jul 2000 11:01:04 +0100
> Sender: greg
> Message-ID: <39...@rubberplant.freeserve.co.uk>
> Date: Mon, 24 Jul 2000 10:01:09 +0000
> From: Greg Cope <gj...@rubberplant.freeserve.co.uk>
> X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.14-5.0 i686)
> X-Accept-Language: en
> MIME-Version: 1.0
> To: Perrin Harkins <pe...@primenet.com>
> CC: Modperl list <mo...@apache.org>
> Subject: Re: YAM (Yet Another Module) - an IPC shared cache thing -
>  anyoneinterested  ?
> References: <Pi...@pharkins.office.etoys.com>
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
> 
> Perrin Harkins wrote:
> >
> > On Fri, 21 Jul 2000, Greg Cope wrote:
> > > I've writen a small IPC sysV based shared cache thingy ... (useing
> > > IPC::ShareLite), and I'd like some comments oin the design if anywants
> > > to crtique...
> >
> > Can you explain how your approach is different from the ones in
> > IPC::Shareable, IPC::Cache, IPC::SharedCache, IPC::MM (using shared hash),
> > File::Cache, and BerkeleyDB, and list some advantages/disadvantag
> > your module?  Your module may be great, but it's hard for people to know
> > which one to use in this crowded field without some explanation of the
> > differences.
 
 I did not realise that the field was so crowded - my appologies - It
 appears that I have opened my mouth too soon - and that these modules
do
 the more than mine, and better.
 
 Basically its a light weight variant of HTML::Template - i.e it allows
 you to define tags, with values, that are substituted into a template
 when you ask for the content.  This template is stored in a Shared
(IPC)
 Cache (again in a very similar way to IPC::SharedCache).  The lightness
 of the module is evident in that it is just over 100 lines (at the
 moment!).
 
 Since I was refered to HTML::Template I then found all thse other
 modules and have been grapleing with wether to use those, or my own.  I
 think I'll carry on with mine for my projects (and as a learning
 excercise) - and use the others when clients need that functionality,
so
 that when I leave they can use the maintained CPAN modules.
 
 Hope that clarifies some of the confusion I appear to have created.
 
 Greg Cope
 
> > - Perrin