[32602] in Perl-Users-Digest
Perl-Users Digest, Issue: 3875 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Wed Feb 6 11:09:23 2013
Date: Wed, 6 Feb 2013 08:09:08 -0800 (PST)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Wed, 6 Feb 2013 Volume: 11 Number: 3875
Today's topics:
A little help with Perl & Email Messages artmerar@gmail.com
Re: A little help with Perl & Email Messages <ben@morrow.me.uk>
Re: A little help with Perl & Email Messages artmerar@gmail.com
Re: A little help with Perl & Email Messages artmerar@gmail.com
Re: A little help with Perl & Email Messages <news@lawshouse.org>
exact print <nospam.gravitalsun.extraantispam@hotmail.nospam.com>
Re: exact print panther.mindc@gmail.com
Re: exact print <nospam.gravitalsun.extraantispam@hotmail.nospam.com>
Re: exact print <news@lawshouse.org>
Re: exact print <nospam.gravitalsun.extraantispam@hotmail.nospam.com>
Re: exact print <news@lawshouse.org>
Re: exact print <r.mariotti@fdcx.net>
Re: exact print <nospam.gravitalsun.antispam@spamno.hotmail.anispam.com.nospam>
Re: exact print <rweikusat@mssgmbh.com>
Re: exact print <nospam.gravitalsun.extraantispam@hotmail.nospam.com>
Re: exact print <rweikusat@mssgmbh.com>
Re: exact print <nospam.gravitalsun.extraantispam@hotmail.nospam.com>
Re: exact print <rweikusat@mssgmbh.com>
Re: Learning to write modules by example. <justin.1211@purestblue.com>
MIME::Lite alternative? <tuxedo@mailinator.com>
Re: MIME::Lite alternative? <ben@morrow.me.uk>
Re: MIME::Lite alternative? <tuxedo@mailinator.com>
Re: OT: Any IT related events in the NYC/Boston area th <uri@stemsystems.com>
t <angelself2@yahoo.com>
Re: t <rweikusat@mssgmbh.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 5 Feb 2013 13:33:12 -0800 (PST)
From: artmerar@gmail.com
Subject: A little help with Perl & Email Messages
Message-Id: <02c19782-476a-4559-84dd-6e1e89a0fa10@googlegroups.com>
Hi,
Ok, our server runs Qmail. In the users home directory we can ut a file, .qmail, which acts like a .forward. So, we can take the incoming messages and forward them to a script:
| /home/johndoe/filter.pl
I want to take the emails and extract the From, To, Subject & Body. I was using Email::Filter and was getting everything, but the body contains all the tags & MIME information, etc.
I'm really looking to only get the body text, without all the tags, etc.
I tried Email::Filter, Email::MIME, MIME::Parser, all with no luck. When I use Email::Filter I start like this: my $mail = Email::Filter->new();
That gives some type of Hash Array: Email::Filter=HASH(0x1f220730)
But all those Perl modules are expecting the input to come from 'somewhere'. But I'm not sure in this case where 'somewhere' is. It is not STDIN, it is not a file, it was forwarded via the .qmail file: | /home/johndoe/filter.pl
So very long story short, any example where I can extract the body text without all the MIME stuff?
Many thanks!
------------------------------
Date: Wed, 6 Feb 2013 13:52:24 +0000
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: A little help with Perl & Email Messages
Message-Id: <op3au9-sjr1.ln1@anubis.morrow.me.uk>
Quoth artmerar@gmail.com:
>
> Ok, our server runs Qmail. In the users home directory we can ut a
> file, .qmail, which acts like a .forward. So, we can take the incoming
> messages and forward them to a script:
>
> | /home/johndoe/filter.pl
>
> I want to take the emails and extract the From, To, Subject & Body. I
> was using Email::Filter and was getting everything, but the body
> contains all the tags & MIME information, etc.
>
> I'm really looking to only get the body text, without all the tags, etc.
>
> I tried Email::Filter, Email::MIME, MIME::Parser, all with no luck.
> When I use Email::Filter I start like this: my $mail =
> Email::Filter->new();
>
> That gives some type of Hash Array: Email::Filter=HASH(0x1f220730)
It gives you an Email::Filter object, which you can manipulate using the
methods in the documentation for that module.
> But all those Perl modules are expecting the input to come from
> 'somewhere'. But I'm not sure in this case where 'somewhere' is. It is
> not STDIN, it is not a file, it was forwarded via the .qmail file: |
> /home/johndoe/filter.pl
Invoking a command from .qmail like that sends the mail through the
command's STDIN.
> So very long story short, any example where I can extract the body text
> without all the MIME stuff?
I can't see anything obvious, but with a half-decent understanding of
how MIME works you should be able to do this with Email::MIME.
Ben
------------------------------
Date: Wed, 6 Feb 2013 06:14:18 -0800 (PST)
From: artmerar@gmail.com
Subject: Re: A little help with Perl & Email Messages
Message-Id: <fe684097-f15c-4a2b-bd62-cc6bd276aeaf@googlegroups.com>
On Wednesday, February 6, 2013 7:52:24 AM UTC-6, Ben Morrow wrote:
> Quoth artmerar@gmail.com:
>
> >
>
> > Ok, our server runs Qmail. In the users home directory we can ut a
>
> > file, .qmail, which acts like a .forward. So, we can take the incoming
>
> > messages and forward them to a script:
>
> >
>
> > | /home/johndoe/filter.pl
>
> >
>
> > I want to take the emails and extract the From, To, Subject & Body. I
>
> > was using Email::Filter and was getting everything, but the body
>
> > contains all the tags & MIME information, etc.
>
> >
>
> > I'm really looking to only get the body text, without all the tags, etc.
>
> >
>
> > I tried Email::Filter, Email::MIME, MIME::Parser, all with no luck.
>
> > When I use Email::Filter I start like this: my $mail =
>
> > Email::Filter->new();
>
> >
>
> > That gives some type of Hash Array: Email::Filter=HASH(0x1f220730)
>
>
>
> It gives you an Email::Filter object, which you can manipulate using the
>
> methods in the documentation for that module.
>
>
>
> > But all those Perl modules are expecting the input to come from
>
> > 'somewhere'. But I'm not sure in this case where 'somewhere' is. It is
>
> > not STDIN, it is not a file, it was forwarded via the .qmail file: |
>
> > /home/johndoe/filter.pl
>
>
>
> Invoking a command from .qmail like that sends the mail through the
>
> command's STDIN.
>
>
>
> > So very long story short, any example where I can extract the body text
>
> > without all the MIME stuff?
>
>
>
> I can't see anything obvious, but with a half-decent understanding of
>
> how MIME works you should be able to do this with Email::MIME.
>
>
>
> Ben
I hate to be a dork, but do you have any sample code? When I look at Email::MIME, it talks about other modules needed and such and I really get lost. Maybe I am not understanding the example, etc........
Thanks in advance.
------------------------------
Date: Wed, 6 Feb 2013 06:27:16 -0800 (PST)
From: artmerar@gmail.com
Subject: Re: A little help with Perl & Email Messages
Message-Id: <89718473-96ab-47dc-ae03-d7d374863b96@googlegroups.com>
On Wednesday, February 6, 2013 7:52:24 AM UTC-6, Ben Morrow wrote:
> Quoth artmerar@gmail.com:
>
> >
>
> > Ok, our server runs Qmail. In the users home directory we can ut a
>
> > file, .qmail, which acts like a .forward. So, we can take the incoming
>
> > messages and forward them to a script:
>
> >
>
> > | /home/johndoe/filter.pl
>
> >
>
> > I want to take the emails and extract the From, To, Subject & Body. I
>
> > was using Email::Filter and was getting everything, but the body
>
> > contains all the tags & MIME information, etc.
>
> >
>
> > I'm really looking to only get the body text, without all the tags, etc.
>
> >
>
> > I tried Email::Filter, Email::MIME, MIME::Parser, all with no luck.
>
> > When I use Email::Filter I start like this: my $mail =
>
> > Email::Filter->new();
>
> >
>
> > That gives some type of Hash Array: Email::Filter=HASH(0x1f220730)
>
>
>
> It gives you an Email::Filter object, which you can manipulate using the
>
> methods in the documentation for that module.
>
>
>
> > But all those Perl modules are expecting the input to come from
>
> > 'somewhere'. But I'm not sure in this case where 'somewhere' is. It is
>
> > not STDIN, it is not a file, it was forwarded via the .qmail file: |
>
> > /home/johndoe/filter.pl
>
>
>
> Invoking a command from .qmail like that sends the mail through the
>
> command's STDIN.
>
>
>
> > So very long story short, any example where I can extract the body text
>
> > without all the MIME stuff?
>
>
>
> I can't see anything obvious, but with a half-decent understanding of
>
> how MIME works you should be able to do this with Email::MIME.
>
>
>
> Ben
Example from website:
use Email::MIME;
my $parsed = Email::MIME->new($message);
my @parts = $parsed->parts; # These will be Email::MIME objects, too.
my $decoded = $parsed->body;
my $non_decoded = $parsed->body_raw;
my $content_type = $parsed->content_type;
Now, where is $message coming from? I do not have a variable with $message. If I try $mail = Email::Filter->new();, that does not work......
------------------------------
Date: Wed, 06 Feb 2013 15:32:03 +0000
From: Henry Law <news@lawshouse.org>
Subject: Re: A little help with Perl & Email Messages
Message-Id: <ocydnTKHVNfu6o_MnZ2dnUVZ8vmdnZ2d@giganews.com>
On 05/02/13 21:33, artmerar@gmail.com wrote:
> So, we can take the incoming messages and forward them to a script:
>
> | /home/johndoe/filter.pl
When you say "forward them to a script", what do you mean? What exactly
will the system do with the message and the program? My guess would be
that, as instructed by this ".qmail" file, the mail client program will
invoke filter.pl and *pass it the text of the message* in some
well-defined way, most likely via STDIN.
> When I use Email::Filter I start like this: my $mail = Email::Filter->new();
> That gives some type of Hash Array: Email::Filter=HASH(0x1f220730)
Er yes, that's a Perl object of type "Email::Filter". I sense that you
need to read up on how to use Perl objects such as that one.
> It is not STDIN, it is not a file, it was forwarded via the .qmail file: | /home/johndoe/filter.pl
See my earlier question: are you sure? From what you've written I do
think it is STDIN. If that's the case then you merely open STDIN inside
"filter.pl", read in the text and pass it to your Email::Filter object.
I've no idea about Email::Filter but someone else suggested Email::MIME
which I do know a bit about, having used it. If you use that module
then something like this might be a place to start:
#!/usr/bin/perl
use strict;
use warnings;
my $msg;
$msg .= $_ while <>;
chomp $msg;
my $email = Email::MIME->new($msg);
# ... etc
There are better ways of slurping in the whole of a STDIN stream but I
don't have time to look them up right now; sorry. I hope this helps.
--
Henry Law Manchester, England
------------------------------
Date: Mon, 4 Feb 2013 10:33:29 +0200
From: "George Mpouras" <nospam.gravitalsun.extraantispam@hotmail.nospam.com>
Subject: exact print
Message-Id: <kenrne$i26$1@news.ntua.gr>
I need to print a text to file from within the script. The printed text must
be the same as the script text.
I do not want to escape every single character of the text, it should be
"pass through". So far nothing worked.
A small script that expose the problem, any help is wellcome.
open FILE, '>test.txt' or die "$^E\n";
print FILE q~
\
\\
\\\
~;
close FILE;
------------------------------
Date: Mon, 4 Feb 2013 02:49:15 -0800 (PST)
From: panther.mindc@gmail.com
Subject: Re: exact print
Message-Id: <9e569283-9250-4e0c-a1ae-548c7ea6ba34@googlegroups.com>
open FILE, '>test.txt' or die "$^E\n";
print FILE <<'F';
\
\\
\\\
F
close FILE;
------------------------------
Date: Mon, 4 Feb 2013 14:56:12 +0200
From: "George Mpouras" <nospam.gravitalsun.extraantispam@hotmail.nospam.com>
Subject: Re: exact print
Message-Id: <keob42$2lp$1@news.ntua.gr>
not good
------------------------------
Date: Mon, 04 Feb 2013 14:50:59 +0000
From: Henry Law <news@lawshouse.org>
Subject: Re: exact print
Message-Id: <gMadnRytJYFOV5LMnZ2dnUVZ8t2dnZ2d@giganews.com>
On 04/02/13 12:56, George Mpouras wrote:
> not good
Why not? I must be misunderstanding your requirement, because the
follow-up post's code seems to work perfectly.
$ cat test.txt
\
\\
\\\
$
A return, followed by the three lines as typed, and another return.
--
Henry Law Manchester, England
------------------------------
Date: Mon, 4 Feb 2013 17:18:56 +0200
From: "George Mpouras" <nospam.gravitalsun.extraantispam@hotmail.nospam.com>
Subject: Re: exact print
Message-Id: <keojfl$1he3$1@news.ntua.gr>
At linux it is ok. At windows does not behave as should ...
------------------------------
Date: Mon, 04 Feb 2013 18:02:45 +0000
From: Henry Law <news@lawshouse.org>
Subject: Re: exact print
Message-Id: <LoKdnVE9zIBYapLMnZ2dnUVZ8gidnZ2d@giganews.com>
On 04/02/13 15:18, George Mpouras wrote:
> At linux it is ok. At windows does not behave as should ...
Again, forgive me George: you've much more experience than I, but I
moved my test program to a Windows image and got this:
C:\WIP>type tryout.pl
use strict;
use warnings;
use 5.010;
use Data::Dumper;
open FILE, '>test.txt' or die "$^E\n"
print FILE <<'F';
\
\\
\\\
F
close FILE;
C:\WIP>type test.txt
\
\\
\\\
C:\WIP>
I was initially suspicious of the apparent extra return at the end of
the file but I looked at test.txt with an editor (inside Win) and there
is only one. The Win shell "type" command seems to add another. So the
output is the same as the Linux version.
What am I missing?
--
Henry Law Manchester, England
------------------------------
Date: Mon, 04 Feb 2013 21:21:06 -0500
From: bobmct <r.mariotti@fdcx.net>
Subject: Re: exact print
Message-Id: <s1r0h8pvn8hpe19t7pduuk50un2f4o4vuf@4ax.com>
On Mon, 04 Feb 2013 18:02:45 +0000, Henry Law <news@lawshouse.org>
wrote:
>On 04/02/13 15:18, George Mpouras wrote:
>> At linux it is ok. At windows does not behave as should ...
>
>Again, forgive me George: you've much more experience than I, but I
>moved my test program to a Windows image and got this:
>
>C:\WIP>type tryout.pl
>use strict;
>use warnings;
>use 5.010;
>
>use Data::Dumper;
>
>open FILE, '>test.txt' or die "$^E\n"
>print FILE <<'F';
>\
>\\
>\\\
>F
>close FILE;
>
>C:\WIP>type test.txt
>\
>\\
>\\\
>
>C:\WIP>
>
>I was initially suspicious of the apparent extra return at the end of
>the file but I looked at test.txt with an editor (inside Win) and there
>is only one. The Win shell "type" command seems to add another. So the
>output is the same as the Linux version.
>
>What am I missing?
ANother thing you could try is printing with FORMATs. The output will
be EXACTLY as described on the format. I've used this technique to
create fixed format files for transferral to dependent agencies with
excellent results. Runs the same on *nix or *doze.
------------------------------
Date: Tue, 5 Feb 2013 23:59:54 +0200
From: "George Mpouras" <nospam.gravitalsun.antispam@spamno.hotmail.anispam.com.nospam>
Subject: Re: exact print
Message-Id: <kervcv$s3g$1@news.ntua.gr>
there is a strange behaviour of activestate petl (5.16) at windows
print FILE q~
\
\\
\\\
~;
prints
\
\
\\
print FILE<<stop_printing;
\
\\
\\\
stop_printing
prints
\
\
------------------------------
Date: Wed, 06 Feb 2013 00:15:26 +0000
From: Rainer Weikusat <rweikusat@mssgmbh.com>
Subject: Re: exact print
Message-Id: <87ehgujo0x.fsf@sapphire.mobileactivedefense.com>
"George Mpouras"
<nospam.gravitalsun.antispam@spamno.hotmail.anispam.com.nospam>
writes:
> there is a strange behaviour of activestate petl (5.16) at windows
>
> print FILE q~
> \
> \\
> \\\
> ~;
>
> prints
>
>
> \
> \
> \\
>
>
>
> print FILE<<stop_printing;
> \
> \\
> \\\
> stop_printing
>
> prints
>
> \
> \
This is not really strange: A here-document whose delimiter is not quoted is
essentially a "-quoted string. The first \ escapes the newline right
after it. The \\-sequence in the seond line cause a \ to be
printed. The third line results in another \ because of the \\ and the
trailing newline is again escaped (which is a no-op).
------------------------------
Date: Wed, 6 Feb 2013 14:30:14 +0200
From: "George Mpouras" <nospam.gravitalsun.extraantispam@hotmail.nospam.com>
Subject: Re: exact print
Message-Id: <ketibb$n3d$1@news.ntua.gr>
if so why windows behaviour is completely different than linux ?
------------------------------
Date: Wed, 06 Feb 2013 12:38:14 +0000
From: Rainer Weikusat <rweikusat@mssgmbh.com>
Subject: Re: exact print
Message-Id: <874nhp62ix.fsf@sapphire.mobileactivedefense.com>
"George Mpouras" <nospam.gravitalsun.extraantispam@hotmail.nospam.com>
writes:
> if so why windows behaviour is completely different than linux ?
When running your two code examples on 'Linux', I get the exact same
output you posted.
------------------------------
Date: Wed, 6 Feb 2013 14:48:44 +0200
From: "George Mpouras" <nospam.gravitalsun.extraantispam@hotmail.nospam.com>
Subject: Re: exact print
Message-Id: <ketje0$171p$1@news.ntua.gr>
try to run them on a windows box and compare the results between windows and
linux
------------------------------
Date: Wed, 06 Feb 2013 12:55:39 +0000
From: Rainer Weikusat <rweikusat@mssgmbh.com>
Subject: Re: exact print
Message-Id: <87zjzh4n5g.fsf@sapphire.mobileactivedefense.com>
"George Mpouras" <nospam.gravitalsun.extraantispam@hotmail.nospam.com>
writes:
> try to run them on a windows box and compare the results between
> windows and linux
I explained the phenomenon you described for 'Linux'. I have no idea
about the behaviours on Windows and - frankly - 'something weird
happening on Windows', isn't that sort-of a tautology? :->
------------------------------
Date: Tue, 5 Feb 2013 09:10:27 +0000
From: Justin C <justin.1211@purestblue.com>
Subject: Re: Learning to write modules by example.
Message-Id: <3tu6u9-ede.ln1@zem.masonsmusic.co.uk>
On 2013-02-01, Ben Morrow <ben@morrow.me.uk> wrote:
>
> Quoth Justin C <justin.1211@purestblue.com>:
>>
>> I've written a few in-house modules for use within the business here
>> and they're ugly. I recently had reason to write a few new ones to
>> replace some procedural stuff that needed to be updated anyway, so I
>> thought I'd do it properly and write some sensible OO modules - a
>> module makes more sense for them anyway.
>>
>> I started off OK, but it soon got ugly again (though much less so).
>> I've been reading perlmodstyle, and I've also read José's Guide for
>> creating Perl modules (though it is a little old). What I think
>> would be useful would be to read the source of a great existing
>> module, one that's been written with 'best practice' in mind. Now I
>> can look at any of the hundreds of modules I have installed but I
>> don't know which ones are considered to be well (or very well)
>> written, so, can people recommend good examples of 'the best way to
>> do it'? I don't want to pick one and find it's the worst one from
>> which to learn by example.
>
> As far as non-Moose OO goes: the TAP::* modules are fairly newly written
> by people who know what they're doing; the CPANPLUS code is also pretty
> clean, as are the various modules making up LWP. However, current best
> practice is to use Moose for OO code, at least for large systems;
> Catalyst would be a good example of a system which was cleaned up a lot
> by switching to Moose.
>
> All OO code that will run on 5.10 or above should at least
>
> use mro "c3";
>
> at the top of the class heirarchy and use the next::method facility
> (documented in perldoc mro) rather than SUPER::.
Thank you, Ben. I'll do some reading.
Justin.
--
Justin C, by the sea.
------------------------------
Date: Sun, 3 Feb 2013 15:06:43 +0100
From: Tuxedo <tuxedo@mailinator.com>
Subject: MIME::Lite alternative?
Message-Id: <kelqtj$k5u$1@news.albasani.net>
Hello,
While looking into alternative modules to process a feedback form,
optionally attach a file, a message with HTML and integrating the file as a
Base64 attachment, I'm considering MIME::Lite. Perhaps MIME::Lite is the
most widely used module for multipart email processing including
attachments. However, the latest MIME-Lite-3.029, from November 2011, has
the following message on its homepage:
"MIME::Lite is not recommended by its current maintainer. There are a
number of alternatives, like Email::MIME or MIME::Entity and Email::Sender,
which you should probably use instead. MIME::Lite continues to accrue weird
bug reports, and it is not receiving a large amount of refactoring due to
the availability of better alternatives. Please consider using something
else."
Source: http://search.cpan.org/~rjbs/MIME-Lite-3.029/lib/MIME/Lite.pm
The "weird reports" is not being exactly specific in terms of which
situations the module may fail and it certainly does not offer a great deal
of confidence in its use.
In addition to the alternatives mentioned by the author, being Email::MIME,
MIME::Entity and Email::Sender, can anyone here recommend their tried and
tested modules, which you may have found particularly useful in handling
multipart email tasks with html and inline attachments?
Many thanks for any advise.
Tuxedo
------------------------------
Date: Sun, 3 Feb 2013 17:38:57 +0000
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: MIME::Lite alternative?
Message-Id: <huj2u9-74k2.ln1@anubis.morrow.me.uk>
Quoth Tuxedo <tuxedo@mailinator.com>:
> Hello,
>
> While looking into alternative modules to process a feedback form,
> optionally attach a file, a message with HTML and integrating the file as a
> Base64 attachment, I'm considering MIME::Lite. Perhaps MIME::Lite is the
> most widely used module for multipart email processing including
> attachments. However, the latest MIME-Lite-3.029, from November 2011, has
> the following message on its homepage:
> "MIME::Lite is not recommended by its current maintainer. There are a
> number of alternatives, like Email::MIME or MIME::Entity and Email::Sender,
> which you should probably use instead. MIME::Lite continues to accrue weird
> bug reports, and it is not receiving a large amount of refactoring due to
> the availability of better alternatives. Please consider using something
> else."
> Source: http://search.cpan.org/~rjbs/MIME-Lite-3.029/lib/MIME/Lite.pm
>
> The "weird reports" is not being exactly specific in terms of which
> situations the module may fail and it certainly does not offer a great deal
> of confidence in its use.
The bug list for MIME-Lite is
https://rt.cpan.org/Public/Dist/Display.html?Name=MIME-Lite , linked
from the distribution's search.cpan.org page.
> In addition to the alternatives mentioned by the author, being Email::MIME,
> MIME::Entity and Email::Sender, can anyone here recommend their tried and
> tested modules, which you may have found particularly useful in handling
> multipart email tasks with html and inline attachments?
I have successfully used Email::MIME with Email::Sender::Simple.
Ben
------------------------------
Date: Sun, 3 Feb 2013 19:51:56 +0100
From: Tuxedo <tuxedo@mailinator.com>
Subject: Re: MIME::Lite alternative?
Message-Id: <kembkd$rg4$1@news.albasani.net>
Ben Morrow wrote:
[..]
> I have successfully used Email::MIME with Email::Sender::Simple.
Thanks for the advise, I will give this combination a try.
Also, maybe Mail::Sender is another good alternative:
http://search.cpan.org/~jenda/Mail-Sender-0.8.22/Sender.pm
Tuxedo
------------------------------
Date: Tue, 05 Feb 2013 01:31:21 -0500
From: Uri Guttman <uri@stemsystems.com>
Subject: Re: OT: Any IT related events in the NYC/Boston area this year???
Message-Id: <87y5f3i85i.fsf@stemsystems.com>
>>>>> "B" == BobMCT <r.mariotti@fdcx.net> writes:
B> It's been quite a while sense the good old LinuxWorld events as well
B> as other IT related ones. I've been searching for events this year
B> being held between Philli, NYC and Boston areas and find virtually
B> none.
B> I see that the bostom.pm group is active here so I ask... is anyone
B> aware of any such events and be willing to share the info?
go to boston.pm.org and sign up for the mailing list. we have monthly
tech meetings and sometimes social ones.
ny has a solid pm group as well. pm.org will have their list info and
site.
neither group has held an 'event' but both have regular meetings.
uri
------------------------------
Date: Wed, 06 Feb 2013 03:41:44 -0800
From: robin <angelself2@yahoo.com>
Subject: t
Message-Id: <ketfhs$dt3$1@adenine.netfront.net>
vxcvxcvxcvxcvxcvxcv
--- news://freenews.netfront.net/ - complaints: news@netfront.net ---
------------------------------
Date: Wed, 06 Feb 2013 12:25:58 +0000
From: Rainer Weikusat <rweikusat@mssgmbh.com>
Subject: Re: t
Message-Id: <87d2wd633d.fsf@sapphire.mobileactivedefense.com>
robin <angelself2@yahoo.com> writes:
> vxcvxcvxcvxcvxcvxcv
>
> --- news://freenews.netfront.net/ - complaints: news@netfront.net ---
It's nice that you included the complaints address. One could make
good use of that. Please consider using test groups for test postings
in future.
------------------------------
Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>
Administrivia:
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
Back issues are available via anonymous ftp from
ftp://cil-www.oce.orst.edu/pub/perl/old-digests.
#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V11 Issue 3875
***************************************
