Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!hplabs!nsc!taux01!tasu77!crehta
From: crehta@tasu77.UUCP (Ran Ever-Hadani)
Newsgroups: comp.mail.mush
Subject: Re: Bcc in auto_hdr (suggestion)
Keywords: mush my_hdr Bcc
Message-ID: <1713@taux01.UUCP>
Date: 17 May 89 13:47:21 GMT
References: <1700@taux01.UUCP> <105202@sun.Eng.Sun.COM>
Sender: netnews@taux01.UUCP
Reply-To: crehta%taux01%nsc.com@sun.com (Ran Ever-Hadani)
Organization: National Semiconductor (IC) Ltd, Israel
Lines: 22

In article <105202@sun.Eng.Sun.COM> argv@sun.UUCP (Dan Heller) writes:
>In article <1700@taux01.UUCP> crehta%taux01%nsc.com@sun.com (Ran Ever-Hadani) writes:
>> I find the auto_hdr option very useful.  I only wish it let you edit the
>> Bcc: header in the same way it treats Cc: .
>> 
>You can do this, but instead of using a null string, use a "blank". e.g.
>my_hdr Bcc: " "
>This way, Bcc: has the value of " " (a space) but spaces are ignored
>in the header-parsing method and the header won't be added.
>
>    dan  <argv@sun.com>

I tried it and the Bcc: does not appear in the edited file;  so
it does not behave as with the Cc: .

Is that a bug? if not, is there a different simple sollution to the problem?

(I could start messing with $visual, i.e. have it point to a shell script
etc., but this does not seem clean).


-- Ran