Some versions of ActivePerl Builds 5xx and 6xx had Bugs that caused empty
strings to be returned when reading a live from an open socket - for
example.
This only happens when perl is used as a ISAPI-DLL. The DLL never unloads
and so, the socket-resources are getting smaller and smaller, everytime it's
used. After a more or less long time, perl will return empty strings here:
$test = <OPENSOCKET>;
Mail::Sender only does a $response =~ /^[45]/ to check if there was an error
(but '' =~ /^[45]/ is false ! so no error ?)
I corrected some bugs in Mail::Sender - it's now v0.7.07.
For example SendEx($a) modified the value of $a in v0.7.05. and $a would
contain unexpected \r in further use.
Mail::Sender now checks for /^220/ when connecting to the SMTP-Server which
should make Mail::Sender report an Error in case of Empty-Responses.
Attached to this Mail is Sender.pm v0.7.07
You should update to the latest 5xx-Build or 6xx-Build.
They don't seem to have the described error (my script is running for months
now).
Have phun :-)
----- Original Message -----
From: "Bill -=Vuud=- Chmura" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, September 30, 2000 5:34 AM
Subject: Another Mail::Sender Problem
This is a wierd problem.
I had a script that uses Mail::Sender running fine on a hosting server. It
was mailing me the log file every night. Works fine.
One friday night I get the last log I will see from this script.
Since then, nothing. I run it manually, and it completes fine - no errors,
no nothing, but no email with a log file. I tried to send it to many
different IP addresses, used many SMTP servers. I also tried the sendmail
command line and that works fine.
The ISP denies making any changes to the box, all the modules are there, I
touched nothing.
Has anyone had a mystery like this?
Thanks - and have a nice day
Sender.pm
