NTP issue – update
From several sides I got information on the NTP problems; John Santos (via OpenVMS SIG) suggested a test for checking whether time was updated, using ntpq (it did) , and Stephen Hoffman showed me where NTPDC is located; but I found that already, and disabled monlist as was suggested – by editing TCPIP$NTP.CONF. Now monlist doesn’t work anymore – not even on localhost (directly), nor does ntpq – runs into a timeout. The router log doesn’t show any more incoming NTP traffic either – what used to be the case when monlist was not disabled. time to dig into the manuals – if available….Enabling monlist – just to be able to do some synchronization – might be a possibility – now incoming traffic to port 123 is disabled….We’ll see.
For the rest, no real surprises:
PMAS statistics for January
Total messages : 1414 = 100.0 o/o
DNS Blacklisted : 0 = .0 o/o (Files: 0)
Relay attempts : 338 = 23.9 o/o (Files: 31)
Accepted by PMAS : 1076 = 76.0 o/o (Files: 31)
Handled by explicit rule
Rejected : 445 = 41.3 o/o (processed), 31.4 o/o (all)
Accepted : 288 = 26.7 o/o (processed), 20.3 o/o (all)
Handled by content
Discarded : 137 = 12.7 o/o (processed), 9.6 o/o (all)
Quarantained : 163 = 15.1 o/o (processed), 11.5 o/o (all)
Delivered : 43 = 3.9 o/o (processed), 3.0 o/o (all)
There have been relay attempts on a few days- on 13-Jan-2014 there were about 100 from one address. Of course these failed.
What goes on behind the doors of the (private) data center