Skip to main content

Bayes_99 result different on 2 accounts.

Comments

15 comments

  • cPanelLauren
    Hi @nosajix I wonder if there isn't an issue with the bayes db on that account - you might try the troubleshooting steps here: BayesNotWorking - Spamassassin Wiki Their bayes faq is really useful/helpful as well and might get you pointed more in the right direction: BayesFaq - Spamassassin Wiki
    0
  • nosajix
    Hi @nosajix I wonder if there isn't an issue with the bayes db on that account - you might try the troubleshooting steps here: BayesFaq - Spamassassin Wiki

    Would this be different per cpanel account?
    0
  • nosajix
    Another odd tidbit - it may not be content related as I tested it where the original sender was a gmail account and it did not trigger it. The emails that did trigger it are cpanel emails from another server... I am going to continue to work on this
    0
  • cPanelLauren
    Interesting, do you happen to also have gmail whitelisted anywhere?
    0
  • cPanelLauren
    Would this be different per cpanel account?

    Yea bayes data is in /home/$user/.spamassassin/
    0
  • nosajix
    Interesting, do you happen to also have gmail whitelisted anywhere?

    No
    0
  • cPanelLauren
    I can't think of a reason that rule wouldn't get hit if the mail content is the same but just originating from a different provider - spam headers might be helpful in this case as well.
    0
  • nosajix
    Can you copy the headers and let me delete them? I feel a bit exposed having that data "out there"
    0
  • cPanelLauren
    So my assumption after seeing these is that because gmail is a more trusted provider it's bayes weight is lighter than the other domain so it's hitting the lower bayesian score
    0
  • nosajix
    ok - so its not the message content but rather the sender domain? strange. I manage both servers, the sending is not a bad actor. I still havent read up on the bayes documentation. guess I'll look there.
    0
  • cPanelLauren
    It's not necessarily that it's a bad actor but that the reputation isn't as strong. You can teach bayes not to do this though, the bayes FAQ i sent should explain how to do this properly using sa-learn.
    0
  • nosajix
    It's not necessarily that it's a bad actor but that the reputation isn't as strong. You can teach bayes not to do this though, the bayes FAQ i sent should explain how to do this properly using sa-learn.

    So - interesting development, it seems according to docs here:
    0
  • cPanelLauren
    That being said, it was removed just yesterday - does cpanel cache dnsbl's? could that be happening here?

    I believe this is more related to the bayesian database each account has. Keep in mind bayesian filters are subject to that users email history and what the system shows them routinely marking as spam - the weight of the bayes_99 rule is determined by this.
    It still doesn't explain why two accounts on this server react differently to the same sender and body though.

    That's really easily explained, they are weighted differently. From the link you posted: [QUOTE]If the user receives the same message via a new unlisted relay, the Bayesian algorithm will assign a high score to it based on previous experience.
    [QUOTE]Conversely, if a user receives a regular newsletter from a fitness club, and one issue makes reference to diet pills and weight loss (which would normally flag the message as spam), the Bayesian algorithm will assign a lower score to it.
    This rule just marks the spam probability based on key words and the user's history.
    Also it seems as though sa-learn is not installed? Installation notes say its included with Spamassassin?

    It should be there but you just may have to call it from the full path like so: /usr/local/cpanel/3rdparty/bin/sa-learn
    0
  • nosajix
    This is an issue still. Bayes_99 is scoring 5 points and I still haven't ben able to fix it. Can you offer any assistance?
    0
  • cPanelLauren
    If the details discussed in this thread previously are not providing assistance, then I'd suggest opening a support ticket at this juncture.
    0

Please sign in to leave a comment.