use Perl

• typos in the spamc section, procmail recipe issue (Score:1)

  by hughescr (4711)

  You've got "spam" instead of "spamc" as the command line name in a bunch of places. Plus, no need to lock while running spamc in your procmail recipe. spamc can have many parallel instances without any problems. If you want to limit the number of child processes spamd starts, you can do that with the -m option to spamd on startup -- any "extra" spamc's will simply wait until a spamd become available.
  • Re:typos in the spamc section, procmail recipe iss (Score:2)

    by 2shortplanks (968)

    Thanks for spotting that. I think I accidentally did that in the spell checker

    You're right about the spamc thing, I should probably let all the spamc's do their work.
    • Re:typos in the spamc section, procmail recipe iss (Score:1)

      by hughescr (4711)

      Well, I wrote spamc/spamd -- and I would recommend letting them all work ;)
      • Re:typos in the spamc section, procmail recipe iss (Score:1)

        by drhyde (1683)

        And thank *you* for doing all the work :-)
• speed of spamc using Mail::Audit? (Score:1)

  by markjugg (792)

  Great article.
  
  So is there a way to have the speed of using spamc while using Mail::Audit? Would simply switching to pperl work?
  
  Thanks.
  
      Mark
  • Re:speed of spamc using Mail::Audit? (Score:2)

    by 2shortplanks (968)

    There's no reason that you couldn't switch to pperl and get most of the benifits of spamc. I think the author uses it (on an industrial scale) for the same stuff (or so he admits here [perl.org].)

    I use procmail over Mail::Audit these days because I've found it to be more reliable - that's not to say I still don't use perl to do most of my mail filtering. Here's the bottom of my procmail script:

    WHERE=`where_to_guv ${MAILDIR} ${DEFAULT}`
    
    :0:
    ${WHERE}

    where_to_guv is a pperl script that just prints out the name of th
• missing "use" or "require" line for "Mail::SpamAss (Score:1)

  by markjugg (792)

  Hmm. Looks like my subject line ran out of characters.
  
  In the original Mail::Audit script in the article, shouldn't there be a line for "use Mail::SpamAssassion" or "require Mail::SpamAssassin" in there somewhere?