Facebook
Twitter
V
vankel
Guest
Hi there,
I would like to suggest a quick fix regarding MailEnable's MTA and SpamAssassin.
Currently, our server is heavily loaded all the time (100% CPU usage) with multiple instances of Perl.exe. From this forum, we came to the conclusion that these processes are caused by Spamassassin screening e-mail messages.
We have another server responsible for a lot more domains and e-mail messages. This server is our e-mail server (no hosting) and thus does not have Plesk installed. We are using MailEnables and Spamassassin at this server too. However the CPU usage is minimal. This is because we have set MailEnable to only use Spamassassin on e-mails less than 100K. The reasons behind this are:
- spams usually won't be big, as spammers do not want to spend time and bandwidth sending spams
- e-mail messages > 100K usually contain binary codes (Word documents, MP3s, etc), and spamassassin will not bypass binaries... having spamassassin screening and learning from binaries isn't helpful and will waste resources
So, our suggestion is to release a patch for Plesk 7.0 and 7.5 that either hard code the size limit, or better yet, let users to configure the size limit in some way.
Thank you.
I would like to suggest a quick fix regarding MailEnable's MTA and SpamAssassin.
Currently, our server is heavily loaded all the time (100% CPU usage) with multiple instances of Perl.exe. From this forum, we came to the conclusion that these processes are caused by Spamassassin screening e-mail messages.
We have another server responsible for a lot more domains and e-mail messages. This server is our e-mail server (no hosting) and thus does not have Plesk installed. We are using MailEnables and Spamassassin at this server too. However the CPU usage is minimal. This is because we have set MailEnable to only use Spamassassin on e-mails less than 100K. The reasons behind this are:
- spams usually won't be big, as spammers do not want to spend time and bandwidth sending spams
- e-mail messages > 100K usually contain binary codes (Word documents, MP3s, etc), and spamassassin will not bypass binaries... having spamassassin screening and learning from binaries isn't helpful and will waste resources
So, our suggestion is to release a patch for Plesk 7.0 and 7.5 that either hard code the size limit, or better yet, let users to configure the size limit in some way.
Thank you.
