Couldn't agree with you more but the developers are unwilling to change to pure 
ASCII because the change would affect other reports that require UTF-8.

We all agree that this is a ridiculous subject line but the Peoplesoft 
developers refuse to alter this because "all other email programs are working 
fine", only Outlook has an issue.

Carl Rimmel
Senior Engineer, HFHS Messaging
Email:  [email protected]
Desk:  248-853-3620
----------------------------------------
HFHS Information Technology
2571 Product Drive
Rochester Hills, MI  48309


-----Original Message-----
From: Ben Scott [mailto:[email protected]] 
Sent: Tuesday, July 14, 2009 4:54 PM
To: MS-Exchange Admin Issues
Subject: Re: Changing Subject Line Limits

On Tue, Jul 14, 2009 at 4:44 PM, Ben Scott<[email protected]> wrote:
> You're assuming octets == glyphs, and
> that's very wrong for the encoded subjects the OP is seeing.

  Of course, I then thought to actually decode the BASE64 we were
given.  The subject line that made it this far is pure ASCII, and also
ridiculously long.

  If the rest of the subject line is pure ASCII, there's no need for
UTF-8 or BASE64.  Reconfigure the sending system not to do that, and
you'll gain at least BASE64 encoding overhead.

  The decoded subject line was:

        PeopleSoft error report: Error: First operand of . is NULL, so cannot
access member Len. (180,236) FUNCLIB_EXT_APP.RESUME.FieldFormula
Name:set_resume_step  PCPC:13552  Statement:

  Per ME2, that should be in the message body, and a summary, e.g.,
"PeopleSoft error report", in the subject.

-- Ben



==============================================================================
CONFIDENTIALITY NOTICE: This email contains information from the sender that 
may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY or otherwise protected 
from disclosure. This email is intended for use only by the person or entity to 
whom it is addressed. If you are not the intended recipient, any use, 
disclosure, copying, distribution, printing, or any action taken in reliance on 
the contents of this email, is strictly prohibited. If you received this email 
in error, please contact the sending party by reply email, delete the email 
from your computer system and shred any paper copies.
 
Note to Patients: There are a number of risks you should consider before using 
e-mail to communicate with us. See our Privacy Policy and Henry Ford My Health 
at www.henryford.com for more detailed information. If you do not believe that 
our policy gives you the privacy and security protection you need, do not send 
e-mail or Internet communications to us.

==============================================================================



Reply via email to