Mail in error
For some reason, NOT ANY message has been received for over a day – not even quarantined or discarded. This is pretty weird, so I took a look and found that PMAS has gone into a “DNS-blacklist ALL” mode. Mail sent from my GMAIL account – that normally would arrive – was blocked as well. Even when I explicitly allowed al mail from gmail.com, of any account from that domain, mail sent from gmail was blocked:
Delivery to the following recipient failed permanently:
(my address)
Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the server for the recipient domain grootersnet.nl by mail.grootersnet.nl. [82.161.236.244].The error that the other server returned was:
554 5.7.0 Address (209.85.223.196) blacklisted (2)
(this was after I disabled the first entry in the configuration).
In order to receive mail – even spam that would otherwise be rejected, discarded or quarantined – I disabled PMAS by opening port 25 and remove the forwarding on port 25 to port 2525 – the one that PMAS listens on. Now mail arrived so it definitively was a PMAS issue. But what cuased it could not be determined.
A few days ago, I downloaded that latest version (PMAS032-050) from Process; I went there after I found I couldn’t create reports for this year and Hunter gracefully admitted he made a mistake and set a new file available – and with this access, I also retrieved this latest version.
I installed it in the right location, moved files (configuration, spam database, log files and statistics database) and restarted PMAS. Now al seems to be in working order again. Just have to copy what’s been quarantined and discarded.
Throttle redefined
The problems I encountered a few days ago: overload to PHP_WASD processes, made Mark Daniel propose another setting. So I have taken some precautions, so the amount of accesses to the blogs is now limited, and hopefully wide enough for normal use, and tight enough to prevent system exhaustion. I’ll monitor this for a few days: you may encounter 503-errrors: stating the service is not available, or some limit is reached. Big abusers may be locked out on a more permanent basis: I now know how to do that 🙂