Worpress update
First action today was an update of WordPress, top version 4.2.9. I could of course do the normal stuff first, but since the EU regulation of data protection has been activated on may 25th, and being an EU citizen, I may be obliged to be compliant and tell you (no matter where you reside) what I do with your data, and why, and – more or less – how. Rest assured: I never have, and never will, share data with others except there is a suspicion of abuse, or an official, legal request to hand over your data – no matter what. Anyway, I changed the page that WordPress hands over as a default.
That is: for this blog, to begin with. The other ones will have a similar page. Since it’s in the database, I will have to copy the contents – or I create one in a generic place and refer to that one.
Maintenance.
Well, the normal stuff. No surprises, as you may expect.
PMAS statistics for May
Total messages : 2978 = 100.0 o/o
DNS Blacklisted : 0 = .0 o/o (Files: 0)
Relay attempts : 218 = 7.3 o/o (Files: 31)
Accepted by PMAS : 2760 = 92.6 o/o (Files: 31)
Handled by explicit rule
Rejected : 2030 = 73.5 o/o (processed), 68.1 o/o (all)
Accepted : 176 = 6.3 o/o (processed), 5.9 o/o (all)
Handled by content
Discarded : 287 = 10.3 o/o (processed), 9.6 o/o (all)
Quarantained : 237 = 8.5 o/o (processed), 7.9 o/o (all)
Delivered : 30 = 1.0 o/o (processed), 1.0 o/o (all)
It is just on 12-May-2018 that there have bee relay attempts from an address hosted by Hostwind.com (23.254.215.49), between
12-MAY-2018 03:10:05.60 and 03:13:08.59 (193 attempts), sending for a bogus user on my domain, to a gmail account that has bee attempted several times before (1029mandaditos@gmail.com). Of course Hostwinds.com has (again) be notified and the network will be blocked (I think it already was – but it may be made a mistake there).
However, there is another problem arising I cannot handle: mail sent using my email address (faked) as sender or as reply-to address. At times I receice messages from postmasters from everywhere in the world that a message cannot be delivered because the recipient does not exist, mailbox is fuill or whatever reason there may be. Luckily I have an easy proof that such a message cannot be sent by me; this page Is still valid.
Signalling on smartphone/font>
Something I am thinking of for quite some time: Signalling of whatever is needed, on my smartphone – and, if possible, a (limited) set of commandprocedures I can start from the same device. Started this – I have Mosquitto (MQTT broker) running on Daphne, and code to send (and receive) messages: thinks to Brett Cameron. I wonder if he took his sources from GitHub – I got them from there – so I’ll ask him if there is any change I should incorporate; but since this one works, I can start with this version. Hopefully i’ll be noted earlier of relay attempts so I can notify Hostwinds at that very moment…
Database problems – again
It has bee quite on this for a while, but I’m plagues with “Connection lost” errors at this moment – each time I edited this page, the connection to the database is lost – and reconnection seems to be failing…