email marked as Spam when it isn't, with 3.20-4

Michael Keightley mk at quadstone.com
Tue Jun 18 16:51:26 IST 2002


I've upgraded from 3.14-3 from 3.20-4, using SpamAssassin 2.30 on Solaris.      I received a number of emails soon afterwards which didn't look like spam, and  didn't have the usual SpamAssassin header added (with the score).               The headers looked like this:                                                                                                                                     X-MailScanner-SpamCheck: SpamAssassin ()                                                                                                                      i.e. nothing between the brackets.  Any idea what is going wrong?  I've had to  revert back to 3.14-3.   Attached are the mailscanner.conf and                  spam.assassin.prefs.conf for V3.20.4.  I've also attached one of the mail       messages that was affected.                                                                                                                                     Michael
-------------- next part --------------
# Configuration file for MailScanner E-Mail Virus Scanner
# This file assumes everything is in the default locations provided
# by the MailScanner and Solaris (using /opt).
#
# Note: If your directories are symlinked (soft-linked) in any way,
#       please put their *real* location in here, not a path that
#       includes any links. You may get some very strange error
#       messages from some of the virus scanners if you don't.

# User to run as (provided for Exim users)
#Run As User = mail

# Group to run as (provided for Exim users)
#Run As Group = mail

# In every batch of virus-scanning, limit the maximum
# a) number of text-only messages to deliver
# b) number of potentially infected messages to unpack and scan
# c) total size of text-only messages to deliver
# d) total size of potentially infected messages to unpack and scan
Max Safe   Messages Per Scan = 500
Max Unsafe Messages Per Scan = 100
Max Safe   Bytes Per Scan = 100000000
Max Unsafe Bytes Per Scan = 50000000

# To avoid resource leaks, re-start periodically.
Restart Every = 14400 # 4 hours

# Name of this host, or just "the MailScanner" if you want to hide this info.
# It can be placed in the Help Desk note contained in virus warnings sent to users.
Host name          = the MailScanner

# Add this extra header to all mail as it is scanned.
# (this must *include* terminating colon).
Mail Header = X-MailScanner:

# Set the mail header to these values for clean/infected messages.
Clean Header       = Found to be clean
Infected Header    = Suspect attachment
Disinfected Header = Disinfected

# Set where to unpack incoming messages before scanning them
Incoming Work Dir  = /var/opt/mailscanner/var/incoming

# Set where to store infected message attachments (if they are kept)
Quarantine Dir     = /var/opt/mailscanner/var/quarantine

# Set where to store the process id so you can easily stop the scanner
Pid File           = /var/opt/mailscanner/var/virus.pid

# Set where to find the attachment filename ruleset.
# The structure of this file is explained elsewhere, but it is used to
# accept or reject file attachments based on their name, regardless of
# whether they are infected or not.
Filename Rules     = /var/opt/mailscanner/etc/filename.rules.conf

# Log all the filenames that are allowed by the Filename Rules, or just
# the filenames that are denied?
Log Permitted Filenames = no

# Set where to find the message text sent to users when one of their
# attachments has been quarantined.
Stored Virus Message Report  = /var/opt/mailscanner/etc/stored.virus.message.txt
Stored Bad Filename Message Report  = /var/opt/mailscanner/etc/stored.filename.message.txt

# Set where to find the message text sent to users when one of their
# attachments has been deleted.
Deleted Virus Message Report = /var/opt/mailscanner/etc/deleted.virus.message.txt
Deleted Bad Filename Message Report = /var/opt/mailscanner/etc/deleted.filename.message.txt

# Set where to find the message text sent to users explaining about the
# attached disinfected documents.
Disinfected Report = /var/opt/mailscanner/etc/disinfected.report.txt

# Set location of incoming mail queue
# and location of outgoing mail queue.
Incoming Queue Dir = /var/spool/mqueue.in
Outgoing Queue Dir = /var/spool/mqueue

# Set whether to use sendmail or exim (default is sendmail)
MTA                = sendmail

# Set how to invoke MTA when sending created message
# (e.g. to sender/recipient saying "found a virus in your message")
Sendmail           = /usr/lib/sendmail

# Sendmail2 is provided for Exim users.
# It defaults to the value supplied for Sendmail.
# It is the command used to attempt delivery of outgoing
# (scanned/cleaned) messages.
# This is not usually required for sendmail.
#Sendmail2          = /usr/sbin/exim -C /etc/exim_send.conf

# Do you want to scan email for viruses?
# A few people have wanted to disable the entire virus scanning.
Virus Scanning     = no

