Welcome to the MacNN Forums.

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

You are here: MacNN Forums > Software - Troubleshooting and Discussion > Applications > appended date in "from" field--reply from MS

appended date in "from" field--reply from MS
Thread Tools
Rich
Guest
Status:
Reply With Quote
Oct 29, 1999, 05:31 PM
 
Thought you all might like to know. Regarding the problem where the date and time are appended to the end of the sender's address, which also gets passed to the TO field when you reply, causing an addressing error unless you manually delete the date information.

I just spoke with MS Tech Support. Apparently the "developers are aware of the issue" and we are to "check the website for a fix".

He was unable to specify a timeframe for the fix
     
ioResult
Guest
Status:
Reply With Quote
Oct 30, 1999, 12:54 AM
 
The reason that some people are seeing this problem has to do with the screwy mail servers to which they are connecting.

Normally when a mail server sends you a message, the beginning of the header looks like this:

Received: from mail.zip.zot by mail.foo.bar (Sendmail 8.6.12/950620.JB) with ESMTP id SAA06945; Tue, 29 Oct 1999 18:36:59 -0500
X-Mailer: someMailer
MIME-Version: 1.0
Message-Id: <[email protected]>
Date: Tue, 29 Oct 1999 15:39:02 -0800
From: nobody@nowhere
To: [email protected]
Subject: Where IS this yellow submarine we supposedly live in?
Content-Transfer-Encoding: Quoted-Printable
Content-Type: Text/Plain; charset=US-ASCII
Content-Disposition: Inline

The header contains one or more received lines, a to, from, subject, date, and a whole bunch of other stuff.

Well if you look at one of the messages where this oddity is happening, you will see the first line of the header of the message is different, like this:

From <somewhere> Tue, 29 Oct 1999 19:38:50 -0500
Received: from mail.zip.zot by mail.foo.bar (Sendmail 8.6.12/950620.JB) with ESMTP id SAA06945; Tue, 29 Oct 1999 18:36:59 -0500
X-Mailer: someMailer
MIME-Version: 1.0
Message-Id: <[email protected]>
Date: Tue, 29 Oct 1999 15:39:02 -0800
From: nobody@nowhere
To: [email protected]
Subject: Where IS this yellow submarine we supposedly live in?
Content-Transfer-Encoding: Quoted-Printable
Content-Type: Text/Plain; charset=US-ASCII
Content-Disposition: Inline

What *IS* that line?

Well, those initial "From" lines are part of the "mbox" message file format used on unix boxes. When you use a unix-based mail package, as messages are added to your mail spool, the unix mail package puts one at the beginning of each message added to the spool so you know when the message was put into the mail spool.

So why are some mail servers erroneously prepending messages that they send to POP mail clients?

I have no idea. They SHOULDN'T be sending out mail with those filer lines prepended to the top of each message. It really is a bug in the mail server software. Yell at whomever makes your mail server software and tell them to stop doing that.

So why doesn't this happen in other e-mail packages?

Well, it seems that the parser inside of OE 5 which parses the headers simply looks for lines beginning with the special header words like "To", "From", "Subject", "Date", etc. where other mail packages are looking for those same words immediately followed by a colon, i.e. "To:", "From:", etc. So because OE isn't expecting that mbox filer line to be at the beginning of the message it receives from the POP server, it doesn't bother checking to see if there's a colon after the "From". As a result it thinks the filer line at the beginning is the "From:" header in the mail message. It is wrong.

So, ultimately there are two things at fault here. First, the goofy mail servers should NOT be sending you mail files with that extra "From ..." line at the top, they are violating the internet's IETF standard, RFC822, by doing that. So yell at them. Secondly, MS didn't write defensive code which is anal-retentive enough to require the colon after the header token. The MS guys evidently never expected to get incorrectly formed messages from any mail servers. They were wrong. They should change their code to look for the colon. So until they do, yell at your ISP or whomever and tell them to get their server to not send you bad RFC822 messages because the stuff they're sending out is wrong.

There is evidently an AppleScript which was written by one of the MS guys which fixes messages you get like this. I think it's available on the unofficial OE site.
http://www.macemail.com/oe/
     
iMacMike
Fresh-Faced Recruit
Join Date: Oct 1999
Location: Lubbock, TX
Status: Offline
Reply With Quote
Oct 30, 1999, 05:35 PM
 
Why is is a server bug when only OE5 seems to have this problem? Why didn't the beta testers find this problem?

OE5 is really a 1.0 release, since the MacOE team has repeatedly said that it is a total re-write. It also seems to me that there is either something lacking in MS's beta test procedures or they just didn't care. There are just too many problems and complaints to have escaped the scrutiny of a large public beta test... or is that what were doing now?

------------------
I work, I play, iMac!
--
"I work, I play, iMac!"
     
   
 
Forum Links
Forum Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Top
Privacy Policy
All times are GMT -4. The time now is 09:17 AM.
All contents of these forums © 1995-2017 MacNN. All rights reserved.
Branding + Design: www.gesamtbild.com
vBulletin v.3.8.8 © 2000-2017, Jelsoft Enterprises Ltd.,