SpamAssassin and whitelisting

We use several forms on our websites that are processed by a formmailer and then send to us via e-mail. In order to ensure that these forms are reaching us in any case, I want to whitelist my e-mail addresses in SpamAssassin.
I did so by adding these two lines to /etc/mail/spamassassin/local.cf:
whitelist_from *@starenterprise.com
whitelistfromrcvd *@starenterprise.com starenterprise.com
The first one whitelists all e-mails that come from our domain.
The second one should ensure that the header domain names are matching the reverse DNS lookup.
It also requires internal_networks to be specified, alternatively it takes over the values from trusted_networks - see http://spamassassin.apache.org/full/3.1.x/doc/MailSpamAssassin_Conf.html#whitelist_and_blacklistoptions
So far so good. I don't have internal_networks set, but trusted_networks and therefore believed that anything worked.
But now I got a spam mail with this header:
Von: [email protected]
Betreff: separation; hath brought me? The new wine, that he,
Datum: 22. November 2006 21:32:56 MEZ
An: [email protected]
Return-Path: <[email protected]>
Received: from murder ([unix socket]) by starenterprise.com (Cyrus v2.2.12-OS X 10.4.8) with LMTPA; Wed, 22 Nov 2006 21:32:54 +0100
Received: from localhost (localhost [127.0.0.1]) by starenterprise.com (Postfix) with ESMTP id 2D070506E93 for <[email protected]>; Wed, 22 Nov 2006 21:32:54 +0100 (CET)
Received: from starenterprise.com ([127.0.0.1]) by localhost (dns1.starenterprise.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 06328-01 for <[email protected]>; Wed, 22 Nov 2006 21:32:52 +0100 (CET)
Received: from 132.248.108.40 (unknown [132.248.108.40]) by starenterprise.com (Postfix) with ESMTP id 86048506E80 for <[email protected]>; Wed, 22 Nov 2006 21:32:49 +0100 (CET)
Received: from c069we.forpsi.com (port=19458 helo=jiuqhxdyem) by 132.248.108.40 with smtp id NQFD3-kQ1YX8-4Qs for [email protected]; Wed, 22 Nov 2006 14:32:56 -0600
X-Sieve: CMU Sieve 2.2
Message-Id: <000a01c70e75$5c801990$062faa3c@jiuqhxdyem>
Mime-Version: 1.0
Content-Type: multipart/related; type="multipart/alternative"; boundary="----=NextPart_000_000C01C70E43.11E5A990"
X-Priority: 3
X-Msmail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2869
X-Mimeole: Produced By Microsoft MimeOLE V6.00.2900.2962
X-Spam-Status: No, hits=-85.89 tagged_above=-999 required=5 tests=BAYES_99, HTML8090, HTMLFONTBIG, HTMLIMAGE_ONLY08, HTMLIMAGE_RATIO02, HTML_MESSAGE, MIMEQP_LONGLINE, RCVDBYIP, RCVDIN_BL_SPAMCOPNET, RCVDINXBL, RCVDNUMERICHELO, USERINWHITELIST
X-Spam-Level:
Where is the problem that caused this mail being whitelisted and how can I prevent this by improving my settings ?

I already use a SPF in my domain's DNS records, although I think that I haven't exactly understood their application (even with this information in DNS, why should a spammer care about ?).
Anyway, I noticed this morning that six spam mails came through, all claimed to be whitelisted. So I have commented out whitelisting in local.cf file.
I belive the tricky part is if your clients sometimes use their computers
elsewhere so that the outgoing mail / smtp server might not be your own and
that might hinder the receiving mailserver from accepting mail from your
users.
You mention an interesting part there, I haven't thought about: What happens when I'm using a dial-up ISP and then sending mails via my mail account ? Am I then not whitelisted although I authenticate myself correctly ?
Alternatively to an other solution someone can provide I also would simply set the score for "USERINWHITELIST" from -100 to let's say -5. Since my intended mails all have scores around two to three maximum, this could also work. Most spam mails came through had around -80 points, so deducting the whitelist score -100 we have +20 points for all other tests; subtracting five points (new whitelist score) we come to +15 - still marked as spam

Similar Messages

  • Spamassassin, auto whitelist, backscatter and spam problems.

    My Mail is handled by an XServe with Mac OS X Server 10.5.5.
    I have many email problems. One of them is an email backscatter problem. Sometimes, but not always, when email is identified as spam, an email gets sent back to the "From" address saying it is spam. This email seems to come directly from my servers, which is bad as spammers usually spoof the From addresses. I have modified amavisd.conf as per below. I changed all the D_BOUNCE instances to D_REJECT, yet still emails seeming to come from my server gets sent back to the From address. This is the relevant bit out of amavisd.conf:
    $finalvirusdestiny = D_REJECT;
    $finalbanneddestiny = D_REJECT;
    $finalspamdestiny = D_REJECT;
    $finalbad_headerdestiny = D_PASS;
    I tried testing this by sending lots of emails that with keywords in them that rules are set up for to add enough points so that such emails get blocked, however, these emails seem to come through. At first I thought this was the AWL's doing, but by examining the headers of the email, there is no X-SPAM header as I'd expect, which makes me believe Spamassassin has not checked the email?? What can cause emails to bypass spamassassin and how do I get spamassassin to check every email? This seems to be a cause of my other problem of a lot of SPAM passing through the spam filter.
    I am also having a lot of trouble understanding the SA AWL.
    Is there any way I can change the scores in the AWL database?
    I have tried:
    spamassassin --remove-addr-from-whitelist=[email protected]
    This outputs a message saying it removed an address from the whitelist, but in reality does absolutely nothing. Way I can tell is by using this script which still shows the same entries for the relevant email address:
    http://spamassassin.apache.org/full/3.0.x/dist/tools/check_whitelist
    I'm stumped. Any answers/thoughts/suggestions would be much appreciated. Please help!

    postfix receives the mail, then passes it to amavisd.
    amavisd decides what scanners to use (clamav/spamassassin and possibly others) and performs the scan
    amavisd might not scan the messages if certain criteria are met (size too large, white list, etc), this is all configurable in amavisd.conf. For example, the size threshold by default may be too small, so messages with large graphics may not be scanned.
    after amavis processes the message, depending on the config of amavis, certain actions are performed (add headers, discard, reject, bounce, etc).
    then amavisd passes the mail back to postfix
    postfix delivers any deliverable mail to cyrus/dovecot and/or processes and bounce/rejection.
    a rejection doesn't work in the above scenario because it's already been accepted by postfix.
    best to discard.
    if you would like to learn more about the flow and logic, look at the amavisd config file
    /etc/amavisd.conf
    and check out the docs
    http://www.ijs.si/software/amavisd/
    Jeff

  • SpamAssassin and too much CPU load

    I have been testing my messaging server and SpamAssassin integration. Everything seems fine except too much CPU load coming from spamd (SpamAssassin's daemon). I am testing them on a UltraSparcII-i, 256MB, Solaris 10 box. When I loaded it with 4msg/min containing 50K ascii text each on the receiving side, the spamd process went up to 90% of CPU load, and then just died silently. My questions;
    1) Is there any performance tuning that I should do to avoid that much CPU load? Or is this just normal?
    2) I have heard of another anti-spam product called dspam. How can I integrate dspam with the Java Messaging Server?
    Thanks!

    Installation of JES Messaging Server by itself suggests 1.2 gig of RAM. SpamAssassin adds to that suggestion.
    You have less than 1/4 of the suggested RAM. You're 'way short.
    SpamAssassin will use cpu. I found that nx x86 box was far less expensive to feed, and works extremely well for Messaging and SpamAssassin. 1 gig or ram for my PC costs about $75. Adding ram to your Sparc will cost mor than a PC complete.
    4 messages/min isn't much, but. . .
    You're likely swapping pretty hard. Check for "I/O wait". I often use "top" for a quick look at such.
    When I switched from an "ultra-5" with 384 megs ram, to an AMD 1200+ with 1 gig of ram, my system went from feeling totally buried to feeling mostly un-used. I'm currently able to handle far more than 4 message/minute, with no overload or swapping.

  • Email being blocked and whitelist denied - HELP?

    Email to verizon.com (.net too) are being blocked by the anti-spam system. I submitted whitelist requests, but just get automated messages in return saying the IP is dynamically assigned. It's not, I've had the same IP on that server for well over 1 year. No spam is going out from the system, and SPF, PTR records are correct.
    Who can I contact to get mail flowing for customers? One of the sites I host is owned by a local Verizon customer, and he can't even get his own web site emails when someone makes a purchase from him. Very frustrating!
    Any help appreciated.
    Solved!
    Go to Solution.

    Your issue has been escalated to a Verizon agent. Before the agent can begin assisting you, they will need to collect further information from you.Please go to your profile page for the forum, and look in the middle, right at the top where you will find an area titled "My Support Cases". You can reach your profile page by clicking on your name beside your post, or at the top left of this page underneath the title of the board.
    Under “My Support Cases” you will find a link to the private board where you and the agent may exchange information. This should be checked on a frequent basis as the agent may be waiting for information from you before they can proceed with any actions. To ensure you know when they have responded to you, at the top of your support case there is a drop down menu for support case options. Open that and choose "subscribe".
    Please keep all correspondence regarding your issue in the private support portal.

  • "Blocked sender" tab and "Whitelist" tab gone

    V blocks entire swaths of my incoming email as spam. The above-mentioned tabs no longer exist in my account since the site was redone. Now I can't even whitelist legit senders. I watched a video about using their spam detector, but it was geared toward the old interface. Mail Options now takes you to the email itself instead of options for email. Oy, vay. Has anyone had any luck by calling their help line? They were useless 2 months ago.

    Outlook Express is not involved here. Verizon blocks spam on their server before it gets to your mailbox. That's not the same as the spam you're
    blocking in OE, which is the next step down the ladder. Think of it as a group of filters, V filtering out the spam first, and then OE filtering out whatever spam gets through
    (if you'tre lucky.)  The issue here is with V's new spam detector.
    Message Edited by Katz on 07-02-2009 09:14 AM

  • Greylisting and whitelisting

    So, I get that 10.6 implements greylisting. Unfortunately it's not working all that well for one of the folks sending to my mail server - ironically from mac.com. Since upgrading his mail always takes an hour to be delivered.
    Is there any way I can specify either a specific address, or failing that, a domain to be whitelisted? In other words, how do I specify what should be exempt from greylisting?
    I don't want to turn off greylisting - it's made a large improvement in the amount of spam we get.

    The greylist policy service is located here:
    /usr/libexec/postfix/greylist.pl
    It is almost a clone of the example postfix greylist policy example from here:
    http://www.postfix.org/SMTPDPOLICYREADME.html
    For what it is worth, the greylisting server never clears the database it uses to store which client addresses have tried to deliver mail to it, so once an address is whitelisted it should stay whitelisted forever. So delivery delays should go away with time as the full range of possible servers from places like mac.com and gmail get remembered.
    If you're adventurous and know some perl, it should be straightforward to modify greylist.pl to check a whitelist file.

  • SpamAssassin and DCC

    Has anybody tried to install DCC tests according the how-to guide at http://wiki.apache.org/spamassassin/InstallingDCC on OS X Server 10.4.8 ? Or are there even OS-related installation instructions available ?

    I found on CPAN this module:
    http://search.cpan.org/~jmason/Mail-SpamAssassin-3.1.7/lib/Mail/SpamAssassin/Plu gin/DCC.pm
    Now SpamAssassin installed on OS X is of an older version, therefore I don't know if this module can be installed over CPAN to the current version of SpamAssassin, can't ?
    The document mentioned in my first post refers installing DCC via wget command which is not available, CPAN is and I'm also a bit familiar with it so I would prefer using this way.

  • 10.5.8 SpamAssassin and FH_DATE_PAST_20XX

    The 10.5.8 standard SpamAssassin is pretty old. It also has a rule (FHDATE_PAST20XX) that tags everything with a date after Jan 1 2010 as 'suspiciously in the future'. First, I tried to change the .cf files that contained this, but that did not work. Then I followed instructions found on the net about updating SpamAssassin on Leopard Server with CPAN, which made a mess of things (parts were installed in /usr/local, parts in /Library/Perl) and SpamAssassin stopped working altogether. Luckily I have a decent CrashPlan backup, so I am now back at square one.
    Question: is there a failsafe way, not using CPAN (I have been burned by CPAN every time I tried to use it) to either update SpamAssassin on Leopard Server to something up to date and working and if not, how do I fix this?
    Thanks,

    This should help:
    http://osx.topicdesk.com/content/view/61/62/
    If you want to bypass installation of dependencies via CPAN, simply download the needed modules and build them the same way SpamAssassin is built in above tutorial.
    HTH,
    Alex

  • Spamassassin and ms5.2 hf 1.21 channel blocking

    Hi,
    iMS5.2 HF 1.21. imta.cnf used custom channel spamcheckrequired to check if spam scanning is enabled (per subscriber). If it is enabled, then pass to ims-ms-spamcheck for spam parsing with loadbalanced spamds or deliver into ims-ms to message store.
    OK so far. The problem occurs during performance testing when some messages are "blocked" or "stuck" in the spamcheckrequired channel. This channel makes an LDAP lookup and to check if the subscriber (recipient) has the spam service switched on. The LDAP part works fine but some messages are blocked in this channel (approx 5-6 / 5000 messages). If I use the command imsimta qm and then look into the spamcheckrequired channel (directory spamcheckrequired) I can see the "blocked" messages. If I then try and delete any of the messages, the q manager tells me it deletes the messages but also gives the error os_map_file: lock failed -11. I can see that the message does exist in the fs. (from the message name and path given when i try the delete command).
    As a futher test, if I reconfig the ims-ms-spamcheck channel to use only a single spamd (not the loadbalancer VIP for the multiple spamd servers) and re-run the test, I never see a blockage in the spamcheckrequired channel (though of course the solution is not performant).
    Any help would be gratfully accepted,
    Thanks, Simon

    I suspect you're going about this the hard way...
    First, the kind of optin/optout stuff you're doing is built into Messaging 6.xx, so it's 'way easier there.
    The error message you're getting is something you get when a thread goes to process a message file, and it's been already processed or in use by another thread. You might want to examine your message flow again.
    iMS 5.2hf2.02 has some fixes, and a new, better keyword for routing stuff outside to scanning channels, "aliasdetourhost". This may indeed be the answer. You need to open a tech support ticket to get the hotfix.

  • Question about the whitelist and installing a Wireless AC card on a Thinkpad Yoga

    Hi,
    So I'm looking at buying a Thinkpad Yoga, but the model I'm looking at doesn't have AC wireless.  I've read up a bit about FRUs and whitelists, and was just wondering if the same model wireless card with two different Lenovo parts numbers will be compatible with each other or if the bios will block it if I don't buy the specific Lenovo part number.

    Yes, you install grub to sda (master boot record), and add the entry for Windows. In the step where you partition the harddrive, you can choose where to create it. Actually it may not be that much of a problem anymore, my boot is on the third partition, after ~15 GB. You can forget about the bootable flag when using grub, it does not care.

  • Bayes Error Question after Spamassassin Upgrade

    I have just upgraded to Version 3.1.5 of the Spamassassin and I am getting the following readout when after I run spamassassin -D --lint
    xserve1:/var/amavis root# spamassassin -D --lint
    [18757] dbg: logger: adding facilities: all
    [18757] dbg: logger: logging level is DBG
    [18757] dbg: generic: SpamAssassin version 3.1.5
    [18757] dbg: config: score set 0 chosen.
    [18757] dbg: util: running in taint mode? yes
    [18757] dbg: util: taint mode: deleting unsafe environment variables, resetting PATH
    [18757] dbg: util: PATH included '/bin', keeping
    [18757] dbg: util: PATH included '/sbin', keeping
    [18757] dbg: util: PATH included '/usr/bin', keeping
    [18757] dbg: util: PATH included '/usr/sbin', keeping
    [18757] dbg: util: final PATH set to: /bin:/sbin:/usr/bin:/usr/sbin
    [18757] dbg: message: ---- MIME PARSER START ----
    [18757] dbg: message: main message type: text/plain
    [18757] dbg: message: parsing normal part
    [18757] dbg: message: added part, type: text/plain
    [18757] dbg: message: ---- MIME PARSER END ----
    [18757] dbg: dns: is Net::DNS::Resolver available? yes
    [18757] dbg: dns: Net::DNS version: 0.59
    [18757] dbg: diag: perl platform: 5.008006 darwin
    [18757] dbg: diag: module installed: Digest::SHA1, version 2.10
    [18757] dbg: diag: module installed: Archive::Tar, version 1.30
    [18757] dbg: diag: module installed: IO::Zlib, version 1.04
    [18757] dbg: diag: module installed: DB_File, version 1.814
    [18757] dbg: diag: module installed: HTML::Parser, version 3.36
    [18757] dbg: diag: module installed: MIME::Base64, version 3.05
    [18757] dbg: diag: module installed: Net::DNS, version 0.59
    [18757] dbg: diag: module installed: Net::SMTP, version 2.29
    [18757] dbg: diag: module installed: Mail::SPF::Query, version 1.999001
    [18757] dbg: diag: module installed: IP::Country::Fast, version 604.001
    [18757] dbg: diag: module installed: Razor2::Client::Agent, version 2.82
    [18757] dbg: diag: module installed: Net::Ident, version 1.20
    [18757] dbg: diag: module not installed: IO::Socket::INET6 ('require' failed)
    [18757] dbg: diag: module installed: IO::Socket::SSL, version 1.0
    [18757] dbg: diag: module installed: Time::HiRes, version 1.68
    [18757] dbg: diag: module installed: DBI, version 1.52
    [18757] dbg: diag: module installed: Getopt::Long, version 2.34
    [18757] dbg: diag: module installed: LWP::UserAgent, version 2.033
    [18757] dbg: diag: module installed: HTTP::Date, version 1.47
    [18757] dbg: ignore: using a test message to lint rules
    [18757] dbg: config: using "/etc/mail/spamassassin" for site rules pre files
    [18757] dbg: config: read file /etc/mail/spamassassin/init.pre
    [18757] dbg: config: read file /etc/mail/spamassassin/v310.pre
    [18757] dbg: config: read file /etc/mail/spamassassin/v312.pre
    [18757] dbg: config: using "/usr/local/share/spamassassin" for sys rules pre files
    [18757] dbg: config: using "/usr/local/share/spamassassin" for default rules dir
    [18757] dbg: config: read file /usr/local/share/spamassassin/10_misc.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/20_advance_fee.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/20_anti_ratware.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/20_body_tests.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/20_compensate.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/20_dnsbl_tests.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/20_drugs.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/20_fake_helo_tests.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/20_head_tests.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/20_html_tests.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/20_meta_tests.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/20_net_tests.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/20_phrases.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/20_****.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/20_ratware.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/20_uri_tests.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/23_bayes.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/25_accessdb.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/25_antivirus.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/25_body_tests_es.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/25_body_tests_pl.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/25_dcc.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/25_dkim.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/25_domainkeys.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/25_hashcash.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/25_pyzor.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/25_razor2.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/25_replace.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/25_spf.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/25_textcat.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/25_uribl.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/30_text_de.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/30_text_fr.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/30_text_it.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/30_text_nl.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/30_text_pl.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/30_text_pt_br.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/50_scores.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/60_awl.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/60_whitelist.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/60_whitelist_dk.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/60_whitelist_dkim.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/60_whitelist_spf.cf
    [18757] dbg: config: read file /usr/local/share/spamassassin/60_whitelist_subject.cf
    [18757] dbg: config: using "/etc/mail/spamassassin" for site rules dir
    [18757] dbg: config: read file /etc/mail/spamassassin/70_sare_adult.cf
    [18757] dbg: config: read file /etc/mail/spamassassin/70_sare_bayes_poison_nxm.cf
    [18757] dbg: config: read file /etc/mail/spamassassin/70_sare_evilnum0.cf
    [18757] dbg: config: read file /etc/mail/spamassassin/70_sare_evilnum1.cf
    [18757] dbg: config: read file /etc/mail/spamassassin/70_sare_evilnum2.cf
    [18757] dbg: config: read file /etc/mail/spamassassin/70_sare_html.cf
    [18757] dbg: config: read file /etc/mail/spamassassin/70_sare_obfu.cf
    [18757] dbg: config: read file /etc/mail/spamassassin/70_sare_oem.cf
    [18757] dbg: config: read file /etc/mail/spamassassin/70_sare_random.cf
    [18757] dbg: config: read file /etc/mail/spamassassin/70_sare_stocks.cf
    [18757] dbg: config: read file /etc/mail/spamassassin/70_sc_top200.cf
    [18757] dbg: config: read file /etc/mail/spamassassin/99_FVGT_Tripwire.cf
    [18757] dbg: config: read file /etc/mail/spamassassin/Chinese_rules.cf
    [18757] dbg: config: read file /etc/mail/spamassassin/local.cf
    [18757] dbg: config: read file /etc/mail/spamassassin/weeds.cf
    [18757] dbg: config: using "/private/var/root/.spamassassin/user_prefs" for user prefs file
    [18757] dbg: config: read file /private/var/root/.spamassassin/user_prefs
    [18757] dbg: plugin: loading Mail::SpamAssassin::Plugin::URIDNSBL from @INC
    [18757] dbg: plugin: registered Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x18796d0)
    [18757] dbg: plugin: loading Mail::SpamAssassin::Plugin::Hashcash from @INC
    [18757] dbg: plugin: registered Mail::SpamAssassin::Plugin::Hashcash=HASH(0x1c828d8)
    [18757] dbg: plugin: loading Mail::SpamAssassin::Plugin::SPF from @INC
    [18757] dbg: plugin: registered Mail::SpamAssassin::Plugin::SPF=HASH(0x1d91a64)
    [18757] dbg: plugin: loading Mail::SpamAssassin::Plugin::Pyzor from @INC
    [18757] dbg: pyzor: network tests on, attempting Pyzor
    [18757] dbg: plugin: registered Mail::SpamAssassin::Plugin::Pyzor=HASH(0x1c66f5c)
    [18757] dbg: plugin: loading Mail::SpamAssassin::Plugin::Razor2 from @INC
    [18757] dbg: razor2: razor2 is available, version 2.82
    [18757] dbg: plugin: registered Mail::SpamAssassin::Plugin::Razor2=HASH(0x466db0)
    [18757] dbg: plugin: loading Mail::SpamAssassin::Plugin::SpamCop from @INC
    [18757] dbg: reporter: network tests on, attempting SpamCop
    [18757] dbg: plugin: registered Mail::SpamAssassin::Plugin::SpamCop=HASH(0x468e68)
    [18757] dbg: plugin: loading Mail::SpamAssassin::Plugin::AWL from @INC
    [18757] dbg: plugin: registered Mail::SpamAssassin::Plugin::AWL=HASH(0x1dd02d0)
    [18757] dbg: plugin: loading Mail::SpamAssassin::Plugin::AutoLearnThreshold from @INC
    [18757] dbg: plugin: registered Mail::SpamAssassin::Plugin::AutoLearnThreshold=HASH(0x1e34100)
    [18757] dbg: plugin: loading Mail::SpamAssassin::Plugin::WhiteListSubject from @INC
    [18757] dbg: plugin: registered Mail::SpamAssassin::Plugin::WhiteListSubject=HASH(0x1e36be0)
    [18757] dbg: plugin: loading Mail::SpamAssassin::Plugin::MIMEHeader from @INC
    [18757] dbg: plugin: registered Mail::SpamAssassin::Plugin::MIMEHeader=HASH(0x1e39d30)
    [18757] dbg: plugin: loading Mail::SpamAssassin::Plugin::ReplaceTags from @INC
    [18757] dbg: plugin: registered Mail::SpamAssassin::Plugin::ReplaceTags=HASH(0x1e3e260)
    [18757] dbg: config: adding redirector regex: /^http:\/\/chkpt\.zdnet\.com\/chkpt\/\w+\/(.*)$/i
    [18757] dbg: config: adding redirector regex: /^http:\/\/www(?:\d+)?\.nate\.com\/r\/\w+\/(.*)$/i
    [18757] dbg: config: adding redirector regex: /^http:\/\/.+\.gov\/(?:.*\/)?externalLink\.jhtml\?.*url=(.*?)(?:&.*)?$/i
    [18757] dbg: config: adding redirector regex: /^http:\/\/redir\.internet\.com\/.+?\/.+?\/(.*)$/i
    [18757] dbg: config: adding redirector regex: /^http:\/\/(?:.*?\.)?adtech\.de\/.*(?:;|\|)link=(.*?)(?:;|$)/i
    [18757] dbg: config: adding redirector regex: m'^http.*?/redirect\.php\?.*(?<=[?&])goto=(.*?)(?:$|[&\#])'i
    [18757] dbg: config: adding redirector regex: m'^https?:/*(?:[^/]+\.)?emf\d\.com/r\.cfm.*?&r=(.*)'i
    [18757] dbg: config: adding redirector regex: m'/(?:index.php)?\?.*(?<=[?&])URL=(.*?)(?:$|[&\#])'i
    [18757] dbg: config: adding redirector regex: m'^http:/*(?:\w+\.)?google(?:\.\w{2,3}){1,2}/url\?.*?(?<=[?&])q=(.*?)(?:$|[&\#] )'i
    [18757] dbg: config: adding redirector regex: m'^http:/*(?:\w+\.)?google(?:\.\w{2,3}){1,2}/search\?.*?(?<=[?&])q=[^&]*?(?<=%2 0|..[=+\s])site:(.*?)(?:$|%20|[\s+&\#])'i
    [18757] dbg: config: adding redirector regex: m'^http:/*(?:\w+\.)?google(?:\.\w{2,3}){1,2}/search\?.*?(?<=[?&])q=[^&]*?(?<=%2 0|..[=+\s])(?:"|%22)(.*?)(?:$|%22|["\s+&\#])'i
    [18757] dbg: config: adding redirector regex: m'^http:/*(?:\w+\.)?google(?:\.\w{2,3}){1,2}/translate\?.*?(?<=[?&])u=(.*?)(?:$ |[&\#])'i
    [18757] warn: config: failed to parse line, skipping: scare RCVD_IN_NJABL_SPAM 3.0
    [18757] dbg: plugin: Mail::SpamAssassin::Plugin::ReplaceTags=HASH(0x1e3e260) implements 'finish_parsing_end'
    [18757] dbg: replacetags: replacing tags
    [18757] dbg: replacetags: done replacing tags
    [18757] dbg: bayes: no dbs present, cannot tie DB R/O: /private/var/root/.spamassassin/bayes_toks
    [18757] dbg: config: score set 1 chosen.
    [18757] dbg: message: ---- MIME PARSER START ----
    [18757] dbg: message: main message type: text/plain
    [18757] dbg: message: parsing normal part
    [18757] dbg: message: added part, type: text/plain
    [18757] dbg: message: ---- MIME PARSER END ----
    [18757] dbg: bayes: no dbs present, cannot tie DB R/O: /private/var/root/.spamassassin/bayes_toks
    [18757] dbg: dns: name server: 209.198.128.11, family: 2, ipv6: 0
    [18757] dbg: dns: testing resolver nameservers: 209.198.128.11, 209.198.128.27
    [18757] dbg: dns: trying (3) google.com...
    [18757] dbg: dns: looking up NS for 'google.com'
    [18757] dbg: dns: NS lookup of google.com using 209.198.128.11 succeeded => DNS available (set dns_available to override)
    [18757] dbg: dns: is DNS available? 1
    [18757] dbg: metadata: X-Spam-Relays-Trusted:
    [18757] dbg: metadata: X-Spam-Relays-Untrusted:
    [18757] dbg: metadata: X-Spam-Relays-Internal:
    [18757] dbg: metadata: X-Spam-Relays-External:
    [18757] dbg: message: no encoding detected
    [18757] dbg: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x18796d0) implements 'parsed_metadata'
    [18757] dbg: uridnsbl: domains to query:
    [18757] dbg: dns: checking RBL sbl-xbl.spamhaus.org., set sblxbl-lastexternal
    [18757] dbg: dns: checking RBL sa-accredit.habeas.com., set habeas-firsttrusted
    [18757] dbg: dns: checking RBL sbl-xbl.spamhaus.org., set sblxbl
    [18757] dbg: dns: checking RBL sa-other.bondedsender.org., set bsp-untrusted
    [18757] dbg: dns: checking RBL combined.njabl.org., set njabl-lastexternal
    [18757] dbg: dns: checking RBL combined.njabl.org., set njabl
    [18757] dbg: dns: checking RBL combined-HIB.dnsiplists.completewhois.com., set whois
    [18757] dbg: dns: checking RBL list.dsbl.org., set dsbl-lastexternal
    [18757] dbg: dns: checking RBL bl.spamcop.net., set spamcop
    [18757] dbg: dns: checking RBL sa-trusted.bondedsender.org., set bsp-firsttrusted
    [18757] dbg: dns: checking RBL combined-HIB.dnsiplists.completewhois.com., set whois-lastexternal
    [18757] dbg: dns: checking RBL dnsbl.sorbs.net., set sorbs-lastexternal
    [18757] dbg: dns: checking RBL dnsbl.sorbs.net., set sorbs
    [18757] dbg: dns: checking RBL iadb.isipp.com., set iadb-firsttrusted
    [18757] dbg: check: running tests for priority: 0
    [18757] dbg: rules: running header regexp tests; score so far=0
    [18757] dbg: rules: ran header rule __HAS_MSGID ======> got hit: "<"@lint_rules>"
    [18757] dbg: rules: ran header rule NO_REAL_NAME ======> got hit: "[email protected]
    [18757] dbg: rules: "
    [18757] dbg: rules: ran header rule __MSGID_OK_DIGITS ======> got hit: "1159381766"
    [18757] dbg: spf: no suitable relay for spf use found, skipping SPF-helo check
    [18757] dbg: eval: all '*From' addrs: [email protected]
    [18757] dbg: eval: all '*To' addrs:
    [18757] dbg: spf: no suitable relay for spf use found, skipping SPF check
    [18757] dbg: rules: ran eval rule NO_RELAYS ======> got hit
    [18757] dbg: spf: cannot get Envelope-From, cannot use SPF
    [18757] dbg: spf: def_spf_whitelist_from: could not find useable envelope sender
    [18757] dbg: rules: ran eval rule __UNUSABLE_MSGID ======> got hit
    [18757] dbg: spf: spf_whitelist_from: could not find useable envelope sender
    [18757] dbg: rules: ran eval rule MISSING_HEADERS ======> got hit
    [18757] dbg: rules: running body-text per-line regexp tests; score so far=3.188
    [18757] dbg: rules: ran body rule __NONEMPTY_BODY ======> got hit: "I"
    [18757] dbg: uri: running uri tests; score so far=3.188
    [18757] dbg: bayes: no dbs present, cannot tie DB R/O: /private/var/root/.spamassassin/bayes_toks
    [18757] dbg: bayes: not scoring message, returning undef
    [18757] dbg: bayes: opportunistic call attempt failed, DB not readable
    [18757] dbg: rules: running raw-body-text per-line regexp tests; score so far=3.188
    [18757] dbg: rules: running full-text regexp tests; score so far=3.188
    [18757] dbg: info: entering helper-app run mode
    [18757] dbg: info: leaving helper-app run mode
    [18757] dbg: razor2: part=0 engine=4 contested=0 confidence=0
    [18757] dbg: razor2: results: spam? 0
    [18757] dbg: razor2: results: engine 8, highest cf score: 0
    [18757] dbg: razor2: results: engine 4, highest cf score: 0
    [18757] dbg: util: current PATH is: /bin:/sbin:/usr/bin:/usr/sbin
    [18757] dbg: pyzor: pyzor is not available: no pyzor executable found
    [18757] dbg: pyzor: no pyzor found, disabling Pyzor
    [18757] dbg: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x18796d0) implements 'check_tick'
    [18757] dbg: check: running tests for priority: 500
    [18757] dbg: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x18796d0) implements 'check_post_dnsbl'
    [18757] dbg: rules: running meta tests; score so far=3.188
    [18757] info: rules: meta test DIGEST_MULTIPLE has undefined dependency 'DCC_CHECK'
    [18757] info: rules: meta test SARE_OBFU_CIALIS has undefined dependency 'SARE_OBFU_CIALIS2'
    [18757] info: rules: meta test FP_MIXED_****3 has undefined dependency 'FP_PENETRATION'
    [18757] dbg: rules: running header regexp tests; score so far=4.666
    [18757] dbg: rules: running body-text per-line regexp tests; score so far=4.666
    [18757] dbg: uri: running uri tests; score so far=4.666
    [18757] dbg: rules: running raw-body-text per-line regexp tests; score so far=4.666
    [18757] dbg: rules: running full-text regexp tests; score so far=4.666
    [18757] dbg: check: running tests for priority: 1000
    [18757] dbg: rules: running meta tests; score so far=4.666
    [18757] dbg: rules: running header regexp tests; score so far=4.666
    [18757] dbg: config: using "/private/var/root/.spamassassin" for user state dir
    [18757] dbg: locker: safe_lock: created /private/var/root/.spamassassin/auto-whitelist.lock.xserve1.topequip.com.18757
    [18757] dbg: locker: safe_lock: trying to get lock on /private/var/root/.spamassassin/auto-whitelist with 0 retries
    [18757] dbg: locker: safe_lock: link to /private/var/root/.spamassassin/auto-whitelist.lock: link ok
    [18757] dbg: auto-whitelist: tie-ing to DB file of type DB_File R/W in /private/var/root/.spamassassin/auto-whitelist
    [18757] dbg: auto-whitelist: db-based [email protected]|ip=none scores 0/0
    [18757] dbg: auto-whitelist: AWL active, pre-score: 4.666, autolearn score: 4.666, mean: undef, IP: undef
    [18757] dbg: auto-whitelist: DB addr list: untie-ing and unlocking
    [18757] dbg: auto-whitelist: DB addr list: file locked, breaking lock
    [18757] dbg: locker: safe_unlock: unlink /private/var/root/.spamassassin/auto-whitelist.lock
    [18757] dbg: auto-whitelist: post auto-whitelist score: 4.666
    [18757] dbg: rules: running body-text per-line regexp tests; score so far=4.666
    [18757] dbg: uri: running uri tests; score so far=4.666
    [18757] dbg: rules: running raw-body-text per-line regexp tests; score so far=4.666
    [18757] dbg: rules: running full-text regexp tests; score so far=4.666
    [18757] dbg: check: is spam? score=4.666 required=2
    [18757] dbg: check: tests=MISSING_HEADERS,MISSING_SUBJECT,NO_REAL_NAME,NO_RECEIVED,NO_RELAYS,TO_CC_ NONE
    [18757] dbg: check: subtests=__HAS_MSGID,__MSGID_OK_DIGITS,__MSGID_OK_HOST,__NONEMPTY_BODY,__SANE_M SGID,__UNUSABLE_MSGID
    [18757] warn: lint: 1 issues detected, please rerun with debug enabled for more information
    I am concerned with the following -
    [18757] dbg: bayes: no dbs present, cannot tie DB R/O: /private/var/root/.spamassassin/bayes_toks
    [18757] dbg: bayes: not scoring message, returning undef
    [18757] dbg: bayes: opportunistic call attempt failed, DB not readable
    I know that I have a failure with the IO::Socket::INET6 also.
    I am also not getting (never have gotten) the BAYES tag when I look at the Raw Source on Spam Emails. I am assuming that error above could be the issue.
    Any help on this would be greatly appreciated. I love this discussion group and it has helped me out of a bind more than once!
    Thanks in advance for your time.
    G5 Power Mac   Mac OS X (10.4.7)  

    Latest news!
    I just looked at a spam email and I see that it is tagged here is the info
    X-Spam-Status: No, hits=-1.827 tagged_above=-999 required=2 tests=BAYES_00,
    DIET_1
    Now I am still concerned about the error I listed above about the Bayes DB. Any help would be great.

  • Auto-whitelist

    Greetings,
    not sure how many people still run 10.4 mail systems. but what the heck
    I have a mail server that has been running spammassassin for years. pumping SA learn and running spamtrainer.
    recently i received OS and postfix error messages regarding insufficient storage space although i had 30gig of room on the drive.
    During a clone operation i discovered a very large Auto-whitelist file in /var/clamav/.spamassassin
    i don't remember setting Auto-Whitelist 1
    mylocal.cf doesn't mention AutoWhitelist
    and my amavisd.conf has it commented out .
    #$saautowhitelist = 0; # turn on AWL (default: false)
    # Bayesian Auto Learn
    auto_learn 1
    # Safe Reporting
    safe_reporting 0
    # Full/Terse Reporting
    usetersereport 0
    # Subject Tag
    subject_tag * Warning: Junk Mail *
    # Rewrite the Subject
    rewrite_subject 0
    # Use Bayesian Filtering
    use_bayes 1
    # OK locals
    ok_locales en
    # OK languages
    ok_languages en fr de ja
    # Required hits to be marked as spam
    required_hits 5
    I ran a test message through SA, i did not see anything referencing Auto-Whitelist.
    here is debug ::: ::
    }mx1:/var/clamav root# spamassassin -D < /private/var/root/Documents/Message1.rtf
    debug: SpamAssassin version 3.0.1
    debug: Score set 0 chosen.
    debug: running in taint mode? yes
    debug: Running in taint mode, removing unsafe env vars, and resetting PATH
    debug: PATH included '/bin', keeping.
    debug: PATH included '/sbin', keeping.
    debug: PATH included '/usr/bin', keeping.
    debug: PATH included '/usr/sbin', keeping.
    debug: Final PATH set to: /bin:/sbin:/usr/bin:/usr/sbin
    debug: using "/etc/mail/spamassassin/init.pre" for site rules init.pre
    debug: config: read file /etc/mail/spamassassin/init.pre
    debug: using "//usr/share/spamassassin" for default rules dir
    debug: config: read file //usr/share/spamassassin/10_misc.cf
    debug: config: read file //usr/share/spamassassin/20antiratware.cf
    debug: config: read file //usr/share/spamassassin/20bodytests.cf
    debug: config: read file //usr/share/spamassassin/20_compensate.cf
    debug: config: read file //usr/share/spamassassin/20dnsbltests.cf
    debug: config: read file //usr/share/spamassassin/20_drugs.cf
    debug: config: read file //usr/share/spamassassin/20fake_helotests.cf
    debug: config: read file //usr/share/spamassassin/20headtests.cf
    debug: config: read file //usr/share/spamassassin/20htmltests.cf
    debug: config: read file //usr/share/spamassassin/20metatests.cf
    debug: config: read file //usr/share/spamassassin/20_phrases.cf
    debug: config: read file //usr/share/spamassassin/20_****.cf
    debug: config: read file //usr/share/spamassassin/20_ratware.cf
    debug: config: read file //usr/share/spamassassin/20uritests.cf
    debug: config: read file //usr/share/spamassassin/23_bayes.cf
    debug: config: read file //usr/share/spamassassin/25body_testses.cf
    debug: config: read file //usr/share/spamassassin/25body_testspl.cf
    debug: config: read file //usr/share/spamassassin/25_hashcash.cf
    debug: config: read file //usr/share/spamassassin/25head_testses.cf
    debug: config: read file //usr/share/spamassassin/25head_testspl.cf
    debug: config: read file //usr/share/spamassassin/25_spf.cf
    debug: config: read file //usr/share/spamassassin/25_uribl.cf
    debug: config: read file //usr/share/spamassassin/30textde.cf
    debug: config: read file //usr/share/spamassassin/30textes.cf
    debug: config: read file //usr/share/spamassassin/30textfr.cf
    debug: config: read file //usr/share/spamassassin/30textit.cf
    debug: config: read file //usr/share/spamassassin/30textnl.cf
    debug: config: read file //usr/share/spamassassin/30textpl.cf
    debug: config: read file //usr/share/spamassassin/30textsk.cf
    debug: config: read file //usr/share/spamassassin/50_scores.cf
    debug: config: read file //usr/share/spamassassin/60_whitelist.cf
    debug: using "//etc/mail/spamassassin" for site rules dir
    debug: config: read file //etc/mail/spamassassin/local.cf
    debug: using "/private/var/root/.spamassassin" for user state dir
    debug: using "/private/var/root/.spamassassin/user_prefs" for user prefs file
    debug: config: read file /private/var/root/.spamassassin/user_prefs
    debug: plugin: loading Mail::SpamAssassin::Plugin::URIDNSBL from @INC
    debug: plugin: registered Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1924840)
    debug: plugin: loading Mail::SpamAssassin::Plugin::Hashcash from @INC
    debug: plugin: registered Mail::SpamAssassin::Plugin::Hashcash=HASH(0x1a8be70)
    debug: plugin: loading Mail::SpamAssassin::Plugin::SPF from @INC
    debug: plugin: registered Mail::SpamAssassin::Plugin::SPF=HASH(0x1af36a4)
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1924840) implements 'parse_config'
    debug: plugin: Mail::SpamAssassin::Plugin::Hashcash=HASH(0x1a8be70) implements 'parse_config'
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1924840) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1924840) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1924840) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1924840) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1924840) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1924840) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1924840) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1924840) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1924840) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1924840) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1924840) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1924840) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1924840) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1924840) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1924840) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1924840) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1924840) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1924840) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1924840) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1924840) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1924840) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1924840) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1924840) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1924840) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1924840) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1924840) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1924840) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1924840) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1924840) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1924840) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1924840) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1924840) inhibited further callbacks
    debug: config: SpamAssassin failed to parse line, skipping: auto_learn 1
    debug: config: SpamAssassin failed to parse line, skipping: safe_reporting 0
    debug: config: SpamAssassin failed to parse line, skipping: usetersereport 0
    debug: config: SpamAssassin failed to parse line, skipping: subject_tag * Warning: Junk Mail *
    debug: config: SpamAssassin failed to parse line, skipping: rewrite_subject 0
    debug: using "/private/var/root/.spamassassin" for user state dir
    debug: bayes: 17114 tie-ing to DB file R/O /private/var/root/.spamassassin/bayes_toks
    debug: bayes: 17114 tie-ing to DB file R/O /private/var/root/.spamassassin/bayes_seen
    debug: bayes: found bayes db version 3
    debug: using "/private/var/root/.spamassassin" for user state dir
    debug: bayes: Not available for scanning, only 0 spam(s) in Bayes DB < 200
    debug: bayes: 17114 untie-ing
    debug: bayes: 17114 untie-ing db_toks
    debug: bayes: 17114 untie-ing db_seen
    debug: Score set 1 chosen.
    debug: bayes: 17114 tie-ing to DB file R/O /private/var/root/.spamassassin/bayes_toks
    debug: bayes: 17114 tie-ing to DB file R/O /private/var/root/.spamassassin/bayes_seen
    debug: bayes: found bayes db version 3
    debug: bayes: Not available for scanning, only 0 spam(s) in Bayes DB < 200
    debug: bayes: 17114 untie-ing
    debug: bayes: 17114 untie-ing db_toks
    debug: bayes: 17114 untie-ing db_seen
    debug: metadata: X-Spam-Relays-Trusted:
    debug: metadata: X-Spam-Relays-Untrusted:
    debug: ---- MIME PARSER START ----
    debug: main message type: text/plain
    debug: parsing normal part
    debug: added part, type: text/plain
    debug: ---- MIME PARSER END ----
    debug: decoding: no encoding detected
    debug: Loading languages file...
    debug: Can't determine language uniquely enough
    debug: metadata: X-Languages:
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1924840) implements 'parsed_metadata'
    debug: is Net::DNS::Resolver available? yes
    debug: Net::DNS version: 0.66
    debug: trying (3) sun.com...
    debug: looking up NS for 'sun.com'
    debug: NS lookup of sun.com succeeded => Dns available (set dns_available to hardcode)
    debug: is DNS available? 1
    debug: uri found: mailto:[email protected]
    debug: uri found: mailto:[email protected]
    debug: uri found: mailto:[email protected]
    debug: uri found: mailto:[email protected]
    debug: uri found: mailto:[email protected]
    debug: URIDNSBL: domains to query: beth.k12.pa.us hetnet.nl aim.com
    debug: all '*From' addrs:
    debug: Running tests for priority: 0
    debug: running header regexp tests; score so far=0
    debug: registering glue method for checkhashcash_doublespend (Mail::SpamAssassin::Plugin::Hashcash=HASH(0x1a8be70))
    debug: registering glue method for checkfor_spf_helopass (Mail::SpamAssassin::Plugin::SPF=HASH(0x1af36a4))
    debug: SPF: message was delivered entirely via trusted relays, not required
    debug: registering glue method for checkhashcashvalue (Mail::SpamAssassin::Plugin::Hashcash=HASH(0x1a8be70))
    debug: all '*To' addrs:
    debug: registering glue method for checkfor_spfsoftfail (Mail::SpamAssassin::Plugin::SPF=HASH(0x1af36a4))
    debug: SPF: message was delivered entirely via trusted relays, not required
    debug: registering glue method for checkfor_spfpass (Mail::SpamAssassin::Plugin::SPF=HASH(0x1af36a4))
    debug: registering glue method for checkfor_spf_helosoftfail (Mail::SpamAssassin::Plugin::SPF=HASH(0x1af36a4))
    debug: registering glue method for checkfor_spf_helofail (Mail::SpamAssassin::Plugin::SPF=HASH(0x1af36a4))
    debug: running body-text per-line regexp tests; score so far=-2.801
    debug: running uri tests; score so far=-2.801
    debug: registering glue method for check_uridnsbl (Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1924840))
    debug: Razor2 is not available
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1924840) implements 'check_tick'
    debug: URIDNSBL: query for hetnet.nl took 1 seconds to look up (multi.surbl.org.:hetnet.nl)
    debug: URIDNSBL: query for aim.com took 1 seconds to look up (multi.surbl.org.:aim.com)
    debug: URIDNSBL: query for beth.k12.pa.us took 1 seconds to look up (multi.surbl.org.:beth.k12.pa.us)
    debug: URIDNSBL: queries completed: 6 started: 8
    debug: URIDNSBL: queries active: at Mon Mar 8 18:06:35 2010
    debug: running raw-body-text per-line regexp tests; score so far=-2.801
    debug: running full-text regexp tests; score so far=-2.801
    debug: Razor2 is not available
    debug: Current PATH is: /bin:/sbin:/usr/bin:/usr/sbin
    debug: Pyzor is not available: pyzor not found
    debug: DCCifd is not available: no r/w dccifd socket found.
    debug: DCC is not available: no executable dccproc found.
    debug: Running tests for priority: 500
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1924840) implements 'checkpostdnsbl'
    debug: URIDNSBL: queries completed: 8 started: 8
    debug: URIDNSBL: queries active: at Mon Mar 8 18:06:35 2010
    debug: waiting 2 seconds for URIDNSBL lookups to complete
    debug: URIDNSBL: queries completed: 0 started: 0
    debug: URIDNSBL: queries active: DNSBL=8 at Mon Mar 8 18:06:35 2010
    debug: URIDNSBL: query for aim.com took 2 seconds to look up (sbl.spamhaus.org.:132.51.12.64)
    debug: URIDNSBL: query for beth.k12.pa.us took 2 seconds to look up (sbl.spamhaus.org.:2.96.96.209)
    debug: URIDNSBL: query for aim.com took 2 seconds to look up (sbl.spamhaus.org.:80.73.200.207)
    debug: URIDNSBL: query for aim.com took 2 seconds to look up (sbl.spamhaus.org.:107.1.236.64)
    debug: URIDNSBL: query for hetnet.nl took 2 seconds to look up (sbl.spamhaus.org.:34.63.75.213)
    debug: URIDNSBL: query for hetnet.nl took 2 seconds to look up (sbl.spamhaus.org.:69.63.75.213)
    debug: URIDNSBL: query for aim.com took 2 seconds to look up (sbl.spamhaus.org.:232.157.188.205)
    debug: URIDNSBL: query for beth.k12.pa.us took 2 seconds to look up (sbl.spamhaus.org.:20.3.172.207)
    debug: URIDNSBL: queries completed: 8 started: 0
    debug: URIDNSBL: queries active: at Mon Mar 8 18:06:36 2010
    debug: done waiting for URIDNSBL lookups to complete
    debug: running meta tests; score so far=-2.801
    debug: running header regexp tests; score so far=-1.231
    debug: running body-text per-line regexp tests; score so far=-1.231
    debug: running uri tests; score so far=-1.231
    debug: running raw-body-text per-line regexp tests; score so far=-1.231
    debug: running full-text regexp tests; score so far=-1.231
    debug: Running tests for priority: 1000
    debug: running meta tests; score so far=-1.231
    debug: running header regexp tests; score so far=-1.231
    debug: running body-text per-line regexp tests; score so far=-1.231
    debug: running uri tests; score so far=-1.231
    debug: running raw-body-text per-line regexp tests; score so far=-1.231
    debug: running full-text regexp tests; score so far=-1.231
    debug: auto-learn: currently using scoreset 1.
    debug: auto-learn: message score: -1.231, computed score for autolearn: -1.231
    debug: auto-learn? ham=0.1, spam=12, body-points=0, head-points=-2.801, learned-points=0
    debug: auto-learn? yes, ham (-1.231 < 0.1)
    debug: Learning Ham
    debug: all '*From' addrs:
    debug: all '*To' addrs:
    debug: uri found: mailto:[email protected]
    debug: uri found: mailto:[email protected]
    debug: uri found: mailto:[email protected]
    debug: uri found: mailto:[email protected]
    debug: uri found: mailto:[email protected]
    debug: lock: 17114 created /private/var/root/.spamassassin/bayes.lock.mx1.beth.k12.pa.us.17114
    debug: lock: 17114 trying to get lock on /private/var/root/.spamassassin/bayes with 0 retries
    debug: lock: 17114 link to /private/var/root/.spamassassin/bayes.lock: link ok
    debug: bayes: 17114 tie-ing to DB file R/W /private/var/root/.spamassassin/bayes_toks
    debug: bayes: 17114 tie-ing to DB file R/W /private/var/root/.spamassassin/bayes_seen
    debug: bayes: found bayes db version 3
    debug: ebd3a443815ae7214b74ef30dfb2c5524e3adf7a@sa_generated: already learnt correctly, not learning twice
    debug: bayes: 17114 untie-ing
    debug: bayes: 17114 untie-ing db_toks
    debug: bayes: 17114 untie-ing db_seen
    debug: bayes: files locked, now unlocking lock
    debug: unlock: 17114 unlink /private/var/root/.spamassassin/bayes.lock
    debug: is spam? score=-1.231 required=5
    debug: tests=ALLTRUSTED,MISSING_DATE,MISSINGSUBJECT
    debug: subtests=_UNUSABLEMSGID
    X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on mx1.beth.k12.pa.us
    X-Spam-Level:
    X-Spam-Status: No, score=-1.2 required=5.0 tests=ALLTRUSTED,MISSINGDATE,
    MISSING_SUBJECT autolearn=unavailable version=3.0.1
    \f0\fs24 \cf0 Return-Path: <[email protected]>\
    Received: from murder ([unix socket]) by bragg.beth.k12.pa.us (Cyrus v2.2.12-OS X 10.4.8) with LMTPA; Sun, 07 Mar 2010 22:32:43 -0500\
    Received: from smtp3.beth.k12.pa.us (smtp3.beth.k12.pa.us [10.135.1.13]) by bragg.beth.k12.pa.us (Postfix) with ESMTP id 3D3F02CE4B19 for <[email protected]>; Sun, 7 Mar 2010 22:32:43 -0500 (EST)\
    Received: from localhost (mx1.beth.k12.pa.us [10.135.1.6]) by smtp3.beth.k12.pa.us (Postfix) with ESMTP id 7E5EB2425D0C for <[email protected]>; Sun, 7 Mar 2010 22:32:07 -0500 (EST)\
    Received: from mx1.beth.k12.pa.us ([127.0.0.1]) by localhost (mx1.beth.k12.pa.us [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 11329-05 for <[email protected]>; Sun, 7 Mar 2010 19:32:06 -0800 (PST)\
    Received: from mail2.beth.k12.pa.us (mail2.beth.k12.pa.us [192.227.0.10]) by mx1.beth.k12.pa.us (Postfix) with ESMTP id 9DDDFCF9E5 for <[email protected]>; Sun, 7 Mar 2010 19:32:06 -0800 (PST)\
    Received: from cpsmtpb-ews07.kpnxchange.com (cpsmtpb-ews07.kpnxchange.com [213.75.39.10]) by mail2.beth.k12.pa.us (Postfix) with ESMTP id 36E83E51479 for <[email protected]>; Sun, 7 Mar 2010 22:32:05 -0500 (EST)\
    Received: from cpbrm-ews29.kpnxchange.com ([10.94.84.160]) by cpsmtpb-ews07.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 8 Mar 2010 04:32:05 +0100\
    Received: from CPSMTPM-EML04.kpnxchange.com ([213.75.39.74]) by cpbrm-ews29.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 8 Mar 2010 04:32:04 +0100\
    Received: from localhost ([10.94.77.199]) by CPSMTPM-EML04.kpnxchange.com with Microsoft SMTPSVC(7.0.6001.18000); Mon, 8 Mar 2010 04:32:04 +0100\
    X-Sieve: CMU Sieve 2.2\
    Content-Class: urn:content-classes:message\
    Mime-Version: 1.0\
    Content-Type: multipart/alternative; boundary="----=_NextPart_00101CABE6F.E8E7FFDB"\
    X-Mimeole: Produced By Microsoft Exchange V6.5\
    Message-Id: <[email protected]>\
    X-Ms-Has-Attach: \
    X-Ms-Tnef-Correlator: \
    Thread-Topic: EU INT LOTTO\
    Thread-Index: Acqbc/3PXjmnUcQsGeSny2PogEEg==\
    X-Originalarrivaltime: 08 Mar 2010 03:32:04.0493 (UTC) FILETIME=[EC150BD0:01CABE6F]\
    X-Recipientdomain: beth.k12.pa.us\
    X-Spam-Status: No, hits=4.117 tagged_above=-999 required=5 tests=BAYES_50, HTML5060, HTML_MESSAGE, MIMEQP_LONGLINE, NOREALNAME, SUBJALLCAPS, UNDISC_RECIPS, UPPERCASE5075\
    X-Spam-Level: **\
    EU INT LOTTO\
    YOUR EMAIL ID HAS WON \'db1,000,000.00, IN THE FIRST CATEGORY, ALL THE E-MAIL ADDRESSES WERE SELECTED THROUGH ELECTRONIC BALLOTING SYSTEM OF INTERNET E-MAIL USERS, FROM WHICH YOUR E-MAIL ADDRESS CAME OUT AS THE WINNING COUPON.\
    Clarification and procedure Contact: [email protected]\
    Tel:\'ca\'ca\'ca\'ca +31-630-861-292\'ca\'ca\'ca\'ca\'ca\'ca\'ca\'ca \
    Miss. Gillian Rowland \
    Qualification winning Number [EU/ILO-564/003/008] \
    Expiring date is 19th of March, 2010.\
    All response should be send Via Email: [email protected]\
    }mx1:/var/clamav root#

    postfix receives the mail, then passes it to amavisd.
    amavisd decides what scanners to use (clamav/spamassassin and possibly others) and performs the scan
    amavisd might not scan the messages if certain criteria are met (size too large, white list, etc), this is all configurable in amavisd.conf. For example, the size threshold by default may be too small, so messages with large graphics may not be scanned.
    after amavis processes the message, depending on the config of amavis, certain actions are performed (add headers, discard, reject, bounce, etc).
    then amavisd passes the mail back to postfix
    postfix delivers any deliverable mail to cyrus/dovecot and/or processes and bounce/rejection.
    a rejection doesn't work in the above scenario because it's already been accepted by postfix.
    best to discard.
    if you would like to learn more about the flow and logic, look at the amavisd config file
    /etc/amavisd.conf
    and check out the docs
    http://www.ijs.si/software/amavisd/
    Jeff

  • Migrating Spamassassin Bayes DB

    I am migrating a 10.5 mailserver to new hardware running 10.6.
    The old mailserver uses a global spamassassin db stored in /var/amavis/.spamassassin and the files in this dir are as follows:
    -rw------- 1 _amavisd _amavisd 42123264 Dec 8 22:42 auto-whitelist
    -rw------- 1 _amavisd _amavisd 25272 Dec 8 22:42 bayes_journal
    -rw------- 1 _amavisd _amavisd 41549824 Dec 8 22:25 bayes_seen
    -rw------- 1 _amavisd _amavisd 5115904 Dec 8 22:25 bayes_toks
    What is the best way to migrate this bayes db to the new server?
    I thought:
    sa-learn --backup > backup.txt
    might work, but this yields basically an empty output file.
    Tips?
    Rusty
    Message was edited by: Rusty Ross

    Thanks, Alex.
    I used spamtrainer.
    A couple questions on that. The first time I ran spamtrainer -r on the new machine, I got a message from spamtrainer that /var/amavis/.spamassassin did not exist, and then spamtrainer went ahead to create the following two files in /var/amavis:
    -rw------- 1 _amavisd _amavisd 41582592 Dec 9 13:21 .spamassassin_seen
    -rw------- 1 _amavisd _amavisd 4202496 Dec 9 13:21 .spamassassin_toks
    So then, I created /var/amavis/.spamassassin and rain spamtrainer -r again.
    This time, spamtrainer created the following two files in /var/amavis/.spamassassin:
    -rw------- 1 _amavisd _amavisd 41582592 Dec 9 13:26 bayes_seen
    -rw------- 1 _amavisd _amavisd 4202496 Dec 9 13:26 bayes_toks
    ...which seems right to me.
    Two questions.
    (1) Can I safely delete .spamassassin_seen and .spamassassin_toks in /var/amavis now?
    (2) Should I be concerned that spamtrainer didn't seem to migrate bayes_journal and auto-whitelist?
    Thanks.

  • Spamassassin odd error messages

    I'm puzzled by this. Starting about 11 days ago, I've gotten the following errors in my procmail log file.
    hostname: illegal option -- -
    usage: hostname [-s] [name-of-host]
    [64745] warn: auto-whitelist: open of auto-whitelist file failed: auto-whitelist: cannot open au
    towhitelistpath /Users/XXX/.spamassassin/auto-whitelist: Inappropriate file type or format
    Log files indicated that this problem did not exist before 12/28/09, and now it pops up anytime procmail calls spamassassin.
    The system is running a fully updated 10.5.8. There is no record of updates between 12/20/09 and today according to /var/log/install.log*. Spamassassin is 3.2.5 and hasn't been updated in ages.
    I tried restoring an old version of auto-whitelist, but it didn't make a difference, as the white list hasn't changed in several months; however, removing the whitelist file and letting a new one get started did make that error go away.
    Any ideas as to what's going on here?
    thanks

    I spoke to (don't remember if it was an ATT guy) told me that ATT seems to have problems with some servers.
    Boy do they ever, I think there's maybe 2 worse ISPs in the whole world.
    Have you heard of this kind of policy? Do you think I'll need to do that?
    Yes, but it's really their problem & you shouldn't have to pay. Only you can decide if you need to do it, but I'd bet Dollars to Donuts it'll be more money down the drain.
    Internal AT&T Manual For Handling All Kinds Of Customer Complaints...
    http://consumerist.com/2007/08/internal-att-manual-for-handling-all-kinds-of-cus tomer-complaints.html
    Should you remain an AT&T customer?...
    http://moneycentral.msn.com/content/SavingandDebt/P90677.asp
    Complaints?...
    http://att.pissedconsumer.com/
    http://www.measuredup.com/company/AT-amp-T-12518/Reviews/Consumer-Complaint-1
    Life Time Value (LTV) measures the subscriber's overall value to the company (based on revenue, account plan, on and off-network and data usage, length of service, etc . ). LTV1 accounts are customers who create a negative profit for the company....
    http://www.mobile-broadband-reviews.com/att-customer-service-1.html

  • SpamAssassin & Razor how-to

    SpamAssassin & Razor how-to:
    When used in conjuction with Vipul's Razor, SpamAssassin's accuracy can really go to new levels, making junkmail filtering far more accurate. Here's how to set both of these up on a Tiger server system (note: be sure to backup your system, or at least make copies of any files you're modifying before starting!):
    First, fix a problem with SpamAssassin's out of the box configuration, by re-creating a symlink. I've found it best to sudo to root, then su to clamav, to get the permissions correct, as follows (warning: this will remove the current database of 'learned junk' if it exists):
    sudo -s
    cd /var/amavis
    mv .spamassassin .spamassassin.old
    su clamav
    ln -s /var/clamav/.spamassassin /var/amavis/.spamassassin
    When you've done this, do 'ls -la' and you should see a line like this:
    lrwxr-xr-x 1 clamav clamav 25 Feb 8 21:51 .spamassassin -> /var/clamav/.spamassassin
    Next, check a few parameters in the '/etc/mail/spamassassin/local.cf' file. First run:
    spamassassin --lint
    If you're running 10.4.2 - 10.4.4, you might see output similar to:
    config: SpamAssassin failed to parse line, skipping: auto_learn 1
    config: SpamAssassin failed to parse line, skipping: safe_reporting 0
    config: SpamAssassin failed to parse line, skipping: usetersereport 0
    config: SpamAssassin failed to parse line, skipping: subject_tag * Warning: Junk Mail *
    config: SpamAssassin failed to parse line, skipping: rewrite_subject 0
    lint: 5 issues detected. please rerun with debug enabled for more information.
    To fix this, first backup your '/etc/mail/spamassassin/local.cf' file, then open the file and change any of the above output, as follows:
    change 'auto_learn' to 'bayesautolearn'
    change 'safe_reporting' to 'safe_report'
    comment out 'usetersereport 0'
    comment out 'subject_tag' and 'rewrite_subject'
    Now issuing 'spamassassin --lint' should just return you to your command prompt without any output. If so, you're all set.
    Next, we need to check a bunch of things in the '/etc/amavisd.conf' file. First, backup your file, then make sure the following lines look as follows (don't forget the semi-colons at the end of each line!):
    $salocal_testsonly = 0;
    I like to set this to 0 (disable), in order to enable network tests by tools such as razor, which can dramatically improve SpamAssassin's accuracy. See below for more details on using Razor.
    $satag_leveldeflt = -999;
    This low threshold causes SpamAssassin to add X-Spam headers to all local messages scoring above -999, which should be all of them.
    $satag2_leveldeflt = 5;
    This is the SpamAssassin score at which to consider a message spam and tag it as such (by modifying the subject line), a good starting point is about 5
    $sakill_leveldeflt = 10;
    If a message's SpamAssassin score reaches this level, then the 'finalspamdestiny' action is taken. I like to set this to around 10, depending on what 'finalspamdestiny' is. Remember, if 'finalspamdestiny' is set to reject mail, this is the score at which the mail will be rejected. I like to start out with the 'D_PASS' setting for starters, which delivers the mail even if this score is reached (see below for more info on the 'finalspamdestiny' setting).
    $saspam_subjecttag = '* Junk Mail *';
    When a message's SpamAssassin score reaches the '$satag2_leveldeflt' score (above), then the text here is added to the beginning of the email subject line.
    $finalspamdestiny = [DDISCARD,D_BOUNCE,DPASS];
    This tells SpamAssassin what to do with a message that reaches the '$sakill_leveldeflt' score. It can be set to one of the three values above (so, for example, to deliver all mail, the line would be $finalspamdestiny = D_PASS;).
    @localdomainsacl = [acl]
    This line tells SpamAssassin which email domains are hosted by the local system, and thus which ones to take action on. Make sure all possible local domains that will be handled by your mail server are listed here. An example would be:
    @localdomainsacl = ( '.myDomain1.com', '.myDomain2.com', '.myDomain3.com' );
    OK: next, if you run virtual domains, make sure this line is uncommented (i.e. no '#' sign at the beginning of the line):
    @localdomainsmaps = ( 1 );
    If the line doesn't exist and you need it, add it after the '@localdomainsacl = ...' line.
    If you want to use razor (see below), make sure to add the following lines, if they don't already exist:
    use_razor2 1
    razor_timeout 10
    score RAZOR2CF_RANGE_51100 4.0
    Whew! OK we're done with the '/etc/amavisd.conf' file. Next, you need to feed junkmail to your system, and lots of it. First, you'll need to set up two 'training' accounts on your system. One called 'junkmail' and one called 'notjunkmail.' This is explained in more detail on page 52 of the Mail Service Admin guide, available here: http://images.apple.com/server/pdfs/MailServicev10.4.pdf.
    After you've set up these accounts, you need to redirect (be sure not to forward!!) around 200 junk and non-junk messages (around 400 total) to each mailbox. This is crucial, and if there aren't enough messages in there, SpamAssassin will be pretty inaccurate. One way to make it easier to feed the boxes is to setup the two IMAP accounts in your mail program. Then you can just drag and drop junk mail from your real account into the inbox for the 'junkmail' account (and likewise for the 'notjunkmail' account). This is a lot easier than the mass redirects. If appropriate, do the same for other users on your system.
    One more thing that is sometimes broken out of the box with Tiger Server is the script that trains the junkmail filter each day (as described in the admin guide from step 4), using the contents of the 'junkmail' and 'notjunkmail' accounts. You'll need to fix this for automatic training of the filter, and an easy way to do this is to the use the great SpamTrainer for OS X, which is available here: http://osx.topicdesk.com/downloads/. Just download and follow the simple instructions, and your training scripts will be all set to run.
    Improving SpamAssasin's accuracy with Razor:
    There are many add-ons that can be enabled which really beef up SpamAssassin's accuracy, and one I like to use is Vipul's Razor. In order to install this, you'll need the Xcode 2.2 developer tools installed on your system. To get Xcode visit the Apple Developer's site, register for a free account, then download and install the tools. Once you've done that, download razor-agents the the razor-agents sdk here. Once downloaded, unpack them like so:
    tar -xvjf razor-agents-2.77.tar.bz2
    tar -xvjf razor-agents-sdk-2.07.tar.bz2
    Then cd into the razor agents sdk dir and install, like so:
    cd razor-agents-sdk-2.07
    perl Makefile.PL
    make
    make test
    make install
    After you've done SDK, cd into the razor agents dir and do likewise, like so:
    cd ../razor-agents-2.77
    perl Makefile.PL
    make
    make test
    make install
    OK - now to set up Razor: if you're still in a root shell (i.e. you see a '#' sign at the end of your shell prompt), then type 'exit' and hit enter to return to your regular user shell (if you're not sure, just open a new terminal window, or ssh session if you're doing this over ssh). Then run:
    razor-admin -create
    which creates a config file in your user home directory. Then choose an email address with which to register razor, and do the registration:
    razor-admin -register [email protected]
    That should do it. Once you've completed these steps and trained SA, your filtering will be much more accurate.
    iBook G4   Mac OS X (10.4.4)  

    Checked my changes and found a mistake, however, I get the following error after I run spamassassin -lint
    serv3:/etc/mail/spamassassin root# spamassassin --lint
    config: SpamAssassin failed to parse line, skipping: safe_report 0
    lint: 1 issues detected. please rerun with debug enabled for more information.
    serv3:/etc/mail/spamassassin root#
    I double checked the local.cf file change to 'safe_report' and it looks good.
    When I run debug, this is what I get:
    serv3:/etc/mail/spamassassin root# spamassassin --lint -D
    debug: SpamAssassin version 3.0.1
    debug: Score set 0 chosen.
    debug: running in taint mode? yes
    debug: Running in taint mode, removing unsafe env vars, and resetting PATH
    debug: PATH included '/bin', keeping.
    debug: PATH included '/sbin', keeping.
    debug: PATH included '/usr/bin', keeping.
    debug: PATH included '/usr/sbin', keeping.
    debug: Final PATH set to: /bin:/sbin:/usr/bin:/usr/sbin
    debug: diag: module not installed: DBI ('require' failed)
    debug: diag: module installed: DB_File, version 1.810
    debug: diag: module installed: Digest::SHA1, version 2.10
    debug: diag: module installed: IO::Socket::UNIX, version 1.21
    debug: diag: module installed: MIME::Base64, version 3.05
    debug: diag: module not installed: Net::DNS ('require' failed)
    debug: diag: module not installed: Net::LDAP ('require' failed)
    debug: diag: module not installed: Razor2::Client::Agent ('require' failed)
    debug: diag: module installed: Storable, version 2.13
    debug: diag: module installed: URI, version 1.35
    debug: ignore: using a test message to lint rules
    debug: using "/etc/mail/spamassassin/init.pre" for site rules init.pre
    debug: config: read file /etc/mail/spamassassin/init.pre
    debug: using "//usr/share/spamassassin" for default rules dir
    debug: config: read file //usr/share/spamassassin/10_misc.cf
    debug: config: read file //usr/share/spamassassin/20antiratware.cf
    debug: config: read file //usr/share/spamassassin/20bodytests.cf
    debug: config: read file //usr/share/spamassassin/20_compensate.cf
    debug: config: read file //usr/share/spamassassin/20dnsbltests.cf
    debug: config: read file //usr/share/spamassassin/20_drugs.cf
    debug: config: read file //usr/share/spamassassin/20fake_helotests.cf
    debug: config: read file //usr/share/spamassassin/20headtests.cf
    debug: config: read file //usr/share/spamassassin/20htmltests.cf
    debug: config: read file //usr/share/spamassassin/20metatests.cf
    debug: config: read file //usr/share/spamassassin/20_phrases.cf
    debug: config: read file //usr/share/spamassassin/20_****.cf
    debug: config: read file //usr/share/spamassassin/20_ratware.cf
    debug: config: read file //usr/share/spamassassin/20uritests.cf
    debug: config: read file //usr/share/spamassassin/23_bayes.cf
    debug: config: read file //usr/share/spamassassin/25body_testses.cf
    debug: config: read file //usr/share/spamassassin/25body_testspl.cf
    debug: config: read file //usr/share/spamassassin/25_hashcash.cf
    debug: config: read file //usr/share/spamassassin/25head_testses.cf
    debug: config: read file //usr/share/spamassassin/25head_testspl.cf
    debug: config: read file //usr/share/spamassassin/25_spf.cf
    debug: config: read file //usr/share/spamassassin/25_uribl.cf
    debug: config: read file //usr/share/spamassassin/30textde.cf
    debug: config: read file //usr/share/spamassassin/30textes.cf
    debug: config: read file //usr/share/spamassassin/30textfr.cf
    debug: config: read file //usr/share/spamassassin/30textit.cf
    debug: config: read file //usr/share/spamassassin/30textnl.cf
    debug: config: read file //usr/share/spamassassin/30textpl.cf
    debug: config: read file //usr/share/spamassassin/30textsk.cf
    debug: config: read file //usr/share/spamassassin/50_scores.cf
    debug: config: read file //usr/share/spamassassin/60_whitelist.cf
    debug: using "//etc/mail/spamassassin" for site rules dir
    debug: config: read file //etc/mail/spamassassin/local.cf
    debug: using "/Users/admin/.spamassassin" for user state dir
    debug: using "/Users/admin/.spamassassin/user_prefs" for user prefs file
    debug: config: read file /Users/admin/.spamassassin/user_prefs
    debug: plugin: loading Mail::SpamAssassin::Plugin::URIDNSBL from @INC
    debug: failed to load Net::DNS::Resolver: Can't locate Net/DNS.pm in @INC (@INC contains: //lib/perl5/site_perl /System/Library/Perl/5.8.6/darwin-thread-multi-2level /System/Library/Perl/5.8.6 /Library/Perl/5.8.6/darwin-thread-multi-2level /Library/Perl/5.8.6 /Library/Perl /Network/Library/Perl/5.8.6/darwin-thread-multi-2level /Network/Library/Perl/5.8.6 /Network/Library/Perl /System/Library/Perl/Extras/5.8.6/darwin-thread-multi-2level /System/Library/Perl/Extras/5.8.6 /Library/Perl/5.8.1) at /System/Library/Perl/Extras/5.8.6/Mail/SpamAssassin/Plugin/URIDNSBL.pm line 113.
    debug: plugin: registered Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x19242e4)
    debug: plugin: loading Mail::SpamAssassin::Plugin::Hashcash from @INC
    debug: plugin: registered Mail::SpamAssassin::Plugin::Hashcash=HASH(0x1ac973c)
    debug: plugin: loading Mail::SpamAssassin::Plugin::SPF from @INC
    debug: plugin: registered Mail::SpamAssassin::Plugin::SPF=HASH(0x1a419d8)
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x19242e4) implements 'parse_config'
    debug: plugin: Mail::SpamAssassin::Plugin::Hashcash=HASH(0x1ac973c) implements 'parse_config'
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x19242e4) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x19242e4) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x19242e4) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x19242e4) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x19242e4) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x19242e4) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x19242e4) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x19242e4) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x19242e4) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x19242e4) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x19242e4) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x19242e4) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x19242e4) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x19242e4) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x19242e4) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x19242e4) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x19242e4) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x19242e4) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x19242e4) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x19242e4) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x19242e4) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x19242e4) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x19242e4) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x19242e4) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x19242e4) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x19242e4) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x19242e4) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x19242e4) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x19242e4) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x19242e4) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x19242e4) inhibited further callbacks
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x19242e4) inhibited further callbacks
    config: SpamAssassin failed to parse line, skipping: safe_report 0
    debug: using "/Users/admin/.spamassassin" for user state dir
    debug: bayes: no dbs present, cannot tie DB R/O: /Users/admin/.spamassassin/bayes_toks
    debug: Score set 1 chosen.
    debug: ---- MIME PARSER START ----
    debug: main message type: text/plain
    debug: parsing normal part
    debug: added part, type: text/plain
    debug: ---- MIME PARSER END ----
    debug: bayes: no dbs present, cannot tie DB R/O: /Users/admin/.spamassassin/bayes_toks
    debug: metadata: X-Spam-Relays-Trusted:
    debug: metadata: X-Spam-Relays-Untrusted:
    debug: decoding: no encoding detected
    debug: Loading languages file...
    debug: Language possibly: en,sco
    debug: metadata: X-Languages: en sco
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x19242e4) implements 'parsed_metadata'
    debug: is Net::DNS::Resolver available? no
    debug: is DNS available? 0
    debug: Running tests for priority: 0
    debug: running header regexp tests; score so far=0
    debug: registering glue method for checkhashcash_doublespend (Mail::SpamAssassin::Plugin::Hashcash=HASH(0x1ac973c))
    debug: registering glue method for checkfor_spf_helopass (Mail::SpamAssassin::Plugin::SPF=HASH(0x1a419d8))
    debug: all '*From' addrs: [email protected]
    debug: registering glue method for checkhashcashvalue (Mail::SpamAssassin::Plugin::Hashcash=HASH(0x1ac973c))
    debug: all '*To' addrs:
    debug: registering glue method for checkfor_spfsoftfail (Mail::SpamAssassin::Plugin::SPF=HASH(0x1a419d8))
    debug: registering glue method for checkfor_spfpass (Mail::SpamAssassin::Plugin::SPF=HASH(0x1a419d8))
    debug: registering glue method for checkfor_spf_helosoftfail (Mail::SpamAssassin::Plugin::SPF=HASH(0x1a419d8))
    debug: registering glue method for checkfor_spf_helofail (Mail::SpamAssassin::Plugin::SPF=HASH(0x1a419d8))
    debug: running body-text per-line regexp tests; score so far=-2.623
    debug: running uri tests; score so far=-2.623
    debug: registering glue method for check_uridnsbl (Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x19242e4))
    debug: Razor2 is not available
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x19242e4) implements 'check_tick'
    debug: running raw-body-text per-line regexp tests; score so far=-2.623
    debug: running full-text regexp tests; score so far=-2.623
    debug: Razor2 is not available
    debug: Current PATH is: /bin:/sbin:/usr/bin:/usr/sbin
    debug: Pyzor is not available: pyzor not found
    debug: DCCifd is not available: no r/w dccifd socket found.
    debug: DCC is not available: no executable dccproc found.
    debug: Running tests for priority: 500
    debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x19242e4) implements 'checkpostdnsbl'
    debug: running meta tests; score so far=-2.623
    debug: running header regexp tests; score so far=-1.053
    debug: running body-text per-line regexp tests; score so far=-1.053
    debug: running uri tests; score so far=-1.053
    debug: running raw-body-text per-line regexp tests; score so far=-1.053
    debug: running full-text regexp tests; score so far=-1.053
    debug: Running tests for priority: 1000
    debug: running meta tests; score so far=-1.053
    debug: running header regexp tests; score so far=-1.053
    debug: using "/Users/admin/.spamassassin" for user state dir
    debug: lock: 16898 created /Users/admin/.spamassassin/auto-whitelist.lock.serv3.aaaaaaaaaaaa.com.16898
    debug: lock: 16898 trying to get lock on /Users/admin/.spamassassin/auto-whitelist with 0 retries
    debug: lock: 16898 link to /Users/admin/.spamassassin/auto-whitelist.lock: link ok
    debug: Tie-ing to DB file R/W in /Users/admin/.spamassassin/auto-whitelist
    debug: auto-whitelist (db-based): [email protected]|ip=none scores 0/0
    debug: AWL active, pre-score: -1.053, autolearn score: -1.053, mean: undef, IP: undef
    debug: DB addr list: untie-ing and unlocking.
    debug: DB addr list: file locked, breaking lock.
    debug: unlock: 16898 unlink /Users/admin/.spamassassin/auto-whitelist.lock
    debug: Post AWL score: -1.053
    debug: running body-text per-line regexp tests; score so far=-1.053
    debug: running uri tests; score so far=-1.053
    debug: running raw-body-text per-line regexp tests; score so far=-1.053
    debug: running full-text regexp tests; score so far=-1.053
    debug: is spam? score=-1.053 required=8
    debug: tests=ALLTRUSTED,MISSING_DATE,MISSING_SUBJECT,NO_REALNAME
    debug: subtests=_HAS_MSGID,__MSGID_OK_DIGITS,__MSGID_OK_HOST,__SANE_MSGID,__UNUSABLEMSGID
    lint: 1 issues detected. please rerun with debug enabled for more information.
    serv3:/etc/mail/spamassassin root#

Maybe you are looking for

  • I can no longer transfer music to a project. i could earlier but something happened and now i can't. any suggestions?

          I need help with dragging music to my video project. I was able to do it at the beggining of the project but now the mouse won't grab the music. Any suggestions?

  • Facing issues in standby database

    standby database is in sync but when we say archive log list "Current log sequence " and "Oldest online log sequence" are not geting updated even though archives are getting applied. Solution :- We can create new standby controlfile in order to get t

  • How much RAM in my iMac?

    I am sitting with a 20 inch iMac, with a 2.16 Ghz Core 2 Duo CPU. Has anyone installed 4 GB or 3 GB of RAM in this model? Would appreciate any advice based on your experiences. Thank you

  • Trying to mpeg file into FCP/is it possible?

    Hello, Trying to import a mpeg file into fcp. I pulled it into my project and put it up on the timeline. Then rendered it but nothing was there. I can open the mpeg with my VLC player. I can not open it with my quicktime player. Does anyone have any

  • New CC account - no apps will install

    I have signed up to Creative Cloud on OS X (Mavericks), but no installers will go past 42% (in fact they all stop at exactly this point). I have tried this too in safe mode, same result, and have downloaded trial versions manually with a view to acti