All the same
No surprises. Mail as usual:

PMAS statistics for January
Total messages    :   2115 = 100.0 o/o
DNS Blacklisted   :      0 =    .0 o/o (Files:  0)
Relay attempts    :    521 =  24.6 o/o (Files: 31)
Accepted by PMAS  :   1594 =  75.3 o/o (Files: 31)
  Handled by explicit rule
         Rejected :    932 =  58.4 o/o (processed),  44.0 o/o (all)
         Accepted :    174 =  10.9 o/o (processed),   8.2 o/o (all)
  Handled by content
        Discarded :    279 =  17.5 o/o (processed),  13.1 o/o (all)
     Quarantained :    173 =  10.8 o/o (processed),   8.1 o/o (all)

and two days with more than usual relay attempts – magain from hosts at hostwinds.com, trying to relay using a bogus sender at my domain to the very same gmail-account:

13-JAN-2019 11:47:15.99 - 11:52:11.83 (242)    emailshop@grootersnet.nl to 1029mandaditos@gmail.com
27-JAN-2019 11:11:48.64 - 11:15:54.46 (231)   emailshop@grootersnet.nl to 1029mandaditos@gmail.com

The subnet is now denied access – in the router.

Trips, Tracks and Travels update
I’m working on the report on our Madeira trip last April; Images have been worked upon, and are all ready, placed in the final destination for publishing, noying yhrit location on GoogleEarth output is ab , and the August trip to Austria is next – taking less time, I hope.

