On Mon, 20 Nov 1995, Craig Sanders wrote:
> Return-Path: <@mongo.pixar.com:[EMAIL PROTECTED]>
> Received: from mongo.pixar.com ([138.72.50.60]) by muffin.pronet.com
> with smtp id <[EMAIL PROTECTED]>
> (Debian /\oo/\ Smail3.1.29.1 #29.33); Mon, 20 Nov 95 09:19 EST
> Received: by mongo.pixar.com (8.7.1) id OAA13629; Sun, 19 Nov 1995 14:19:16
> -0800 (PST)
> Old-Return-Path: <[EMAIL PROTECTED]>
> Date: Mon, 20 Nov 1995 09:16:06 +1100 (EST)
> From: Craig Sanders <[EMAIL PROTECTED]>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Ack! it's doing this again (or maybe the debian-user list at mongo.pixar.com
is doing that).
Sometimes it's [EMAIL PROTECTED], sometimes it's [EMAIL PROTECTED], once
or twice it's even been [EMAIL PROTECTED] as it should be.
> Reply-To: [EMAIL PROTECTED]
> To: Debian-User <[EMAIL PROTECTED]>
> Subject: HELP! bad smail configuration...smailconfig problem?
> Message-Id: <[EMAIL PROTECTED]>
^^^^^^
This should be my FQDN as well. Is this a pine problem or a smail problem?
aha! that's it. just tried "ls -al | mail -s test [EMAIL PROTECTED]"
(my standard test message) and the headers are perfect!
The problem is in pine, not smail.
That explains why I thought I had it fixed yesterday, only to find that
my headers were still being screwed up today! I did all my testing from
the shell.
> X-No-Junk-Mail: Do not send me junk mail under any circumstances
> Mime-Version: 1.0
> Content-Type: TEXT/PLAIN; charset=US-ASCII
> Resent-Message-ID: <"qSCZX.A.VQD.H06rw"@mongo>
> Resent-From: [EMAIL PROTECTED]
> X-Mailing-List: <[EMAIL PROTECTED]> archive/latest/2803
> X-Loop: [EMAIL PROTECTED]
> Precedence: list
> Resent-Sender: [EMAIL PROTECTED]
Craig
--
[EMAIL PROTECTED] [EMAIL PROTECTED]
* Unix Consulting: Installation, Configuration, & Support. *
* --- Also, contact me if you need your Dos/Win/OS2 LAN connected to --- *
* --- the Internet. --- *
