| Hi Debbie,
.0> I have the following problem reported by a customer. Has this been
.0> QAR'ed? Should I?
Have you been able to reproduce this problem? I've tried several
times and have not been successful in doing so.
.0> ... I found that the spacing problem only happens with *'s
.0> and text formatting.
So this is telling me that if any character other than "*" is used
the problem does not occur?
Are other user's at the customer site experiencing the same problem
if they create/send/receive headers/footers of similar syntax?
.0> ... I tried to change formats to see if the problem still existed and
.0> nothing changed.
What other formats where tried?
.0> I go into cover memo under format and add the path of the text file I'm
.0> appending to the ending of my message. I go into font and select courier 10
.0> as my font, then save and click ok.
What are the "exact" settings in the 'Cover Memo Style' dialog box for "Options"
and "Fonts?"
Can we obtain the "exact" text format file that was used?
.0> The text file is appended ok and looks ok before I send the message, but the
.0> receiver gets a space in the *'s (1st and last line) and the lines wrap.
"The receiver?" Is it "one" receiver having the problem or "all" receivers?
What font is being used in the "read" window?
If the message is exported to a DOS directory and viewed is the space still there?
Does the message placed in the OUTBOX looked corrupted?
Does the message appear corrupt if sent to users on the same server?
Is this message going through any gateways?
Thanks,
Joe
|