[24887] in SIPB bug reports
oh.
daemon@ATHENA.MIT.EDU (Laurel H Bobrow)
Fri Aug 5 12:04:51 2005
From laurel@MIT.EDU Fri Aug 05 16:04:51 2005
Return-Path: <laurel@MIT.EDU>
Delivered-To: bug-sipb-mtg@CHARON.mit.edu
Received: (qmail 26660 invoked from network); 5 Aug 2005 16:04:51 -0000
Received: from grand-central-station.mit.edu (18.7.21.82)
by charon.mit.edu with SMTP; 5 Aug 2005 16:04:51 -0000
Received: from outgoing-legacy.mit.edu (OUTGOING-LEGACY.MIT.EDU [18.7.22.104])
by grand-central-station.mit.edu (8.12.4/8.9.2) with ESMTP id j75G4oXw019006
for <bug-sipb@mit.edu>; Fri, 5 Aug 2005 12:04:50 -0400 (EDT)
Received: from PRINTER-ON-FIRE.MIT.EDU (PRINTER-ON-FIRE.MIT.EDU [18.243.2.60])
)
by outgoing-legacy.mit.edu (8.12.4/8.12.4) with ESMTP id j75G4g0w006721
for <bug-sipb@mit.edu>; Fri, 5 Aug 2005 12:04:43 -0400 (EDT)
Date: Fri, 5 Aug 2005 12:04:42 -0400 (EDT)
From: Laurel H Bobrow <laurel@MIT.EDU>
To: bug-sipb@mit.edu
Subject: oh.
Message-ID: <Pine.LNX.4.62L.0508051201490.31528@printer-on-fire.MIT.EDU>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Score: 3.227
X-Spam-Level: *** (3.227)
X-Spam-Flag: NO
X-Scanned-By: MIMEDefang 2.42
i figured out that this is a pop/imap problem, and hadn't realized that
the fact that i was using sipb pine-imap was unusual since it's what a
friend set up for me to use before freshman year and i didn't realize that
it wasn't the conventional sipb pine and that the new pine you sent would
be pop. so yeah, i've found out how to get my messages back on the server.
sorry for the previous email. ~laurel
