Page 3 of 7 FirstFirst 12345 ... LastLast
Results 21 to 30 of 62
  1. #21
    Untangle Ninja gotkimchi's Avatar
    Join Date
    Jan 2007
    Location
    Bay Area
    Posts
    2,106

    Default

    I think the 6.1 is set to fail closed vs the 6.0 is fail open. You might want to try this:

    To set this setting to fail closed (the default):

    psql -U postgres uvm
    UPDATE settings.n_spam_smtp_config SET fail_closed = true;





    To set it to fail open:

    psql -U postgres uvm
    UPDATE settings.n_spam_smtp_config SET fail_closed = false;



    Please run these from the command line.
    to be understood, you must first understand. :)
    Attention: Support and help on the Untangle Forums is provided by volunteers and community members like yourself. If you need Untangle support please call or email support@untangle.com

  2. #22
    Master Untangler Big D's Avatar
    Join Date
    Nov 2008
    Posts
    719

    Default

    Running on Intel core duo dual core 2.4GHZ processor and 2GB of memory I see the boxes steadily eat 1GB of memory all the time. If its a low load time maybe a little under 500-750 MB range.

    Not sure why it would run fine for a few hours after a fresh load less it takes time for it to build a database and cause overhead.

  3. #23
    Master Untangler
    Join Date
    May 2008
    Location
    Ohio
    Posts
    161

    Default

    Quote Originally Posted by gotkimchi View Post
    I think the 6.1 is set to fail closed vs the 6.0 is fail open. You might want to try this:

    To set this setting to fail closed (the default):

    psql -U postgres uvm
    UPDATE settings.n_spam_smtp_config SET fail_closed = true;





    To set it to fail open:

    psql -U postgres uvm
    UPDATE settings.n_spam_smtp_config SET fail_closed = false;



    Please run these from the command line.
    I've got the same problem where email is blocked with a spam score of 0. In reality almost if not all email is starting to be blocked. I've executed both ways ( true/false ) with a response of UPDATE 2, to no avail.

    3GB 3.0ghz 74GIGs free <1meg ram used 35% processor

    tail syslog reports a lot of :
    cannot open bayes database R/W lock failed: Interrupted system call
    prefork: server reached --max-children setting, consider raising it
    oh and can't open /var/log/fuzzyocr for writing

    This has happened ever since updating manually to 6.1, which seemed to go without a hitch.

  4. #24
    Master Untangler Big D's Avatar
    Join Date
    Nov 2008
    Posts
    719

    Default

    sounds like your bayes list may have gotten corrupt.

    I believe you can find the bayes list here. /home/spamc/.spamassassin

    I haven't seen this exact problem yet. Heres a link with some interesting information.

    http://www.nabble.com/bayes_toks.exp...d22502372.html
    Last edited by Big D; 04-28-2009 at 01:08 PM.

  5. #25
    Master Untangler
    Join Date
    May 2008
    Location
    Ohio
    Posts
    161

    Default

    Quote Originally Posted by Big D View Post
    sounds like your bayes list may have gotten corrupt.

    I believe you can find the bayes list here. /home/spamc/.spamassassin

    I haven't seen this exact problem yet. Heres a link with some interesting information.

    http://www.nabble.com/bayes_toks.exp...d22502372.html
    Hmmmm, interesting, I can't find spamassassin in spamc or anyplace that says it should be that is referenced in that link

  6. #26
    Master Untangler Big D's Avatar
    Join Date
    Nov 2008
    Posts
    719

    Default

    the link talks about red hat linux in particular so no they wont reference the right directories however its still spamassassin so the general idea is the same. In /home/spamc/.spamassassin this directory is hidden and can be listed with a "ls -la" command.

    Code:
    sa-learn  -D  --force-expire
    This command caught my eye and then the suggestion to look for bayes_toks.expire files in the spamassassin directory. I don't believe that link lead to a solution though. Think the guy just scheduled a cron job to clear out the files and run that command every so often.

  7. #27
    Master Untangler
    Join Date
    Oct 2007
    Posts
    109

    Default

    I also have this problem on several boxes that got updated to 6.1
    I have emails with a score of 0 and an Action of "quarantine message" yet the emails are not in the Quarantine so i can release them.
    I've run that command:
    /usr/bin/rush -e "Untangle::RemoteUvmContext.nodeManager.node('untangle-node-spamassassin').enableSmtpFailClosed(false)"


    Any ideas?

  8. #28
    Newbie
    Join Date
    Jul 2007
    Posts
    12

    Default

    I am having the same issue that just started today

  9. #29
    Master Untangler Big D's Avatar
    Join Date
    Nov 2008
    Posts
    719

    Default

    Do you have tarpitting on ? I saw one time where we would have mysterious spam score 0 get quarantined but couldn't find the message in quarantine. Only when we turned tarpitting off did the message magically appear in the recipients mailbox. Still no clue how that happened.

  10. #30
    Master Untangler
    Join Date
    May 2008
    Location
    Ohio
    Posts
    161

    Default

    I think a combination of the To set it to fail open:

    psql -U postgres uvm
    UPDATE settings.n_spam_smtp_config SET fail_closed = false;

    and a force of the spamassassin bayes expire did the trick. Mail started to flow again and people could send email.

Page 3 of 7 FirstFirst 12345 ... LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

SEO by vBSEO 3.6.0 PL2