# Which Virus Scanning package to use:
# sophos    from www.sophos.com, or
# mcafee    from www.mcafee.com, or
# command   from www.command.co.uk, or
# kaspersky from www.kaspersky.com, or
# inoculate from www.cai.com/products/inoculateit.htm, or
# inoculan  from ftp.ca.com/getbbs/linux.eng/inoctar.LINUX.Z, or
# nod32     from www.nod32.com, or
# f-secure  from www.f-secure.com, or
# f-prot    from www.f-prot.com
# panda     from www.panda.com (?), or
# rav       from www.rav.com (?)
#
# Note: If you want to use multiple virus scanners, then this should be a
# comma-separated list of virus scanners. For example:
# Virus Scanner      = sophos, f-prot
#
Virus Scanner = sophos

# Where the Virus scanner is installed. This is the command needed to run it.
#
# Note: If you want to use multiple virus scanners, then this should be a
# comma-separated list of commands, **in the same order** as they are listed
# in the "Virus Scanner" keyword just above. For example:
# Sweep = /opt/sophos/bin/sophoswrapper, /opt/f-prot/f-protwrapper
#
Sweep = /opt/sophos/bin/sophoswrapper

# The maximum length of time the commercial virus scanner is allowed to run
# for 1 batch of messages (in seconds).
Virus Scanner Timeout = 300

# Expand TNEF attachments using an external program?
# This should be "yes" except for Sophos and McAfee (when it can be "no")
# as Sophos and McAfee have the facility built-in.
Expand TNEF        = yes

# Where the MS-TNEF expander is installed.
# This is EITHER the full command (including maxsize option) that runs
# the external TNEF expander binary,
# OR the keyword "internal" which will make MailScanner use the Perl
# module that does the same job.
# They are both provided as I am unsure which one is faster and which
# one is capable of expanding more file formats (there are plenty!).
#
# The --maxsize option limits the maximum size that any expanded
# attachment
# may be. It helps protect against Denial Of Service attacks in TNEF
# files.
#TNEF Expander    = internal
TNEF Expander      = /var/opt/mailscanner/bin/tnef --maxsize=100000000

# The maximum length of time the TNEF Expander is allowed to run for 1 message.
# (in seconds)
TNEF Timeout       = 120

# What should the attachments be called that replace virus-infected files?
Attachment Warning Filename = MailScanWarning.txt

# Should these replacements be attachments (yes) or in the message body (no)
Warning Is Attachment = no

# Should we scan all messages, including plain-text messages which are normally
# harmless? This should be "yes" since the MyParty message appeared.
Scan All Messages = yes

# Once we have removed viruses from an email message and replaced them with
# VirusWarning.txt attachments, should we deliver the clean result to the
# original recipients (or just delete them if "no")?
Deliver To Recipients = yes

# Do you want to put some text on the front of the subject line when
# it contained a virus which has been removed
Virus Modify Subject = yes

# What text do we want to put on the front (gets followed by a " ")
Virus Subject Text = {VIRUS?}

# Deliver messages with viruses removed to their original recipients
# if they came from a local address, or just delete them so no-one knows
# we have a virus outbreak on our site?
Deliver From Local Domains = yes

# Notify the senders of infected messages that they should check out
# their systems?
Notify Senders = no

# Set where to find the message text sent to the senders of infected
# messages.
#Sender Report = /opt/mailscanner/etc/sender.report.txt
Sender Virus Report        = /var/opt/mailscanner/etc/sender.virus.report.txt
Sender Bad Filename Report = /var/opt/mailscanner/etc/sender.filename.report.txt
Sender Error Report        = /var/opt/mailscanner/etc/sender.error.report.txt

# Notify the local postmaster when any infections are found?
Notify Local Postmaster = yes

# Include the full headers of each message in the postmaster notification?
Postmaster Gets Full Headers = yes

# Set email address of who to notify about any infections found.
# Should put your full domain name here too,
#    e.g. postmaster at your.domain.com
Local Postmaster = mailscanner at quadstone.com

# Set what to do with infected attachments or messages.
# keep   ==> Store under the "Quarantine Dir"
# delete ==> Just delete them
#Action = delete
Action = keep

# Do you want to quarantine the original *entire* message as well as
# just the infected attachment
Quarantine Whole Message = no

# Should I attempt to disinfect infected attachments and then deliver
# the clean ones
Deliver Disinfected Files = yes

