More of the usual
Monthly maintenance showed – again – nothing special. Even mail reports are as expected:
PMAS statistics for May
Total messages : 1532 = 100.0 o/o
DNS Blacklisted : 0 = .0 o/o (Files: 0)
Relay attempts : 132 = 8.6 o/o (Files: 31)
Accepted by PMAS : 1400 = 91.3 o/o (Files: 31)
Handled by explicit rule
Rejected : 576 = 41.1 o/o (processed), 37.5 o/o (all)
Accepted : 145 = 10.3 o/o (processed), 9.4 o/o (all)
Handled by content
Discarded : 250 = 17.8 o/o (processed), 16.3 o/o (all)
Quarantained : 94 = 6.7 o/o (processed), 6.1 o/o (all)
Delivered : 335 = 23.9 o/o (processed), 21.8 o/o (all)
No (exceptional amounts of) relay attempts this month.
Had my certificates renewed automatically, without a problem. Just not all on the same day anymore, after skipping a few days due to apparent connections issues a few months back. But as long as it works nicely, it is no problem. Good thing renewal is attempted after 60 days (in the program) so there is a 30 day period to recover if something is broken.
On the content management system
There as been no real progress on the new blog presenter, introduced some time ago. Getting the blogs show the way they are now, as based of WordPress, is a challenge in itself. It means I have to master both Javascript and jquery to get it working, and it uses scripts of WordPress. Of course, I could copy them into my own environment (shouldn’t be a problem since WP is open-source) but even so – the aim is to be independent of WordPress (or any PHP code). Another feature I would like to use is WASD’s ability of a RuntTimeEngine – similar to PHPWASD (for PHP based code) or PYTRE (for Python code). There is an example program provided in the WASD package, I will probably start with a hardcoded, stripped-down basic version to present the pages and extend this by incorporating bits and pieces of flexibility.
However, I’m too much involved in a few other things that need to be done as well, outside programming…