I NEED TO CHECK ON THE PERFORMANCE. It is getting worse and worsen and I don’t have a clou what causes the delays, losing connection with the database…I suspect MariaDB, or PHP (older version which _should_ work, as it always has… Restarting MariaDB makes a difference.


Update to WASD
Checking the WASD server log las week, I noted that WASD had silently crashed and restarted several times since last update:
-HTTPD-F-WHEN, 12-DEC-2018 19:32:30.98
-HTTPD-F-WHERE, module:VM line:939
-HTTPD-F-WHAT, lib$get_vm()
%HTTPD-F-EXIT, 12-DEC-2018 19:32:31, WASD:80 %X10158264
-HTTPD-F-TRACE, 0000000000239F74
-HTTPD-F-TRACE, 0000000000388658
-HTTPD-F-TRACE, 00000000001B8398
-HTTPD-F-TRACE, 00000000001A1CDC
-HTTPD-F-TRACE, 0000000000264784
-HTTPD-F-TRACE, 0000000000262F74
(all requests that were loaded at that time, or last 100?)
$ httpd /priority=4 /SYSUAF=RELAXED
WASD VMS Web Services, Copyright (C) 1996-2018 Mark G.Daniel.
This package (all associated programs), comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it under the
conditions of the GNU GENERAL PUBLIC LICENSE, version 3, or any later version.
%HTTPD-I-IMAGE, HTTPD_SSL 11.3.0 09-DEC-2018 19:04:04.31 $116$DKA100:[WEB.WASD_ROOT.][AXP]HTTPD_SSL.EXE
%HTTPD-I-STARTUP, 12-DEC-2018 19:32:47
%HTTPD-I-ALIGN, start collecting alignment faults (64kB,128,0xFFFFFFF0)
%HTTPD-I-SYSTEM, AlphaServer DS10 617 MHz VMS V8.4
%HTTPD-I-TCPIP, HP TCPIP$IPC_SHR V5.7-ECO5 (08-NOV-2014 13:06:10.02)
%HTTPD-I-ODS5, supported by Alpha VMS V8.4
%HTTPD-I-ODS, directory parser enabled
%HTTPD-I-GMT, +00:00
%HTTPD-I-INSTANCE, supervisor
%HTTPD-I-GZIP, using LIBZ_SHR32 V1.2.3
%HTTPD-I-GBLSEC, existing global section of 32 page(let)s

Noted Mark Daniels, he supplied a set of sources that have been updated due to other and this issue, got these, installed them, recompiled the server and installed it (version 11.3.0a).

See if the issue is solved, during the next weeks.


New Year cleanup
2018’s last mail statistics:

PMAS statistics for December
Total messages  :  2269 = 100.0 o/o
DNS Blacklisted  :   0 =  .0 o/o (Files: 0)
Relay attempts  :  270 = 11.8 o/o (Files: 31)
Accepted by PMAS :  1999 = 88.1 o/o (Files: 31)
 Handled by explicit rule
     Rejected :  1374 = 68.7 o/o (processed), 60.5 o/o (all)
     Accepted :  142 =  7.1 o/o (processed),  6.2 o/o (all)
 Handled by content
    Discarded :  289 = 14.4 o/o (processed), 12.7 o/o (all)
   Quarantained :  169 =  8.4 o/o (processed),  7.4 o/o (all)
    Delivered :   25 =  1.2 o/o (processed),  1.1 o/o (all)

Just one day with a larger amount of relay attempts – as usual, it seems, using bogus grootersnet.nl senders from Hostwinds.com, trying to reach that single gmail address:

14-DEC-2018 01:03:27.69 - 01:07:32.90 (242 entries) from

All files that were created in 2018 have now been moved to their archive directory, ready to be stored offline.

Blocked sites
The last few weeks there is a new spammer on the block, sending via, or from, Amazon AWS servers. Also, some AWS connections were trying to access the webserver with over 50 connections, port by port. What I found out in the logfiles, have now been blocked in the router, in order to block that type of applications altogether, when arriving via Amazon.

This has been done with quite a number of sites last year, causing a significant drop in spam messages, but the router could be quite busy when these sites try to get in continuously. The plan is to notify these (otherwise well-behaving) providers that their systems are used by ill-behaving clients, but whether that will prevent problems remains to be seen.

DHCP trouble
Last week, I tried to cleanup DHCP a bit, because there should be one address for most services: the cluster alias. But where this works fine, it made the DHCP server non-responsive. No errors, no logging, it just didn’t react on requests. So I revered one or two settings to be Diana, and now it does work again… In retrospect, I may have known: the default location of the protocol-environment is SYS$SYSDEVICE:[TCPIP$DHCP] where other services reside on SYS$SPECIFIC:.


Done some updates.
WASD and ALAMODE – which is related to WASD – have been upgraded to the latest version: 11.3, which includes OpenSSL 1.1.1a – and by that, TLS 1.3.
No issues here except that once again, the server wasn’t stopped when I restarted WASD. I created a small script that takes care of stopping the current server and start the new one – once the files are copied to the right directory; WASD upgrade does this, but ALAMODE needed to be relocated by hand: of course, now part of this script.
Second, I did an upgrade of the current theme (twenty-seventeen) and installed a plugin to have some control over the layout; I could do the same by changing the CSS file but this plugin offers more flexibility and control – and changes the right things. At least, once payed a (small) fee. However, done that causes the server to crash on one position in system space, though the virtual address is different; Also it happens in different scripts. This is an older version of PHP, maybe that could cause the problem – seen how a newer version behaves (7.2 will be installed as well, nice test).

But the seven day trial seemed to have done the job also. Tomorrow I’ll try PHP 7.2 (found the reason why other versions didn’t work because of “ident mismatch”…), it should work, and improve performance because it caches pages. We’ll see. If the problem with the plug-in is not solved, I’ll ask a refund.

And WordPress 5.0 has arrived – time to give it a try first.


Just the usual
No surprises – except that the number of emails given by the reporting script seems a bit low:

PMAS statistics for November
Total messages    :   3032 = 100.0 o/o
DNS Blacklisted   :      0 =    .0 o/o (Files:  0)
Relay attempts    :    515 =  16.9 o/o (Files: 30)
Accepted by PMAS  :   2517 =  83.0 o/o (Files: 30)
  Handled by explicit rule
         Rejected :   1853 =  73.6 o/o (processed),  61.1 o/o (all)
         Accepted :    134 =   5.3 o/o (processed),   4.4 o/o (all)
  Handled by content
        Discarded :    306 =  12.1 o/o (processed),  10.0 o/o (all)
     Quarantained :    188 =   7.4 o/o (processed),   6.2 o/o (all)
        Delivered :     36 =   1.4 o/o (processed),   1.1 o/o (all)

No idea why – perhaps last reboot has to do with it.

Apart from thet, just the usual relay- attempts, by”someone”@grootersnet.nl to 1029mandaditos@gmail.com

5-NOV-2018 09:05:48.34 to 09:10:07.29 (230) from
23-NOV-2018 14:12:24.43 to 14:18:10.86 (234) from

There is something in the firewall that still allows these addresses (from Hostwinds.com) to the server. I have blocked them but I must have missed something…

Since Mark Daniel mentioned a new version of WASD (11.3), this will be installed some time this weekend. It may also be the moment to get on with later versions of PHP, but that will be after the update proved to be Ok.

And, as you will have noted, I changed theme :). Some updates will be done as well (an update, adding a few plugins to customize (and emove obsolete ones).
WP 5.0 is due to be released but I’ll test it before updating the blogs – there are quite a few changes in maintaining them.