Conference iosg::all-in-1_v30

3779.0. "Subject field corrupted" by ULYSSE::DAVID (Guy David @VBE) Wed Jan 19 1994 19:33

    Hello,
    
    I've also posted the following problem in the ALL-IN-1 Personal Assistant 
    conference.
    
    On a system running VMS 5.5-2, ALL-IN-1 v3.0-1, and ALL-IN-1 Personal 
    Assistant v1.1, I've noticed a problem in messages that are automatically 
    forwarded by A1PA to a distribution list.
    The subject of these messages is corrupted, the original subject is 
    correctly used but extra blank characters are added at the end. When 
    reading the message, there's a continuation character on the right end of 
    the subject field, even in wide screen.
    
    The consequences are :
    - when printing, the subject field is omitted.
    - when transfering to VMS (DT SV), an error message is issued
    
    %OA-E-NOCOPY, Problem with COPY function - file "[-]GUY.TXT"                 
     -RMS-F-RSZ, invalid record size                                              
    %OA-I-LASTLINE, Document copied to VMS file                                  
    
     and only part of the message header is copied.
    
    Is this a known problem with the COPY function ?
    
    Thanks for your help,
    
    Guy.
    

    APA sticks a special character on the end of the subject line so that
    it can be recognised by another APA system, or it self, to stop
    different APA rules forawrding messages in a loop.
    
    Unfortunately, I think, if the document is in WPS-PLUS the effect is to
    produce a line that's too long for the text DSAB to handle, and
    sometimes odd things happen when you try to manually forward such a
    message, e.g. ALL-IN-1 ACCVIOs....
    
    Graham

If you do a Gold-R (Right Margin) or RM while reading the message you will 
see the characters 'APA' at the very end of the subject line.


Richard

    You're right, with RM, I see the 'APA' characters.
    I hope something will be done in next releases of ALL-IN-1, or A1PA to 
    clear this out.
    Thanks for the explanation,
    Guy.