Subject: Re: Domane name stamping

From: Laurie Cuthbert <[email-masked]>
Date: Tue, 7 Dec 1993 14:39:14 GMT

On Tue, 7 Dec 1993 14:11:35 +0000 (GMT) Philip Hazel wrote:

>> Aha. I too am running smail, but I am running with Nigel Metheringham's 
> bindlib, with maximum header re-writing turned on. Thus I don't get 
> messages delivered with no qualification. You can get these mods from 
> amp.york.ac.uk if you are interested. 

That sounds like a good idea - it might cure a number of other problems
> 
> HOWEVER, this morning I munged a message in a folder by hand to remove the 
> qualifications, and pine 3.88 still displayed it to me with "cus.cam.ac.uk" 
> added to each address. Wait ... dim bell rings ... I have it. It is only 
> with "full headers" turned OFF that I get it qualified. If I turn "full 
> headers" on, the message is displayed exactly as it is in the folder. 

This is true, except with us it adds theMACHINE NAME when headers are OFF, but I've 
discovered only in the inbox - when I open the same message saved in the received folder it 
puts on a proper qualifucation - as I go backwards and forwards between the folders it 
consistently changes things:

in the INBOX:

Date: Tue, 7 Dec 93 14:23 GMT
From: Laurie Cuthbert <laurie@osprey>
Reply to: Laurie Cuthbert <[email-masked]>
To: laurie@osprey
Subject: test

in the received folder:

Date: Tue, 7 Dec 93 14:23 GMT
From: Laurie Cuthbert <[email-masked]>
To: [email-masked]
Subject: test
 
Stranger and stranger!

> This does not bother me. What bothered me in 3.07 was that if you replied 
> to such a message, it added the machine name. This is no longer the case in 
> 3.8x; the domain name gets added when creating the addressee when replying. 
> This was the reason I patched 3.07, but didn't need to patch 3.8x.
> 
That is exactly the problem with us - if you reply from the INBOX it _does_ reply to the machine 
name.

I'm copying this to the list again to see if anyone else has seen it.

Thanks anyway

Laurie

---

From: Philip Hazel <[email-masked]>
Date: Tue, 7 Dec 1993 15:08:07 +0000 (GMT)

> That is exactly the problem with us - if you reply from the INBOX it _does_ reply to the machine 

Aha! That's the difference. I had not tried replying from the INBOX. I 
would think that is a bug, which the Pine people would like to hear about.
I'll do a test to see if I can confirm it, and post to the list myself if I 
can.

Philip

--
Philip Hazel                   University Computing Service,
[email-masked]             New Museums Site, Cambridge CB2 3QG,
[email-masked]          England.  Phone: +44 223 334714

---

From: David L Miller <[email-masked]>
Date: Tue, 7 Dec 1993 10:51:19 -0800 (PST)

Laurie,

Is one of your folders a remote IMAP folder?  If that is the case, an
unqualified name will get a different qualification.  In the case of a local
folder, the address is getting generated locally, so the local hostname
information is used.  If user-domain is set in your .pinerc it will be used,
otherwise the hostname returned by the system (as modified by the
use-only-domain variable) will be used.  For an IMAP folder, Pine uses an
envelope generated by the IMAP server and thus will use the server's
hostname.  In any case, pine or imapd just makes the best guess it can with
the information it has available. 

The full headers mode just displays the raw message with no parsing or
formatting. 

I hope this clears things up a little!

--DLM

|\ |  |\/|  David L. Miller    [email-masked]  (206) 685-6240
|/ |_ |  |  Software Engineer, Pine Development Team   (206) 685-4045 (FAX)
University of Washington, Networks & Distributed Computing
4545 15th Ave NE, Seattle WA 98105, USA

---

From: Laurie Cuthbert <[email-masked]>
Date: Tue, 7 Dec 1993 20:26:33 +0000 (GMT)

David

You have given us the answer!

The received folder is a local folder - this gets the correct 
fully-qualified name, INBOX is an IMAP folder (actually on the same 
machine) and this only gets given the hostname.

I can prove this by changing the inbox-path to be either accessed by IMAP 
or simply as a path:

inbox-path={osprey}inbox

inbox-path=/var/spool/mail/laurie

(the outgoing header is correct because we correct that in smail)

Is there any way to modify the interpretation of the header in IMAP 
folders to preferably mimic the behaviour with the local folder - it 
would certainly be a lot neater. In fact, it would even be better to 
leave the name unqualified rather than to add the hostname.

We intend to move away from NFS mounted mail folders as soon as possible 
and move entirely to IMAP so this actually is slightly inconvenient.

I agree that the MUA should NOT generate unqualified addresses - and we 
are rapidly throwing away those that are guilty (including Eudora), but 
it is difficult to get rid of them all. (It is impossible to stop 
everyone using /usr/ucb/mail !!)

The problem didn't surface until recently because it was masked by the UK 
configuration kit for sendmail which enables us to force qualification of 
all headers. Having changed to smail, which does distinguish between 
envelope and message headers it has now shown up.

Thanks again

Regards

Laurie