[32259] in Perl-Users-Digest
Perl-Users Digest, Issue: 3526 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Sun Oct 23 16:09:30 2011
Date: Sun, 23 Oct 2011 13:09:07 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Sun, 23 Oct 2011 Volume: 11 Number: 3526
Today's topics:
Re: File::Copy::copy With File Handles <nospam-abuse@ilyaz.org>
Re: Issue with Time::Local <jurgenex@hotmail.com>
Re: Issue with Time::Local <rweikusat@mssgmbh.com>
Re: Issue with Time::Local <rweikusat@mssgmbh.com>
Re: Issue with Time::Local <jurgenex@hotmail.com>
Re: Issue with Time::Local <jurgenex@hotmail.com>
Re: Issue with Time::Local <rweikusat@mssgmbh.com>
Re: Issue with Time::Local <rweikusat@mssgmbh.com>
Re: Issue with Time::Local <jwkrahn@example.com>
Net-SMTP on Win32 converts \n to \r\n and destroys PDF <andreas.pfaff.wangen@gmail.com>
Re: Net-SMTP on Win32 converts \n to \r\n and destroys <ben@morrow.me.uk>
Re: Net-SMTP on Win32 converts \n to \r\n and destroys <andreas.pfaff.wangen@gmail.com>
Re: Net-SMTP on Win32 converts \n to \r\n and destroys <andreas.pfaff.wangen@gmail.com>
Re: Registered Child Molester "Red E. Kilowatt" aka Ken <john@castleamber.com>
Re: Registered Child Molester John Bokma (john@castleam <invaild12345@aol.com>
Re: Registered Child Molester John Bokma (john@castleam <john@castleamber.com>
Registered Child Molester John Bokma (john@castleamber. <tired.of.padgett@gmail.com>
Re: Tricky STDERR issue under windows philkime@kime.org.uk
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Sat, 22 Oct 2011 00:15:32 +0000 (UTC)
From: Ilya Zakharevich <nospam-abuse@ilyaz.org>
Subject: Re: File::Copy::copy With File Handles
Message-Id: <slrnja42p4.km4.nospam-abuse@panda.math.berkeley.edu>
On 2011-10-19, MaggotChild <hsomob1999@yahoo.com> wrote:
>> On non-Unix systems (more specifically, on Win32 and I believe VMS)
>> File::Copy calls the system file-copy routine (CopyFile on Win32) if you
>> pass it filenames. This will preserve things like ACLs, extended
>> attributes, NTFS streams, and so on.
>
> I had ignored the obvious and interpreted "loss of information" to
> mean loss of the file's data, not necessarily metadata. Which lead to
> me to believe that for some subtle reason File::Copy couldn't be used
> reliably copy data streams. Thanks for the clarification.
The division into data/metadata is a tricky stuff. For example, "the
metadata" may contain the character encoding of a text file. If lost,
it would render the "data" completely useless.
Or the "thumbnail lower-resolution image" of a photo file. On
filesystems with arbitrary metadata allowed, the natural place for the
thumbnail image is in the metadata. On legacy filesystems, the viewer
program would be forced to either recalculate it each time, or put it
into the EXIF sections of the file (thus changing "THE DATA") or keep
it somewhere where it does not survive renaming of the file.
Yours,
Ilya
------------------------------
Date: Fri, 21 Oct 2011 17:08:23 -0700
From: Jürgen Exner <jurgenex@hotmail.com>
Subject: Re: Issue with Time::Local
Message-Id: <2924a75s3g1nsv6umsi4coh3racpns8ti0@4ax.com>
Rainer Weikusat <rweikusat@mssgmbh.com> wrote:
>Why would this 'usually be a mistake'?
Because reusing existing, well-tested code instead of re-inventing the
wheel is a sign of good software development.
jue
------------------------------
Date: Sat, 22 Oct 2011 15:08:05 +0100
From: Rainer Weikusat <rweikusat@mssgmbh.com>
Subject: Re: Issue with Time::Local
Message-Id: <871uu5t8ze.fsf@sapphire.mobileactivedefense.com>
Jürgen Exner <jurgenex@hotmail.com> writes:
> Rainer Weikusat <rweikusat@mssgmbh.com> wrote:
>>Why would this 'usually be a mistake'?
>
> Because reusing existing, well-tested code instead of re-inventing
> the wheel is a sign of good software development.
And not using code by someone who believes to have invented something
as important and lasting as 'the wheel' just because he has managed to
split a string using a library routine would be a sign of common
sense: People who overestimate the importance of their work that
grossly quite obviously lack the compentence necessary for a sensible
assessment.
Totschlagargumente benutzt man, weil man sonst keine hat.
------------------------------
Date: Sat, 22 Oct 2011 15:13:54 +0100
From: Rainer Weikusat <rweikusat@mssgmbh.com>
Subject: Re: Issue with Time::Local
Message-Id: <87obx9jeql.fsf@sapphire.mobileactivedefense.com>
Ben Morrow <ben@morrow.me.uk> writes:
> Quoth Rainer Weikusat <rweikusat@mssgmbh.com>:
>> Ben Morrow <ben@morrow.me.uk> writes:
>> >
>> > It's usually a mistake to try to parse date formats yourself. Use
>> > DateTime instead.
>>
>> Why would this 'usually be a mistake'?
>
> Because, as this thread has demonstrated, it's extremely easy to get it
> wrong.
Well then, what's wrong with the code in question:
my $date_string = '2011-01-31 17:30:55';
my ($date, $time) = split /\s+/, $date_string;
my ($y, $m, $d) = split /-/, $date;
my ($hr, $min, $sec) = split /:/, $time;
This splits a complex string into components. I can't see any error in
here.
------------------------------
Date: Sat, 22 Oct 2011 07:58:05 -0700
From: Jürgen Exner <jurgenex@hotmail.com>
Subject: Re: Issue with Time::Local
Message-Id: <n9m5a7tvpc5536iqlh1tcgmgh3h2qlb516@4ax.com>
Rainer Weikusat <rweikusat@mssgmbh.com> wrote:
>Ben Morrow <ben@morrow.me.uk> writes:
>> Quoth Rainer Weikusat <rweikusat@mssgmbh.com>:
>>> Ben Morrow <ben@morrow.me.uk> writes:
>>> >
>>> > It's usually a mistake to try to parse date formats yourself. Use
>>> > DateTime instead.
>>>
>>> Why would this 'usually be a mistake'?
>>
>> Because, as this thread has demonstrated, it's extremely easy to get it
>> wrong.
>
>Well then, what's wrong with the code in question:
>
>my $date_string = '2011-01-31 17:30:55';
>my ($date, $time) = split /\s+/, $date_string;
>
>my ($y, $m, $d) = split /-/, $date;
>my ($hr, $min, $sec) = split /:/, $time;
>
>This splits a complex string into components. I can't see any error in
>here.
Nor can anyone else. You are missing the point by several miles.
jue
------------------------------
Date: Sat, 22 Oct 2011 08:04:55 -0700
From: Jürgen Exner <jurgenex@hotmail.com>
Subject: Re: Issue with Time::Local
Message-Id: <fgm5a7p7ap2ib6dnve3ipkli2glvppo8bq@4ax.com>
Rainer Weikusat <rweikusat@mssgmbh.com> wrote:
>Jürgen Exner <jurgenex@hotmail.com> writes:
>> Rainer Weikusat <rweikusat@mssgmbh.com> wrote:
>>>Why would this 'usually be a mistake'?
>>
>> Because reusing existing, well-tested code instead of re-inventing
>> the wheel is a sign of good software development.
>
>And not using code by someone who believes to have invented something
>as important and lasting as 'the wheel' just because he has managed to
>split a string using a library routine would be a sign of common
>sense: People who overestimate the importance of their work that
>grossly quite obviously lack the compentence necessary for a sensible
>assessment.
Obviously the task wasn't as simple as you are painting it, otherwise
the OP wouldn't have made that error.
On the other hand you are right: if the OP had used the module, then he
would this honorable NG would have missed this great entertainment..
>Totschlagargumente benutzt man, weil man sonst keine hat.
"Kein Programm ist nutzlos. Es kann immer noch als schlechtes Beispiel
dienen."
No program is useless. It can always serve as an example for poor
programming.
jue
------------------------------
Date: Sat, 22 Oct 2011 17:29:42 +0100
From: Rainer Weikusat <rweikusat@mssgmbh.com>
Subject: Re: Issue with Time::Local
Message-Id: <87k47xc7m1.fsf@sapphire.mobileactivedefense.com>
Jürgen Exner <jurgenex@hotmail.com> writes:
> Rainer Weikusat <rweikusat@mssgmbh.com> wrote:
>>Ben Morrow <ben@morrow.me.uk> writes:
>>> Quoth Rainer Weikusat <rweikusat@mssgmbh.com>:
>>>> Ben Morrow <ben@morrow.me.uk> writes:
>>>> >
>>>> > It's usually a mistake to try to parse date formats yourself. Use
>>>> > DateTime instead.
>>>>
>>>> Why would this 'usually be a mistake'?
>>>
>>> Because, as this thread has demonstrated, it's extremely easy to get it
>>> wrong.
>>
>>Well then, what's wrong with the code in question:
>>
>>my $date_string = '2011-01-31 17:30:55';
>>my ($date, $time) = split /\s+/, $date_string;
>>
>>my ($y, $m, $d) = split /-/, $date;
>>my ($hr, $min, $sec) = split /:/, $time;
>>
>>This splits a complex string into components. I can't see any error in
>>here.
>
> Nor can anyone else. You are missing the point by several miles.
The code I requoted above led to a comment 'trying to parse date
formats yourself is usually a mistake'. But no mistake was made when
parsing this date. Instead, the OP made a mistake when calling a
subroutine provided by some module. If error-prone activities are
better avoided (highly debatable since humans learn by making mistakes
and having to correct them), the obvious conclusion would be that
'trying to use existing Perl modules' must be the thing which is
'usually a mistake'. All of this together makes preciously little
sense. Consequently, something must be missing here, namely,
an argument supporting the 'is usually a mistake' assertion.
------------------------------
Date: Sat, 22 Oct 2011 17:42:39 +0100
From: Rainer Weikusat <rweikusat@mssgmbh.com>
Subject: Re: Issue with Time::Local
Message-Id: <87fwilc70g.fsf@sapphire.mobileactivedefense.com>
Jürgen Exner <jurgenex@hotmail.com> writes:
> Rainer Weikusat <rweikusat@mssgmbh.com> wrote:
>>Jürgen Exner <jurgenex@hotmail.com> writes:
>>> Rainer Weikusat <rweikusat@mssgmbh.com> wrote:
>>>>Why would this 'usually be a mistake'?
>>>
>>> Because reusing existing, well-tested code instead of re-inventing
>>> the wheel is a sign of good software development.
>>
>>And not using code by someone who believes to have invented something
>>as important and lasting as 'the wheel' just because he has managed to
>>split a string using a library routine would be a sign of common
>>sense: People who overestimate the importance of their work that
>>grossly quite obviously lack the compentence necessary for a sensible
>>assessment.
>
> Obviously the task wasn't as simple as you are painting it, otherwise
> the OP wouldn't have made that error.
The OP tried to use some non-core Perl module and apparently, without
reading the documentation first. That's certainly an error (or at
least bound to cause 'surprises') but not a coding error.
------------------------------
Date: Sat, 22 Oct 2011 22:54:23 -0700
From: "John W. Krahn" <jwkrahn@example.com>
Subject: Re: Issue with Time::Local
Message-Id: <k_Noq.722$Qd1.556@newsfe02.iad>
SSS Develop wrote:
>
> When i run the following script, I get error:
>
> Day '31' out of range 1..28 at exp.pl line 18
perldoc -f localtime
localtime EXPR
localtime
Converts a time as returned by the time function to a
9-element list with the time analyzed for the local time
zone. Typically used as follows:
# 0 1 2 3 4 5 6 7 8
($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) =
localtime(time);
All list elements are numeric, and come straight out of the
C `struct tm'. $sec, $min, and $hour are the seconds,
minutes, and hours of the specified time.
$mday is the day of the month, and $mon is the month
itself, in the range 0..11 with 0 indicating January and 11
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
indicating December. This makes it easy to get a month
^^^^^^^^^^^^^^^^^^^
name from a list:
my @abbr = qw( Jan Feb Mar Apr May Jun Jul Aug Sep Oct
Nov Dec );
print "$abbr[$mon] $mday";
# $mon=9, $mday=18 gives "Oct 18"
$year is the number of years since 1900, not just the last
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
two digits of the year. That is, $year is 123 in year
2023. The proper way to get a complete 4-digit year is
simply:
$year += 1900;
Otherwise you create non-Y2K-compliant programs--and you
wouldn't want to do that, would you?
> use strict;
> use warnings;
> use Time::Local;
>
> my $date_string = '2011-01-31 17:30:55';
> my ($date, $time) = split /\s+/, $string;
>
> my ($y, $m, $d) = split /-/, $date;
> my ($hr, $min, $sec) = split /:/, $time;
>
> print timelocal($sec,$min,$hr,$d,$m,$y);
my ( $y, $m, $d, $hr, $min, $sec ) = $date_string =~ /\d+/g
print timelocal( $sec, $min, $hr, $d, $m - 1, $y - 1900 );
John
--
Any intelligent fool can make things bigger and
more complex... It takes a touch of genius -
and a lot of courage to move in the opposite
direction. -- Albert Einstein
------------------------------
Date: Sun, 23 Oct 2011 08:24:54 -0700 (PDT)
From: andipfaff <andreas.pfaff.wangen@gmail.com>
Subject: Net-SMTP on Win32 converts \n to \r\n and destroys PDF attachments etc.
Message-Id: <7a0cdf66-86a5-4e58-ae55-1aa3d288c963@gy7g2000vbb.googlegroups.com>
Hi everybody,
I try to send emails with an attched PDF on Windows with ActiveState
v5.8.9. I am using Mime-Lite to create the message an as_string() to
convert it to a variable.
$msg_body = $msg->as_string();
If I write this variable to a file with binmode the \n in the PDF is
written as \n.
When sending the Mail the attached PDF is unreadable because the \n
have been replaced by \r\n somewhere. I suggest this happend in
$smtp->datasend($msg_body);
How can I tell Perl or the library to handle this in binmode?
Thanks in advance
Andi
------------------------------
Date: Sun, 23 Oct 2011 12:06:06 -0500
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: Net-SMTP on Win32 converts \n to \r\n and destroys PDF attachments etc.
Message-Id: <buydnTu2Lf7j1DnTnZ2dnUVZ8v-dnZ2d@bt.com>
Quoth andipfaff <andreas.pfaff.wangen@gmail.com>:
> Hi everybody,
>
> I try to send emails with an attched PDF on Windows with ActiveState
> v5.8.9. I am using Mime-Lite to create the message an as_string() to
> convert it to a variable.
> $msg_body = $msg->as_string();
>
> If I write this variable to a file with binmode the \n in the PDF is
> written as \n.
> When sending the Mail the attached PDF is unreadable because the \n
> have been replaced by \r\n somewhere. I suggest this happend in
> $smtp->datasend($msg_body);
>
> How can I tell Perl or the library to handle this in binmode?
You can't. Bare \ns are illegal in a mail message: you need to base64
encode files like PDFs which contain binary data.
How are you attaching the PDF? If you tell MIME::Lite it's a PDF, with a
Type => "application/pdf" parameter, it should handle the base64 for you
automatically.
Ben
------------------------------
Date: Sun, 23 Oct 2011 10:28:53 -0700 (PDT)
From: andipfaff <andreas.pfaff.wangen@gmail.com>
Subject: Re: Net-SMTP on Win32 converts \n to \r\n and destroys PDF attachments etc.
Message-Id: <7c4d2b27-1bf2-40a8-9514-3db511c1e70e@v15g2000vbm.googlegroups.com>
On 23 Okt., 19:06, Ben Morrow <b...@morrow.me.uk> wrote:
> Quoth andipfaff <andreas.pfaff.wan...@gmail.com>:
>
> > Hi everybody,
>
> > I try to send emails with an attched PDF on Windows with ActiveState
> > v5.8.9. I am using Mime-Lite to create the message an as_string() to
> > convert it to a variable.
> > $msg_body = $msg->as_string();
>
> > If I write this variable to a file with binmode the \n in the PDF is
> > written as \n.
> > When sending the Mail the attached PDF is unreadable because the \n
> > have been replaced by \r\n somewhere. I suggest this happend in
> > $smtp->datasend($msg_body);
>
> > How can I tell Perl or the library to handle this in binmode?
>
> You can't. Bare \ns are illegal in a mail message: you need to base64
> encode files like PDFs which contain binary data.
>
> How are you attaching the PDF? If you tell MIME::Lite it's a PDF, with a
> Type => "application/pdf" parameter, it should handle the base64 for you
> automatically.
>
> Ben
Hi,
I am using mime-lite to attach it. Type is application/pdf but I
cannot add the Encoding: Base64 because the script will no longer send
the mail then (without error message). I have to leave the encoding
away and then it is being sent 8Bit encoded.
But I do not think mime-lite ist the problem. Just sending nothing
else then one \n in a mailbody will result in a 0x0D0x0A in the
received mail. Even using mime-lite for sending the mail instead of
net-smtp and datasend() will do that.
This is the code:
$pagetosend = qq(<html>\r\n<body>$mail_text\r\n</body>\r\n</html>);
$msg = MIME::Lite->new (From => $email_abs, To => $email_empf, Subject
=> $db_mail_subject, Type => 'multipart/Mixed', Data => $pagetosend);
$msg->attach(Type => 'text/html; charset=utf-8', Data => $pagetosend,
Encoding => 'Base64');
$msg->attach(Type => 'application/pdf', Path =>
$mail_attachment_filename, Filename => $mail_attachment_filename,
Disposition => 'attachment');
$msg_body = $msg->as_string();
#method 1
MIME::Lite->send('smtp', $email_server, Port=>$email_server_port);
$msg->send();
#method 2
$msg_body = $msg->as_string();
....
$smtp->datasend($msg_body);
$smtp->dataend();
$smtp->quit;
------------------------------
Date: Sun, 23 Oct 2011 11:26:24 -0700 (PDT)
From: andipfaff <andreas.pfaff.wangen@gmail.com>
Subject: Re: Net-SMTP on Win32 converts \n to \r\n and destroys PDF attachments etc.
Message-Id: <c96ab5aa-9c25-4447-ac0a-d9b4e70fb5e1@hv4g2000vbb.googlegroups.com>
On 23 Okt., 19:28, andipfaff <andreas.pfaff.wan...@gmail.com> wrote:
> On 23 Okt., 19:06, Ben Morrow <b...@morrow.me.uk> wrote:
>
>
>
>
>
> > Quoth andipfaff <andreas.pfaff.wan...@gmail.com>:
>
> > > Hi everybody,
>
> > > I try to send emails with an attched PDF on Windows with ActiveState
> > > v5.8.9. I am using Mime-Lite to create the message an as_string() to
> > > convert it to a variable.
> > > $msg_body = $msg->as_string();
>
> > > If I write this variable to a file with binmode the \n in the PDF is
> > > written as \n.
> > > When sending the Mail the attached PDF is unreadable because the \n
> > > have been replaced by \r\n somewhere. I suggest this happend in
> > > $smtp->datasend($msg_body);
>
> > > How can I tell Perl or the library to handle this in binmode?
>
> > You can't. Bare \ns are illegal in a mail message: you need to base64
> > encode files like PDFs which contain binary data.
>
> > How are you attaching the PDF? If you tell MIME::Lite it's a PDF, with a
> > Type => "application/pdf" parameter, it should handle the base64 for you
> > automatically.
>
> > Ben
>
> Hi,
>
> I am using mime-lite to attach it. Type is application/pdf but I
> cannot add the Encoding: Base64 because the script will no longer send
> the mail then (without error message). I have to leave the encoding
> away and then it is being sent 8Bit encoded.
>
> But I do not think mime-lite ist the problem. Just sending nothing
> else then one \n in a mailbody will result in a 0x0D0x0A in the
> received mail. Even using mime-lite for sending the mail instead of
> net-smtp and datasend() will do that.
>
> This is the code:
> $pagetosend = qq(<html>\r\n<body>$mail_text\r\n</body>\r\n</html>);
> $msg = MIME::Lite->new (From => $email_abs, To => $email_empf, Subject
> => $db_mail_subject, Type => 'multipart/Mixed', Data => $pagetosend);
> $msg->attach(Type => 'text/html; charset=utf-8', Data => $pagetosend,
> Encoding => 'Base64');
> $msg->attach(Type => 'application/pdf', Path =>
> $mail_attachment_filename, Filename => $mail_attachment_filename,
> Disposition => 'attachment');
> $msg_body = $msg->as_string();
> #method 1
> MIME::Lite->send('smtp', $email_server, Port=>$email_server_port);
> $msg->send();
> #method 2
> $msg_body = $msg->as_string();
> ....
> $smtp->datasend($msg_body);
> $smtp->dataend();
> $smtp->quit;- Zitierten Text ausblenden -
>
> - Zitierten Text anzeigen -
Sorry I found the error. I did not give the correct mime-type to mime-
lite.
------------------------------
Date: Sat, 22 Oct 2011 17:12:33 -0500
From: John Bokma <john@castleamber.com>
Subject: Re: Registered Child Molester "Red E. Kilowatt" aka Ken Padgett and JoAnn Padgett [858-450-3562, KEN-PADGETT.COM (74.117.221.143), kpd@morningsinger.com, Advantage Publishers Group] 68.71.137.60 [aww-faq.org] 3134 Mercer Lane, San Diego, CA 92122 Has
Message-Id: <87lisc65gu.fsf@castleamber.com>
Rosemarie Shiver <tired.of.padgett@gmail.com> writes:
Just fuck off and die already, pathetic clown.
--
John Bokma j3b
Blog: http://johnbokma.com/ Perl Consultancy: http://castleamber.com/
Perl for books: http://johnbokma.com/perl/help-in-exchange-for-books.html
------------------------------
Date: Sat, 22 Oct 2011 22:29:14 -0400
From: "WeReo_BoY" <invaild12345@aol.com>
Subject: Re: Registered Child Molester John Bokma (john@castleamber.com, contact@johnbokma.com) johnbokma.com, castleamber.com, johnbokma.com/perl/help-in-exchange-for-books.html Has Met His Match!
Message-Id: <j7vu5s$tjk$1@dont-email.me>
"Rosemarie Shiver" <tired.of.padgett@gmail.com> wrote in message
news:b64ed6b0-b5e3-4577-95c6-c7ad13b76a3c@c1g2000vbw.googlegroups.com...
> This aberrated jackass has been bullying, libeling, and harassing
> innocent folks for years, but finally his reign of terror is coming to
> a close. My guess is that ICANN and Godaddy would like to know about
> his BOGUS registration! This whacko likes dark complected Mexican
> boys around seven (7) years old for anal sex!!
>
> Rosemarie Shiver
> P.S. Johnnie boy, you are one fucking dumbass! More to CUM unless you
> disappear!
>
> http://www.velocityreviews.com/forums/t358011-re-john-bokma-harassment.html
>
> http://www.justskins.com/forums/fw-evidence-john-bokma-67539.html
>
> http://www.google.com/search?q=joh+bokma&rls=com.microsoft:en-zw&ie=UTF-8&oe=UTF-8&startIndex=&startPage=1&rlz=1I7ADFA_enUS453
>
> http://www.facebook.com/j.j.j.bokma
>
> http://www.google.com/search?q=johnbokma.com&rls=com.microsoft:en-zw&ie=UTF-8&oe=UTF-8&startIndex=&startPage=1&rlz=1I7ADFA_enUS453
>
> http://who.godaddy.com/whois.aspx?domain=johnbokma.com&prog_id=GoDaddy
>
>
> http://who.godaddy.com/whois.aspx?k=LbmVCfcKk/FDt2trUlZDFQ==&domain=castleamber.com&prog_id=GoDaddy
>
> Registrant:
> Castle Amber
>
> Lorenzo Barcelata 24
> Indeco Animas
> Xalapa, Veracruz C.P. 91190
> Mexico
>
> Registered through: GoDaddy.com, Inc. (http://www.godaddy.com)
> Domain Name: CASTLEAMBER.COM
> Created on: 10-Dec-97
> Expires on: 09-Dec-11
> Last Updated on: 10-Oct-10
>
> Administrative Contact:
> Bokma, John contact@johnbokma.com
> Castle Amber
> Lorenzo Barcelata 24
> Indeco Animas
> Xalapa, Veracruz C.P. 91190
> Mexico
> +52.12281065636
>
> Technical Contact:
> Bokma, John contact@johnbokma.com
> Castle Amber
> Lorenzo Barcelata 24
> Indeco Animas
> Xalapa, Veracruz C.P. 91190
> Mexico
> +52.12281065636
>
> Domain servers in listed order:
> NS2.SLICEHOST.NET
> NS1.SLICEHOST.NET
> NS3.SLICEHOST.NET
>
> ============================================================================================
> Resume of John Bokma
> Personal Details
> Name: John Bokma
> Date of birth: February 15, 1967
> Email: use contact form
> Languages: Dutch (native), English (fluently)
>
> Summary
> Extensive experience as a programmer with the Perl programming
> language (including OOP) and the Java programming language (including
> J2EE components like: JDBC, servlets/JSP with Tomcat/Apache, and XML
> parsing).
>
> Multiskilled GNU/Linux, and Microsoft Windows. Effective, efficient,
> concise and creative worker. Self-employed as programmer, using
> "Castle Amber" for company name, since 1994.
>
> Strengths
> Creative brainstorming facilitator. Defines the problem. Finds
> practical solutions. Familiar with a wide range of development tools
> and programming languages.
>
> Interests
> Maintaining my personal website / blog Hacking and Hiking in Mexico.
>
> Reading (technical books, science, police procedure, science fiction
> and fantasy), scorpions and other arachnids, hiking.
>
> You can download my resume as a PDF file (105 KB).
If you've got proper documentation, he's not the "only one" around here.
------------------------------
Date: Sat, 22 Oct 2011 18:20:14 -0500
From: John Bokma <john@castleamber.com>
Subject: Re: Registered Child Molester John Bokma (john@castleamber.com, contact@johnbokma.com) johnbokma.com, castleamber.com, johnbokma.com/perl/help-in-exchange-for-books.html Has Met His Match!
Message-Id: <87mxcs3975.fsf@castleamber.com>
Rosemarie Shiver <tired.of.padgett@gmail.com> writes:
Yawn!
--
John Bokma j3b
Blog: http://johnbokma.com/ Perl Consultancy: http://castleamber.com/
Perl for books: http://johnbokma.com/perl/help-in-exchange-for-books.html
------------------------------
Date: Sat, 22 Oct 2011 16:03:29 -0700 (PDT)
From: Rosemarie Shiver <tired.of.padgett@gmail.com>
Subject: Registered Child Molester John Bokma (john@castleamber.com, contact@johnbokma.com) johnbokma.com, castleamber.com, johnbokma.com/perl/help-in-exchange-for-books.html Has Met His Match!
Message-Id: <b64ed6b0-b5e3-4577-95c6-c7ad13b76a3c@c1g2000vbw.googlegroups.com>
This aberrated jackass has been bullying, libeling, and harassing
innocent folks for years, but finally his reign of terror is coming to
a close. My guess is that ICANN and Godaddy would like to know about
his BOGUS registration! This whacko likes dark complected Mexican
boys around seven (7) years old for anal sex!!
Rosemarie Shiver
P.S. Johnnie boy, you are one fucking dumbass! More to CUM unless you
disappear!
http://www.velocityreviews.com/forums/t358011-re-john-bokma-harassment.html
http://www.justskins.com/forums/fw-evidence-john-bokma-67539.html
http://www.google.com/search?q=joh+bokma&rls=com.microsoft:en-zw&ie=UTF-8&oe=UTF-8&startIndex=&startPage=1&rlz=1I7ADFA_enUS453
http://www.facebook.com/j.j.j.bokma
http://www.google.com/search?q=johnbokma.com&rls=com.microsoft:en-zw&ie=UTF-8&oe=UTF-8&startIndex=&startPage=1&rlz=1I7ADFA_enUS453
http://who.godaddy.com/whois.aspx?domain=johnbokma.com&prog_id=GoDaddy
http://who.godaddy.com/whois.aspx?k=LbmVCfcKk/FDt2trUlZDFQ==&domain=castleamber.com&prog_id=GoDaddy
Registrant:
Castle Amber
Lorenzo Barcelata 24
Indeco Animas
Xalapa, Veracruz C.P. 91190
Mexico
Registered through: GoDaddy.com, Inc. (http://www.godaddy.com)
Domain Name: CASTLEAMBER.COM
Created on: 10-Dec-97
Expires on: 09-Dec-11
Last Updated on: 10-Oct-10
Administrative Contact:
Bokma, John contact@johnbokma.com
Castle Amber
Lorenzo Barcelata 24
Indeco Animas
Xalapa, Veracruz C.P. 91190
Mexico
+52.12281065636
Technical Contact:
Bokma, John contact@johnbokma.com
Castle Amber
Lorenzo Barcelata 24
Indeco Animas
Xalapa, Veracruz C.P. 91190
Mexico
+52.12281065636
Domain servers in listed order:
NS2.SLICEHOST.NET
NS1.SLICEHOST.NET
NS3.SLICEHOST.NET
============================================================================================
Resume of John Bokma
Personal Details
Name: John Bokma
Date of birth: February 15, 1967
Email: use contact form
Languages: Dutch (native), English (fluently)
Summary
Extensive experience as a programmer with the Perl programming
language (including OOP) and the Java programming language (including
J2EE components like: JDBC, servlets/JSP with Tomcat/Apache, and XML
parsing).
Multiskilled GNU/Linux, and Microsoft Windows. Effective, efficient,
concise and creative worker. Self-employed as programmer, using
"Castle Amber" for company name, since 1994.
Strengths
Creative brainstorming facilitator. Defines the problem. Finds
practical solutions. Familiar with a wide range of development tools
and programming languages.
Interests
Maintaining my personal website / blog Hacking and Hiking in Mexico.
Reading (technical books, science, police procedure, science fiction
and fantasy), scorpions and other arachnids, hiking.
You can download my resume as a PDF file (105 KB).
------------------------------
Date: Sun, 23 Oct 2011 11:20:26 -0700 (PDT)
From: philkime@kime.org.uk
Subject: Re: Tricky STDERR issue under windows
Message-Id: <9398225.602.1319394026409.JavaMail.geo-discussion-forums@yqp37>
I tested this and it does work with the external library if I add fflush() =
and recompile it. This library is compiled completely separately from the p=
erl module (it's used by an XS module, it isn't part of it) so it uses utte=
rly vanilla C stdio which perl doesn't/can't redefine.
------------------------------
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 3526
***************************************
