Subject: Bad msgno in mail_fetchstructure

From: Martin Leung <[email-masked]>
Date: Tue, 23 Apr 1996 19:26:49 +0800

My colleagues frequently got the following error messages when using
pine,

  [ Cannot open file for writing ]

  [ Can't create addrbook.lu   Using temp file ]

  [ Bad msgno in mail_fetchstructure ]

He is using Pine on Win95 and the mail server is running PDMF on VMS.
The problem appeared on both 3.92 and 3.93.

Part of the log file is listed below,

================== begin of log file =========================

About to open folder "INBOX"    inbox: "INBOX"
IMAP mm_notify NIL : {usthk.ust.hk}INBOX :  IMAP2+ Server PMDF5.0-5 at 
Fri, 12 Apr 1996 09:21:35 +0800
Opened folder "{usthk.ust.hk}INBOX" with 3 messages
Sorting by Arrival
IMAP 09:20:43 4/12 mm_log babble: Find of mailbox outside context: 
C:\intruptd
- mailcap_free -

    ---- MAIN_MENU_SCREEN ----

 ---- MAIL INDEX ----

 ---- INDEX MANAGER ----

  -----  MAIL VIEW  -----
done.

 ---- MAIL INDEX ----

 ---- INDEX MANAGER ----

  -----  MAIL VIEW  -----
done.
done.
IMAP mm_notify warning : {usthk.ust.hk}INBOX : Can't checkpoint mailbox 
or mailbox shrunk: INBOX
IMAP 09:28:21 4/12 mm_log babble: CHECK completed
about to end_tty_driver
Pine Panic: Bad msgno in mail_fetchstructure

save_debug_on_crash: Version 3.92: debug level 2

                   : Fri Apr 12 09:31:57 1996

Attempting to save debug file to pinecrsh.txt

===================== end of log file ============================

Any idea ?

Rgds.
Martin

---

From: Portia Shao <[email-masked]>
Date: Tue, 23 Apr 1996 17:32:29 -0700 (PDT)

> IMAP mm_notify warning : {usthk.ust.hk}INBOX : Can't checkpoint mailbox 

this means someone is accessing the mailbox from elsewhere and had 
expunged it. Are you absolutely sure that this user is the only one 
accessing the mail from Pine? The mailbox (folder) may be accessed 
elsewhere using VMS MAIL, or another Pine or any IMAP client, or even a 
POP3 client.

> ===================== end of log file ============================

     +--------------------------------------------------------------------+
     |  /portia     [email-masked]                              |
     |  Innosoft International Inc. (818)919-3600 voice, (818)919-3614 fax|
     |  1050 East Garvey Ave South, West Covina, CA 91790                 |
     +--- http://www.innosoft.com/www_root/doc/app-notes/popnimap.html ---+

---

From: kremžská HOŘČICE <[email-masked]>
Date: Wed, 24 Apr 1996 08:52:02 +0200

> elsewhere using VMS MAIL, or another Pine or any IMAP client, or even a 

    I can't speak for VMS Pine, but this will not happen with Normal Pine
or IMAP, which (as Mark Crispin will relate in gory detail over a few
pitchers of fine Czech beers) perform file locking so that one Pine or
IMAP session can detect when another tries to access the same mailbox and
gracefully decide who gets to take charge.

    All bets are off when NFS mounting of the spool enters the picture, or
when non-Pine non-IMAP mail programs are used, which could be just about
anything else, such as a POP client, Elm, or what have you, and stumble
over all sorts of toes.

    I've happily gutted any NFS mounting of our mail spool, and gone
further by restricting it to IMAP-only in a sealed-server/blackbox type of
configuration, and it will be hard to convince me of the benefits of doing
otherwise.  Of course, I don't have thousands of Elm, /bin/mail, RMAIL,
and the like users to breathe down my neck here....

Barry Bouwsma  <[email-masked]>
Radio Purrraha, Czechistan

---

From: Ben Parker <[email-masked]>
Date: Thu, 25 Apr 1996 13:47:18 +0300 (GMT+0300)

Sorry if this is a FAQ that I haven't seen elsewhere but could someone 
show me the line in inetd.conf to start imapd?

Thanks,
Ben
Nairobi

---

From: Mark Shadley <[email-masked]>
Date: Thu, 25 Apr 1996 12:05:39 -0700 (PDT)

> show me the line in inetd.conf to start imapd?

imap2	stream	tcp	nowait	root	/usr/sbin/tcpd	/usr/sbin/imapd

Mark

---

From: "Dan N. Harrington" <[email-masked]>
Date: Thu, 25 Apr 1996 14:03:51 -0700 (PDT)

Has anyone ported Pine 3.93 for FreeBSD 2.1 yet?  I have tried and tried 
but failed miserably.  I worked out about 5 or 6 problems but got stuck 
on addrbook.c.  Any tips?  Or maybe any patches/ports etc?
Thanks much,
Dan

--
Dan Harrington
[email-masked]
Pager: 509-336-4337

---

From: Ben Parker <[email-masked]>
Date: Fri, 26 Apr 1996 14:28:25 +0300 (GMT+0300)

Flushed with success on that question... Is there any way for Pine to 
honour read receipts?

Thanks,
Ben

---

From: David L Miller <[email-masked]>
Date: Fri, 26 Apr 1996 10:31:47 -0700 (PDT)

We will be investigating the proposals of the Notary working group for
inclusion in Pine 4.x.  Until then, there is no standardized way to
request (or respond to) a read-receipt.  Some mail programs have
ad-hoc "solutions," but they have the potential to seriously
compromise privacy (I bet the SPAMers would _love_ to know who
actually read their stuff ;) 

|\ |  |\/|  David L. Miller    [email-masked]  (206) 685-6240
|/ |_ |  |  Software Engineer, Pine Development Team   (206) 685-4045 (FAX)
University of Washington, Networks & Distributed Computing, JE-20
4545 15th Ave NE, Seattle WA 98105, USA

On Fri, 26 Apr 1996, Ben Parker wrote:

> Errors-To: [email-masked]
> Sender: [email-masked]
> Date: Fri, 26 Apr 1996 14:28:25 +0300 (GMT+0300)
> From: Ben Parker <[email-masked]>
> To: [email-masked]
> Subject: Next question: Read Receipts
> In-Reply-To: <[email-masked]>
> Message-ID: <[email-masked]>
> Read-Receipt-To: [email-masked]
>

---

From: Ray Cummins <[email-masked]>
Date: Sat, 27 Apr 1996 09:28:40 -0400 (EDT)

> on addrbook.c.  Any tips?  Or maybe any patches/ports etc?

      Pine 3.93 is available as a port and a package for FreeBSD at
ftp.cdrom.com, in the /FreeBSD/incoming directory.  ("build neb" works
too, but you'll probably want the port anyway.)

---

From: Terry Gray <[email-masked]>
Date: Sat, 27 Apr 1996 15:11:08 -0700 (PDT)

Actually the Notary working group has completed its work, which was on
Delivery Service Notifications.  There is now a separate working group
focused on the read-receipt issue.  (FYI: As far as I know, there is no
intent to mandate automatic responses to read-receipt; I suspect most
sites will choose to let individuals decide whether a read-receipt is
sent. )

-teg