Subject: How can I define *empty* Fcc in address book?

From: Andrej Borsenkow <[email-masked]>
Date: Wed, 15 May 1996 15:48:42 +0400 (MOW)

Hi, pine users!

I try to supress Fcc for some addresses (examples are some mail
archives/robots; I don't want to klog disk with copies of requests).

It doesn't work :-( If I leave  Fcc field in address book entry for a
address empty, I get default Fcc as user-name.

If I try to set it to "" (two double-qoutes), I get "" as Fcc when
composing.

Yes, I can always delete Fcc when composing new message - so it is not the
point. The point is, how to *not* be prompted with Fcc at all.

Do I miss something, or is it a bug?

BTW fcc-name-rule is set to "by-recipient" 

greetings

-------------------------------------------------------------------------
Andrej Borsenkow 		Fax:   +7 (095) 252 01 05
SNI ITS Moscow			Tel:   +7 (095) 252 13 88

NERV:  borsenkow.msk		E-Mail: [email-masked]
-------------------------------------------------------------------------

---

From: Steve Hubert <[email-masked]>
Date: Wed, 15 May 1996 11:50:44 -0700 (PDT)

> Do I miss something, or is it a bug?

Didn't think of it.  3.94 will interpret "" in the Fcc field in the
address book to mean no fcc.  Thanks for the suggestion.

Steve Hubert <[email-masked]>
Networks and Distributed Computing, Univ. of Washington, Seattle

---

From: [email-masked] (Orjan Johansen)
Date: 19 May 1996 03:15:36 GMT

In article <[email-masked]>, Thomas Ulich <[email-masked]> wrote:
>There's another immediate solution.  Define the FCC field to be
>
>	/dev/null
>
>and the FCcopy will get lost automatically.  I did that often by hand,
>directly in the composing-FCC field.

I tried that by hand myself (Pine 3.91, Linux), and it worked - sort of.
I got an error message about write failed.

Greetings,
Ørjan.

---

From: Barry Landy <[email-masked]>
Date: Fri, 17 May 1996 11:55:09 +0100

Since the spec used to be precisely that FCC="" meant no FCC, this is a
BUG. 
(I know because we fell into this by accident when we first introduced
Pine to the mass audience, and we could not understand for a while why
people were losing their FCCs).

On 15 May 1996, Steve Hubert wrote:

:>On Wed, 15 May 1996, Andrej Borsenkow wrote:
:>
:>> If I try to set it to "" (two double-qoutes), I get "" as Fcc when
:>> composing.
:>> 
:>> Yes, I can always delete Fcc when composing new message - so it is not the
:>> point. The point is, how to *not* be prompted with Fcc at all.
:>> 
:>> Do I miss something, or is it a bug?
:>
:>Didn't think of it.  3.94 will interpret "" in the Fcc field in the
:>address book to mean no fcc.  Thanks for the suggestion.
:>
:>Steve Hubert <[email-masked]>
:>Networks and Distributed Computing, Univ. of Washington, Seattle
:>
:>
:>
:>

-------------------------------------------------------------------------------
Barry Landy                        Computer Laboratory:+44 1223 334600
Head of Systems and Development    Direct line:        +44 1223 334713
University of Cambridge Computing Service
New Museums Site                   Email:[email-masked]
Pembroke Street, Cambridge CB2 3QG

---

From: Nancy McGough <[email-masked]>
Date: Fri, 17 May 1996 09:35:17 -0400

On 16 May 1996, Thomas Ulich wrote:
> and the FCcopy will get lost automatically.

Assuming the person isn't using PC Pine for Windows/Winsock...

  -Nancy

---

From: [email-masked] (Thomas Ulich)
Date: 20 May 1996 00:41:01 GMT

Orjan Johansen ([email-masked]) wrote:
: In article <[email-masked]>, Thomas Ulich <[email-masked]> wrote:
: >There's another immediate solution.  Define the FCC field to be
: >
: >	/dev/null
: >
: >and the FCcopy will get lost automatically.  I did that often by hand,
: >directly in the composing-FCC field.
: 
: I tried that by hand myself (Pine 3.91, Linux), and it worked - sort of.
: I got an error message about write failed.

Which let's me assume that the rights for the device /dev/null are messed
up.  It should be rw-rw-rw- so that everybody can dump trash into it. :-)

-- 
Thomas Ulich  NEW e-mail: [email-masked]  www: http://cc.oulu.fi/~thu/
 
      Inuit say:  He who looks long upon the aurora soon goes mad.

---

From: [email-masked] (Thomas Ulich)
Date: 21 May 1996 16:05:54 GMT

Orjan Johansen ([email-masked]) wrote:
: >Which let's me assume that the rights for the device /dev/null are messed
: >up.  It should be rw-rw-rw- so that everybody can dump trash into it. :-)
: 
: Not at all, the permissions are right, and both cat >/dev/null and
: cat >>/dev/null from the command line work.

: [Message append failed: Invalid argument]
: Write to /dev/null failed
: 
: ls -l gives crw-rw-rw- (for special device, I assume.)
: I guess pine is trying to seek to the end of the device, or something.

Hmmm.  Strange.  I just tried it again with 3.93 under Solaris 2.4 on our
good ol' IPXbox, and it worked fine.  Same result for doing it directly
in the composer or putting it already in an address book entry.  And I know
that it worked before I upgraded from 3.91.  But maybe the Linux binaries
have a bug?  Recompile, pine I mean, not Linux of course?  Otherwise I have
worked with Linux since 1992 and it always worked well, even in those early
days.  Oh, one more thing F.Y.I. I checked the correct rights for /dev/null
and you are absolutely correct.

Still wondering...

---

From: [email-masked] (Orjan Johansen)
Date: 21 May 1996 04:10:20 GMT

>up.  It should be rw-rw-rw- so that everybody can dump trash into it. :-)

Not at all, the permissions are right, and both cat >/dev/null and
cat >>/dev/null from the command line work.

Error messages (more or less, they passed by quickly and I could only copy one
with the mouse:)
[Message append failed: Invalid argument]
Write to /dev/null failed

ls -l gives crw-rw-rw- (for special device, I assume.)
I guess pine is trying to seek to the end of the device, or something.

Greetings,
Ørjan.