02-Dec-2008

Software port blog
Read on the OpenVMS ITRC: John Apps and Brett Cameron took a task on their shoulders in porting an OpenSource messaging suite to OpenVMS. It’s named (Open)AMQP and they will keep you informed on the blog on this project.
It’s an interesting piece of work, given the pricing op BEA MQ (the former Digital Message Queue) and IBM’s Websphere MQ. It would be a nice addition to the OpenVMS portfolio – but alas, I’m lacking time to get into it at this moment. But if you are, this blog also contains links where to get the documentation and kits.

01-Dec-2008

Monthly maintenance
Housekeeping is one of those jobs that needs to be done. “Cleaning the mess”. Not yet automated…Well, that’s life.

Mail statistics

The over-all number has been decreasing over the last months, I learned that a hosting site from where lots of spam originated, was isolated fby ISP’s. This may well be a cause of less spam.
November is no exception:

PMAS statistics for November
Total messages    : 3271 = 100.0 o/o
DNS Blacklisted   : 2308 =  70.5 o/o (Files: 30)
Relay attempts    :  109 =   3.3 o/o (Files: 30)
Processed by PMAS :  854 =  26.1 o/o (Files: 30)
        Discarded :  287 =  33.6 o/o (processed),   8.7 o/o (all)
     Quarantained :  227 =  26.5 o/o (processed),   6.9 o/o (all)
        Delivered :  340 =  39.8 o/o (processed),  10.3 o/o (all)

There has been a site that has tried to login as “Administartor” over 2000 times in a few hours. It orginates from a .cn domain. Of course it failed because this is no Windows box – and this site has been banned from the system as a suspected intruder. I leave it that way 😉

There have been the ususal attempts to tamper the site, thinking it is Windows- or Linux based AND using default installations. The ususal stuff, but not that much… And the often repeating /w00tw00t.at.ISC.SANS.DFind:) stuff shows up again, more than the last weeks – again, without result.
PHP
I’m more concerned on the PHP trouble, that seems to concentrate now to PCRE not buildt with UTF-8 support. Some could be bypassed by changing one OPTION record: BLOG_CHARSET set to something else than “UTF-8”, but in other places, the test is omitted and that causes problems as well. I’ll have to find out where this test is needed before ver getting into UTF-8 translation, and see what trouble may arise from there. Or do a rebuild of PHP_SHR after having compiled PCRE – the routine dealing with regular expressions – with UTF-8 support. Quite a job since I’ll have to figure out the full logical environment and see if all required files are present.
Or, like Robert Atkinson replied on the WASD mailing list:

“Just another one to add to the “Why can’t HP release a fully functional, recent version of PHP?” list.”

Changing the PHP code is easier, I think. And quicker.