steed@TECHUNIX.BITNET (Ze'ev Shtadler) (09/12/89)
I noticed a problem when I tried to relpy the following letter:
--- Forwarded mail from TeX-Euro, Distribution, List, for, Eropean, TeX, Users,
<TEX-EURO@DHDURZ1.bitnet>
>From TEX-EURO@DHDURZ1.bitnet Tue Sep 12 13:30:07 1989
Received: by techunix.bitnet (sendmail 5.61/7.2a)
id AA13220; Tue, 12 Sep 89 14:30:02 +0300
Message-Id: <8909121130.AA13220@techunix.bitnet>
Received: from TAUNIVM.TAU.AC.IL for TEX-EURO@DHDURZ1.BITNET with BSMTP (1.0);
Tue, 12 Sep 89 11:29:59 GMT
Received: by TAUNIVM (Mailer R2.03B) id 4544; Tue, 12 Sep 89 13:28:15 IST
Date: Tue, 12 Sep 89 10:07:00 N
Reply-To: TeX-Euro Distribution List for Eropean TeX Users
<TEX-EURO@DHDURZ1.bitnet>
Sender: TeX-Euro Distribution List for Eropean TeX Users
<TEX-EURO@DHDURZ1.bitnet>
From: VANSOEST@HENUT5.bitnet
Subject: query: Use of printer-resident PostScript fonts
To: Ze'ev Shtadler <STEED@techunix.technion.ac.il>
[Contents Deleted.]
--- End of forwarded message from TeX-Euro, Distribution, List, for, Eropean,
TeX, Users, <TEX-EURO@DHDURZ1.bitnet>
As you can see in the "End of forwarded message" line above, Mush
treats the "Sender:" and "Reply-To:" headers as containing multiple
addresses: "TeX-Euro, Distribution, List, for, Eropean, TeX, Users,
<TEX-EURO@DHDURZ1.bitnet>". It seems that Mush treats line
continuation as an implicit comma - therefore forces the sender
name to be a list of senders. I checked UCB-Mail and didn't find
that feature/bug there. I don't know much about the mail standards,
but I don't see any harm in NOT inserting the implicit comma.
Ze'ev.
--
Ze'ev Shtadler. ARPANET: steed%techunix.bitnet@cunyvm.cuny.edu
Computer Science Faculty, UUCP: ...!psuvax1!techunix.bitnet!steed
Technion, Israel Institute of Technology, BITNET: steed@techunix
Haifa Israel Domain: steed@techunix.technion.ac.il
Phone (work): (+972) 4-294304 CSNET: steed%techunix.bitnet@csnet-relay.csnetdheller@cory.Berkeley.EDU (Dan Heller) (09/13/89)
In article <8909121243.AA15988@techunix.bitnet> Ze'ev Shtadler <steed%TECHUNIX.BITNET@mitvma.mit.edu> writes: > I noticed a problem when I tried to relpy the following letter: > > Sender: TeX-Euro Distribution List for Eropean TeX Users > <TEX-EURO@DHDURZ1.bitnet> > From: VANSOEST@HENUT5.bitnet > Subject: query: Use of printer-resident PostScript fonts > To: Ze'ev Shtadler <STEED@techunix.technion.ac.il> > > As you can see in the "End of forwarded message" line above, Mush > treats the "Sender:" and "Reply-To:" headers as containing multiple > addresses: "TeX-Euro, Distribution, List, for, Eropean, TeX, Users, > <TEX-EURO@DHDURZ1.bitnet>". It seems that Mush treats line > continuation as an implicit comma - therefore forces the sender > name to be a list of senders. Almost correct. Mush treats multiple headers that are similar as one header and implicitly adds a comma: To: dheller@cory.berkeley.edu To: argv@sun.com when replied to, this would generate: To: dheller@cory.berkeley.edu, argv@sun.com The situation you see above is due to some other problem, I'm sure. Not 100% sure, but pretty sure :-) I'm not sure which version you're using, but my current version doesn't have that problem. for those interested, the "current" version I'm talking about is the current version of mushview not yet available. It will be when bart comes back from vacation (sometime this week, I suppose). Dan Heller <island!argv@sun.com>