# Local domain name, or filename containing a list of local domain names
# The file supports blank entries, '#' and ';' comment characters and
# uses the first word off each line. This should be compatible with all
# such lines in a sendmail or Exim configuration file.
#Local Domains = /opt/mailscanner/etc/localdomains.conf
Local Domains = /var/opt/mailscanner/etc/localdomains.conf

# Filename containing a list (1 on each line) of the exact names of
# viruses you want to quietly delete or quarantine without informing
# either the sender or the recipient. Any email messages containing one
# of the viruses listed in this file will be quietly deleted. The only
# person who will be warned about the virus will be the local postmaster.
#
# Make the virus names in this file as specific as possible, in order
# to avoid any accidents with files which both
# 1) have a filename containing the name of a listed viruses, *and*
# 2) are infected with viruses whose names are not listed.
#
# In other words, you will be just fine so long as you list the exact
# names of viruses, e.g. "W32/Klez-H" and "W32/Klez-G", not just
# generic names that catch many different viruses, e.g. "Klez".
#Viruses To Quietly Delete = /opt/mailscanner/etc/viruses.to.delete.conf

# Mark infected messages in the message body.
# There can now be more than 1 of these configuration lines here, so you can
# break the warning message over multiple lines.
Mark Infected Messages = yes
Inline Text Warning = Warning: This message has had one or more attachments removed.
Inline Text Warning = Warning: Please read the "MailScanWarning.txt" attachment(s) for more information.
Inline HTML Warning = <P><B><FONT SIZE="+1" COLOR="red">Warning: </FONT>This message has had one or more attachments removed.<BR>Please read the "MailScanWarning.txt" attachment(s) for more information.</B><BR></P>

# Sign clean messages in the message body.
# There can be more than 1 of these configuration lines here, so you can
# break the signature message over multiple lines.
# Note that enabling this option will add to the overall system load as some
# major optimisations will no longer be possible!
Sign Clean Messages = no
Inline Text Signature = --
Inline Text Signature = This message has been scanned for viruses and
Inline Text Signature = dangerous content by MailScanner, and is
Inline Text Signature = believed to be clean.
Inline HTML Signature = <BR>--
Inline HTML Signature = <BR>This message has been scanned for viruses and
Inline HTML Signature = <BR>dangerous content by
Inline HTML Signature = <A HREF="http://www.mailscanner.info/"><B>MailScanner</B></A>,
Inline HTML Signature = and is<BR>believed to be clean.

# Do you want to archive all mail in a directory for later inspection?
# Be warned if you are in the UK: this may well be illegal due to RIPA
# and DPA restrictions!
Archive Mail = no

# Where to store the mail archive.
# Be warned: this is likely to get big very quickly.
Archive Mail Dir = /var/spool/MailArchive

#
# Per-Domain Scanning and Spam Detection
#
# Do we want to only scan certain named domains for viruses and spam?
Scanning By Domain = no

# Filename listing all the domains we want to scan
Domains To Scan = /var/opt/mailscanner/etc/domains.to.scan.conf

# Do we want to add a MailScanner header to messages we have not scanned
Sign Unscanned Messages = yes

# What do we want to put in the header
Unscanned Header = not scanned: please contact your email provider for details

#
# Spam Detection
#
# Should the anti-spam checks be done on all incoming messages?
Spam Checks = yes

# Set the name of the extra header to add to all messages found to be
# likely spam.
Spam Header = X-MailScanner-SpamCheck:

# Do you want to put some text on the front of the subject line when
# we think it is spam?
Spam Modify Subject = yes

# What text do we want to put on the front (gets followed by a " ")
Spam Subject Text = {SPAM?}

# Action to take when a message is detected as being spam:
#   deliver ==> Deliver it to the recipient
#   store   ==> Move it to the quarantine
#   delete  ==> Delete it completely
# or else it can be a filename containing per-user and per-domain spam
# actions.
# Spam Action = /opt/mailscanner/etc/spam.actions.conf
Spam Action = deliver

# Do we want to log every spam message, including why it was spam?
# Doing so may well slow down a busy server.
Log Spam = no

# Do we have the SpamAssassin package installed?
# This is a very good, very clever heuristics-based spam checker.
# For more info & installation instructions, see http://spamassassin.taint.org/
Use SpamAssassin = yes

# Set the maximum size of message which we will check with SpamAssassin
# Don't set this too large as your system load will get very high processing
# huge messages.
Max SpamAssassin Size = 50000

# Set the maximum time to allow SpamAssassin to process 1 message
SpamAssassin Timeout = 10

