The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

problem with cpanel installing Mail SpamAssassin

Discussion in 'E-mail Discussions' started by Mani, Jul 29, 2007.

  1. Mani

    Mani Well-Known Member

    Joined:
    Dec 22, 2003
    Messages:
    117
    Likes Received:
    0
    Trophy Points:
    16
    got 2 servers online today and after installing cpanel found spamd is failed

    then i did run

    Code:
    /scripts/fixspamassassinfailedupdate
    ended up with

    Code:
    Spamassassin Update Failed, reinstalling!
    Method: Perl Expect
    Fetching CPAN timestamp...Done
    Testing connection speed...(this could take a while)...Done
    Ping:8.249 Testing connection speed to www.mednor.net using pureperl...(159250.00 bytes/s)...Done
    Ping:15.654 Testing connection speed to mirrors.kernel.org using pureperl...(105466.67 bytes/s)...Done
    Ping:18.812 Testing connection speed to cpan-sj.viaverio.com using pureperl...(20953.33 bytes/s)...Done
    Three usable mirrors located
    Three usable mirrors located
    Mirror Check passed for www.mednor.net (/index.html)
    commit: wrote '/usr/lib/perl5/5.8.8/CPAN/Config.pm'
    CPAN: File::HomeDir loaded ok (v0.65)
    CPAN: Storable loaded ok (v2.16)
    Going to read /home/.cpan/Metadata
      Database was generated on Sat, 28 Jul 2007 20:51:00 GMT
    cPCPAN: Module holdback ( held back to 3.2.1)
    Running get for module 'Mail::SpamAssassin'
    
      The module Mail::SpamAssassin isn't available on CPAN.
    
      Either the module has not yet been uploaded to CPAN, or it is
      temporary unavailable. Please contact the author to find out
      more about the status. Try 'i Mail::SpamAssassin'.
    Running get for module 'Mail::SpamAssassin'
    CPAN: Digest::SHA loaded ok (v5.45)
    CPAN: LWP::UserAgent loaded ok (v2.036)
    CPAN: Time::HiRes loaded ok (v1.9707)
    CPAN: YAML loaded ok (v0.65)
    Fetching with LWP:
      http://69.72.164.155/pub/CPAN/authors/id/CHECKSUMS
    
    Warning: No checksum for cPCPAN in /home/.cpan/sources/authors/id/CHECKSUMS.
    
    The cause for this may be that the file is very new and the checksum
    has not yet been calculated, but it may also be that something is
    going awry right now.
    Proceed? [yes]
    CPAN: File::Temp loaded ok (v0.18)
    Package seems to come without Makefile.PL.
      (The test -f "/home/.cpan/build/anon-5pWQhE/Makefile.PL" returned false.)
      Writing one on our own (setting NAME to MailSpamAssassin)
    Unable to install module Mail::SpamAssassin, because it cannot be fetched from CPAN at /scripts/cPScript/cPCPAN.pm line 258.

    upcp --force did not help

    I installed SpamAssassin 3.1.9 manually and worked but wanted to find out how to solve this exact problem

    currently on cp v 10 perl 5.8.8 but did try all of them untill the current verison all the same

    the servers resolve domains and ping other domains every thing else seems to be ok just cant think where this issue pops from maybe too sleepy to think more.
     
    #1 Mani, Jul 29, 2007
    Last edited: Jul 29, 2007
  2. jerrybell

    jerrybell Well-Known Member

    Joined:
    Nov 27, 2006
    Messages:
    90
    Likes Received:
    0
    Trophy Points:
    6
    I'm having the same problem with an existing set of cpanel servers. It seems that the cpanel supported version (3.2.1) was taken off of cpan due to some vulnerabilities, and now cpanel is no longer able to install spamassassin.
     
  3. Mani

    Mani Well-Known Member

    Joined:
    Dec 22, 2003
    Messages:
    117
    Likes Received:
    0
    Trophy Points:
    16
    The problem is that the author removed SpamAssassin 3.2.1 from all servers, and it caused problems

    you have to install 3.2.2 your self untill cpanel solve this thru update
     
  4. deddy

    deddy Well-Known Member

    Joined:
    Oct 13, 2003
    Messages:
    131
    Likes Received:
    0
    Trophy Points:
    16
    I checked CPAN regarding version 3.2.2
    It isn't available there.
    What's up with Mail::SpamAssassin on CPAN ?
     
  5. Mani

    Mani Well-Known Member

    Joined:
    Dec 22, 2003
    Messages:
    117
    Likes Received:
    0
    Trophy Points:
    16
  6. Igor The Troll

    Igor The Troll Registered

    Joined:
    Jul 31, 2007
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    Japan
    Spammassassin on Cpanel 11 not working

    Okay guys I know it is a bug but what can we do?

    I am on a shared server hosting account and they are not telling me anything but wait for an update from Cpanel.

    Can you tell me when will the update be out?

    If it is going to take a long time is there a third party script that I can install in my account that will stop Spam?

    Thank you
     
  7. Mani

    Mani Well-Known Member

    Joined:
    Dec 22, 2003
    Messages:
    117
    Likes Received:
    0
    Trophy Points:
    16
    Igor

    ask your host to install it manually

    they can install 3.1.9 or even 3.2.2 untill cpnael do some thing about this
     
  8. deddy

    deddy Well-Known Member

    Joined:
    Oct 13, 2003
    Messages:
    131
    Likes Received:
    0
    Trophy Points:
    16
    version 3.2.1 is back on CPAN. You should be able to install it.

    Please run

    /scripts/checkperlmodules

    This should fix your problem ;)

    If you are not able to run this command as "root"
    ask your provider to do this for you.
     
    #8 deddy, Jul 31, 2007
    Last edited: Jul 31, 2007
  9. Mani

    Mani Well-Known Member

    Joined:
    Dec 22, 2003
    Messages:
    117
    Likes Received:
    0
    Trophy Points:
    16
    I think you mean

    /usr/local/cpanel/bin/checkperlmodules
     
  10. deddy

    deddy Well-Known Member

    Joined:
    Oct 13, 2003
    Messages:
    131
    Likes Received:
    0
    Trophy Points:
    16
    That's the same ;)
     
  11. chirpy

    chirpy Well-Known Member

    Joined:
    Jun 15, 2002
    Messages:
    13,475
    Likes Received:
    20
    Trophy Points:
    38
    Location:
    Go on, have a guess
    cPanel moved checkperlmodules to /scripts while back in v11.

    As Mani has said, spamassassin developers screwed up their CPAN repository entry, so you either have to wait their fix to propagate the CPAN network or install from source.
     
  12. Mani

    Mani Well-Known Member

    Joined:
    Dec 22, 2003
    Messages:
    117
    Likes Received:
    0
    Trophy Points:
    16
    nice to see ya here chripy

    well they seems fixed it, it works fine now unless if they change again

    for my self since I depend on stables only am still V 10
     
  13. opt2bout

    opt2bout Well-Known Member

    Joined:
    Nov 10, 2006
    Messages:
    58
    Likes Received:
    0
    Trophy Points:
    6
    SA Not working

    We're running 3.22 as installed by one of the latest cPanel 11 (C15845) updates, but even with SpamAssassin turned on by the client's control panel, we're not getting any checks at all.

    SpamD is running, and if we run a few of the messages through spamassassin in test mode, we get high scores and the correct proposed subject rewrites.

    Currently we get nothing if it goes through Exim, no header rewrites with spamassassin version information, no score, nothing.

    Does anyone else have this problem? Any suggestions?

    EDIT: turning SA on globally doesn't make any difference
     
    #13 opt2bout, Aug 1, 2007
    Last edited: Aug 1, 2007
  14. sparek-3

    sparek-3 Well-Known Member

    Joined:
    Aug 10, 2002
    Messages:
    1,384
    Likes Received:
    23
    Trophy Points:
    38
    cPanel Access Level:
    Root Administrator
    I believe this may be a problem with SpamAssassin 3.2.2 and DCC. I saw a lot of problems regarding this overnight, apparently most of our servers were upgraded to SpamAssassin 3.2.2 last night and we have been having a lot of spam problems since.

    I created a patch that should resolve this. I got the information for the patch at:

    http://www.gossamer-threads.com/lists/spamassassin/commits/105775

    I just applied the patch this morning, and so far everything looks better, but as always proceed at your own risk.

    You probably want to back up the affected file first. This will only work if you are running Perl 5.8.8. It might work if you change the paths accordingly, but I don't know, all of our servers are running Perl 5.8.8.

    cp /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Util.pm /root

    Now apply the patch:

    chmod 644 /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Util.pm
    patch -p0 < spam322util.patch.txt
    chmod 444 /usr/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Util.pm
    /scripts/restartsrv_spamd


    (Is the chmod to 644 and then back to 444 necessary? I'm not sure, at 444 the file is not suppose to be writeable, but you are doing this as root, so I don't know. At any rate the above steps will work, it just may include a few unnecessary steps).

    The patch file is included.

    Again, proceed with caution in regards to this. If you experience any problems, remember you backed up the Util.pm file in your /root directory on the server so you can always restore it.
     

    Attached Files:

  15. opt2bout

    opt2bout Well-Known Member

    Joined:
    Nov 10, 2006
    Messages:
    58
    Likes Received:
    0
    Trophy Points:
    6
    Thanks for the patch.

    We initiated a call to the server's hosting provider before doing anything. Their first instinct was that it is a perl issue. However we are running Perl 5.8.7.

    After they got through (they didn't document to us what they did), I ended up with SpamAssassin working, in a new and strange way...

    The X-Spam-Report header is being populated even if the message is not spam. The header is the typical "This message is spam, ..." message. And, if the message IS flagged as spam, the header stays the same...but the attachment of the original mail message is not created. You basically get the entire message delivered with the Subject header re-written with "***SPAM***"

    Not liking this...and not sure if going back to 3.2.1 would resolve the issue...I think we were on 3.1.8 before the cPanel update.

    I went ahead an applied your patch just in case...nothing seemed to change before or after.

    Thanks
     
  16. cPanelDavidG

    cPanelDavidG Technical Product Specialist

    Joined:
    Nov 29, 2006
    Messages:
    11,279
    Likes Received:
    8
    Trophy Points:
    38
    Location:
    Houston, TX
    cPanel Access Level:
    Root Administrator
    You may want to consider upgrading to Perl 5.8.8 (instructions are on the sticky thread about migrating to cPanel 11). This will reduce the number of issues you may experience with cPanel 11.
     
  17. opt2bout

    opt2bout Well-Known Member

    Joined:
    Nov 10, 2006
    Messages:
    58
    Likes Received:
    0
    Trophy Points:
    6
    Done, thanks!

    This doesn't appear to be the issue with the SpamAssassin changes.

    Question: Does the way CP 11 handle SA checks inline affect how the message is rewritten if flagged as spam?

    In earlier CP11 releases, if a rule flagged the message as spam, we still got the x-spam-report header populated correctly with the original Email message attached with the spam report in the body as well.

    Now, just the Subject header gets rewritten.

    What I'm trying to figure out is when this stopped happening, and if its the Exim configuration modified during the upcp or if its SA itself.

    Does anyone know if going to Mailscanner instead gives us the original results?
     
  18. cPanelDavidG

    cPanelDavidG Technical Product Specialist

    Joined:
    Nov 29, 2006
    Messages:
    11,279
    Likes Received:
    8
    Trophy Points:
    38
    Location:
    Houston, TX
    cPanel Access Level:
    Root Administrator
    I know some things recently changed with SA itself with regards to how it indicates something as spam. I also know that the Exim configuration is updated in some updates, hence we advise against modifying the configuration file directly - encouraging the use of the WHM interface as a means to customize the Exim configuration so your changes are preserved during updates.
     
  19. opt2bout

    opt2bout Well-Known Member

    Joined:
    Nov 10, 2006
    Messages:
    58
    Likes Received:
    0
    Trophy Points:
    6
    We only use Exim to keep the configuration file. In fact, I've reset the configuration after our host provider got through changing things...not sure what they are doing, but I like most of my cPanel installs to be as canned as possible.

    Can't find anything on SA's site to indicate that they've changed anything that would affect how the original message was attached along with the Spam report.

    I see in the inline ACLs in the Exim config where the header is rewritten, but no code showing where the original message is added as an attachment to the spam reported message.

    I guess we have to disable the inline rules and use the old spamassassin system until we can find a way to replicate this ourselves.

    EDIT: Yes, disabling the ACL rules puts things back...messages are being processed, but the spam header rewrites, etc. ***SPAM*** are old school "[SPAM]" ... we didn't have to do this before. I'd prefer using the rules inside Exim's ACL, but not sure how to go about writing our own to do the necessary modification to the mail message like it did before.
     
    #19 opt2bout, Aug 2, 2007
    Last edited: Aug 2, 2007
  20. jackflash

    jackflash Member

    Joined:
    Apr 28, 2005
    Messages:
    8
    Likes Received:
    0
    Trophy Points:
    1
    opt2bout:

    I did an update today and am experiencing the same issue with the original e-mail being modified rather than attached. I would like to get them as attachments again. Can you provide a bit more detail about what ACL rules you removed/disabled?

    Another point of interest: At update time, exim gave me errors about not being able to merge my modified exim.conf with the new file. Even though I manually tried to merge them as instructed, it didn't work and mail wasn't being processed. Therefore the big block of ACL rules in the advanced editor has the new default rules. I suspect this is where the problem lies, but don't know how to fix it.

    Thanks.

    [Edit: Since posting my question, I have selected the option "Use the old transport based spamassassin system instead of the new acl style one" on the Exim Configuration Editor page and now get spam with the original messages as attachments again. Odd, really, because I had been using a v11 release for the past few months (I think it was R11631) and the upgrade I made today to the current R16448 handles spam differently. What a shame that I'll have to miss out on some improved functionality, but I can't have false positives permanently altered either.]
     
    #20 jackflash, Aug 24, 2007
    Last edited: Aug 24, 2007
Loading...

Share This Page