Subject: Getting Desperate Re. Date Field Problem

From: Bruce Toews <[email-masked]>
Date: Thu, 26 Dec 1996 20:35:06 -0600 ()

I have posted this question before recently, but nobody seems to have an
answer. I will try one more time, hoping that someone has recently joined
this list who can help.

I have what seems to be an intermitent problem with Pine when I send mail.
The host I'm running Pine off of is Red Hat Linux version 4. The kernal is
2.0.18, and it's being run on an Alpha. We're using Pine 3.95. It seems
that usually, though not always, in the Date: header of my messages, where
it should be putting my time zone (CST) in parentheses, it is instead
putting a control-A (^a) in parentheses instead. This screws things up for
some people, changing their screen colors. I'm not using the newsgroup,
but rather the pine-info mailing list. Can anyone possibly shed some light
on why the system is doing this and what I can perhaps do? Thanks very
much for your assistance.

Bruce

---

From: Gregor J Jones <[email-masked]>
Date: Fri, 27 Dec 1996 13:01:04 -0500 (EST)

On Thu, 26 Dec 1996, Bruce Toews wrote:
 
 | I have posted this question before recently, but nobody seems to have
 | an answer.

 | It seems that usually, though not always, in the Date: header of my
 | messages, where it should be putting my time zone (CST) in parentheses, 
 | it is instead | putting a control-A (^a) in parentheses instead.

I don't have really have an answer, but just so you don't feel too
lonely... 

I am using MSDOS and PCPine, but also have access to a Unix version. I
looked at your message with a DOS editor and it does indeed have a real
'crl-A' character in the Date: header.

In PCPine, the information for this header is taken from an environment
variable TZ, which has to be set on each machine. Mine is set to EST5EDT
in one of my startup files. The details for this are in the Pine Technical
Notes. I looked there for Unix information, but couldn't find anything. 
However, I checked on the Unix machine where I have access to Pine, and
there there is the same environment variable! It seems to me that Unix
Pine probably uses this as does PCPine, so your problem should be
something like, 1) this environment variable is not set correctly, 2) 
Pine cannot access it, 3) Pine is incorrectly setup so it is misreading
it.

Hope that helps.

Yours

Gregor
__ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __
Gregor J Jones                                    Tel: 617-638-5336 (Lab)
Department of Physiology                               617-262-8205 (Home)
Boston University School of Medicine              Fax: 617-638-4273
Boston MA 02118

---

From: Bruce Toews <[email-masked]>
Date: Fri, 27 Dec 1996 12:16:13 -0600 ()

> Pine cannot access it, 3) Pine is incorrectly setup so it is misreading

I checked, and the TZ variable is set correctly. I appreciate the
response, but regretably, the problem remains. Plus, it is intermitent,
which makes no sense. Does anyone know if a CTRL/A has any significance
for Pine?

Bruce