# Set the location of the SpamAssassin user_prefs file. If you want to
# stop SpamAssassin doing all the RBL checks again, then you can add
# "skip_rbl_checks = 1" to this file.
# This must be defined if "Compile SpamAssasin Once = yes".
SpamAssassin Prefs File = /var/opt/mailscanner/etc/spam.assassin.prefs.conf

# Set this option to yes to enable the automatic whitelisting functions
# available within SpamAssassin. This will cause addresses from which you
# get real mail to be marked, so that it never incorrectly tags mail from
# there as being spam.
# Note: Personally, I would always set this to yes, but the functionality
#       is quite new so I didn't want to enable it by default in case there
#       are problems with it.
SpamAssassin Auto Whitelist = yes

# Should we compile all the SpamAssassin code once, or do it separately
# for every message. There certainly used to be bugs in SpamAssassin
# that meant this needed to be switched off, but these may have been
# fixed. It is a lot faster with it switched on.
# If you get a lot of false positives from SpamAssassin, switch this off.
Compile SpamAssassin Once = yes

# If you set this to yes, then the SpamAssassin report header will be
# included in all messages, not just those which are spam.
Always Include SpamAssassin Report = no

# Set the list of database names and their corresponding DNS domains.
# All of these databases work in a similar way, allowing the simple use
# of multiple databases.
# See www.ordb.org and www.mail-abuse.org for more information.
# Note: If also using SpamAssassin, it is quicker to comment out all
#       these and let SpamAssassin do it (which it does by default).
# Note: There is a complete list of these databases at
#       http://www.declude.com/JunkMail/Support/ip4r.htm.
Spam List = ORDB-RBL, relays.ordb.org.
# You might find these 2 useful as well.
#Spam List = spamcop.net, bl.spamcop.net.
#Spam List = osirusoft.com, relays.osirusoft.com.
# MAPS now charge for their services, so you'll have to buy a contract before
# attempting to use the next 3 lines.
#Spam List = MAPS-RBL, blackholes.mail-abuse.org.
#Spam List = MAPS-DUL, dialups.mail-abuse.org.
#Spam List = MAPS-RSS, relays.mail-abuse.org.
# This next line works for JANET UK Academic sites only
Spam List = MAPS-RBL+, rbl-plus.mail-abuse.org.

# And build a similar list for the RBL domains that work on the name
# of the domain rather than the IP address of the exact machine that
# is listed. This way the RBL controllers can blacklist entire
# domains very quickly and easily.
# These are disabled by default, as they will slow down the spam checks.
#Spam Domain List = RFC-IGNORANT-DSN, dsn.rfc-ignorant.org.
#Spam Domain List = RFC-IGNORANT-POSTMASTER, postmaster.rfc-ignorant.org.
#Spam Domain List = RFC-IGNORANT-ABUSE, abuse.rfc-ignorant.org.
#Spam Domain List = RFC-IGNORANT-WHOIS, whois.rfc-ignorant.org.

# Set the maximum total time per message to do all "Spam List" checks
Spam List Timeout = 5

# Define local networks from whom you should always accept mail, and
# never mark it as spam. This is useful in case your own mail servers
# are ever in the ORBS or MAPS lists.
Accept Spam From = 190.80.190.
Accept Spam From = 192.168.192.
Accept Spam From = 192.168.198.

# Define a list of email addresses and email domains from whom you should
# always accept mail, and never mark it as spam. This is useful in case
# someone you correspond with a lot has their mail servers in the ORBS or
# MAPS lists.
Spam White List = /var/opt/mailscanner/etc/spam.whitelist.conf

#
# Advanced Features
# =================
#
# Don't bother changing anything below this unless you really know what
# you are doing.
#

# Set Debug to 1 to stop it running as a daemon
# and produce more verbose output
Debug = 0

# Attempt immediate delivery of messages, or just place them in the outgoing
# queue for the MTA to deliver at a time of its own choosing?
# If attempting immediate delivery, do them one at a time,
#                                or do them in batches of 30 at a time?
# Delivery Method = queue
# Delivery Method = individual
Delivery Method = batch

# How to lock spool files.
# Don't set this unless you *know* you need to.
# For sendmail, it defaults to "flock".
# For Exim, it defaults to "posix".
# No other type is implemented.
#Lock Type          = flock

# Where to put the virus scanning engine lock files.
# These lock files are used between MailScanner and the virus signature
# "autoupdate" scripts, to ensure that they aren't both working at the
# same time (which could cause MailScanner to let a virus through).
Lock File Dir = /tmp

