Bug#348667: procmail: ignores COMSAT option, sets to 'no' regardless of configuration.
Hello. Apparently, procmail 3.22-14 has entered testing today (don't know why yet), so I have uploaded procmail_3.22-15 for unstable, which hopefully fixes this bug, but I'm not completely sure. Will close this bug by hand once I verify that it's actually fixed. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#348667: procmail: ignores COMSAT option, sets to 'no' regardless of configuration.
Summary of what I know about this bug so far:
* The minimal .procmailrc to reproduce it is like this:
LOGFILE=$HOME/log
VERBOSE=yes
COMSAT=yes
:0:
foo
* It happens in etch using *either* version 3.22-11 or 3.22-13 as
far as such version has been built under etch.
* It does not happen in etch using *either* version 3.22-11 or 3.22-13 as
far as such version has been built under sarge.
* It does not happen in sarge using *either* version 3.22-11 or 3.22-13 as
far as such version has been built under sarge.
This is really funny.
By comparing build trees, I see that autoconf.h has this line
#define IP_localhost {127,0,0,1}
when built under sarge, but not when built under woody. If such line
is put in config.h before the build, the problem seems to go away.
Most probably, that will be the fix in 3.22-14, but I would still like
to know why autoconf behaves differently.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#348667: procmail: ignores COMSAT option, sets to 'no' regardless of configuration.
reopen 348667 thanks On Wed, 18 Jan 2006, Thomas Lakofski wrote: > OK. But if I use COMSAT=yes, the same behaviour is seen. That's a different problem, then. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#348667: procmail: ignores COMSAT option, sets to 'no' regardless of configuration.
On Wed, 18 Jan 2006, Santiago Vila wrote:
From: Santiago Vila <[EMAIL PROTECTED]>
To: Thomas Lakofski <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Date: Wed, 18 Jan 2006 14:12:25 +0100 (CET)
Subject: Re: Bug#348667: procmail: ignores COMSAT option,
sets to 'no' regardless of configuration.
On Wed, 18 Jan 2006, Thomas Lakofski wrote:
I found the origin of the COMSAT= configuration -- it was related
to the resolution of a previous bugrep on procmail from 2001:
I see. That was a workaround for a bug which procmail had in 2001.
The current procmail does not have that bug, so it is in your own
interest that you stop using the workaround, as it was never
guaranteed to work.
OK. I have removed it. I tend to leave configuration alone until
something breaks... Not bad going at 4+ years.
Thanks,
thomas
--
Thomas Lakofski +4470 9228 8229'Reality is that which,
gnupg550C DD74 4C38 FAC2 E870when you stop believing in it,
1024D/527D151D 360C A37B BB79 527D 151Ddoesn't go away' --PKD
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#348667: procmail: ignores COMSAT option, sets to 'no' regardless of configuration.
On Wed, 18 Jan 2006, Thomas Lakofski wrote: > I found the origin of the COMSAT= configuration -- it was related > to the resolution of a previous bugrep on procmail from 2001: I see. That was a workaround for a bug which procmail had in 2001. The current procmail does not have that bug, so it is in your own interest that you stop using the workaround, as it was never guaranteed to work. -- 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.)
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 + From [EMAIL PROTECTED] Wed Jan 18 04:10:30 2006 Return-path: <[EMAIL PROTECTED]> Received: from pizarro.unex.es ([158.49.8.2] ident=postfix) by spohr.debian.org with esmtp (Exim 4.50) id 1EzC12-0007Yg-85 for [EMAIL PROTECTED]; Wed, 18 Jan 2006 04:02:20 -0800 Received: from localhost (almendralejo.unex.es [158.49.8.199]) by pizarro.unex.es (Postfix/MJ-1.08) with ESMTP id 1C3DCD13C9; Wed, 18 Jan 2006 13:02:15 +0100 (CET) Received: from pizarro.unex.es ([158.49.8.2]) by localhost (emilio [158.49.17.20]) (amavisd-new, port 10024) with ESMTP id 10480-10; Wed, 18 Jan 2006 13:05:17 +0100 (CET) Received: from guadiana.unex.es (guadiana.unex.es [158.49.17.23]) by pizarro.unex.es (Postfix/MJ-1.08) with ESMTP id BEDB9D1398; Wed, 18 Jan 2006 13:02:10 +0100 (CET) Received: from cantor.unex.es ([158.49.18.105]) by guadiana.unex.es with esmtp (Exim 3.35 #1 (Debian)) id 1EzC0w-00035q-00; Wed, 18 Jan 2006 13:02:10 +0100 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, gnupg550C DD74 4C38 FAC2 E870when you stop believing in it, 1024D/527D151D 360C A37B BB79 527D 151Ddoesn't go away' --PKD -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#348667: procmail: ignores COMSAT option, sets to 'no' regardless of configuration.
Package: procmail
Version: 3.22-13
Severity: normal
[top of .procmailrc]
SHELL=/bin/sh
PATH=/bin:/usr/bin:/usr/bin
PMDIR=$HOME/.procmail
MAILDIR=$HOME/mail/lists
LOGFILE=$PMDIR/log
DEFAULT=/home/thomas/mail/default/bcc
LOGABSTRACT=all
VERBOSE=no
COMSAT=no
[snip all the rules in the middle]
:0
* ^X-Original-To: [EMAIL PROTECTED]
{
COMSAT=
:0:
/var/mail/thomas
}
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.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Versions of packages procmail depends on:
ii libc6 2.3.5-12 GNU C Library: Shared libraries an
Versions of packages procmail recommends:
ii postfix [mail-transport-agent 2.2.8-4A high-performance mail transport
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
