I think this is still happening in 2004, at least in my case (fully updated to 11.2.5). I just tested this yesterday, trying to get past the corporate SMTP (internally, we use Exchange, but that interfaces to a Unix system at the firewall). The following text will get broken:
(begin test stream ... To reproduce the problem, remove the ">" at the start of each line, and get rid of the newline at the start of the lines that begin with "> f and" and "> c ...") > Two items on the agenda. > > 1 . Updated GSRP from Felix (see > http://www.ieee802.org/1/files/public/docs2006/avb-feng-GSRP-v0p4-060328.pdf ) > 2. Initial SW outline (checklist of AVB-specific control actions needed in > bridges/DTE) (see > http://www.ieee802.org/1/files/public/docs2006/avb-mjt-sw-outline-r1-060327.pd > f and > http://www.ieee802.org/1/files/public/docs2006/avb-mjt-sw-outline-r1-060327.do > c ... This last is an MS Word outline that others can use/modify) (end of test stream) If the above stream is put in an outgoing message, then select view->source you get: Two items on the agenda. 1 . Updated GSRP from Felix (see http://www.ieee802.org/1/files/public/docs2006/avb-feng-GSRP-v0p4-060328.pd= f ) 2. Initial SW outline (checklist of AVB-specific control actions needed in bridges/DTE) (see=20 http://www.ieee802.org/1/files/public/docs2006/avb-mjt-sw-outline-r1-060327= . pdf and=20 http://www.ieee802.org/1/files/public/docs2006/avb-mjt-sw-outline-r1-060327= . doc ... This last is an MS Word outline that others can use/modify) ARGH! The "327.pdf and" in the middle of the line enumerated "2." in the test stream gets turned into "327=<nl>.<nl>pdf and=20" ... Note the isolated <nl>.<nl>! Now it turns out that almost *everyone* these days doesn't have a problem with the isolated period (thank goodness!) so this is not a problem with my personal ISP's SMTP, but somehow the corporate Unix firewall hasn't been updated in this century ... > From: Barry Wainwright > Date: Wed, 26 Jul 2006 19:34:59 -0700 > To: "Entourage:mac Talk" <[email protected]> > Conversation: Period equals "end of message" > Subject: Re: Period equals "end of message" > > Hi, I'm here! > > Yes, this was an issue in vX, and was fixed at some point (If I recall > correctly, it was only an issue when the single period was 'linewrapped' to > a line on it's own, never when you typed '<return><period><return>'. > > However, as Beth says, this was fixed (for mail) at some point, either in > one of the vX service packs or in the update to 2004. News is a different > kettle of fish and we discovered much later that the issue was still present > for news messages (worse in fact, because any line starting with a period > would truncate a news message). > > I'm 99.9% sure it was fixed by 11.2.1, but why not apply the latest updates > to bring yourself up to 11.2.5 anyway - even if it doesn't fix that issue > there will be several bug & security issues fixed besides. > > -- > Barry > > >> From: Beth Rosengard <[EMAIL PROTECTED]> >> Reply-To: "Entourage:mac Talk" <[email protected]> >> Date: Tue, 25 Jul 2006 23:12:57 -0700 >> To: "Entourage:mac Talk" <[email protected]> >> Conversation: Period equals "end of message" >> Subject: Re: Period equals "end of message" >> >> Hi Barbara, >> >> Are you talking about all plain text messages or just those sent to >> newsgroups, by any chance? The reason I ask is that the bug was fixed a few >> versions back (though it didn't exist at all in Entourage 2001!) *except* >> for newsgroups. If you're seeing this outside of the newsgroup environment, >> then I'm at a loss. >> >> Barry Wainwright, who looks in here from time to time, knows more about the >> issue than I do, so keep checking back. >> >> Beth >> >> >> On 7/25/06 12:04 PM, "Barbara Alfors" <[EMAIL PROTECTED]> wrote: >> >>> We've just realized that our plain text messages are getting truncated if >>> there happens to be a single period at the start of a line. This happens >>> occasionally due to line wrapping. >>> >>> Apparently this problem is due to Entourage's inability to compensate for >>> default SMTP behavior (my understanding is that mail clients are supposed to >>> do this). Does anyone have a fix for this problem? I'm currently using >>> 11.2.1, but it doesn't appear that newer versions have solved the problem. >>> >>> It's been suggested that the solution is to use HTML email, but I find that >>> idea repugnant. -- Michael D. Johas Teener -- http://xri.net/=Michael.Johas.Teener --- PGP ID 0x3179D202 -- To unsubscribe: <mailto:[EMAIL PROTECTED]> archives: <http://www.mail-archive.com/entourage-talk%40lists.letterrip.com/> old-archive: <http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