# What to do when you get several MailScanner headers in one message,
# from multiple MailScanner servers. Values are
# "append"  : Append the new data to the existing header
# "add"     : Add a new header
# "replace" : Replace the old data with the new data
# Default is "append"
Multiple Headers = append

# Some versions of Microsoft Outlook generate unparsable Rich Text
# format attachments. Do we want to deliver these bad attachments anyway?
# Setting this to yes introduces the slight risk of a virus getting through,
# but if you have a lot of troubled Outlook users you might need to do this.
# We are working on a replacement for the TNEF decoder.
Deliver Unparsable TNEF = no

# When attempting delivery of outgoing messages, should we do it in the
# background or wait for it to complete? The danger of doing it in the
# background is that the machine load goes ever upwards while all the
# slow sendmail processes run to completion. However, running it in the
# foreground may cause the mail server to run too slowly.
Deliver In Background = yes

# Minimum acceptable code stability status -- if we come across code
# that's not at least as stable as this, we barf.
# This is currently only used to check that you don't end up using untested
# virus scanner support code without realising it.
# Levels used are:
# none          - there may not even be any code.
# unsupported   - code may be completely untested, a contributed dirty hack,
#                 anything, really.
# alpha         - code is pretty well untested. Don't assume it will work.
# beta          - code is tested a bit. It should work.
# supported     - code *should* be reliable.
#
# Don't even *think* about setting this to anything other than "beta" or
# "supported" on a system that receives real mail until you have tested it
# yourself and are happy that it is all working as you expect it to.
# Don't set it to anything other than "supported" on a system that could
# ever receive important mail.
Minimum Code Status = supported

-------------- next part --------------
# MailScanner
# MailScanner users, please see the comments at the bottom of this file.
# MailScanner
#
# SpamAssassin user preferences file.
#
# Format:
#
#   required_hits n
#               (how many hits are required to tag a mail as spam.)
#
#   auto_report_threshold n
#               (spams with this many hits or more, will be reported
#               as spam straightaway without requiring human verification.)
#
#   score SYMBOLIC_TEST_NAME n
#               (if this is omitted, 1 is used as a default score.
#               Set the score to 0 to ignore the test.)
#
# # starts a comment, whitespace is not significant.
#
###########################################################################

###########################################################################
# First of all, the generally useful stuff; thresholds and the whitelist
# of addresses which, for some reason or another, often trigger false
# positives.

required_hits           5
auto_report_threshold   30

# Whitelist and blacklist addresses are *not* patterns; they're just normal
# strings.  one exception is that "*@isp.com" is allowed.  They should be in
# lower-case.  You can either add multiple addrs on one line,
# whitespace-separated, or you can use multiple lines.
#
# Monty Solomon: he posts from an ISP that has often been the source of spam
# (no fault of his own ;), and sometimes uses Bcc: when mailing.
#
whitelist_from          monty at roscom.com

# Add your blacklist entries in the same format...
#
# blacklist_from        friend at public.com

# Mail using languages used in these country codes will not be marked
# as being possibly spam in a foreign language.
#
ok_locales              en

# By default, the subject lines of suspected spam will be tagged.
# This can be disabled here.
#
# rewrite_subject 0

# By default, spamassassin will include its report in the body
# of suspected spam. Enabling this causes the report to go in the
# headers instead. Using 'use_terse_report' for this is recommended.
#
# report_header 1

# By default, SpamAssassin uses a fairly long report format.
# Enabling this uses a shorter format which includes all the
# information in the normal one, but without the superfluous
# explanations.
#
# use_terse_report 0

# By default, spamassassin will change the Content-type: header of
# suspected spam to "text/plain". This is a safety feature. If you
# prefer to leave the Content-type header alone, set this to 0.
#
# defang_mime 0

# By default, SpamAssassin will run RBL checks.  If your ISP already
# does this, set this to 1.
#
skip_rbl_checks 1

###########################################################################
# Add your own customised scores for some tests below.  The default scores are
# read from the installed "spamassassin.cf" file, but you can override them
# here.  To see the list of tests and their default scores, go to
# http://spamassassin.taint.org/tests.html .

# MailScanner: Comment out the next line to enable DCC checking if you
#              have dcc installed (optional part of SpamAssassin)
score DCC_CHECK 0.0

