Report forwarded to debian-bugs-dist@lists.debian.org, jdassen@wi.LeidenUniv.nl (J.H.M. Dassen):
Bug#8214; Package mutt.
debian-bugs-dist@lists.debian.orgjdassen@wi.LeidenUniv.nl (J.H.M. Dassen)
Subject: Bug#8214: mutt 0.66-1 :
Reply-To: heiko@os.inf.tu-dresden.de (Heiko Schlittermann), 8214@bugs.debian.org
Resent-From: heiko@os.inf.tu-dresden.de (Heiko Schlittermann)
Resent-To: debian-bugs-dist@lists.debian.org
Resent-CC: jdassen@wi.LeidenUniv.nl (J.H.M. Dassen)
Resent-Date: Fri, 21 Mar 1997 07:48:03 GMT
Resent-Message-ID:
Resent-Sender: iwj@debian.org
X-Debian-PR-Package: mutt
X-Debian-PR-Keywords:
X-Loop: owner@bugs.debian.org
Received: via spool by bugs@bugs.debian.org id=B.8589295904757
(code B ref -1); Fri, 21 Mar 1997 07:48:03 GMT
Message-Id:
Date: Fri, 21 Mar 1997 08:31:21 +0100 (MET)
From: heiko@os.inf.tu-dresden.de (Heiko Schlittermann)
To: submit@bugs.debian.org
Package: mutt
Version: 0.66-1
-- System Information
Debian Release: 1.2
Kernel Version: Linux runner 2.0.27 #20 Sat Jan 4 00:49:33 MET 1997 i586
Versions of the packages mutt depends on:
libc5 Version: 5.4.20-1
slang0.99.34 Version: 0.99.38-1
smail Version: 3.2-3 (Provides Virtual Package mail-transport-agent)
--
Multiple concurrent copies of mutt cause corrupt mailbox. (Elm
prevents this by locking itself against running multiple instances for
the same user -- probably not the best solution but better than the
current mutt behaviour.)
Heiko
--
email : heiko@lotte.sax.de heiko@debian.org heiko@sax.de
pgp : A1 7D F6 7B 69 73 48 35 E1 DE 21 A7 A8 9A 77 92
finger: heiko@sax.sax.de heiko@master.debian.org
Acknowledgement sent to heiko@os.inf.tu-dresden.de (Heiko Schlittermann):
New bug report received and forwarded. Copy sent to jdassen@wi.LeidenUniv.nl (J.H.M. Dassen).
-t
From: owner@bugs.debian.org (Ian Jackson)
To: heiko@os.inf.tu-dresden.de (Heiko Schlittermann)
Subject: Bug#8214: Acknowledgement (was: mutt 0.66-1 :)
Message-ID:
In-Reply-To:
References:
Thank you for the problem report you have sent regarding Debian Linux.
This is an automatically generated reply, to let you know your message has
been received. It is being forwarded to the developers' mailing list for
their attention; they will reply in due course.
Your message has been sent to the package maintainer(s):
jdassen@wi.LeidenUniv.nl (J.H.M. Dassen)
If you wish to submit further information on your problem, please send
it to 8214@bugs.debian.org (and *not* to
bugs@bugs.debian.org).
Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.
Ian Jackson
(maintainer, Debian bug tracking system)
Received: (at submit) by bugs.debian.org; 21 Mar 1997 07:33:10 +0000
Received: (qmail 4754 invoked from network); 21 Mar 1997 07:33:09 -0000
Received: from runner.inf.tu-dresden.de (root@141.76.48.98)
by master.debian.org with SMTP; 21 Mar 1997 07:33:09 -0000
Received: by runner.inf.tu-dresden.de
id m0w7ynJ-0007QhC
(Debian Smail-3.2 1996-Jul-4 #2); Fri, 21 Mar 1997 08:31:21 +0100 (MET)
Message-Id:
Date: Fri, 21 Mar 1997 08:31:21 +0100 (MET)
From: heiko@os.inf.tu-dresden.de (Heiko Schlittermann)
To: submit@bugs.debian.org
Subject: mutt 0.66-1 :
Package: mutt
Version: 0.66-1
-- System Information
Debian Release: 1.2
Kernel Version: Linux runner 2.0.27 #20 Sat Jan 4 00:49:33 MET 1997 i586
Versions of the packages mutt depends on:
libc5 Version: 5.4.20-1
slang0.99.34 Version: 0.99.38-1
smail Version: 3.2-3 (Provides Virtual Package mail-transport-agent)
--
Multiple concurrent copies of mutt cause corrupt mailbox. (Elm
prevents this by locking itself against running multiple instances for
the same user -- probably not the best solution but better than the
current mutt behaviour.)
Heiko
--
email : heiko@lotte.sax.de heiko@debian.org heiko@sax.de
pgp : A1 7D F6 7B 69 73 48 35 E1 DE 21 A7 A8 9A 77 92
finger: heiko@sax.sax.de heiko@master.debian.org
Information forwarded to debian-bugs-dist@lists.debian.org, jdassen@wi.LeidenUniv.nl (J.H.M. Dassen):
Bug#8214; Package mutt.
debian-bugs-dist@lists.debian.orgjdassen@wi.LeidenUniv.nl (J.H.M. Dassen)
Subject: Bug#8214: mutt 0.66-1 :
Reply-To: jdassen@wi.leidenuniv.nl (J.H.M.Dassen), 8214@bugs.debian.org
Resent-From: jdassen@wi.leidenuniv.nl (J.H.M.Dassen)
Resent-To: debian-bugs-dist@lists.debian.org
Resent-CC: jdassen@wi.LeidenUniv.nl (J.H.M. Dassen)
Resent-Date: Fri, 21 Mar 1997 08:33:02 GMT
Resent-Message-ID:
Resent-Sender: iwj@debian.org
X-Debian-PR-Package: mutt
X-Debian-PR-Keywords:
X-Loop: owner@bugs.debian.org
Received: via spool by 8214-bugs@bugs.debian.org id=B8214.8589331685448
(code B ref 8214); Fri, 21 Mar 1997 08:33:02 GMT
Organization: Leiden University,
Dept. of Mathematics & Computer Science,
The Netherlands
Message-ID: <19970321093500.63543@wi.leidenuniv.nl>
Date: Fri, 21 Mar 1997 09:35:00 +0100
From: jdassen@wi.leidenuniv.nl (J.H.M.Dassen)
To: heiko@os.inf.tu-dresden.de (Heiko Schlittermann), 8214@bugs.debian.org
References:
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.66
In-Reply-To: ; from Heiko Schlittermann on Fri, Mar 21, 1997 at 08:31:21AM +0100
On Mar 21, Heiko Schlittermann wrote
> Multiple concurrent copies of mutt cause corrupt mailbox.
Do you actually get a corrupt mailbox, or just a message from one of the
running mutts about a corrupt mailbox? I.e., if you start a new mutt on that
mailbox, does it complain about corruption?
> (Elm prevents this by locking itself against running multiple instances
> for the same user -- probably not the best solution but better than the
> current mutt behaviour.)
Mutt uses dot locking (as per Debian policy) when rewriting a mailbox, so no
two mutt processes can actually write concurrently.
I've done a quick test, and have been unable to get an actually corrupt
mailbox; the only thing that happened was that if copy A succeeded in
writing, copy B would give a 'corrupt mailbox' error.
Ray
--
PATRIOTISM A great British writer once said that if he had to choose
between betraying his country and betraying a friend he hoped he would
have the decency to betray his country.
- The Hipcrime Vocab by Chad C. Mulligan
Acknowledgement sent to jdassen@wi.leidenuniv.nl (J.H.M.Dassen):
Extra info received and forwarded to list. Copy sent to jdassen@wi.LeidenUniv.nl (J.H.M. Dassen).
-t
From: owner@bugs.debian.org (Ian Jackson)
To: jdassen@wi.leidenuniv.nl (J.H.M.Dassen)
Subject: Bug#8214: Info received (was Bug#8214: mutt 0.66-1 :)
Message-ID:
In-Reply-To: <19970321093500.63543@wi.leidenuniv.nl>
References: <19970321093500.63543@wi.leidenuniv.nl>
Thank you for the additional information you have supplied regarding
this problem report. It has been forwarded to the developer(s) and
to the developers' mailing list to accompany the original report.
Your message has been sent to the package maintainer(s):
jdassen@wi.LeidenUniv.nl (J.H.M. Dassen)
If you wish to continue to submit further information on your problem,
please send it to 8214@bugs.debian.org, as before.
Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.
Ian Jackson
(maintainer, Debian bug tracking system)
Received: (at 8214) by bugs.debian.org; 21 Mar 1997 08:32:47 +0000
Received: (qmail 5446 invoked from network); 21 Mar 1997 08:32:43 -0000
Received: from zeus.wi.leidenuniv.nl (HELO mailhost.wi.leidenuniv.nl) (root@132.229.128.1)
by master.debian.org with SMTP; 21 Mar 1997 08:32:42 -0000
Received: from hermes.wi.leidenuniv.nl (jdassen@hermes [132.229.128.3])
by mailhost.wi.leidenuniv.nl (8.6.10a/SBH-1.20.1-M) with ESMTP id JAA10132
Fri, 21 Mar 1997 09:38:04 +0100 (MET)
Organization: Leiden University,
Dept. of Mathematics & Computer Science,
The Netherlands
Received: from (jdassen@localhost)
by hermes.wi.leidenuniv.nl (8.6.10a/FHM-1.01-S) id JAA21447
Fri, 21 Mar 1997 09:35:01 +0100 (MET)
Message-ID: <19970321093500.63543@wi.leidenuniv.nl>
Date: Fri, 21 Mar 1997 09:35:00 +0100
From: jdassen@wi.leidenuniv.nl (J.H.M.Dassen)
To: heiko@os.inf.tu-dresden.de (Heiko Schlittermann), 8214@bugs.debian.org
Subject: Re: Bug#8214: mutt 0.66-1 :
References:
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.66
In-Reply-To: ; from Heiko Schlittermann on Fri, Mar 21, 1997 at 08:31:21AM +0100
On Mar 21, Heiko Schlittermann wrote
> Multiple concurrent copies of mutt cause corrupt mailbox.
Do you actually get a corrupt mailbox, or just a message from one of the
running mutts about a corrupt mailbox? I.e., if you start a new mutt on that
mailbox, does it complain about corruption?
> (Elm prevents this by locking itself against running multiple instances
> for the same user -- probably not the best solution but better than the
> current mutt behaviour.)
Mutt uses dot locking (as per Debian policy) when rewriting a mailbox, so no
two mutt processes can actually write concurrently.
I've done a quick test, and have been unable to get an actually corrupt
mailbox; the only thing that happened was that if copy A succeeded in
writing, copy B would give a 'corrupt mailbox' error.
Ray
--
PATRIOTISM A great British writer once said that if he had to choose
between betraying his country and betraying a friend he hoped he would
have the decency to betray his country.
- The Hipcrime Vocab by Chad C. Mulligan
Information forwarded to debian-bugs-dist@lists.debian.org, jdassen@wi.LeidenUniv.nl (J.H.M. Dassen):
Bug#8214; Package mutt.
debian-bugs-dist@lists.debian.orgjdassen@wi.LeidenUniv.nl (J.H.M. Dassen)
Subject: Bug#8214: mutt 0.66-1 :
Reply-To: heiko@sax.de, 8214@bugs.debian.org
Resent-From: Heiko Schlittermann
Resent-To: debian-bugs-dist@lists.debian.org
Resent-CC: jdassen@wi.LeidenUniv.nl (J.H.M. Dassen)
Resent-Date: Fri, 21 Mar 1997 09:03:02 GMT
Resent-Message-ID:
Resent-Sender: iwj@debian.org
X-Debian-PR-Package: mutt
X-Debian-PR-Keywords:
X-Loop: owner@bugs.debian.org
Received: via spool by 8214-bugs@bugs.debian.org id=B8214.8589349185713
(code B ref 8214); Fri, 21 Mar 1997 09:03:02 GMT
Message-ID: <19970321100004.43762@ipf.de>
Date: Fri, 21 Mar 1997 10:00:04 +0100
From: Heiko Schlittermann
To: "J.H.M.Dassen"
Cc: Heiko Schlittermann , 8214@bugs.debian.org
References: <19970321093500.63543@wi.leidenuniv.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.66
X-Phone: +49-172-7909055
On Mar 21, J.H.M.Dassen wrote
: On Mar 21, Heiko Schlittermann wrote
: > Multiple concurrent copies of mutt cause corrupt mailbox.
:
: Do you actually get a corrupt mailbox, or just a message from one of the
: running mutts about a corrupt mailbox? I.e., if you start a new mutt on that
: mailbox, does it complain about corruption?
Sorry, NOT the mailbox gets corrupted.
: I've done a quick test, and have been unable to get an actually corrupt
: mailbox; the only thing that happened was that if copy A succeeded in
: writing, copy B would give a 'corrupt mailbox' error.
Exactly.
But probably {we,you,the mutt author} should think about preventing such
concurrently running mutts. At least let's issue a warnung (a la vim).
Imagine, one mutt is started. The second mutt is started. In the second
mutt you carefully delete 123 out of 538 messages (tag them as deleted, not
actually sync the mailbox). Inside the first mutt the mailbox is synced.
The second mutt dies ... and you have the do the selection again ..
Heiko
Acknowledgement sent to heiko@sax.de:
Extra info received and forwarded to list. Copy sent to jdassen@wi.LeidenUniv.nl (J.H.M. Dassen).
-t
From: owner@bugs.debian.org (Ian Jackson)
To: heiko@sax.de
Subject: Bug#8214: Info received (was Bug#8214: mutt 0.66-1 :)
Message-ID:
In-Reply-To: <19970321100004.43762@ipf.de>
References: <19970321100004.43762@ipf.de>
Thank you for the additional information you have supplied regarding
this problem report. It has been forwarded to the developer(s) and
to the developers' mailing list to accompany the original report.
Your message has been sent to the package maintainer(s):
jdassen@wi.LeidenUniv.nl (J.H.M. Dassen)
If you wish to continue to submit further information on your problem,
please send it to 8214@bugs.debian.org, as before.
Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.
Ian Jackson
(maintainer, Debian bug tracking system)
Received: (at 8214) by bugs.debian.org; 21 Mar 1997 09:01:58 +0000
Received: (qmail 5711 invoked from network); 21 Mar 1997 09:01:55 -0000
Received: from runner.inf.tu-dresden.de (root@141.76.48.98)
by master.debian.org with SMTP; 21 Mar 1997 09:01:55 -0000
Received: by runner.inf.tu-dresden.de
id m0w80BA-0007QhC
(Debian Smail-3.2 1996-Jul-4 #2); Fri, 21 Mar 1997 10:00:04 +0100 (MET)
Message-ID: <19970321100004.43762@ipf.de>
Date: Fri, 21 Mar 1997 10:00:04 +0100
From: Heiko Schlittermann
To: "J.H.M.Dassen"
Cc: Heiko Schlittermann , 8214@bugs.debian.org
Subject: Re: Bug#8214: mutt 0.66-1 :
References: <19970321093500.63543@wi.leidenuniv.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.66
X-Phone: +49-172-7909055
Reply-To: heiko@sax.de
On Mar 21, J.H.M.Dassen wrote
: On Mar 21, Heiko Schlittermann wrote
: > Multiple concurrent copies of mutt cause corrupt mailbox.
:
: Do you actually get a corrupt mailbox, or just a message from one of the
: running mutts about a corrupt mailbox? I.e., if you start a new mutt on that
: mailbox, does it complain about corruption?
Sorry, NOT the mailbox gets corrupted.
: I've done a quick test, and have been unable to get an actually corrupt
: mailbox; the only thing that happened was that if copy A succeeded in
: writing, copy B would give a 'corrupt mailbox' error.
Exactly.
But probably {we,you,the mutt author} should think about preventing such
concurrently running mutts. At least let's issue a warnung (a la vim).
Imagine, one mutt is started. The second mutt is started. In the second
mutt you carefully delete 123 out of 538 messages (tag them as deleted, not
actually sync the mailbox). Inside the first mutt the mailbox is synced.
The second mutt dies ... and you have the do the selection again ..
Heiko
Information forwarded to debian-bugs-dist@lists.debian.org, jdassen@wi.LeidenUniv.nl (J.H.M. Dassen):
Bug#8214; Package mutt.
debian-bugs-dist@lists.debian.orgjdassen@wi.LeidenUniv.nl (J.H.M. Dassen)
Subject: Bug#8214: [heiko@os.inf.tu-dresden.de: Re: Bug#8214: mutt 0.66-1 :]
Reply-To: jdassen@wi.leidenuniv.nl (J.H.M.Dassen), 8214@bugs.debian.org
Resent-From: jdassen@wi.leidenuniv.nl (J.H.M.Dassen)
Resent-To: debian-bugs-dist@lists.debian.org
Resent-CC: jdassen@wi.LeidenUniv.nl (J.H.M. Dassen)
Resent-Date: Fri, 21 Mar 1997 09:18:06 GMT
Resent-Message-ID:
Resent-Sender: iwj@debian.org
X-Debian-PR-Package: mutt
X-Debian-PR-Keywords:
X-Loop: owner@bugs.debian.org
Received: via spool by 8214-bugs@bugs.debian.org id=B8214.8589358375839
(code B ref 8214); Fri, 21 Mar 1997 09:18:06 GMT
Organization: Leiden University,
Dept. of Mathematics & Computer Science,
The Netherlands
Message-ID: <19970321101933.29104@wi.leidenuniv.nl>
Date: Fri, 21 Mar 1997 10:19:33 +0100
From: jdassen@wi.leidenuniv.nl (J.H.M.Dassen)
To: mutt-users@cs.hmc.edu (Mutt users mailing list)
Cc: 8214@bugs.debian.org
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary=6TrnltStXW4iwmi0
X-Mailer: Mutt 0.66
--6TrnltStXW4iwmi0
Content-Type: text/plain; charset=us-ascii
[This was reported as a bug through the Debian bugtracking system; please
keep the Cc: 8214@bugs.debian.org].
I agree with this feature request. IMHO, it would be best if mutt would lock
a mailbox for as long as it is the current one, instead of only when
writing; if a second mutt is started on the mailbox, it should be in
read-only mode. It would be nice to have a status_format sequence to
indicate read-only mode, and have this used in the default status_format.
Greetings,
Ray
--
UNFAIR Term applied to advantages enjoyed by other people which we tried
to cheat them out of and didn't manage. See also DISHONESTY, SNEAKY,
UNDERHAND and JUST LUCKY I GUESS.
- The Hipcrime Vocab by Chad C. Mulligan
--6TrnltStXW4iwmi0
Content-Type: message/rfc822
Content-Description: Forwarded message from heiko@os.inf.tu-dresden.de (Heiko Schlittermann)
Return-Path:
Received: from runner.inf.tu-dresden.de (root@runner.inf.tu-dresden.de [141.76.48.98])
by mailhost.wi.leidenuniv.nl (8.6.10a/SBH-1.20.1-M) with ESMTP id KAA10872
for ; Fri, 21 Mar 1997 10:07:34 +0100 (MET)
Received: by runner.inf.tu-dresden.de
id m0w80BA-0007QhC
(Debian Smail-3.2 1996-Jul-4 #2); Fri, 21 Mar 1997 10:00:04 +0100 (MET)
Message-ID: <19970321100004.43762@ipf.de>
Date: Fri, 21 Mar 1997 10:00:04 +0100
From: Heiko Schlittermann
To: "J.H.M.Dassen"
Cc: Heiko Schlittermann , 8214@bugs.debian.org
Subject: Re: Bug#8214: mutt 0.66-1 :
References: <19970321093500.63543@wi.leidenuniv.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.66
X-Phone: +49-172-7909055
Reply-To: heiko@sax.de
Status: O
On Mar 21, J.H.M.Dassen wrote
: On Mar 21, Heiko Schlittermann wrote
: > Multiple concurrent copies of mutt cause corrupt mailbox.
:
: Do you actually get a corrupt mailbox, or just a message from one of the
: running mutts about a corrupt mailbox? I.e., if you start a new mutt on that
: mailbox, does it complain about corruption?
Sorry, NOT the mailbox gets corrupted.
: I've done a quick test, and have been unable to get an actually corrupt
: mailbox; the only thing that happened was that if copy A succeeded in
: writing, copy B would give a 'corrupt mailbox' error.
Exactly.
But probably {we,you,the mutt author} should think about preventing such
concurrently running mutts. At least let's issue a warnung (a la vim).
Imagine, one mutt is started. The second mutt is started. In the second
mutt you carefully delete 123 out of 538 messages (tag them as deleted, not
actually sync the mailbox). Inside the first mutt the mailbox is synced.
The second mutt dies ... and you have the do the selection again ..
Heiko
--6TrnltStXW4iwmi0--
Acknowledgement sent to jdassen@wi.leidenuniv.nl (J.H.M.Dassen):
Extra info received and forwarded to list. Copy sent to jdassen@wi.LeidenUniv.nl (J.H.M. Dassen).
-t
From: owner@bugs.debian.org (Ian Jackson)
To: jdassen@wi.leidenuniv.nl (J.H.M.Dassen)
Subject: Bug#8214: Info received (was [heiko@os.inf.tu-dresden.de: Re: Bug#8214: mutt 0.66-1 :])
Message-ID:
In-Reply-To: <19970321101933.29104@wi.leidenuniv.nl>
References: <19970321101933.29104@wi.leidenuniv.nl>
Thank you for the additional information you have supplied regarding
this problem report. It has been forwarded to the developer(s) and
to the developers' mailing list to accompany the original report.
Your message has been sent to the package maintainer(s):
jdassen@wi.LeidenUniv.nl (J.H.M. Dassen)
If you wish to continue to submit further information on your problem,
please send it to 8214@bugs.debian.org, as before.
Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.
Ian Jackson
(maintainer, Debian bug tracking system)
Received: (at 8214) by bugs.debian.org; 21 Mar 1997 09:17:17 +0000
Received: (qmail 5835 invoked from network); 21 Mar 1997 09:17:15 -0000
Received: from zeus.wi.leidenuniv.nl (HELO mailhost.wi.leidenuniv.nl) (root@132.229.128.1)
by master.debian.org with SMTP; 21 Mar 1997 09:17:14 -0000
Received: from hermes.wi.leidenuniv.nl (jdassen@hermes [132.229.128.3])
by mailhost.wi.leidenuniv.nl (8.6.10a/SBH-1.20.1-M) with ESMTP id KAA11122
Fri, 21 Mar 1997 10:22:37 +0100 (MET)
Organization: Leiden University,
Dept. of Mathematics & Computer Science,
The Netherlands
Received: from (jdassen@localhost)
by hermes.wi.leidenuniv.nl (8.6.10a/FHM-1.01-S) id KAA21500
Fri, 21 Mar 1997 10:19:33 +0100 (MET)
Message-ID: <19970321101933.29104@wi.leidenuniv.nl>
Date: Fri, 21 Mar 1997 10:19:33 +0100
From: jdassen@wi.leidenuniv.nl (J.H.M.Dassen)
To: mutt-users@cs.hmc.edu (Mutt users mailing list)
Cc: 8214@bugs.debian.org
Subject: [heiko@os.inf.tu-dresden.de: Re: Bug#8214: mutt 0.66-1 :]
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary=6TrnltStXW4iwmi0
X-Mailer: Mutt 0.66
--6TrnltStXW4iwmi0
Content-Type: text/plain; charset=us-ascii
[This was reported as a bug through the Debian bugtracking system; please
keep the Cc: 8214@bugs.debian.org].
I agree with this feature request. IMHO, it would be best if mutt would lock
a mailbox for as long as it is the current one, instead of only when
writing; if a second mutt is started on the mailbox, it should be in
read-only mode. It would be nice to have a status_format sequence to
indicate read-only mode, and have this used in the default status_format.
Greetings,
Ray
--
UNFAIR Term applied to advantages enjoyed by other people which we tried
to cheat them out of and didn't manage. See also DISHONESTY, SNEAKY,
UNDERHAND and JUST LUCKY I GUESS.
- The Hipcrime Vocab by Chad C. Mulligan
--6TrnltStXW4iwmi0
Content-Type: message/rfc822
Content-Description: Forwarded message from heiko@os.inf.tu-dresden.de (Heiko Schlittermann)
Return-Path:
Received: from runner.inf.tu-dresden.de (root@runner.inf.tu-dresden.de [141.76.48.98])
by mailhost.wi.leidenuniv.nl (8.6.10a/SBH-1.20.1-M) with ESMTP id KAA10872
for ; Fri, 21 Mar 1997 10:07:34 +0100 (MET)
Received: by runner.inf.tu-dresden.de
id m0w80BA-0007QhC
(Debian Smail-3.2 1996-Jul-4 #2); Fri, 21 Mar 1997 10:00:04 +0100 (MET)
Message-ID: <19970321100004.43762@ipf.de>
Date: Fri, 21 Mar 1997 10:00:04 +0100
From: Heiko Schlittermann
To: "J.H.M.Dassen"
Cc: Heiko Schlittermann , 8214@bugs.debian.org
Subject: Re: Bug#8214: mutt 0.66-1 :
References: <19970321093500.63543@wi.leidenuniv.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.66
X-Phone: +49-172-7909055
Reply-To: heiko@sax.de
Status: O
On Mar 21, J.H.M.Dassen wrote
: On Mar 21, Heiko Schlittermann wrote
: > Multiple concurrent copies of mutt cause corrupt mailbox.
:
: Do you actually get a corrupt mailbox, or just a message from one of the
: running mutts about a corrupt mailbox? I.e., if you start a new mutt on that
: mailbox, does it complain about corruption?
Sorry, NOT the mailbox gets corrupted.
: I've done a quick test, and have been unable to get an actually corrupt
: mailbox; the only thing that happened was that if copy A succeeded in
: writing, copy B would give a 'corrupt mailbox' error.
Exactly.
But probably {we,you,the mutt author} should think about preventing such
concurrently running mutts. At least let's issue a warnung (a la vim).
Imagine, one mutt is started. The second mutt is started. In the second
mutt you carefully delete 123 out of 538 messages (tag them as deleted, not
actually sync the mailbox). Inside the first mutt the mailbox is synced.
The second mutt dies ... and you have the do the selection again ..
Heiko
--6TrnltStXW4iwmi0--
Information forwarded to debian-bugs-dist@lists.debian.org, jdassen@wi.LeidenUniv.nl (J.H.M. Dassen):
Bug#8214; Package mutt.
debian-bugs-dist@lists.debian.orgjdassen@wi.LeidenUniv.nl (J.H.M. Dassen)
Subject: Bug#8214: mutt 0.66-1 :
Reply-To: Wichert Akkerman , 8214@bugs.debian.org
Resent-From: Wichert Akkerman
Resent-To: debian-bugs-dist@lists.debian.org
Resent-CC: jdassen@wi.LeidenUniv.nl (J.H.M. Dassen)
Resent-Date: Fri, 21 Mar 1997 09:18:09 GMT
Resent-Message-ID:
Resent-Sender: iwj@debian.org
X-Debian-PR-Package: mutt
X-Debian-PR-Keywords:
X-Loop: owner@bugs.debian.org
Received: via spool by 8214-bugs@bugs.debian.org id=B8214.8589358375840
(code B ref 8214); Fri, 21 Mar 1997 09:18:09 GMT
From: Wichert Akkerman
Message-Id: <199703210917.KAA20511@pc135a.wi.leidenuniv.nl>
In-Reply-To: <19970321093500.63543@wi.leidenuniv.nl> from "J.H.M.Dassen" at "Mar 21, 97 09:35:00 am"
To: jdassen@wi.leidenuniv.nl, 8214@bugs.debian.org
Date: Fri, 21 Mar 1997 10:17:10 +0100 (MET)
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
In a previous message J.H.M.Dassen said:
> I've done a quick test, and have been unable to get an actually corrupt
> mailbox; the only thing that happened was that if copy A succeeded in
> writing, copy B would give a 'corrupt mailbox' error.
Maybe the message `corrupt mailbox' should be changed to read `mailbox
has changed' or `unexpected change in mailbox', since that seems to be
the real problem.
Wichert.
Acknowledgement sent to Wichert Akkerman <wakkerma@pc135a.wi.leidenuniv.nl>:
Extra info received and forwarded to list. Copy sent to jdassen@wi.LeidenUniv.nl (J.H.M. Dassen).
-t
From: owner@bugs.debian.org (Ian Jackson)
To: Wichert Akkerman
Subject: Bug#8214: Info received (was Bug#8214: mutt 0.66-1 :)
Message-ID:
In-Reply-To: <199703210917.KAA20511@pc135a.wi.leidenuniv.nl>
References: <199703210917.KAA20511@pc135a.wi.leidenuniv.nl>
Thank you for the additional information you have supplied regarding
this problem report. It has been forwarded to the developer(s) and
to the developers' mailing list to accompany the original report.
Your message has been sent to the package maintainer(s):
jdassen@wi.LeidenUniv.nl (J.H.M. Dassen)
If you wish to continue to submit further information on your problem,
please send it to 8214@bugs.debian.org, as before.
Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.
Ian Jackson
(maintainer, Debian bug tracking system)
Received: (at 8214) by bugs.debian.org; 21 Mar 1997 09:17:17 +0000
Received: (qmail 5836 invoked from network); 21 Mar 1997 09:17:15 -0000
Received: from pc135a.wi.leidenuniv.nl (wakkerma@132.229.16.152)
by master.debian.org with SMTP; 21 Mar 1997 09:17:14 -0000
Received: (from wakkerma@localhost) by pc135a.wi.leidenuniv.nl (8.8.3/8.8.3) id KAA20511; Fri, 21 Mar 1997 10:17:10 +0100
From: Wichert Akkerman
Message-Id: <199703210917.KAA20511@pc135a.wi.leidenuniv.nl>
Subject: Re: Bug#8214: mutt 0.66-1 :
In-Reply-To: <19970321093500.63543@wi.leidenuniv.nl> from "J.H.M.Dassen" at "Mar 21, 97 09:35:00 am"
To: jdassen@wi.leidenuniv.nl, 8214@bugs.debian.org
Date: Fri, 21 Mar 1997 10:17:10 +0100 (MET)
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
In a previous message J.H.M.Dassen said:
> I've done a quick test, and have been unable to get an actually corrupt
> mailbox; the only thing that happened was that if copy A succeeded in
> writing, copy B would give a 'corrupt mailbox' error.
Maybe the message `corrupt mailbox' should be changed to read `mailbox
has changed' or `unexpected change in mailbox', since that seems to be
the real problem.
Wichert.
Changed bug title.
Request was from jdassen@wi.leidenuniv.nl (J.H.M.Dassen)
to control@bugs.debian.org.
Received: (at control) by bugs.debian.org; 21 Mar 1997 09:24:52 +0000
Received: (qmail 5889 invoked from network); 21 Mar 1997 09:24:49 -0000
Received: from zeus.wi.leidenuniv.nl (HELO mailhost.wi.leidenuniv.nl) (root@132.229.128.1)
by master.debian.org with SMTP; 21 Mar 1997 09:24:49 -0000
Received: from hermes.wi.leidenuniv.nl (jdassen@hermes [132.229.128.3])
by mailhost.wi.leidenuniv.nl (8.6.10a/SBH-1.20.1-M) with ESMTP id KAA11205
for ; Fri, 21 Mar 1997 10:30:15 +0100 (MET)
Organization: Leiden University,
Dept. of Mathematics & Computer Science,
The Netherlands
Received: from (jdassen@localhost)
by hermes.wi.leidenuniv.nl (8.6.10a/FHM-1.01-S) id KAA21514
Fri, 21 Mar 1997 10:27:11 +0100 (MET)
Message-ID: <19970321102710.12167@wi.leidenuniv.nl>
Date: Fri, 21 Mar 1997 10:27:11 +0100
From: jdassen@wi.leidenuniv.nl (J.H.M.Dassen)
To: control@bugs.debian.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.66
retitle 8214 Feature request wrt concurrent access
forwarded 8214 mutt-users@cs.hmc.edu (Mutt users mailing list)
forwarded 8210 mutt-users@cs.hmc.edu (Mutt users mailing list)
end
--
POPULATION EXPLOSION Unique in human experience, an event which happened
yesterday but which everyone swears won't happen until tomorrow.
- The Hipcrime Vocab by Chad C. Mulligan
Noted your statement that bug has been forwarded to mutt-users@cs.hmc.edu (Mutt users mailing list).
Request was from jdassen@wi.leidenuniv.nl (J.H.M.Dassen)
to control@bugs.debian.org.
Received: (at control) by bugs.debian.org; 21 Mar 1997 09:24:52 +0000
Received: (qmail 5889 invoked from network); 21 Mar 1997 09:24:49 -0000
Received: from zeus.wi.leidenuniv.nl (HELO mailhost.wi.leidenuniv.nl) (root@132.229.128.1)
by master.debian.org with SMTP; 21 Mar 1997 09:24:49 -0000
Received: from hermes.wi.leidenuniv.nl (jdassen@hermes [132.229.128.3])
by mailhost.wi.leidenuniv.nl (8.6.10a/SBH-1.20.1-M) with ESMTP id KAA11205
for ; Fri, 21 Mar 1997 10:30:15 +0100 (MET)
Organization: Leiden University,
Dept. of Mathematics & Computer Science,
The Netherlands
Received: from (jdassen@localhost)
by hermes.wi.leidenuniv.nl (8.6.10a/FHM-1.01-S) id KAA21514
Fri, 21 Mar 1997 10:27:11 +0100 (MET)
Message-ID: <19970321102710.12167@wi.leidenuniv.nl>
Date: Fri, 21 Mar 1997 10:27:11 +0100
From: jdassen@wi.leidenuniv.nl (J.H.M.Dassen)
To: control@bugs.debian.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.66
retitle 8214 Feature request wrt concurrent access
forwarded 8214 mutt-users@cs.hmc.edu (Mutt users mailing list)
forwarded 8210 mutt-users@cs.hmc.edu (Mutt users mailing list)
end
--
POPULATION EXPLOSION Unique in human experience, an event which happened
yesterday but which everyone swears won't happen until tomorrow.
- The Hipcrime Vocab by Chad C. Mulligan
Information forwarded to debian-bugs-dist@lists.debian.org, jdassen@wi.LeidenUniv.nl (J.H.M. Dassen):
Bug#8214; Package mutt.
debian-bugs-dist@lists.debian.orgjdassen@wi.LeidenUniv.nl (J.H.M. Dassen)
Subject: Bug#8214: mutt 0.66-1 :
Reply-To: heiko@sax.de, 8214@bugs.debian.org
Resent-From: Heiko Schlittermann
Resent-To: debian-bugs-dist@lists.debian.org
Resent-CC: jdassen@wi.LeidenUniv.nl (J.H.M. Dassen)
Resent-Date: Fri, 21 Mar 1997 10:18:05 GMT
Resent-Message-ID:
Resent-Sender: iwj@debian.org
X-Debian-PR-Package: mutt
X-Debian-PR-Keywords:
X-Loop: owner@bugs.debian.org
Received: via spool by 8214-bugs@bugs.debian.org id=B8214.8589387806234
(code B ref 8214); Fri, 21 Mar 1997 10:18:05 GMT
Message-ID: <19970321105925.10759@ipf.de>
Date: Fri, 21 Mar 1997 10:59:25 +0100
From: Heiko Schlittermann
To: Wichert Akkerman ,
8214@bugs.debian.org
References: <19970321093500.63543@wi.leidenuniv.nl> <199703210917.KAA20511@pc135a.wi.leidenuniv.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.66
X-Phone: +49-172-7909055
On Mar 21, Wichert Akkerman wrote
: In a previous message J.H.M.Dassen said:
: > I've done a quick test, and have been unable to get an actually corrupt
: > mailbox; the only thing that happened was that if copy A succeeded in
: > writing, copy B would give a 'corrupt mailbox' error.
:
: Maybe the message `corrupt mailbox' should be changed to read `mailbox
: has changed' or `unexpected change in mailbox', since that seems to be
: the real problem.
Sounds good, at least as intermediate solution.
Heiko
Acknowledgement sent to heiko@sax.de:
Extra info received and forwarded to list. Copy sent to jdassen@wi.LeidenUniv.nl (J.H.M. Dassen).
-t
From: owner@bugs.debian.org (Ian Jackson)
To: heiko@sax.de
Subject: Bug#8214: Info received (was Bug#8214: mutt 0.66-1 :)
Message-ID:
In-Reply-To: <19970321105925.10759@ipf.de>
References: <19970321105925.10759@ipf.de>
Thank you for the additional information you have supplied regarding
this problem report. It has been forwarded to the developer(s) and
to the developers' mailing list to accompany the original report.
Your message has been sent to the package maintainer(s):
jdassen@wi.LeidenUniv.nl (J.H.M. Dassen)
If you wish to continue to submit further information on your problem,
please send it to 8214@bugs.debian.org, as before.
Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.
Ian Jackson
(maintainer, Debian bug tracking system)
Received: (at 8214) by bugs.debian.org; 21 Mar 1997 10:06:20 +0000
Received: (qmail 6232 invoked from network); 21 Mar 1997 10:06:19 -0000
Received: from runner.inf.tu-dresden.de (root@141.76.48.98)
by master.debian.org with SMTP; 21 Mar 1997 10:06:18 -0000
Received: by runner.inf.tu-dresden.de
id m0w816b-0007QhC
(Debian Smail-3.2 1996-Jul-4 #2); Fri, 21 Mar 1997 10:59:25 +0100 (MET)
Message-ID: <19970321105925.10759@ipf.de>
Date: Fri, 21 Mar 1997 10:59:25 +0100
From: Heiko Schlittermann
To: Wichert Akkerman ,
8214@bugs.debian.org
Subject: Re: Bug#8214: mutt 0.66-1 :
References: <19970321093500.63543@wi.leidenuniv.nl> <199703210917.KAA20511@pc135a.wi.leidenuniv.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.66
X-Phone: +49-172-7909055
Reply-To: heiko@sax.de
On Mar 21, Wichert Akkerman wrote
: In a previous message J.H.M.Dassen said:
: > I've done a quick test, and have been unable to get an actually corrupt
: > mailbox; the only thing that happened was that if copy A succeeded in
: > writing, copy B would give a 'corrupt mailbox' error.
:
: Maybe the message `corrupt mailbox' should be changed to read `mailbox
: has changed' or `unexpected change in mailbox', since that seems to be
: the real problem.
Sounds good, at least as intermediate solution.
Heiko
Information forwarded to debian-bugs-dist@lists.debian.org, jdassen@wi.LeidenUniv.nl (J.H.M. Dassen):
Bug#8214; Package mutt.
debian-bugs-dist@lists.debian.orgjdassen@wi.LeidenUniv.nl (J.H.M. Dassen)
Subject: Bug#8214: [heiko@os.inf.tu-dresden.de: Re: Bug#8214: mutt 0.66-1 :]
Reply-To: daia@stoilow.imar.ro, 8214@bugs.debian.org
Resent-From: Liviu Daia
Resent-To: debian-bugs-dist@lists.debian.org
Resent-CC: jdassen@wi.LeidenUniv.nl (J.H.M. Dassen)
Resent-Date: Fri, 21 Mar 1997 13:48:00 GMT
Resent-Message-ID:
Resent-Sender: iwj@debian.org
X-Debian-PR-Package: mutt
X-Debian-PR-Keywords:
X-Loop: owner@bugs.debian.org
Received: via spool by 8214-bugs@bugs.debian.org id=B8214.8589518977849
(code B ref 8214); Fri, 21 Mar 1997 13:48:00 GMT
Message-Id: <199703211345.PAA01536@euler>
Date: Fri, 21 Mar 1997 15:45:28 +0200
From: Liviu Daia
To: "J.H.M.Dassen"
Cc: Mutt users mailing list , 8214@bugs.debian.org
References: <19970321101933.29104@wi.leidenuniv.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.66
X-Url: http://www.imar.ro/~daia/
X-Pgp-Fingerprint: E6 C9 17 E5 27 84 E1 24 62 7A FC AB 1D 64 84 AE
On 21 March 1997, J.H.M.Dassen wrote:
> I agree with this feature request. IMHO, it would be best if mutt
> would lock a mailbox for as long as it is the current one, instead
> of only when writing; if a second mutt is started on the mailbox, it
> should be in read-only mode. It would be nice to have a status_format
> sequence to indicate read-only mode, and have this used in the default
> status_format.
> Date: Fri, 21 Mar 1997 10:00:04 +0100
> From: Heiko Schlittermann
> To: "J.H.M.Dassen"
> Cc: Heiko Schlittermann , 8214@bugs.debian.org
> Subject: Re: Bug#8214: mutt 0.66-1 :
> X-Mailer: Mutt 0.66
>
> On Mar 21, J.H.M.Dassen wrote
> : On Mar 21, Heiko Schlittermann wrote
> : > Multiple concurrent copies of mutt cause corrupt mailbox.
> :
> : Do you actually get a corrupt mailbox, or just a message from one of
> : the running mutts about a corrupt mailbox? I.e., if you start a new
> : mutt on that mailbox, does it complain about corruption?
>
> Sorry, NOT the mailbox gets corrupted.
>
> : I've done a quick test, and have been unable to get an actually
> : corrupt mailbox; the only thing that happened was that if copy A
> : succeeded in writing, copy B would give a 'corrupt mailbox' error.
>
> Exactly.
>
> But probably {we,you,the mutt author} should think about preventing
> such concurrently running mutts. At least let's issue a warnung (a la
> vim).
>
> Imagine, one mutt is started. The second mutt is started. In the
> second mutt you carefully delete 123 out of 538 messages (tag them as
> deleted, not actually sync the mailbox). Inside the first mutt the
> mailbox is synced. The second mutt dies ... and you have the do the
> selection again ..
We've been through this before, and it seems that locking the
mailbox on reading is unacceptable, for a number of reasons. I suggested
a better solution (well, at least IMO...) to this problem some time ago,
but at the time there seemed to be very little interest about that, so
I gave up. Basically, my idea was to re-parse the folder if the mailbox
was "externally modified", and then try to guess which messages where in
the mailbox before the change by comparing the "message-id:" fields, and
restore the flags accordingly.
The obvious problems with this approach would be that (1) not
all messages have a "message-id:" field (this is the case f.i. for
messages obtained by splitting a digest with formail), and (2) the
"message-id:"'s are not necessarily unique, since you can have more than
one copies of the same message in the same mailbox. There is nothing we
can do about either of them. Still, this solution seems better than the
current behaviour...
Regards,
Liviu
--
Dr. Liviu Daia e-mail: daia@stoilow.imar.ro
Institute of Mathematics web page: http://www.imar.ro/~daia
of the Romanian Academy PGP key: finger daia@stoilow.imar.ro
Acknowledgement sent to daia@stoilow.imar.ro:
Extra info received and forwarded to list. Copy sent to jdassen@wi.LeidenUniv.nl (J.H.M. Dassen).
-t
From: owner@bugs.debian.org (Ian Jackson)
To: daia@stoilow.imar.ro
Subject: Bug#8214: Info received (was [heiko@os.inf.tu-dresden.de: Re: Bug#8214: mutt 0.66-1 :])
Message-ID:
In-Reply-To: <199703211345.PAA01536@euler>
References: <199703211345.PAA01536@euler>
Thank you for the additional information you have supplied regarding
this problem report. It has been forwarded to the developer(s) and
to the developers' mailing list to accompany the original report.
Your message has been sent to the package maintainer(s):
jdassen@wi.LeidenUniv.nl (J.H.M. Dassen)
If you wish to continue to submit further information on your problem,
please send it to 8214@bugs.debian.org, as before.
Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.
Ian Jackson
(maintainer, Debian bug tracking system)
Received: (at 8214) by bugs.debian.org; 21 Mar 1997 13:44:57 +0000
Received: (qmail 7847 invoked from network); 21 Mar 1997 13:44:39 -0000
Received: from stoilow.imar.ro (193.226.4.129)
by master.debian.org with SMTP; 21 Mar 1997 13:44:34 -0000
Received: from dial2.imar.ro by stoilow.imar.ro; (5.65/1.1.8.2/19Jan95-0917PM)
id AA19055; Fri, 21 Mar 1997 15:44:31 +0200
Received: (from daia@localhost) by euler (8.8.4/8.6.9) id PAA01536; Fri, 21 Mar 1997 15:45:30 +0200
Message-Id: <199703211345.PAA01536@euler>
Date: Fri, 21 Mar 1997 15:45:28 +0200
From: Liviu Daia
To: "J.H.M.Dassen"
Cc: Mutt users mailing list , 8214@bugs.debian.org
Subject: Re: [heiko@os.inf.tu-dresden.de: Re: Bug#8214: mutt 0.66-1 :]
References: <19970321101933.29104@wi.leidenuniv.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.66
Reply-To: daia@stoilow.imar.ro
X-Url: http://www.imar.ro/~daia/
X-Pgp-Fingerprint: E6 C9 17 E5 27 84 E1 24 62 7A FC AB 1D 64 84 AE
On 21 March 1997, J.H.M.Dassen wrote:
> I agree with this feature request. IMHO, it would be best if mutt
> would lock a mailbox for as long as it is the current one, instead
> of only when writing; if a second mutt is started on the mailbox, it
> should be in read-only mode. It would be nice to have a status_format
> sequence to indicate read-only mode, and have this used in the default
> status_format.
> Date: Fri, 21 Mar 1997 10:00:04 +0100
> From: Heiko Schlittermann
> To: "J.H.M.Dassen"
> Cc: Heiko Schlittermann , 8214@bugs.debian.org
> Subject: Re: Bug#8214: mutt 0.66-1 :
> X-Mailer: Mutt 0.66
>
> On Mar 21, J.H.M.Dassen wrote
> : On Mar 21, Heiko Schlittermann wrote
> : > Multiple concurrent copies of mutt cause corrupt mailbox.
> :
> : Do you actually get a corrupt mailbox, or just a message from one of
> : the running mutts about a corrupt mailbox? I.e., if you start a new
> : mutt on that mailbox, does it complain about corruption?
>
> Sorry, NOT the mailbox gets corrupted.
>
> : I've done a quick test, and have been unable to get an actually
> : corrupt mailbox; the only thing that happened was that if copy A
> : succeeded in writing, copy B would give a 'corrupt mailbox' error.
>
> Exactly.
>
> But probably {we,you,the mutt author} should think about preventing
> such concurrently running mutts. At least let's issue a warnung (a la
> vim).
>
> Imagine, one mutt is started. The second mutt is started. In the
> second mutt you carefully delete 123 out of 538 messages (tag them as
> deleted, not actually sync the mailbox). Inside the first mutt the
> mailbox is synced. The second mutt dies ... and you have the do the
> selection again ..
We've been through this before, and it seems that locking the
mailbox on reading is unacceptable, for a number of reasons. I suggested
a better solution (well, at least IMO...) to this problem some time ago,
but at the time there seemed to be very little interest about that, so
I gave up. Basically, my idea was to re-parse the folder if the mailbox
was "externally modified", and then try to guess which messages where in
the mailbox before the change by comparing the "message-id:" fields, and
restore the flags accordingly.
The obvious problems with this approach would be that (1) not
all messages have a "message-id:" field (this is the case f.i. for
messages obtained by splitting a digest with formail), and (2) the
"message-id:"'s are not necessarily unique, since you can have more than
one copies of the same message in the same mailbox. There is nothing we
can do about either of them. Still, this solution seems better than the
current behaviour...
Regards,
Liviu
--
Dr. Liviu Daia e-mail: daia@stoilow.imar.ro
Institute of Mathematics web page: http://www.imar.ro/~daia
of the Romanian Academy PGP key: finger daia@stoilow.imar.ro
Information forwarded to debian-bugs-dist@lists.debian.org, jdassen@wi.LeidenUniv.nl (J.H.M. Dassen):
Bug#8214; Package mutt.
debian-bugs-dist@lists.debian.orgjdassen@wi.LeidenUniv.nl (J.H.M. Dassen)
Subject: Bug#8214: heiko@os.inf.tu-dresden.de: Re: Bug#8214: mutt 0.66-1 :]
Reply-To: jdassen@wi.leidenuniv.nl (J.H.M.Dassen), 8214@bugs.debian.org
Resent-From: jdassen@wi.leidenuniv.nl (J.H.M.Dassen)
Resent-To: debian-bugs-dist@lists.debian.org
Resent-CC: jdassen@wi.LeidenUniv.nl (J.H.M. Dassen)
Resent-Date: Fri, 21 Mar 1997 14:18:02 GMT
Resent-Message-ID:
Resent-Sender: iwj@debian.org
X-Debian-PR-Package: mutt
X-Debian-PR-Keywords:
X-Loop: owner@bugs.debian.org
Received: via spool by 8214-bugs@bugs.debian.org id=B8214.8589536628021
(code B ref 8214); Fri, 21 Mar 1997 14:18:02 GMT
Organization: Leiden University,
Dept. of Mathematics & Computer Science,
The Netherlands
Message-ID: <19970321151526.03985@wi.leidenuniv.nl>
Date: Fri, 21 Mar 1997 15:15:26 +0100
From: jdassen@wi.leidenuniv.nl (J.H.M.Dassen)
To: daia@stoilow.imar.ro, 8214@bugs.debian.org
References: <19970321101933.29104@wi.leidenuniv.nl> <199703211345.PAA01536@euler>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.66
In-Reply-To: <199703211345.PAA01536@euler>; from Liviu Daia on Fri, Mar 21, 1997 at 03:45:28PM +0200
On Mar 21, Liviu Daia wrote
> We've been through this before, and it seems that locking the mailbox
> on reading is unacceptable, for a number of reasons.
Liviu, I've missed this discussion (probably it was before I started using
mutt); if it is not too much trouble, can you please give me a short list of
reasons in private email?
TIA,
Ray
--
UNFAIR Term applied to advantages enjoyed by other people which we tried
to cheat them out of and didn't manage. See also DISHONESTY, SNEAKY,
UNDERHAND and JUST LUCKY I GUESS.
- The Hipcrime Vocab by Chad C. Mulligan
Acknowledgement sent to jdassen@wi.leidenuniv.nl (J.H.M.Dassen):
Extra info received and forwarded to list. Copy sent to jdassen@wi.LeidenUniv.nl (J.H.M. Dassen).
-t
From: owner@bugs.debian.org (Ian Jackson)
To: jdassen@wi.leidenuniv.nl (J.H.M.Dassen)
Subject: Bug#8214: Info received (was Bug#8214: [heiko@os.inf.tu-dresden.de: Re: Bug#8214: mutt 0.66-1 :])
Message-ID:
In-Reply-To: <19970321151526.03985@wi.leidenuniv.nl>
References: <19970321151526.03985@wi.leidenuniv.nl>
Thank you for the additional information you have supplied regarding
this problem report. It has been forwarded to the developer(s) and
to the developers' mailing list to accompany the original report.
Your message has been sent to the package maintainer(s):
jdassen@wi.LeidenUniv.nl (J.H.M. Dassen)
If you wish to continue to submit further information on your problem,
please send it to 8214@bugs.debian.org, as before.
Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.
Ian Jackson
(maintainer, Debian bug tracking system)
Received: (at 8214) by bugs.debian.org; 21 Mar 1997 14:14:22 +0000
Received: (qmail 8010 invoked from network); 21 Mar 1997 14:13:40 -0000
Received: from zeus.wi.leidenuniv.nl (HELO mailhost.wi.leidenuniv.nl) (root@132.229.128.1)
by master.debian.org with SMTP; 21 Mar 1997 14:13:30 -0000
Received: from hermes.wi.leidenuniv.nl (jdassen@hermes [132.229.128.3])
by mailhost.wi.leidenuniv.nl (8.6.10a/SBH-1.20.1-M) with ESMTP id PAA19305
Fri, 21 Mar 1997 15:18:30 +0100 (MET)
Organization: Leiden University,
Dept. of Mathematics & Computer Science,
The Netherlands
Received: from (jdassen@localhost)
by hermes.wi.leidenuniv.nl (8.6.10a/FHM-1.01-S) id PAA23111
Fri, 21 Mar 1997 15:15:26 +0100 (MET)
Message-ID: <19970321151526.03985@wi.leidenuniv.nl>
Date: Fri, 21 Mar 1997 15:15:26 +0100
From: jdassen@wi.leidenuniv.nl (J.H.M.Dassen)
To: daia@stoilow.imar.ro, 8214@bugs.debian.org
Subject: Re: Bug#8214: [heiko@os.inf.tu-dresden.de: Re: Bug#8214: mutt 0.66-1 :]
References: <19970321101933.29104@wi.leidenuniv.nl> <199703211345.PAA01536@euler>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.66
In-Reply-To: <199703211345.PAA01536@euler>; from Liviu Daia on Fri, Mar 21, 1997 at 03:45:28PM +0200
On Mar 21, Liviu Daia wrote
> We've been through this before, and it seems that locking the mailbox
> on reading is unacceptable, for a number of reasons.
Liviu, I've missed this discussion (probably it was before I started using
mutt); if it is not too much trouble, can you please give me a short list of
reasons in private email?
TIA,
Ray
--
UNFAIR Term applied to advantages enjoyed by other people which we tried
to cheat them out of and didn't manage. See also DISHONESTY, SNEAKY,
UNDERHAND and JUST LUCKY I GUESS.
- The Hipcrime Vocab by Chad C. Mulligan
Information forwarded to debian-bugs-dist@lists.debian.org, jdassen@wi.LeidenUniv.nl (J.H.M. Dassen):
Bug#8214; Package mutt.
debian-bugs-dist@lists.debian.orgjdassen@wi.LeidenUniv.nl (J.H.M. Dassen)
Subject: Bug#8214: [daia@stoilow.imar.ro: Re: Several bugs]
Reply-To: jdassen@wi.leidenuniv.nl, 8214@bugs.debian.org
Resent-From: jdassen@wi.leidenuniv.nl
Resent-To: debian-bugs-dist@lists.debian.org
Resent-CC: jdassen@wi.LeidenUniv.nl (J.H.M. Dassen)
Resent-Date: Mon, 13 Oct 1997 07:33:30 GMT
Resent-Message-ID:
Resent-Sender: iwj@debian.org
X-Debian-PR-Message: report 8214
X-Debian-PR-Package: mutt
X-Debian-PR-Keywords:
X-Loop: owner@bugs.debian.org
Received: via spool by 8214-bugs@bugs.debian.org id=B8214.87672788712436
(code B ref 8214); Mon, 13 Oct 1997 07:33:30 GMT
Organization: Leiden University,
Dept. of Mathematics & Computer Science,
The Netherlands
Message-ID: <19971013083756.62428@wi.leidenuniv.nl>
Date: Mon, 13 Oct 1997 08:37:56 +0100
From: jdassen@wi.leidenuniv.nl
To: 8210-done@bugs.debian.org, 8214@bugs.debian.org, 10514@bugs.debian.org,
10972@bugs.debian.org, 11064@bugs.debian.org, 11995@bugs.debian.org,
13135@bugs.debian.org, 13299@bugs.debian.org, 13746@bugs.debian.org,
11383@bugs.debian.org
Mime-Version: 1.0
Content-Type: message/rfc822
Content-Description: Forwarded message from daia@stoilow.imar.ro
X-Mailer: Mutt 0.84
Return-Path:
Received: from stoilow.imar.ro (stoilow.imar.ro [193.226.4.129])
by mailhost.wi.leidenuniv.nl (8.6.10a/SBH-1.20.1-M) with SMTP id UAA02142
for ; Fri, 10 Oct 1997 20:46:54 +0100 (MET)
Received: from dial1.imar.ro by stoilow.imar.ro; (5.65/1.1.8.2/19Jan95-0917PM)
id AA09650; Fri, 10 Oct 1997 21:48:34 +0200
Received: (from daia@localhost)
by euler.imar.ro (8.8.4/8.8.4)
id WAA05357; Fri, 10 Oct 1997 22:44:59 +0300
Message-Id: <19971010224459.04079@euler.imar.ro>
Date: Fri, 10 Oct 1997 22:44:59 +0300
From: Liviu Daia
To: jdassen@wi.leidenuniv.nl
Cc: mutt-dev@cs.hmc.edu
Subject: Re: Several bugs
Reply-To: daia@stoilow.imar.ro
References: <19971010162031.32315@wi.leidenuniv.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.86
In-Reply-To: <19971010162031.32315@wi.leidenuniv.nl>; from jdassen@wi.leidenuniv.nl on Fri, Oct 10, 1997 at 04:20:11PM +0100
X-Url: http://www.imar.ro/~daia
X-Pgp-Fingerprint: E6 C9 17 E5 27 84 E1 24 62 7A FC AB 1D 64 84 AE
Content-Length: 5091
Lines: 176
On 10 October 1997, jdassen@wi.leidenuniv.nl
wrote:
[...]
> At you can find
> a list of unresolved bugs in the Debian package. Some additional
> information relating to several of them is attached.
[...]
Bug#8210:
=========
| The key doesn't work when editing an input field such as the
| To: field. All it does is beep.
This has been fixed in recent versions.
Bug#8214:
=========
| Multiple concurrent copies of mutt cause corrupt mailbox. (Elm
| prevents this by locking itself against running multiple instances for
| the same user -- probably not the best solution but better than the
| current mutt behaviour.)
My patch "mbox_check" (still under testing on mutt-dev) will address
this issue.
Bug#10514:
==========
| Mutt doesn't create the Mail directory AND it doesn't complain when
| that directory doesn't exist and you try to save something to a
| folder! The failed save will be silently ignored.
My patch "mx_open" for the development version [0.86] fixes this
behaviour.
Bug#10972:
==========
| Viewer should not hide part of 8-bit characters if charset isn't
| ISO 8859-*
This is a trade off that allows people without correct locale
settings to use Mutt. My patch "locales_hack" for [0.86] should fix
that.
| and should not make wrong assumption number_of_bytes ==
| number_of_glyphs_on_the_screen while wrapping lines. `set
| nosmart_warp' doesn't help.
Mutt doesn't support Unicode characters yet. It probably won't be
added before version 1.0 either.
Bug#11064:
==========
| If you want to create a keyboard macro that searches for the regex
| '^From: ' you have to use '^^From: ' instead.
My patch "carets" for [0.86] documents this behaviour.
Bug#11383:
==========
| Changes charset from unicode-?-?-utf-7 to us-ascii (RFC 1642).
As I said, Mutt doesn't support Unicodes yet.
Bug#11995:
==========
| Mutt doesn't display date's characters out of ISO-8859-* printable
| characters range properly.
My patch "locales_hack" for [0.86] addresses that.
| Also IMHO date_format should include %c and LANG variable should be
| utilisied.
No. There are good reasons for using the "C" locale internally. If
you need to change the locales used by dates you need to set the $locale
variable in your .muttrc .
Bug#13135:
==========
| If one starts xterm with xterm -bg blue -fg white and then run mutt
| and exit, the background colour stays black instead of turning back to
| blue.
This was fixed in a recent version on Mutt. If you still get this
behaviour, you have either a broken terminfo entry, or a buggy curses
library.
Bug#13299:
==========
| Prior to mutt version 0.84 (I think this is right), I could use
| backspace in mutt to delete the character to the left of the
| cursor. Now it functions like delete does and deletes the character
| under the cursor. Backspace continues to function normally in all
| other programs.
|
| If I set TERM=linux (in an xterm), backspace works as I would expect
| in mutt. It also works as I want it to if I run mutt at the linux
| console.
Your terminfo entry for "xterm" is broken. There are two ways to
fix that:
(1) The easy way, affecting only Mutt behaviour:
- press ^V at the shell prompt to see what character your
key generates in "xterm", and note that value; it will
probably be "^?";
- add a line
bind editor \C? backspace
to your .muttrc (replace "\C?" above with the appropriate sequence).
(2) The hard way, fixing the terminfo entry:
- press ^V at the shell prompt to see what character your
key generates in "xterm", and note that value as above;
- do an
infocmp >file
- edit "file" and change
kbs=^H (or whatever)
to
kbs=\177 (or whatever your key generates)
- add lines
TERMINFO=$HOME/.terminfo
export TERMINFO
to your ~/.profile, and also run them on the command line in order to
take effect in the current session too (adapt this to your shell if
you're not using /bin/sh);
- do a
tic file
Everything should be ok after that.
Bug#13746:
===========
| /etc/Muttrc has the following bind commands:
|
| bind index Home first-message # PC-isms
| bind index End last-message
|
| Mutt's manual isn't real clear about it, but it turns out that the
| keynames are case-sensitive so the bind commands should be:
|
| bind index home first-message # PC-isms
| bind index end last-message
Mutt have these bindings by default in [0.86], so you don't need to
add them to Muttrc.
| Also, for some reason, the delete key doesn't work in the builtin line
| editor. Adding the following bind command fixes it.
|
| bind editor delete delete-char
This has been fixed in a recent version.
Regards,
Liviu
--
Dr. Liviu Daia e-mail: daia@stoilow.imar.ro
Institute of Mathematics web page: http://www.imar.ro/~daia
of the Romanian Academy PGP key: finger daia@stoilow.imar.ro
Acknowledgement sent to jdassen@wi.leidenuniv.nl:
Extra info received and forwarded to list. Copy sent to jdassen@wi.LeidenUniv.nl (J.H.M. Dassen).
-t
From: owner@bugs.debian.org (Ian Jackson)
To: jdassen@wi.leidenuniv.nl
Subject: Bug#8214: Info received (was [daia@stoilow.imar.ro: Re: Several bugs])
Message-ID:
In-Reply-To: <19971013083756.62428@wi.leidenuniv.nl>
References: <19971013083756.62428@wi.leidenuniv.nl>
X-Debian-PR-Message: ack-info-maintonly 8214
Thank you for the additional information you have supplied regarding
this problem report. It has been forwarded to the developer(s) and
to the developers' mailing list to accompany the original report.
Your message has been sent to the package maintainer(s):
jdassen@wi.LeidenUniv.nl (J.H.M. Dassen)
If you wish to continue to submit further information on your problem,
please send it to 8214@bugs.debian.org, as before.
Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.
Ian Jackson
(maintainer, Debian bug tracking system)
Received: (at 8214) by bugs.debian.org; 13 Oct 1997 07:31:27 +0000
Received: (qmail 12325 invoked from network); 13 Oct 1997 07:31:21 -0000
Received: from zeus.wi.leidenuniv.nl (HELO mailhost.wi.leidenuniv.nl) (root@zeus.wi.leidenuniv.nl@132.229.128.1)
by 205.229.104.5 with SMTP; 13 Oct 1997 07:31:21 -0000
Received: from hermes.wi.leidenuniv.nl (jdassen@hermes [132.229.128.3])
by mailhost.wi.leidenuniv.nl (8.6.10a/SBH-1.20.1-M) with ESMTP id IAA23982
Mon, 13 Oct 1997 08:32:56 +0100 (MET)
Organization: Leiden University,
Dept. of Mathematics & Computer Science,
The Netherlands
Received: from (jdassen@localhost)
by hermes.wi.leidenuniv.nl (8.6.10a/FHM-1.01-S) id IAA10271
Mon, 13 Oct 1997 08:37:57 +0100 (MET)
Message-ID: <19971013083756.62428@wi.leidenuniv.nl>
Date: Mon, 13 Oct 1997 08:37:56 +0100
From: jdassen@wi.leidenuniv.nl
To: 8210-done@bugs.debian.org, 8214@bugs.debian.org, 10514@bugs.debian.org,
10972@bugs.debian.org, 11064@bugs.debian.org, 11995@bugs.debian.org,
13135@bugs.debian.org, 13299@bugs.debian.org, 13746@bugs.debian.org,
11383@bugs.debian.org
Subject: [daia@stoilow.imar.ro: Re: Several bugs]
Mime-Version: 1.0
Content-Type: message/rfc822
Content-Description: Forwarded message from daia@stoilow.imar.ro
X-Mailer: Mutt 0.84
Return-Path:
Received: from stoilow.imar.ro (stoilow.imar.ro [193.226.4.129])
by mailhost.wi.leidenuniv.nl (8.6.10a/SBH-1.20.1-M) with SMTP id UAA02142
for ; Fri, 10 Oct 1997 20:46:54 +0100 (MET)
Received: from dial1.imar.ro by stoilow.imar.ro; (5.65/1.1.8.2/19Jan95-0917PM)
id AA09650; Fri, 10 Oct 1997 21:48:34 +0200
Received: (from daia@localhost)
by euler.imar.ro (8.8.4/8.8.4)
id WAA05357; Fri, 10 Oct 1997 22:44:59 +0300
Message-Id: <19971010224459.04079@euler.imar.ro>
Date: Fri, 10 Oct 1997 22:44:59 +0300
From: Liviu Daia
To: jdassen@wi.leidenuniv.nl
Cc: mutt-dev@cs.hmc.edu
Subject: Re: Several bugs
Reply-To: daia@stoilow.imar.ro
References: <19971010162031.32315@wi.leidenuniv.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.86
In-Reply-To: <19971010162031.32315@wi.leidenuniv.nl>; from jdassen@wi.leidenuniv.nl on Fri, Oct 10, 1997 at 04:20:11PM +0100
X-Url: http://www.imar.ro/~daia
X-Pgp-Fingerprint: E6 C9 17 E5 27 84 E1 24 62 7A FC AB 1D 64 84 AE
Content-Length: 5091
Lines: 176
On 10 October 1997, jdassen@wi.leidenuniv.nl
wrote:
[...]
> At you can find
> a list of unresolved bugs in the Debian package. Some additional
> information relating to several of them is attached.
[...]
Bug#8210:
=========
| The key doesn't work when editing an input field such as the
| To: field. All it does is beep.
This has been fixed in recent versions.
Bug#8214:
=========
| Multiple concurrent copies of mutt cause corrupt mailbox. (Elm
| prevents this by locking itself against running multiple instances for
| the same user -- probably not the best solution but better than the
| current mutt behaviour.)
My patch "mbox_check" (still under testing on mutt-dev) will address
this issue.
Bug#10514:
==========
| Mutt doesn't create the Mail directory AND it doesn't complain when
| that directory doesn't exist and you try to save something to a
| folder! The failed save will be silently ignored.
My patch "mx_open" for the development version [0.86] fixes this
behaviour.
Bug#10972:
==========
| Viewer should not hide part of 8-bit characters if charset isn't
| ISO 8859-*
This is a trade off that allows people without correct locale
settings to use Mutt. My patch "locales_hack" for [0.86] should fix
that.
| and should not make wrong assumption number_of_bytes ==
| number_of_glyphs_on_the_screen while wrapping lines. `set
| nosmart_warp' doesn't help.
Mutt doesn't support Unicode characters yet. It probably won't be
added before version 1.0 either.
Bug#11064:
==========
| If you want to create a keyboard macro that searches for the regex
| '^From: ' you have to use '^^From: ' instead.
My patch "carets" for [0.86] documents this behaviour.
Bug#11383:
==========
| Changes charset from unicode-?-?-utf-7 to us-ascii (RFC 1642).
As I said, Mutt doesn't support Unicodes yet.
Bug#11995:
==========
| Mutt doesn't display date's characters out of ISO-8859-* printable
| characters range properly.
My patch "locales_hack" for [0.86] addresses that.
| Also IMHO date_format should include %c and LANG variable should be
| utilisied.
No. There are good reasons for using the "C" locale internally. If
you need to change the locales used by dates you need to set the $locale
variable in your .muttrc .
Bug#13135:
==========
| If one starts xterm with xterm -bg blue -fg white and then run mutt
| and exit, the background colour stays black instead of turning back to
| blue.
This was fixed in a recent version on Mutt. If you still get this
behaviour, you have either a broken terminfo entry, or a buggy curses
library.
Bug#13299:
==========
| Prior to mutt version 0.84 (I think this is right), I could use
| backspace in mutt to delete the character to the left of the
| cursor. Now it functions like delete does and deletes the character
| under the cursor. Backspace continues to function normally in all
| other programs.
|
| If I set TERM=linux (in an xterm), backspace works as I would expect
| in mutt. It also works as I want it to if I run mutt at the linux
| console.
Your terminfo entry for "xterm" is broken. There are two ways to
fix that:
(1) The easy way, affecting only Mutt behaviour:
- press ^V at the shell prompt to see what character your
key generates in "xterm", and note that value; it will
probably be "^?";
- add a line
bind editor \C? backspace
to your .muttrc (replace "\C?" above with the appropriate sequence).
(2) The hard way, fixing the terminfo entry:
- press ^V at the shell prompt to see what character your
key generates in "xterm", and note that value as above;
- do an
infocmp >file
- edit "file" and change
kbs=^H (or whatever)
to
kbs=\177 (or whatever your key generates)
- add lines
TERMINFO=$HOME/.terminfo
export TERMINFO
to your ~/.profile, and also run them on the command line in order to
take effect in the current session too (adapt this to your shell if
you're not using /bin/sh);
- do a
tic file
Everything should be ok after that.
Bug#13746:
===========
| /etc/Muttrc has the following bind commands:
|
| bind index Home first-message # PC-isms
| bind index End last-message
|
| Mutt's manual isn't real clear about it, but it turns out that the
| keynames are case-sensitive so the bind commands should be:
|
| bind index home first-message # PC-isms
| bind index end last-message
Mutt have these bindings by default in [0.86], so you don't need to
add them to Muttrc.
| Also, for some reason, the delete key doesn't work in the builtin line
| editor. Adding the following bind command fixes it.
|
| bind editor delete delete-char
This has been fixed in a recent version.
Regards,
Liviu
--
Dr. Liviu Daia e-mail: daia@stoilow.imar.ro
Institute of Mathematics web page: http://www.imar.ro/~daia
of the Romanian Academy PGP key: finger daia@stoilow.imar.ro
Information forwarded to debian-bugs-dist@lists.debian.org, jdassen@wi.LeidenUniv.nl (J.H.M. Dassen (Ray)):
Bug#8214; Package mutt.
debian-bugs-dist@lists.debian.orgjdassen@wi.LeidenUniv.nl (J.H.M. Dassen (Ray))
Subject: Bug#8214: OK to send e-mail?
Reply-To: owl@owlseye.com, 8214@bugs.debian.org
Resent-From: owl@owlseye.com
Resent-To: debian-bugs-dist@lists.debian.org
Resent-CC: jdassen@wi.LeidenUniv.nl (J.H.M. Dassen (Ray))
Resent-Date: Sat, 28 Mar 1998 17:18:00 GMT
Resent-Message-ID:
Resent-Sender: iwj@debian.org
X-Debian-PR-Message: report 8214
X-Debian-PR-Package: mutt
X-Debian-PR-Keywords:
X-Loop: owner@bugs.debian.org
Received: via spool by 8214-bugs@bugs.debian.org id=B8214.89110499824941
(code B ref 8214); Sat, 28 Mar 1998 17:18:00 GMT
Date: Sat, 28 Mar 1998 11:51:17 -0500 (EST)
Message-Id: <199803281651.LAA06106@ns.owlseye.com>
From: owl@owlseye.com
To: 8214@bugs.debian.org
OK to send an e-mail to 8214@bugs.debian.org?
Acknowledgement sent to owl@owlseye.com:
Extra info received and forwarded to list. Copy sent to jdassen@wi.LeidenUniv.nl (J.H.M. Dassen (Ray)).
-t
From: owner@bugs.debian.org (Ian Jackson)
To: owl@owlseye.com
Subject: Bug#8214: Info received (was OK to send e-mail?)
Message-ID:
In-Reply-To: <199803281651.LAA06106@ns.owlseye.com>
References: <199803281651.LAA06106@ns.owlseye.com>
X-Debian-PR-Message: ack-info-maintonly 8214
Thank you for the additional information you have supplied regarding
this problem report. It has been forwarded to the developer(s) and
to the developers' mailing list to accompany the original report.
Your message has been sent to the package maintainer(s):
jdassen@wi.LeidenUniv.nl (J.H.M. Dassen (Ray))
If you wish to continue to submit further information on your problem,
please send it to 8214@bugs.debian.org, as before.
Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.
Ian Jackson
(administrator, Debian bugs database)
Received: (at 8214) by bugs.debian.org; 28 Mar 1998 17:09:58 +0000
Received: (qmail 24937 invoked from network); 28 Mar 1998 17:09:57 -0000
Received: from unknown (HELO ns.owlseye.com) (owl@208.151.38.212)
by debian.novare.net with SMTP; 28 Mar 1998 17:09:57 -0000
Received: (from owl@localhost) by ns.owlseye.com (8.8.8/8.7.3) id LAA06106; Sat, 28 Mar 1998 11:51:17 -0500 (EST)
Date: Sat, 28 Mar 1998 11:51:17 -0500 (EST)
Message-Id: <199803281651.LAA06106@ns.owlseye.com>
From: owl@owlseye.com
To: 8214@bugs.debian.org
Reply-To: owl@owlseye.com
Subject: OK to send e-mail?
OK to send an e-mail to 8214@bugs.debian.org?
Information forwarded to debian-bugs-dist@lists.debian.org, jdassen@wi.LeidenUniv.nl (J.H.M. Dassen (Ray)):
Bug#8214; Package mutt.
debian-bugs-dist@lists.debian.orgjdassen@wi.LeidenUniv.nl (J.H.M. Dassen (Ray))
Subject: Bug#8214: Is Your Web Site Posted?
Reply-To: site@siteposter.com, 8214@bugs.debian.org
Resent-From: site@siteposter.com
Resent-To: debian-bugs-dist@lists.debian.org
Resent-CC: jdassen@wi.LeidenUniv.nl (J.H.M. Dassen (Ray))
Resent-Date: Fri, 03 Apr 1998 15:48:00 GMT
Resent-Message-ID:
Resent-Sender: iwj@debian.org
X-Debian-PR-Message: report 8214
X-Debian-PR-Package: mutt
X-Debian-PR-Keywords:
X-Loop: owner@bugs.debian.org
Received: via spool by 8214-bugs@bugs.debian.org id=B8214.89161769132662
(code B ref 8214); Fri, 03 Apr 1998 15:48:00 GMT
Date: Fri, 3 Apr 1998 04:28:05 -0500
Message-Id: <199804030928.EAA25752@www.siteposter.com>
From: site@siteposter.com
To: 8214@bugs.debian.org
To: 8214@bugs.debian.org
Is Your Web Site Posted?
SitePoster will post your site to 50 search engines for $89.
We guarantee your satisfaction, or you pay nothing!
Millions of people every day use search engines to find web sites.
SitePoster makes your site easier to find by posting it to the top 50 search engines.
Here's how it works:
1. Fill out the form below, and return it to us.
2. We'll post your site to the top 50 search engines within two business days and send
you a full promotion report.
3. Pay nothing now. We'll send you a bill for $89 with the promotion report. If you're
not completely happy, simply write "cancel" on the bill, and you'll owe nothing.
THE SEARCH ENGINES
Here's the list of top search engines to which we'll post your site:
Alta Vista, Excite, Galaxy, HotBot, Infoseek, Lycos, Magellan, Open Text Web Index,
Web Crawler, BizWeb, New Riders WWW Yellow Pages, LinkMonster, True North,
Northern Light, YelloWWWeb, The Weekly Bookmark, The Galactic Galaxy, TurnPike,
Unlock:The Information Exchange, Your WebScout, Manufacturers Information
Network, Net Happenings, Net Mall, Web World Internet Directory, WebVenture
Hotlist, What's New, WhatUSeek, JumpLink, Linkcentre Directory, InfoSpace, Jayde
Online Directory, BC Internet, BizCardz Business Directory, Net-Announce, New Page
ListOne World Plaza, PageHost A-Z, PeekABoo, Project Cool, Scrub The Web, Seven
Wonders, Sserv, Starting Point, Web 100, Web Walker, Where2Go, World Wide Business
Yellow Pages, Wow! Web Wonders!, WWW Worm, JumpCity.
ORDER FORM
Hit the REPLY button on your e-mail program and fill out the following information.
(This information will be posted to the search engines/indexes):
URL: http://
Site Title:
Description (250 characters):
Key words (250 characters, in descending order of importance):
Your name:
Company Name:
Address:
City: State/Prov: Zip/Postal Code:
Telephone:
Fax:
Email address:
Contact e-mail address (in case we have questions about this order):
If billing a different address, please complete the following:
Addressee:
Company Name:
Address:
City: State/Prov: Zip/Postal Code:
Telephone:
Fax:
Email address:
TERMS
Terms are net 15 days from date of invoice.
______________________________________________________________________
SitePoster, Inc.
1440 Whalley Avenue - Suite 239
New Haven, CT 06515
Phone: (203) 928-9207
Fax: (203) 389-8074
E-mail: site@siteposter.com
Acknowledgement sent to site@siteposter.com:
Extra info received and forwarded to list. Copy sent to jdassen@wi.LeidenUniv.nl (J.H.M. Dassen (Ray)).
-t
From: owner@bugs.debian.org (Ian Jackson)
To: site@siteposter.com
Subject: Bug#8214: Info received (was Is Your Web Site Posted?)
Message-ID:
In-Reply-To: <199804030928.EAA25752@www.siteposter.com>
References: <199804030928.EAA25752@www.siteposter.com>
X-Debian-PR-Message: ack-info-maintonly 8214
Thank you for the additional information you have supplied regarding
this problem report. It has been forwarded to the developer(s) and
to the developers' mailing list to accompany the original report.
Your message has been sent to the package maintainer(s):
jdassen@wi.LeidenUniv.nl (J.H.M. Dassen (Ray))
If you wish to continue to submit further information on your problem,
please send it to 8214@bugs.debian.org, as before.
Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.
Ian Jackson
(administrator, Debian bugs database)
Received: (at 8214) by bugs.debian.org; 3 Apr 1998 15:34:51 +0000
Received: (qmail 32659 invoked from network); 3 Apr 1998 15:34:51 -0000
Received: from unknown (HELO www.siteposter.com) (site@206.252.212.132)
by debian.novare.net with SMTP; 3 Apr 1998 15:34:51 -0000
Received: (from site@localhost)
by www.siteposter.com (8.8.7/8.8.7) id EAA25752;
Fri, 3 Apr 1998 04:28:05 -0500
Date: Fri, 3 Apr 1998 04:28:05 -0500
Message-Id: <199804030928.EAA25752@www.siteposter.com>
From: site@siteposter.com
To: 8214@bugs.debian.org
Reply-To: site@siteposter.com
Subject: Is Your Web Site Posted?
To: 8214@bugs.debian.org
Is Your Web Site Posted?
SitePoster will post your site to 50 search engines for $89.
We guarantee your satisfaction, or you pay nothing!
Millions of people every day use search engines to find web sites.
SitePoster makes your site easier to find by posting it to the top 50 search engines.
Here's how it works:
1. Fill out the form below, and return it to us.
2. We'll post your site to the top 50 search engines within two business days and send
you a full promotion report.
3. Pay nothing now. We'll send you a bill for $89 with the promotion report. If you're
not completely happy, simply write "cancel" on the bill, and you'll owe nothing.
THE SEARCH ENGINES
Here's the list of top search engines to which we'll post your site:
Alta Vista, Excite, Galaxy, HotBot, Infoseek, Lycos, Magellan, Open Text Web Index,
Web Crawler, BizWeb, New Riders WWW Yellow Pages, LinkMonster, True North,
Northern Light, YelloWWWeb, The Weekly Bookmark, The Galactic Galaxy, TurnPike,
Unlock:The Information Exchange, Your WebScout, Manufacturers Information
Network, Net Happenings, Net Mall, Web World Internet Directory, WebVenture
Hotlist, What's New, WhatUSeek, JumpLink, Linkcentre Directory, InfoSpace, Jayde
Online Directory, BC Internet, BizCardz Business Directory, Net-Announce, New Page
ListOne World Plaza, PageHost A-Z, PeekABoo, Project Cool, Scrub The Web, Seven
Wonders, Sserv, Starting Point, Web 100, Web Walker, Where2Go, World Wide Business
Yellow Pages, Wow! Web Wonders!, WWW Worm, JumpCity.
ORDER FORM
Hit the REPLY button on your e-mail program and fill out the following information.
(This information will be posted to the search engines/indexes):
URL: http://
Site Title:
Description (250 characters):
Key words (250 characters, in descending order of importance):
Your name:
Company Name:
Address:
City: State/Prov: Zip/Postal Code:
Telephone:
Fax:
Email address:
Contact e-mail address (in case we have questions about this order):
If billing a different address, please complete the following:
Addressee:
Company Name:
Address:
City: State/Prov: Zip/Postal Code:
Telephone:
Fax:
Email address:
TERMS
Terms are net 15 days from date of invoice.
______________________________________________________________________
SitePoster, Inc.
1440 Whalley Avenue - Suite 239
New Haven, CT 06515
Phone: (203) 928-9207
Fax: (203) 389-8074
E-mail: site@siteposter.com