I had seven different versions of Perl on the VM where I build POPFile and managed to pick 819 instead of 820. I've rebuilt with 820, can folks out there test that this actually works on a less screwed up machine than mine!
John.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
RC3 has the same problems as RC2 on my environment (Windows XP SP2).
RC3 for Windows don't work. It requires List::Util perl module which is not included in the installer package.
The class-platform version is working welln on Mac OS X Tiger.
Naoki
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Naoki, I am guessing that you have some Japanese messages in your message history because RC3 is OK on my English Win98SE system. I installed everything using RC3, including Kakasi and SSL, but do not get any complaints about missing Perl Modules.
RC3 is still using the old Kakasi.pm file used in all previous POPFile releases. This file is v1.05 which is 2,591 bytes long and dated 17 December 2000.
However the Perl Package Manager (PPM4) shipped with ActivePerl 5.8.8 Build 820 has installed a newer version of the Kakasi package (v2.04) into my ActivePerl installation.
In this new package, the Kakasi.pm file is 7,845 bytes long and is dated 7 April 2007. (The binary files (auto\Text\Kakasi\Kakasi.dll etc) are the same size as the ones in RC3 but the contents are different.)
Perhaps the problem you have found is because the Kakasi package in RC3 is not compatible with the rest of the minimal Perl in RC3?
I had to make several changes to the installer as a result of upgrading from 5.8.8 Build 819 to 5.8.8 Build 820 so I would not be surprised to find that some more are required in order to get Kakasi working again. But I'll need some help as I don't use Kakasi.
The missing SSL files have not been uploaded to the POPFile web site yet as I need to regain access (all I have managed to do so far is regain CVS access after my recent computer problems).
Brian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This log says that the HTML::Template modules has a problem.
Then, I tried to find out the cause of the problem:
E:\PROGRA~1\POPFile>perl -MHTML::Template -e "print $HTML::Template::VERSION;"
Can't locate List/Util.pm in @INC (@INC contains: E:/PROGRA~1/POPFile/lib .) at
E:/PROGRA~1/POPFile/lib/Scalar/Util.pm line 12.
Compilation failed in require at E:/PROGRA~1/POPFile/lib/HTML/Template.pm line 9
16.
BEGIN failed--compilation aborted at E:/PROGRA~1/POPFile/lib/HTML/Template.pm li
ne 916.
Compilation failed in require.
BEGIN failed--compilation aborted.
(I installed POPFile on the E drive.)
According to this result, Scalar::Util requires List::Util and
the module does not exist.
I have not checked the Text::Kakasi module. I'll check it out.
Naoki
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the Message Capture output - it looks like you were were using a clean install to test RC3. I checked again on my system and it still worked.
Then I noticed you were running without the system tray icon and my RC3 installation was running with the icon. When I disabled the system tray icon I got the same errors as in your report.
My attempt to check the HTML::Template version number also failed as you reported.
Adding the missing List::Util files solved those two problems (I added the binary files for List::Util even though it seemed to work without them).
I'll update CVS to add these files to the minimal Perl. I am also going to make the installer check that the correct version of ActivePerl is available at compile-time.
Brian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
>> I'll update CVS to add these files to the minimal Perl ... [and] make the installer check that the correct version of ActivePerl is available at compile-time <<
Both changes are now in CVS.
Brian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
>> Then I noticed you were running without the system tray icon and my RC3 installation was running with the icon. When I disabled the system tray icon I got the same errors as in your report. <<
When I enabled the system tray icon the problem disappeared. Thanks.
But I don't know why disabling the system tray icon cause an error.
>> Adding the missing List::Util files solved those two problems (I added the binary files for List::Util even though it seemed to work without them). <<
Yes, on my environment, after adding the List::Util module POPFile UI works.
>> I'll update CVS to add these files to the minimal Perl. I am also going to make the installer check that the correct version of ActivePerl is available at compile-time. <<
Thanks.
Naoki
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
>> But I don't know why disabling the system tray icon cause an error. <<
The two system tray programs (popfileib.exe & popfileif.exe) don't bother to check which Perl modules are installed but the other two programs (popfileb.exe & popfilef.exe) use the popfile.pck file to check for some modules and can add some warning messages to the log file.
This is not the first time that "system tray icon" mode has worked better than the other mode.
I guess that deleting or renaming the popfile.pck file would let RC3 run without the system tray icon.
Brian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
>> I had to make several changes to the installer as a result of upgrading from 5.8.8 Build 819 to 5.8.8 Build 820 so I would not be surprised to find that some more are required in order to get Kakasi working again. But I'll need some help as I don't use Kakasi. <<
Kakasi has no problems with RC3. The Kakasi module is same as POPFile v0.22.4's and seems to compatible with ActivePerl build 820.
Although we may need to update the module to v2.04, the current version (v1.05) has no problems with the build 820.
On Mac OS X, I'm using v2.04 of Text::Kakasi.
Naoki
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
>> The missing SSL files have not been uploaded to the POPFile web site yet as I need to regain access (all I have managed to do so far is regain CVS access after my recent computer problems). <<
>> But then the POPFile installer requires the "MD5SUMS" file this time. I couldn't find the file in the CVS. Brian, where is the "MD5SUMS" file, and are there the other files required by the installer? <<
The file is not in CVS. The file is supposed to contain the MD5 sum for every file in the patch directory so I assumed it would be updated whenever the contents of the directory get updated (a bit like the way that the release notes are not in CVS because they are supposed to get updated when a new release is built).
You can use the MD5SUMS file I used to test my code:
It does not matter what EOL the MD5SUMS file uses because the installer can cope with CRLF or LF.
For testing I created MD5SUMS using "md5sum * > MD5SUMS" on my Linux box and I also tried using a Windows program (MD5summer) which creates a slightly different output file. The installer could cope with both formats.
The installer only tries to download two files from the POPFile website: 0.22.x.pcf and MD5SUMS.
Brian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
>> The file is not in CVS. The file is supposed to contain the MD5 sum for every file in the patch directory so I assumed it would be updated whenever the contents of the directory get updated (a bit like the way that the release notes are not in CVS because they are supposed to get updated when a new release is built). <<
>> The installer only tries to download two files from the POPFile website: 0.22.x.pcf and MD5SUMS <<
I must have been half-asleep when I wrote that!
The 0.22.5 installer tries to download THREE files from the POPFile website - I forgot to mention the SSL_pm.pat file.
0.22.x.pcf and MD5SUMS are the new files I added when I updated the installer for 0.22.5; the SSL_pm.pat file has been used by the installer for so long that I forgot to mention it.
Next time I'll try to remember to look at the code before I answer.
Brian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The minimal Perl has changed a lot for the 0.22.5 release.
I don't use POPFile's XMLRPC module so it is possible that the minimal Perl in 0.22.5 RC3 does not include everything needed by that module. It would be a big help if someone could test the XMLRPC features in RC3.
The Start Menu now has a shortcut which makes it very easy to capture any messages complaining about missing Perl components:
>I don't use POPFile's XMLRPC module so it is possible
>that the minimal Perl in 0.22.5 RC3
I use XMLRPC a lot. It was working till 0.22.5 RC1.
You may use this to test: http://www.niconnect.com/POPFile/about.html
Set XMLRPC to port 8081.
It's a file (msg eml gif txt exe etc) analyser. It doesn't matter if ascii or binary.
Just an experiment :-)
BTW, RC2 didn't install.
RC3 installed, but it didn't open Browser Interface. XMLRPC worked well in RC3.
I needed to downgrade to RC1.
A user reported that the SSL module has a problem.
IO::Socket::SSL module seems to OK but POPFile can't connect to the POP3 server via SSL.
Here's the Message Capture log:
------------------------------------------------------------
POPFile Message Capture Utility v0.1.6
------------------------------------------------------------
POPFILE_ROOT = E:\PROGRA~1\POPFile
POPFILE_USER = C:\DOCUME~1\sent\APPLIC~1\POPFile
Using 'popfileif.exe' to run POPFile
------------------------------------------------------------
(report started 02-Jun-2007 @ 14:05:56)
------------------------------------------------------------
POPFile Engine loading
Loading...
{core: windows}
{core: mq history logger config}
{classifier: wordmangle bayes}
{interface: html xmlrpc}
{proxy: pop3}
{services:}
POPFile Engine v0.22.5 starting
Initializing...
{core: config history logger mq windows}
{classifier: bayes wordmangle}
{interface: html xmlrpc}
{proxy: pop3}
{services:}
Starting...
{core: config history logger mq windows}
{classifier: bayes wordmangle}
{interface: html xmlrpc}
{proxy: pop3}
{services:}
POPFile Engine v0.22.5 running
Undefined subroutine &IO::Socket::SSL::SSL_HANDLE::weaken called at E:/PROGRA~1/POPFile/lib/IO/Socket/SSL.pm line 538, <GEN3> line 1.
POPFile Engine v0.22.5 stopping
Stopping...
{classifier: bayes wordmangle}
{core: config history logger mq windows}
{interface: html xmlrpc}
{proxy: pop3}
{services:}
--
The error occurs when a mail client sends "USER mail.example.com:account:ssl" command
to POPFile.
I think the cause of this problem is same as the UI's (which I already reported).
(IO::Socket::SSL module requires Scalar::Util module and Scalar::Util module requires
List::Util module.)
After adding List::Util module (from ActivePerl build 820), the problem disappeared.
Naoki
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You can download and test 0.22.5 here:
http://popfile.sf.net/popfile-0.22.5RC3.zip
http://popfile.sf.net/popfile-0.22.5RC3-windows.zip
I had seven different versions of Perl on the VM where I build POPFile and managed to pick 819 instead of 820. I've rebuilt with 820, can folks out there test that this actually works on a less screwed up machine than mine!
John.
John,
RC3 has the same problems as RC2 on my environment (Windows XP SP2).
RC3 for Windows don't work. It requires List::Util perl module which is not included in the installer package.
The class-platform version is working welln on Mac OS X Tiger.
Naoki
Naoki, I am guessing that you have some Japanese messages in your message history because RC3 is OK on my English Win98SE system. I installed everything using RC3, including Kakasi and SSL, but do not get any complaints about missing Perl Modules.
RC3 is still using the old Kakasi.pm file used in all previous POPFile releases. This file is v1.05 which is 2,591 bytes long and dated 17 December 2000.
However the Perl Package Manager (PPM4) shipped with ActivePerl 5.8.8 Build 820 has installed a newer version of the Kakasi package (v2.04) into my ActivePerl installation.
In this new package, the Kakasi.pm file is 7,845 bytes long and is dated 7 April 2007. (The binary files (auto\Text\Kakasi\Kakasi.dll etc) are the same size as the ones in RC3 but the contents are different.)
Perhaps the problem you have found is because the Kakasi package in RC3 is not compatible with the rest of the minimal Perl in RC3?
I had to make several changes to the installer as a result of upgrading from 5.8.8 Build 819 to 5.8.8 Build 820 so I would not be surprised to find that some more are required in order to get Kakasi working again. But I'll need some help as I don't use Kakasi.
The missing SSL files have not been uploaded to the POPFile web site yet as I need to regain access (all I have managed to do so far is regain CVS access after my recent computer problems).
Brian
Brian,
There's no messages in my history.
Here's the Message Capture log:
------------------------------------------------------------
POPFile Message Capture Utility v0.1.6
------------------------------------------------------------
POPFILE_ROOT = E:\PROGRA~1\POPFile
POPFILE_USER = C:\DOCUME~1\sent\APPLIC~1\POPFile
Using 'popfilef.exe' to run POPFile
------------------------------------------------------------
(report started 12-May-2007 @ 22:16:14)
------------------------------------------------------------
ERROR: POPFile needs Perl module HTML::Template, please install it.
POPFile Engine loading
Loading...
{core: windows}
{core: mq history logger config}
{classifier: wordmangle bayes}
{interface: html}
{proxy: pop3}
{services:}
POPFile Engine v0.22.5 starting
Initializing...
{core: config history logger mq windows}
{classifier: bayes wordmangle}
{interface: html}
{proxy: pop3
A copy of POPFile appears to be running.
Attempting to signal the previous copy.
Waiting 10 seconds for a reply.
The other POPFile (1324) failed to signal back, starting new copy (984)
}
{services:}
Starting...
{core: config history logger mq windows}
{classifier: bayes wordmangle}
{interface: html}
{proxy: pop3}
{services:}
POPFile Engine v0.22.5 running
Can't locate object method "new" via package "HTML::Template" at E:\PROGRA~1\POPFile/UI/HTML.pm line 2825.
------------------------------------------------------------
Status code: 2
------------------------------------------------------------
(report finished 12-May-2007 @ 22:17:31)
------------------------------------------------------------
This log says that the HTML::Template modules has a problem.
Then, I tried to find out the cause of the problem:
E:\PROGRA~1\POPFile>perl -MHTML::Template -e "print $HTML::Template::VERSION;"
Can't locate List/Util.pm in @INC (@INC contains: E:/PROGRA~1/POPFile/lib .) at
E:/PROGRA~1/POPFile/lib/Scalar/Util.pm line 12.
Compilation failed in require at E:/PROGRA~1/POPFile/lib/HTML/Template.pm line 9
16.
BEGIN failed--compilation aborted at E:/PROGRA~1/POPFile/lib/HTML/Template.pm li
ne 916.
Compilation failed in require.
BEGIN failed--compilation aborted.
(I installed POPFile on the E drive.)
According to this result, Scalar::Util requires List::Util and
the module does not exist.
I have not checked the Text::Kakasi module. I'll check it out.
Naoki
Naoki,
Thanks for the Message Capture output - it looks like you were were using a clean install to test RC3. I checked again on my system and it still worked.
Then I noticed you were running without the system tray icon and my RC3 installation was running with the icon. When I disabled the system tray icon I got the same errors as in your report.
My attempt to check the HTML::Template version number also failed as you reported.
Adding the missing List::Util files solved those two problems (I added the binary files for List::Util even though it seemed to work without them).
I'll update CVS to add these files to the minimal Perl. I am also going to make the installer check that the correct version of ActivePerl is available at compile-time.
Brian
>> I'll update CVS to add these files to the minimal Perl ... [and] make the installer check that the correct version of ActivePerl is available at compile-time <<
Both changes are now in CVS.
Brian
Brian,
>> Then I noticed you were running without the system tray icon and my RC3 installation was running with the icon. When I disabled the system tray icon I got the same errors as in your report. <<
When I enabled the system tray icon the problem disappeared. Thanks.
But I don't know why disabling the system tray icon cause an error.
>> Adding the missing List::Util files solved those two problems (I added the binary files for List::Util even though it seemed to work without them). <<
Yes, on my environment, after adding the List::Util module POPFile UI works.
>> I'll update CVS to add these files to the minimal Perl. I am also going to make the installer check that the correct version of ActivePerl is available at compile-time. <<
Thanks.
Naoki
>> But I don't know why disabling the system tray icon cause an error. <<
The two system tray programs (popfileib.exe & popfileif.exe) don't bother to check which Perl modules are installed but the other two programs (popfileb.exe & popfilef.exe) use the popfile.pck file to check for some modules and can add some warning messages to the log file.
This is not the first time that "system tray icon" mode has worked better than the other mode.
I guess that deleting or renaming the popfile.pck file would let RC3 run without the system tray icon.
Brian
Brian,
>> I had to make several changes to the installer as a result of upgrading from 5.8.8 Build 819 to 5.8.8 Build 820 so I would not be surprised to find that some more are required in order to get Kakasi working again. But I'll need some help as I don't use Kakasi. <<
Kakasi has no problems with RC3. The Kakasi module is same as POPFile v0.22.4's and seems to compatible with ActivePerl build 820.
Although we may need to update the module to v2.04, the current version (v1.05) has no problems with the build 820.
On Mac OS X, I'm using v2.04 of Text::Kakasi.
Naoki
>> Kakasi has no problems with RC3. The Kakasi module is same as POPFile v0.22.4's and seems to compatible with ActivePerl build 820. <<
Thanks for checking this.
Brian
Brian,
>> The missing SSL files have not been uploaded to the POPFile web site yet as I need to regain access (all I have managed to do so far is regain CVS access after my recent computer problems). <<
I've copied 0.22.x.pcf file from the CVS branch to the POPFile web site:
http://popfile.sourceforge.net/ssl-patch/0.22.x.pcf
But then the POPFile installer requires the "MD5SUMS" file this time.
I couldn't find the file in the CVS.
Brian, where is the "MD5SUMS" file, and are there the other files required by the installer?
Naoki
>> But then the POPFile installer requires the "MD5SUMS" file this time. I couldn't find the file in the CVS. Brian, where is the "MD5SUMS" file, and are there the other files required by the installer? <<
The file is not in CVS. The file is supposed to contain the MD5 sum for every file in the patch directory so I assumed it would be updated whenever the contents of the directory get updated (a bit like the way that the release notes are not in CVS because they are supposed to get updated when a new release is built).
You can use the MD5SUMS file I used to test my code:
http://www.sugelan.co.uk/popfile/ssl-patch/MD5SUMS
It does not matter what EOL the MD5SUMS file uses because the installer can cope with CRLF or LF.
For testing I created MD5SUMS using "md5sum * > MD5SUMS" on my Linux box and I also tried using a Windows program (MD5summer) which creates a slightly different output file. The installer could cope with both formats.
The installer only tries to download two files from the POPFile website: 0.22.x.pcf and MD5SUMS.
Brian
Brian,
>> The file is not in CVS. The file is supposed to contain the MD5 sum for every file in the patch directory so I assumed it would be updated whenever the contents of the directory get updated (a bit like the way that the release notes are not in CVS because they are supposed to get updated when a new release is built). <<
Thanks for the information.
I've created MD5SUMS file on the SF.net shell:
http://popfile.sourceforge.net/ssl-patch/MD5SUMS
And I've uploaded SSL_pm.pat from CVS.
The installer seems to be satisfied.
Naoki
>> The installer only tries to download two files from the POPFile website: 0.22.x.pcf and MD5SUMS <<
I must have been half-asleep when I wrote that!
The 0.22.5 installer tries to download THREE files from the POPFile website - I forgot to mention the SSL_pm.pat file.
0.22.x.pcf and MD5SUMS are the new files I added when I updated the installer for 0.22.5; the SSL_pm.pat file has been used by the installer for so long that I forgot to mention it.
Next time I'll try to remember to look at the code before I answer.
Brian
The minimal Perl has changed a lot for the 0.22.5 release.
I don't use POPFile's XMLRPC module so it is possible that the minimal Perl in 0.22.5 RC3 does not include everything needed by that module. It would be a big help if someone could test the XMLRPC features in RC3.
The Start Menu now has a shortcut which makes it very easy to capture any messages complaining about missing Perl components:
Start -- Programs -- POPFile -- Support -- Message Capture utility
Brian
Brian,
>I don't use POPFile's XMLRPC module so it is possible
>that the minimal Perl in 0.22.5 RC3
I use XMLRPC a lot. It was working till 0.22.5 RC1.
You may use this to test:
http://www.niconnect.com/POPFile/about.html
Set XMLRPC to port 8081.
It's a file (msg eml gif txt exe etc) analyser. It doesn't matter if ascii or binary.
Just an experiment :-)
BTW, RC2 didn't install.
RC3 installed, but it didn't open Browser Interface. XMLRPC worked well in RC3.
I needed to downgrade to RC1.
HTH,
Adrian Nicolaiev
http://www.niconnect.com
>> RC3 installed, but it didn't open Browser Interface <<
I made a mistake in the minimal Perl which means the UI does not work if you run POPFile without the system tray icon.
If you enable the system tray icon then the UI should work (though there may still be things that do not work properly)
>> You may use this to test <<
Thnaks for the link, I will try testing XMLRPC on my system
Brian
Brian,
>> It would be a big help if someone could test the XMLRPC features in RC3. <<
I've tested the RC3's XMLRPC interface with Joseph's xmltraintest.py on Windows XP SP2 and it worked.
xmltraintest.py:
http://popfile.jciv.com/xmltraintest.html
And Nicolaiev's POPFile File Analyser also worked well.
POPFile File Analyser:
http://www.niconnect.com/POPFile/about.html
I think there's no problems with the XMLRPC feature.
Naoki
A user reported that the SSL module has a problem.
IO::Socket::SSL module seems to OK but POPFile can't connect to the POP3 server via SSL.
Here's the Message Capture log:
------------------------------------------------------------
POPFile Message Capture Utility v0.1.6
------------------------------------------------------------
POPFILE_ROOT = E:\PROGRA~1\POPFile
POPFILE_USER = C:\DOCUME~1\sent\APPLIC~1\POPFile
Using 'popfileif.exe' to run POPFile
------------------------------------------------------------
(report started 02-Jun-2007 @ 14:05:56)
------------------------------------------------------------
POPFile Engine loading
Loading...
{core: windows}
{core: mq history logger config}
{classifier: wordmangle bayes}
{interface: html xmlrpc}
{proxy: pop3}
{services:}
POPFile Engine v0.22.5 starting
Initializing...
{core: config history logger mq windows}
{classifier: bayes wordmangle}
{interface: html xmlrpc}
{proxy: pop3}
{services:}
Starting...
{core: config history logger mq windows}
{classifier: bayes wordmangle}
{interface: html xmlrpc}
{proxy: pop3}
{services:}
POPFile Engine v0.22.5 running
Undefined subroutine &IO::Socket::SSL::SSL_HANDLE::weaken called at E:/PROGRA~1/POPFile/lib/IO/Socket/SSL.pm line 538, <GEN3> line 1.
POPFile Engine v0.22.5 stopping
Stopping...
{classifier: bayes wordmangle}
{core: config history logger mq windows}
{interface: html xmlrpc}
{proxy: pop3}
{services:}
POPFile Engine v0.22.5 terminated
------------------------------------------------------------
Status code: 0
------------------------------------------------------------
(report finished 02-Jun-2007 @ 14:26:59)
------------------------------------------------------------
--
The error occurs when a mail client sends "USER mail.example.com:account:ssl" command
to POPFile.
I think the cause of this problem is same as the UI's (which I already reported).
(IO::Socket::SSL module requires Scalar::Util module and Scalar::Util module requires
List::Util module.)
After adding List::Util module (from ActivePerl build 820), the problem disappeared.
Naoki