Subject: @unspecified-domain

From: Marc Fournier <[email-masked]>
Date: Wed, 16 Jul 1997 09:40:04 -0300 (ADT)

Hi...

	After spending a good deal of time trying to debug this in 
sendmail, and having asked it of the sendmail ppl, I've finally narrowed
down a problem with mail to being pine, not sendmail, related...

	If I send email To: <localuser>, using a client like Pegasus,
that connects via SMTP to my local mail server, it gets delivered to
the localuser with a header that says:

To: <localuser>

	Since there is no domain attached to it, when I bring it up in 
Pine with 'full headers disabled', it tells me that its:

To: <localuser>@unspecified-domain

	But, if I bring it up with 'full headers enabled', it comes up
correctly...

	Of course, if I try to reply to the email, including all
recipients, it tries to send to <localuser>@unspecified-domain

	Since I'm trying to convince ppl to switch *to* pine for email,
from elm, and since a good portion of our campus is using Pegasus, I'd
like to fix this "bug" so that pine is usable.  Someone in Pegasus shouldn't
have to enter '<localuser>@<localdomain>', if its to be locally delivered...

	Has anyone else seen this?  Is there a way of fixing it?

	This is under Solaris 2.5.1, using both 3.91 and 3.96 (3.96 being 
the binary available at UofW)...

---

From: Edward M Greshko <[email-masked]>
Date: Wed, 16 Jul 1997 22:57:23 +0800 (GMT)

> the binary available at UofW)...

Seen it?  No, all of my systems are configured properly.  :-) :-)

I suspect your system may not be properly setup to return a domainname.
Take a look in your /etc/hosts file.  Does the host name appear in the
table before the FQDN?  Like this:

xx.xx.xx.xx	foo foo.bar.com

If so, try setting it to:

xx.xx.xx.xx	foo.bar.com foo

which is what it should be anyway.

Also, you may be able to work around your problem by looking into the
"user-doamin" in the setup/config and setting that in the system-wide
pine config file.  

Another thing, which may not be related, is to set the "defaultdomain"
in /etc ... but maybe that only has to do with NIS.

Ed

-- 
Edward M. Greshko                  Technical Manager, Electronic Commerce
                                   Control Data Asia/Pacific Region
Voice: +886-2-715-2222 x287        6/F, 131 Nanking East Road, Section 3
FAX  : +886-2-712-9197             Taipei, Taiwan R.O.C

---

From: Marc Fournier <[email-masked]>
Date: Wed, 16 Jul 1997 20:29:09 -0300 (ADT)

> Seen it?  No, all of my systems are configured properly.  :-) :-)

	Since I just started working here a few months back, and am
still wading through various "interesting features" left by my 
predecessor...I still learning what is and isn't configured properly...

> which is what it should be anyway.

	Good suggestion, but the end result, I fear, wouldn't be what 
I need :(

	See, the problem is that I have a network of something like 5k
computers (mostly notebooks) that is now configured to read mail and
send mail through one central mail server.  Probably a good 75% of
the mail readers used happens to be Pegasus.

	Now, if I send email from pine, there is no problem, since pine
will (and does) automatically add the domain (@acadiau.ca) to any address
that I just type the local userid for...that is, on outbound email.  But,
Pegasus doesn't do this, which, for my purposes, I can live with...

	What I would like is that if pine displays a message with a header
like:

To: unixsys,[email-masked]

	It leaves it like that, instead of:

To: unixsys@unspecified-domain,[email-masked]

	Which would solve my problem.

	*If*, by your explanation, my system were "properly configured",
I believe you are suggesting that pine should give me:

To: [email-masked],[email-masked]

	As iceberg.acadiau.ca is the system that I'm running my pine
session from...except that there is no user named unixsys on iceberg,
and the domain should be set to @acadiau.ca, if anything...

	Not sure if that makes much more sense then my original...

> "user-doamin" in the setup/config and setting that in the system-wide

	Good thought, tried that...it does set the outgoing @acadiau.ca,
but doesn't seem to handle the inbound stuff... :(