mailscanner suspcious process.
Any thoughts why mailscanner would start echoing these errors.
Only just started recently, probably since upadating to 8.0.14 late last week.
I'm aware that 5.9.124.53:24441 has something to do with Pyzor, which could be related to SpamAssasin.
/usr/local/cpanel/3rdparty/perl/528/bin/perl
Command Line (often faked in exploits):
MailScanner: waiting for messages
Network connections by the process (if any):
udp: 213.171.xxx.xxx:36679 -> 5.9.124.53:24441
Files open by the process (if any):
/dev/null
/dev/null
/dev/null
/usr/mailscanner/usr/share/MailScanner/perl/MailScanner/CustomConfig.pm
/usr/mailscanner/usr/share/MailScanner/perl/MailScanner/ConfigDefs.pl
/usr/mailscanner/usr/share/MailScanner/perl/custom/GenericSpamScanner.pm
/var/spool/MailScanner/incoming/SpamAssassin.cache.db
I'm aware that 5.9.124.53:24441 has something to do with Pyzor, which could be related to SpamAssasin.
-
Still trying to figure this out. If I look in my processes list I see 2 x processes for Mailscanner. MailScanner: starting child MailScanner: waiting for messages If I stop and restart mailscanner, 2 processes start again, the PIDs change. Then an hour later, I see the message again. 0 -
Apparently It is normal, you need to add this line to /etc/csf/csf.pignore and restart csf and lfd: pcmd:MailScanner:.* Odd how I never needed it before now though. 0 -
@keat63 Maybe some changes to either CSF or MailScanner, but both of those are 3rd party applications and they would the best outlet for answers on their behavior or changes in it. 0 -
Dont you just love forums. :) Searching for the issue that i'm currently facing on my new server, and found my own answer. 0
Please sign in to leave a comment.
Comments
4 comments