Subject: Locked folders

From: [email-masked] (Tom Tappan)
Date: Mon, 5 Aug 1996 12:00:11 -0400

We are running Pine 3.90 on a Linux system.  Ithas been used as a dedicated mail
server without problem.

This past weekend we installed an NCSA Web Server unto the system.  The home
page offers the possibility of e-mail to our school.  This morning we find
that none of our users can open Pine folders in anything except read-only
mode.   Also the old UNIX mail program will not write the outgoing files
to the /tmp directory.  As near as I can tell the permissions look normal.

Any help would be apprpreciated.

Thank you.
	Thomas W. Tappan
	[email-masked]

---

From: [email-masked] (Tim Mooney)
Date: 7 Aug 1996 11:51:02 -0500

In article <[email-masked]>,
> to the /tmp directory.  As near as I can tell the permissions look normal.

Find one of the folders that's displaying the `read-only' problem, and peek
through the folder with a program (less, od -c) that will let you view out
of band characters.  See if there are out-of-band characters in the headers,
especially immediately preceding the `From '.

If there are out-of-band characters in the headers, delete them with an
editor that can handle them, and then try reading the mail with pine and see
if it fixes the problem.

Tim
-- 
Tim Mooney                              [email-masked]
Information Technology Services         (701) 231-1076 (Voice)
Room 242-J1, IACC Bldg.                 (701) 231-8541 (FAX)
North Dakota State University, Fargo, ND 58105

---

From: Michael Schuyler <[email-masked]>
Date: Wed, 7 Aug 1996 17:35:36 -0700 (PDT)

> especially immediately preceding the `From '.

We've been experiencing the same sort of thing since we implemented 3.95,
but I'm not convinced this problem is coming from Pine at al. However,
consistently, there is an extra "F" in front of the "From" of the first
message in the inbox. Taking it out with an editor fixes the problem. But
why is it happening in the first place? beats me. 

      o o o o o o o . . .   _~~~~~~~~~~~~~~~~~~~~~\_ _/~~~~~~~~~~~~~~~~~~\_
    o      _____            |   Kitsap Regional    | |   LinkNet Support  |
  .][__n_n_|DD[  ====_____  |      Library         | |   'least we try!   |
 >(________|__|_[_________]_|______________________|_|____________________|_
 _/oo OOOOO oo`  ooo   ooo  'o^o^o            o^o^o` 'o^o              o^o`
============================================================================
Support: (360) 405-9131 Fax:(360) 405-9128 [email-masked]
Michael Schuyler:     Voice:(360) 405-9139 [email-masked]

---

From: Tim Mooney <[email-masked]>
Date: Wed, 7 Aug 1996 21:41:26 -0500 (CDT)

When we last communicated, Michael Schuyler wrote:
 
)On 7 Aug 1996, Tim Mooney wrote:
)
)> > that none of our users can open Pine folders in anything except read-only
)> > mode.   Also the old UNIX mail program will not write the outgoing files
)> > to the /tmp directory.  As near as I can tell the permissions look normal.
)> 
)> Find one of the folders that's displaying the `read-only' problem, and peek
)> through the folder with a program (less, od -c) that will let you view out
)> of band characters.  See if there are out-of-band characters in the headers,
)> especially immediately preceding the `From '.
)
)We've been experiencing the same sort of thing since we implemented 3.95,
)but I'm not convinced this problem is coming from Pine at al. However,
)consistently, there is an extra "F" in front of the "From" of the first
)message in the inbox. Taking it out with an editor fixes the problem. But
)why is it happening in the first place? beats me. 

Actually, we haven't gone to 3.95 on our general purpose hosts (they're
still using 3.91), and we've only seen this problem on our Digital Unix
hosts.  I sent some email to the osf-managers mailing list a couple months
ago and got lots of responses that other people were seeing the same thing.
Many people suspected problems with the POP daemon a lot of us use (qualcomm's
popper), but I've been able to verify that a lot of the people that get
the junk in the headers are *not* POP mail users.  With Digital Unix, it
appears the problem may be in /bin/mail, the local delivery agent.  I've not
been able to completely verify this, but many of us have narrowed the list
of possibilities to just that.

I have no idea what would be causing the problem on other systems, but it
could be something similar.

Tim