#
# Added for MailScanner 14/6/2002
# If you specify these scores, SpamAssassin will do RBL checks as well as
# MailScanner, which just wastes CPU power and network bandwidth. Either
# do them here by uncommenting the rules below (if you have paid for them)
# or else uncomment the "skip_rbl_checks" line above and let MailScanner
# do the checks instead.
#
#score RCVD_IN_BL_SPAMCOP_NET    4
# These next 3 will cost you money, see mailscanner.conf.
#score RCVD_IN_RBL               10
#score RCVD_IN_RSS               1
#score RCVD_IN_DUL               1

-------------- next part --------------
>From imp-bounces at lists.horde.org  Tue Jun 18 15:44:56 2002
Return-Path: <imp-bounces at lists.horde.org>
Received: from quadstone.com (postie.quadstone.co.uk [194.80.190.3])
        by edinburgh.quadstone.com (8.12.3/8.12.3) with ESMTP id g5IEitTs006343
        for <mk at edinburgh.quadstone.com>; Tue, 18 Jun 2002 15:44:56 +0100 (BST)
Received: from vlad.horde.org (vlad.horde.org [199.175.137.148])
        by quadstone.com (8.12.3/8.12.3) with ESMTP id g5IEi3qU025409
        for <mk at quadstone.com>; Tue, 18 Jun 2002 15:44:04 +0100 (BST)
Received: from vlad.horde.org (localhost [127.0.0.1])
        by vlad.horde.org (Postfix) with ESMTP
        id 9387F6CB; Tue, 18 Jun 2002 07:43:50 -0700 (PDT)
Delivered-To: imp at lists.horde.org
Received: from smapps2.cdcna.com (smapps2.cdcna.com [63.66.5.42])
        by vlad.horde.org (Postfix) with ESMTP id B1B065E1
        for <imp at lists.horde.org>; Tue, 18 Jun 2002 07:43:43 -0700 (PDT)
Received: from cdcna.com (localhost [127.0.0.1])
        by smapps2.cdcna.com (8.9.3/8.9.3) with ESMTP id KAA14402
        for <imp at lists.horde.org>; Tue, 18 Jun 2002 10:42:21 -0400 (EDT)
Received: (from ssmtp at localhost)
        by cdcna.com (8.9.3/8.9.3) id KAA14397
        for <imp at lists.horde.org>; Tue, 18 Jun 2002 10:42:21 -0400 (EDT)
From: m.ibarra at cdcixis-na.com
X-Authentication-Warning: smapps2.cdcna.com: ssmtp set sender to
        <m.ibarra at cdcixis-na.com> using -f
Received: from mailps2(10.90.60.67) by smapps2 via smap (V2.1)
        id sma014389; Tue, 18 Jun 02 10:42:07 -0400
Received: from winntsvr.cdcna.com (winntsvr [10.90.20.57])
        by mailps2.cdcna.com (8.9.3/8.9.3) with ESMTP id KAA20908
        for <imp at lists.horde.org>; Tue, 18 Jun 2002 10:43:23 -0400 (EDT)
Received: by winntsvr.cdcna.com with Internet Mail Service (5.5.2650.21)
        id <LYD67RN0>; Tue, 18 Jun 2002 10:43:27 -0400
Message-ID: <9877566273EED511A7560008C716DA06011360BF at exchcpn1.cdcna.com>
To: imp at lists.horde.org
Date: Tue, 18 Jun 2002 10:43:24 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
        charset="iso-8859-1"
Subject: {SPAM?} [imp] Errors when viewing messages
X-BeenThere: imp at lists.horde.org
X-Mailman-Version: 2.1b2+
Precedence: list
List-Id: IMP mailing list <imp.lists.horde.org>
List-Post: <mailto:imp at lists.horde.org>
List-Subscribe: <http://lists.horde.org/mailman/listinfo/imp>,
        <mailto:imp-request at lists.horde.org?subject=subscribe>
List-Unsubscribe: <http://lists.horde.org/mailman/listinfo/imp>,
        <mailto:imp-request at lists.horde.org?subject=unsubscribe>
List-Archive: <http://lists.horde.org/archives/imp>
List-Help: <mailto:imp-request at lists.horde.org?subject=help>
Sender: imp-bounces at lists.horde.org
Errors-To: imp-bounces at lists.horde.org
X-MailScanner: Found to be clean
X-SpamCheck: SpamAssassin ()
Status: RO
Content-Length: 274
Lines: 10

Horde, imp, etc. Latest CVS as of this AM.
Php-4.2.1

Notice: Undefined variable: sub in
/usr/local/apache/htdocs/horde/imp/message.php on line 341

--
IMP mailing list
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: imp-unsubscribe at lists.horde.org



More information about the MailScanner mailing list