ConfigServer Community Forum

Lineikosen wrote:You can increase the PT_USERMEM limit. By setting the value of PT_USERMEM to a higher value than 200 may help you.

It's already set to 400 although I don't see how this will help the false reporting?

Regards

Neil

I've followed the advice in this post however I'm still getting reports like: Time: Tue Oct 18 07:04:10 2016 +0100 Account: mailman Resource: Process Time Exceeded: 185573 > 1800 (seconds) Executable: /usr/bin/python Command Line: /usr/bin/python /usr/local/cpanel/3rdparty/mailman/bin/qrunner --runn...

Yes, the filename.rules.rules file contains: From: 127.0.0.1 and From: postmaster@[i]<hostname>[/i] /usr/mailscanner/etc/filename.no.rules.conf The email in Mailwatch reports: Virus: N Blocked File: Y Other Infection: N Report: MailScanner: No programs allowed ([i]filename[/i]) Regards Neil

When I release a quarantined email (because of a file attachment) the released email immediately gets re-quarantined and never gets released. The filetype.rules.rule file already contains: From: 127.0.0.1 and From: postmaster@servername.com /usr/mailscanner/etc/filetype.no.rules.conf How do I preven...

I know this is not the reply you are seeking but have you tried zipping the .exe (assuming it's an .exe) file and resending? Unfortunately I'm not the sender, and anyway, Mailscanner still looks inside zip files! This may be what you seek: http://www.configserver.com/techfaq/faqlist.php?catid=5&...

Mailscanner is blocking some legitimate emails with the following error: MailScanner: No programs allowed (Templates) If I release the email, the released email gets re-blocked with the same error and ends up back in quarantine! How do I get these emails through to the recipient? The persons domain ...

I love some of the reports you can do with the Mailwatch front end. What would be great is if we could provide this functionality to our customers, but limit it to producing reports on their domains hosted in WHM.

Cheers,

Neil
http://www.purleyhosting.com

But that doesn't mean what you are trying to do can't be done right?

I would of thought the same thing could be done by using two rules, one to block all incoming port 22 from *, then allowing it from your IP?

Cheers,


Neil