[Resolved] SpamCop Reporting Not Arriving at SpamCop

[Firewalls4Life]

I registered an account with SpamCop.net to use the custom email address for reporting Spam received by my server to the SpamCop.net service.

I entered my SpamCop address into the settings at "Mail Scanner Front-End >> MailControl UI Settings >> SpamCop Reporting (If you have an email address to forward spam to SpamCop you can list it here to have new options added to the UI)";

This now exposes the new user interface button in MailControl view to "Report to SpamCop". I can select a spam message and choose to report it, but it does not appear to actually send off the email or arrive at SpamCop.

Manually pasting in headers and message bodies at SpamCop works, however I do not see any error messages or diagnostics from MailScanner Front End in MailControl when reporting the message to SpamCop.

[Firewalls4Life]

Tailing the Exim main log shows me this error.

Code: Select all

# tail -f /var/log/exim_mainlog
2018-11-24 16:38:05 SMTP connection from [127.0.0.1]:57608 (TCP/IP connection count = 1)
2018-11-24 16:38:05 TLS error on connection from localhost (myserver.mydomain.tld) [127.0.0.1]:57608 (SSL_accept): error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol
2018-11-24 16:38:05 SMTP connection from localhost (myserver.mydomain.tld) [127.0.0.1]:57608 closed by EOF

[Firewalls4Life]

I had to follow the instructions here to get it to work; lowering the protocol compatibility to older versions and using weaker ciphers. I'm not happy with that. Can we have the script updated to use newer better protocols and ciphers? ie: TLS 1.2, 1.3, and better ciphers?

https://forums.cpanel.net/threads/outlo ... st-2498287

[ForumAdmin]

We'll have a fix for this in the next release of MSFE, the issue is with the cpan perl module being used to forward emails. Other methods are fine as they do not use that module.

[Firewalls4Life]

Excellent. Thank you for the update

[Firewalls4Life]

I wanted to confirm after installing the update v8.20 today that the issue is now resolved. I reverted the changes to the Exim protocols and ciphers to get back to a more secure setup.