Bug#348667: acknowledged by developer (Re: Bug#348667: procmail: ignores COMSAT option, sets to 'no' regardless of configuration.)

Thomas Lakofski Wed, 18 Jan 2006 04:33:16 -0800

OK.  But if I use COMSAT=yes, the same behaviour is seen.


What more information would you need to examine the problem?

On Wed, 18 Jan 2006, Debian Bug Tracking System wrote:

From: Debian Bug Tracking System <[EMAIL PROTECTED]>
To: Thomas Lakofski <[EMAIL PROTECTED]>
Date: Wed, 18 Jan 2006 04:18:13 -0800
Subject: Bug#348667 acknowledged by developer (Re: Bug#348667: procmail:
    ignores COMSAT option, sets to 'no' regardless of configuration.)
Reply-To: [EMAIL PROTECTED]

This is an automatic notification regarding your Bug report
#348667: procmail: ignores COMSAT option, sets to 'no' regardless of 
configuration.,
which was filed against the procmail package.

It has been closed by one of the developers, namely
Santiago Vila <[EMAIL PROTECTED]>.

Their explanation is attached below.  If this explanation is
unsatisfactory and you have not received a better one in a separate
message then please contact the developer, by replying to this email.

Debian bug tracking system administrator
(administrator, Debian Bugs database)

Received: (at 348667-done) by bugs.debian.org; 18 Jan 2006 12:10:30 +0000

From [EMAIL PROTECTED] Wed Jan 18 04:10:30 2006

Date: Wed, 18 Jan 2006 13:01:02 +0100 (CET)
From: Santiago Vila <[EMAIL PROTECTED]>
To: Thomas Lakofski <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Subject: Re: Bug#348667: procmail: ignores COMSAT option, sets to 'no'
regardless of configuration.
In-Reply-To: <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at unex.es
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
        autolearn=no version=2.60-bugs.debian.org_2005_01_02

On Wed, 18 Jan 2006, Thomas Lakofski wrote:

Package: procmail
Version: 3.22-13
Severity: normal

[...]
COMSAT=
[...]

COMSAT in this section can be set to 'yes' or 'y' or blank as previously
suggested from a prior bugreport, but regardless of setting the log
reads as follows:

procmail: Match on "^X-Original-To: [EMAIL PROTECTED]"
procmail: Assigning "COMSAT=yes"
procmail: Assigning "COMSAT=no"
procmail: Locking "/var/mail/thomas.lock"
procmail: Assigning "LASTFOLDER=/var/mail/thomas"
procmail: Opening "/var/mail/thomas"
procmail: Acquiring kernel-lock
procmail: Unlocking "/var/mail/thomas.lock"

This has happened since the recent upgrades this month.


I don't know where you got the idea that COMSAT= is acceptable.
This is what the manual says:

      When assigning boolean values to variables like VERBOSE,  DELIVERED  or
      COMSAT, procmail accepts as true every string starting with: a non-zero
      value, `on', `y', `t' or `e'.  False is every string starting  with:  a
      zero value, `off', `n', `f' or `d'.

My reading of this is that the behaviour of COMSAT= is undefined and
you should not rely on it. Please use yes or no, or anything which is
properly documented.


--
Thomas Lakofski      +4470 9228 8229            'Reality is that which,
gnupg            550C DD74 4C38 FAC2 E870    when you stop believing in it,
1024D/527D151D   360C A37B BB79 527D 151D        doesn't go away' --PKD


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#348667: acknowledged by developer (Re: Bug#348667: procmail: ignores COMSAT option, sets to 'no' regardless of configuration.)

Reply via email to