03-Mar-2013

Maintenance
Nothing strange….
Except it has been quiet on the SPAM front:
PMAS statistics for February
Total messages    :   2482 = 100.0 o/o
DNS Blacklisted   :    740 =  29.8 o/o (Files: 28)
Relay attempts    :     28 =   1.1 o/o (Files: 28)
Accepted by PMAS  :   1714 =  69.0 o/o (Files: 28)
 Handled by explicit rule
        Rejected :   1120 =  65.3 o/o (processed),  45.1 o/o (all)
        Accepted :    232 =  13.5 o/o (processed),   9.3 o/o (all)
 Handled by content
       Discarded :     86 =   5.0 o/o (processed),   3.4 o/o (all)
    Quarantained :    239 =  13.9 o/o (processed),   9.6 o/o (all)
       Delivered :     37 =   2.1 o/o (processed),   1.4 o/o (all)
Also, there were just a few relay attempts: there were some but none of the files where these are logged, exceeded 4 blocks in size.
Weird, though, is the number of messages on port can (blocked by the router) that seem to be originated by the VMS server; apart from messages on port 53 (BIND). there are similar messages from a load of other, high-numbered ports to the same address that BIND seems to access on port 53. There is no reason why these addresses would be accessed, I don’t find them in any other logfile.
I didn’t see these before because I left them out of the SYSLOG signaling, and I included that last Thursday.
Some more tests on WordPress
I reversed parameter max_execution_time in PHP.INI back to its default of 30 seconds, and included the mapping definitions that are required to show images and stylesheets. Now the normal page comes up nicely, and rather fast, but the admin pages remain a problem: there is an error that causes an error so the admin page does not show up directly; the URL in the browser is updated, so it is happening within wp-admin/index.php. However, directly accessing this file – by using the spec in the browser address window, the pages show up nicely, though the widgets don’t: “Incoming Links” show the infamous “IO error” message on cron.php – though I have no proof that there are over 512 channels opened – and the other ones: “Plugins”, “WordPress blog” and “Other WordPress News” are stopped because the maximum execution time has expired – in different locations. These are accesses to external locations from within the PHP code, WATCH doesn’t show these accesses!
Though I have created replies to the WASD mailing list, something seems to have gone wrong: the list does not include the last mails…..