NethServer Version: NS7
I’ve now been running the new EMail2 for around 24 hours and wanted to share a couple of the anomalies I’ve found so far.
Basically I mainly run the POP3 Proxy to retrieve emails, for multiple accounts, from my external email provider. There is a machine in my local network that also can send emails directly to NS. There is a local service on NS that also sends out emails, plus as part of the test, I also sent myself emails directly to NS from a couple of external accounts.
Here first is the history report:
OK, so what am I seeing that I think is wrong.
Most, but strangely not all, the emails sent directly to NS appear in the report twice, highlighted in red.
Next, the emails highlighted under the Action column are all being delivered to my Windows mail client without modification:
Even when it really shouldn’t have:
The status is showing greylisted items:
But they are not listed in the history. Also, I have no idea what they might be, as apart from the emails I deliberately sent direct to NS all other emails were retrieved via POP3, where greylisting shouldn’t be invoked.
It looks like p3scan has not quite handed over total responsibility to rspamd for classifying incoming emails:
I’m seeing hundreds of error messages flooding the logs:
Mar 10 16:38:20 Nethserver rspamd: <e1e5b7>; csession; rspamd_controller_check_password: allow unauthorized connection from a trusted IP 127.0.0.1
Mar 10 16:38:21 Nethserver rspamd: <08e2a6>; csession; rspamd_controller_check_password: allow unauthorized connection from a trusted IP 127.0.0.1
The other issue I spotted was in regard to the statistics of messages scanned/clean/greylisted/etc. but I think that was probably caused by the redis issue I reported in the other thread.
I still have copies of all the emails highlighted in this report, should any more information be required.
BTW This is not meant to be a negative thread against this new feature. I, personally, think it’s a fantastic effort and thanks are due to all the folks who contributed to it.