I have noticed since updating cPanel to the latest build, that Mailscanner Frontend no longer seems to see spamassassin the same way. Spam scanning is continuing, but when running a --lint test, Mailwatch can not properly run the command due to the non-existance of spamassassin.
I had to create a symlink to sa-learn just so that the Bayes Database output would work... but a *lot* of mail is...
Though it seems that MailScanner FE and MailQueues are functioning behind the scenes, the front-end in WHM is failing with the new version installed.
I get:
Internal Server Error
500
No response from subprocess (/usr/local/cpanel/whostmgr/docroot/cgi/addon_mailscanner.cgi) with exit signal: 2
cpsrvd/11.36.0.2 Server at server.rockoids.net
I presume you're aware of what you have to do about...
If I enabled Spamassassin via TweakSettings in WHM, would this cause errors in any of your utilities: mailscanner, scf, cxf and so on?
The reason I ask, the new version of cPanel now includes new rule features in cPanel ---> User Level and Account Level filtering. These new rule features are called Spam Status, Spam Bar and Spam Score. So if Spamassassin is off in TweakSettings, then when...
i would like to know if is possible to stop to verify the Spam and viruses for internal email? The problem is that i´m losing many emails from internal domains, or for same domain too, and this emails not appear on the MailWatch.
Having an issue with a client sending email (via DirectPC) which happens to be blacklisted (no option of getting a new IP or getting unlisted),,, But here is the issue, according to Mail Watch not all of their email is getting flagged as blacklisted.
Under the Received Via: the RBL is NOT marked, but in the SpamAssassin area, Listed in RBL: is marked with a Y ...
Hello, I'm trying to block notification+zrdo6pzre=gz@facebookmail.com in the Server Spam Blacklist window in the Frontend but it seems it's not being saved, the window is always empty. Can someone verify this?
I am assuming (hoping) that the option to forward spam to spam at domain dot com really means forward to spam at realhosteddomain, i.e. that a hosting customer who is hosting thisisnotarealdomain dot com can create a spam at thisisnotarealdomain dot com mailbox, choose the option to forward to spam at domain dot com, and then messages detected as spam by MailScanner will be forwarded to spam at...
Your tool for the firewall has that great option of having a cluster information. It would be great if you had this option for mailscanner, so that our servers could share the spam information.
Unsure if this is a Mailscanner FE / Mailscanner topic, so I've gone for FE as this is where the logs were :)
I've just been reviewing my Mailscanner FE - MailWatch logs, and found an entry that is spam whitelisted from one of my domains in MailWatch:
myserver is my email server
oneofmydomains is, well one of my domains :)
Message Headers:
Received: from dsl-243-50-76.telkomadsl dot...
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum