MailScanner Unable to Call SpamAssassin
Re: MailScanner Unable to Call SpamAssassin
I had this issue as well, but a CPanel forced update fixed it.
I will use the perlinstaller if it happens again.
I will use the perlinstaller if it happens again.
-
- Junior Member
- Posts: 1
- Joined: 20 Oct 2011, 14:24
Re: MailScanner Unable to Call SpamAssassin
I tried that command it did not work for me. Still get "You want to use SpamAssassin but have not installed it."
Any other suggestions?
Any other suggestions?
Re: MailScanner Unable to Call SpamAssassin
I just started to see this after noticing a lot of spam coming through. A restart includes:
"I will run without SpamAssassin for now, you will not detect much spam until you install SpamAssassin."
Any other ideas?
"I will run without SpamAssassin for now, you will not detect much spam until you install SpamAssassin."
Any other ideas?
-
- Moderator
- Posts: 1524
- Joined: 01 Oct 2008, 09:24
Re: MailScanner Unable to Call SpamAssassin
Looks like another problem with another new NetAddr::IP, however this time associated with the Socket6 perl module. try doing this:
Code: Select all
/scripts/perlinstaller --force Socket6
Re: MailScanner Unable to Call SpamAssassin
There is a post on cPanel that suggests we might need to roll back to NetAddr::IP .48:
checkperlmodules-perl-module-netaddr-ip-could-not-installed-239282.html
(can't post full URL)
checkperlmodules-perl-module-netaddr-ip-could-not-installed-239282.html
(can't post full URL)
Last edited by RickG on 20 Oct 2011, 19:56, edited 1 time in total.
Re: MailScanner Unable to Call SpamAssassin
Thank you!
/scripts/perlinstaller --force Socket6
resolved the issue.
/scripts/perlinstaller --force Socket6
resolved the issue.
Re: MailScanner Unable to Call SpamAssassin
The fix worked for me, but since I don't get a lot of spam, I AGAIN didn't notice it was down until someone notified me very late in the day. Is there a way to track this and get a warning when this happens? It would be nice to know if spam scanning is broken through an automated system.
Re: MailScanner Unable to Call SpamAssassin
Is this error message below also because of this cPanel update? I get this everytime I try to flag as spam in mailwatch. I tried both of the suggestions in previous posts but still getting the error messages. Just started doing it.
SA Learn: netset: cannot include 0:0:0:0:0:0:0:1/128 as it has already been included, netset: cannot include 0:0:0:0:0:0:0:1/128 as it has already been included, Learned tokens from 1 message(s) (1 message(s) examined)
SA Learn: netset: cannot include 0:0:0:0:0:0:0:1/128 as it has already been included, netset: cannot include 0:0:0:0:0:0:0:1/128 as it has already been included, Learned tokens from 1 message(s) (1 message(s) examined)
Re: MailScanner Unable to Call SpamAssassin
Yes, we think this is also because of the same perl module, NetAddr::IP. Nothing we can do about it until the developer fixes it. This particular error doesn't seem to cause any real issues as far as we know.
nootkan wrote:Is this error message below also because of this cPanel update? I get this everytime I try to flag as spam in mailwatch. I tried both of the suggestions in previous posts but still getting the error messages. Just started doing it.
SA Learn: netset: cannot include 0:0:0:0:0:0:0:1/128 as it has already been included, netset: cannot include 0:0:0:0:0:0:0:1/128 as it has already been included, Learned tokens from 1 message(s) (1 message(s) examined)
Re: MailScanner Unable to Call SpamAssassin
Thanks for your reply Sarah, so is the learning process still working then? I can still click the SA spam-submit and it will learn?