10/28   Gah! HOw do I keep spamassassin's files from putting me over
        quota? I have STFW. I spent a couple hours, actually. I lack
        sufficient clue to find the answer.
        \_ Add a 'rm -f LSPAM' line to your .login.
           \_ What does that do? I don't know of an "LSPAM" file.
              \_ Um, if you never see LSPAM files, never mind.
           \_ Does this mean someone else is using ifile?
              \_ Guilty as charged.
                 \_ Wow.
        \_ Link the following files in ~/.spamassassin to /dev/null
           (using ln -s):
                auto-whitelist.db@ -> /dev/null
                bayes_journal@ -> /dev/null
                bayes_seen@ -> /dev/null
                bayes_toks@ -> /dev/null
           \_ Hmm. Maybe I'm asking too much, but is there a way to stay
              under quota that doesn't involve crippling bayesian filtering?
              I don't get why I'd be the only person whose bayes_* files are
              going over quota. I just haven't heard what people are doing
              about it given sa's populariry.
              \_ You aren't the only one. I asked for a quota increase.
                 It's not like it's a lot of space.
              \_ Google for Mail::SpamAssassin::Conf, and look at the
                 following configuration settings:
                 bayes_journal_max_size
                 bayes_expiry_max_db_size
                 bayes_auto_expire
                 bayes_learn_to_journal
                \_ Alrighty. The trouble is answers web-wide are good for the
                   quotas on particular systems. I would like some suggested
                   values for these items (which all go into .spamassassin/
                   user_prefs for others trying to learn from this thread) that
                   are good for soda.
        \_ I have all these files like bayes_toks.expire7965 that I am pretty
           sure I did not used to have. What is going on?
           \_ http://csua.org/u/80t