[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

Title:*OLD* ALL-IN-1 (tm) Support Conference
Notice:Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:IOSG::PYE
Created:Thu Jan 30 1992
Last Modified:Tue Jan 23 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:4343
Total number of notes:18308

615.0. "Subject line in WPS document" by BUFFER::BRODERICK (I hate it when this name gets truncated) Fri May 01 1992 01:42

I have a miscellaneous, probably real easy to answer question about using WP
and sending mail.  (I'm trying to work a problem with a customer regarding our
FGATE (fax)product, but it looks like an ALL-IN-1 IOS or WPS issue.  And I'm a
novice ALL-IN-1 IOS user.

When he sends mail from the WP subsystem, to a VMS Mail user, he gets the
following header lines in the top of the body:

   Author:
   Date:
   Posted-date:
   Subject:

The problem is that the subject line is padded out to over 80 columns (which
causes our software to handle it differently. I was trying to reproduce it to
see who is putting that line there that long.  But, whenever I send mail from
WP, I don't get a "Subject:" line in the message body. (I only get the first
3.)  

How do I get the "Subject:" line to appear?
   
                                                                 _Mike
T.RTitleUserPersonal
Name
DateLines
615.1Different versions of ALL-IN-1 ?IOSG::SHOVEDave Shove -- REO-D/3CFri May 01 1992 11:219
    If you do the send from the EM system, you can enter the subject.
    
    I have a feeling thaty whether you get a subject when sending from WP
    depends on the version of ALL-IN-1 (I think we fixed this in some
    version, possibly v2.4), so this could explain the difference - maybe
    your system is an older version than the customer's?
    
    Hopefully this will jog someone's memory as to the exact versions,
    Dave.
615.2subject padded to 81 chars?BUFFER::BRODERICKI hate it when this name gets truncatedThu May 07 1992 17:079
>    depends on the version of ALL-IN-1 (I think we fixed this in some
>    version, possibly v2.4), so this could explain the difference - maybe

That would make sense.  We have V2.3 and I imagine the customer has V2.4
(haven't asked him yet though).

So is it a bug or a feature that the line is padded out to 81 characters?

                                                                    _Mike
615.3Some more prodding....IOSG::PYEGraham - ALL-IN-1 Sorcerer's ApprenticeThu May 07 1992 18:3717
    We fixed the fact that a document sent from WP didn't get a subject in
    V2.4. This was actually broken in V2.3, since it worked OK in V2.2...
    
    However I also remember the bug where the title was too long, but as I
    recall, the problem was in read, where the title/subject field form the
    DAF didn't get trailing spaces stripped off, so that when it was read
    it put a little diamond out in column 80. This caused some display
    devices (some sort of fax or something I think) to switch into 132
    column mode and be unreadable!
    
    Naturally I can't find that fix either, but I think the person who did
    it left the group some time ago, so it was probably in V2.4...
    
    Graham
    
    PS Perhaps between us, Dave and I can get someone to remember the whole
    story!
615.4You can also try forward IOSG::WDAVIESWinton Davies,IOSGThu May 07 1992 19:348
    Actually I fixed this one in v3.0...
          
    What was happening was the WP title (a fixed length field of 80 chars)
    was being directly copied without being trimmed in to the message
    subject field. This 80 character length was causing certain FAX m/cs
    to flip over into 132 mode.         
    
    Winton
615.5MUst be REALLY fixed by nowAIMTEC::WICKS_AThe Mancs will NEVER win the lgeThu May 07 1992 23:2512
    Mike,
    
    This also appears as note 1243 in the archived version of this
    conference.
    
    I can't help but think that this was fixed by another ex-mail-developer
    during v2.4 who is still based in Reading so we now have at least 3 
    occurrences of this 'bug' being fixed and all in different years!!
    
    regards,
    
    Andrew.D.Wicks