Subject: rfc 822 again !

From: Francois Donze <[email-masked]>
Date: Wed, 1 Dec 1993 16:27:27 +0100 (French Winter)

Hi,

I just upgrade from 3.07 to 3.88 and noticed that the address beautifier 
has been improved. In 3.07 when I received a mail from a VAX-VMS node on 
my Ultrix system, strange things appeared  on the notification bottom 
line, in  the from field but I could easily cope with that.

Now, in 3.88 when I receive a mail from decnetnode::user, the notification 
bottom line is decnetnode@(null). Thus I don't know who is the sender.

When I read the message, the From field is something like:

If I want to reply to this user, the To field is something like:

decnetnode: : , Comments-which-are-in-round-braces-in-the-original-header 
<[email-masked].> ; ;

Actually, the above is a very big problem when I decide to reply. In this 
case, the To field gets automatically filled up with:

decnetnode:,
	     : ,
	     Comments-which-are-in-round-braces-in-the-original-header
	     ;,
	     ;

This means that I have to ^K 4 times and then put a correct To field. 
With 3.07, only one ^K was Ok.

My question is:
Is there something existin/planned for telling pine not to go thru the 
rfc822-address beautifier for incoming messages? I am thinking of a 
parameter in .pinerc for example.

Rgds,
/francois
------------------------------------------------------------------------------
Digital Equipment SARL		|			   |
950 Route des Colles - BP 027	|      Francois Donze	   |
06901 SOPHIA ANTIPOLIS		|--------------------------|francois donze@VBO
	FRANCE			|			   |  ULYSSE::DONZE
 Tel: (33) 92.95.54.81 		|E-mail: [email-masked] |  DTN: 828-5481
 Fax: (33) 92.95.62.34		|			   |
------------------------------------------------------------------------------

---

From: Earl Fogel <[email-masked]>
Date: Wed, 1 Dec 1993 11:23:16 -0600 (CST)

> bottom line is decnetnode@(null). Thus I don't know who is the sender.

I've made the following changes to pine3.88/imap/non-ANSI/c-client/rfc822.c
to allow our local Ultrix users to reply to mail from DECnet nodes.

Earl Fogel
Computing Services              phone: (306) 966-4861
University of Saskatchewan      email: [email-masked]
--

% diff rfc822.c.orig rfc822.c
790c790
<   char *p,*s;
---
>   char *p,*p1,*s;
798a799,816
> #ifndef STRICT_RFC822
>     /*
>      * convert host::user (DECnet address) to user@host
>      */
>     if ( (p1 = rfc822_parse_phrase (string)) && *p1 == ':' && *(p1+1) == ':') {
>         *p1 = '\0';
>         strcpy(tmp, string);
>         p1 += 2;
>         while (*p1)
>             *p++ = *p1++;
>         *p++ = '@';
>         p1 = tmp;
>         while (*p1)
>             *p++ = *p1++;
>         *p++ = ' ';
> 	p = string;
>     }
> #endif

---

From: "Jackie \"Oh!\" Owen" <[email-masked]>
Date: Wed, 1 Dec 1993 12:53:54 -0500 (EST)

Along those same lines, we're experiencing a similar problem for outgoing
messages where when you send mail to a DECnet address (e.g., host::doe),
pine automatically appends the local hostname (becomes
host::[email-masked]) which will not go through.  As Francois
asked, is there something in .pinerc that can be modified so that the
@ultrix.ramapo.edu is not automatically appended? 

Thanks in advance,

Jackie O.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Jackie Loucks Owen				Network Administrator
[email-masked]				Ramapo College of NJ
						Mahwah, NJ

        "Time flies like an arrow.  Fruit flies like a banana."
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

---

From: Mark Crispin <[email-masked]>
Date: Thu, 2 Dec 1993 23:07:03 -0800 (PST)

Hello -

     At the present time Pine only supports addresses in RFC-822 format, that
is, Internet Standard format.  Pine may, in the future, support non-Internet
format addresses such as DECnet or UUCP, but we can't make any promises at the
present time.

     Anyone who has dealt with multiple address formats with sendmail can tell
many horror stories about this topic.  It is not an easy problem.

     It is important to recognize that Pine is not ``beautifying'' addresses
out of some sense of esthetics.  Rather, Pine is parsing the addresses into an
internal data structure, which it uses both for the filtered display and for
constructing a reply.  What you see from Pine is Pine's understanding of what
the addresses in the message contain.

     When reading incoming messages, you can display the exact header of the
message, warts and all, by using the H command.  This toggles you between
literal and filtered header display.

     There is nothing that can be done about sending outgoing messages; when
entering an address in the composer you are actually entering a command to a
command input processor.  If that processor does not understand the address
format, it can't represent it in any reasonable fashion.

     There is a possible workaround, however; you can try using quoted
strings.  That is, instead of typing
	foo::bar::zap::user
type
	"foo::bar::zap::user"
This has been rumored to work at a number of sites, although it does require
some intelligence on the part of your mailer.  It has one major benefit; the
resulting address will be in valid Internet format so if the message escapes
to the non-DECnet world, it will be something that others can parse.

-- Mark --