[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

2422.0. "Mail status CONSULTE (NOTED)" by BERN01::MATSUI (Sandra Matsui, Berne Switzerland) Tue Mar 16 1993 18:53

    software:  VMS 5.5
               ALL-IN-1 V3.0 french
    
    my customer has reported a problem when reading a mail message received
    from the postmaster.
    
    user sends a mail with delivery receipt.
    
    the delivery receipt arrives in folder ARRIVE (INBOX) and has status
    NON LU (UNREAD).
    
    user reads the delivery receipt.  it appears on the screen formatted as
    a normal ascii text and not as a mail message (i.e. no mail header).
    
    <CR> to end reading the delivery receipt.
    
    it now has status CONSULTE (NOTED).
    
    my test system has german as primary language and french as secondary
    language.  i have sent mails with delivery receipts and then have had
    to rename folders to get my EINGANG folder to be the ARRIVE folder.
    
    when i have managed to reproduce the above behaviour, execution is in
    the MAIL READ function.  when the error occurs, MAIL READ calls WPLIST
    to display the document instead of LIST_DOCUMENT.
    
    ![MAIL]   Display document
    ![FUNC]   Function: DO, Cmd line: WPLIST
    
    another weird thing is that at one point OA$CURDOC_TYPE ends up
    containing the value MESSSAGE (yes, 3 S's).
    
    i won't be able to log on to the customer system until Friday.  He
    claims that this error also occurs for mail messages that arrive from
    another node.
    
    does anyone have some helpful ideas as to how i could localize the
    problem?
    
    thanks for taking the time to read my lengthy description.
    
    Sandra
T.RTitleUserPersonal
Name
DateLines
2422.1Localisation Problem?IOSG::PYEGraham - ALL-IN-1 Sorcerer&#039;s ApprenticeWed Mar 17 1993 09:2811
    This sounds like it might be a localisation problem. Something may not
    have been correctly translated, so the message type or status isn't
    being recognised properly. Unfortunately we make it very difficult for
    the translators by storing the same string in several different places,
    all of them having to be set to exactly the same thing for things to
    work correctly....
    
    You might want to contact Frankfurt (See note 1788.8 for details) to
    see if this is a known I18N problem, or if they can help you.
    
    Graham
2422.2Got the same problemKETJE::CAPPELLEMANSThe Dark side of the \FORCEWed Mar 24 1993 08:4018
I've deleted my previous entered reply as it was completely wrong....
GBLPAGFIL has nothing to do with the problem.
I investigated a little bit further and this is what I've found.

The problem occurs when a mail is received through MAILbus.
This only happens (as far that I've tested it) if the MAIL BODY is WPS-PLUS,
if the MAIL has a TEXT body, then it work's fine (for example when sending MAIL
from TeamLinks). 
Looking in OA$BUILD, the only reference I've found to MESSSAGE (with 3 S) is
in the Message file OA.A1$MSG and it's called
OA$_LANG_MAIL_TYPE, I've tried to correct the spelling, recompiled/installed
the Message file, but still the same story.
I saw a reference to this message symbol is in OA$LIB:OASYMMSG.MAR 
Is OA$_LANG_MAIL_TYPE included somewhere at link time, or is it more tricky?

Any help is welcome
Best regards
Pierre
2422.3Which version of ALL-IN-1 again?AIMTEC::WICKS_AOscar the Grouch is an Optimist!Wed Mar 24 1993 08:5112
    Pierre,
    
    Come again ...
    
    OA.A1$MSG was introduced in v3.0 
    OASYMMSG.MAR was removed in v3.0
    
    Too early in the morning for me...
    
    regards,
    
    Andrew.d.Wicks
2422.4Old Upgrade file....KETJE::CAPPELLEMANSThe Dark side of the \FORCEWed Mar 24 1993 12:557
Right,

I'm Running V3.0 and the OASYMMSG.MAR wasn't cleaned up after upgarding.

Too soon after lunch....

Pierre
2422.5Check symbols in all places!IOSG::PYEGraham - ALL-IN-1 Sorcerer&#039;s ApprenticeWed Mar 24 1993 14:3820
    In the English V3.0 kit, the word 'NOTED' is defined in:
    
    EM.A1$MSG
    	TABLE_STATUS     <READ, SENT, UNREAD, UNSENT, NOTED, ......
    
    OA.A1$MSG
    	LANG_MAIL_STATUS <UNSENT,SENT,READ,UNREAD,ARCHIVED,NOTED, ....
    
    OALLV.BLI
    	OA$GT_STS_READING    : $OA_GSLIT ('NOTED')
    
    Note that the definition in OALLV.BLI provides the two special symbols
    (defined in OAGBL.BLI) OA$MAIL_NOTED and OA$STS_NOTED.
    
    Check that these, and the other READ, UNREAD etc. symbols are all
    translated to the *SAME* things.
    
    Graham
    
    PS Oh, and if they aren't, send your bug to Frankfurt, not me!!
2422.6Frankfurt bugfixesBERN01::MATSUISandra Matsui, Berne SwitzerlandThu Mar 25 1993 10:1734
hi all,

i've been away on a course.  i found the solution to my problem in Frankfurt.

PETRUS::A1$ENG3:[DIAMOND.BUGFIXES$PUBLIC.language]README.TXT

where language is GERMAN, FRENCH, etc.

this file lists the bugs that have been found and corrected.  the necessary
files are also in the directory.

i am doing a holiday replacement for a colleague and didn't realize that
he had forgotten to install the bugfixes.

one thing to note for the french language is that the script DOCDB.SCP does
not work.  correct the part for "MESSAGE" .MAIL_TYPE should be .TYPE and 
MAIL_STATUS should be TYPE.

the remarks in the README.TXT are correct:  change CAB$ records with
.type "MESSAGE" or "MESSSAGE" to "MAIL"
.type "LISTE DISTRIB." or "LISTE DISTR." to "DISTRIB LIST"

one change that was not mentioned is that you should check PROFIL entries
for distribution lists (.user contains "@" or ":") to make sure that for 
the field 
.maides "PUBLIPOST." is changed to "MAIL-LIST"

we installed the bugfixes on a customer system last Friday night, but
haven't heard from the customer since then.

i will give my feedback to the people in Frankfurt.

thanks for you answers
Sandra
2422.7RE: 5 OK but...KETJE::CAPPELLEMANSThe Dark side of the \FORCEThu Mar 25 1993 13:5710
1) I think the problem was due to the wrong translation of MAIL to MESSSAGE not
the NOTED I18N,

2) Apparently it wasn't enough to correct the message file.

3) more nasty, why was this problem not occuring with mails having a TEXT body???


Best regards and many thanks
Pierre
2422.8more languages for the worldPAULUS::HOFMANNStefan Hofmann, LC Frankfurt, ISEMon Mar 29 1993 08:5226
    ... as we are talking about I18n:
    
    ALL-IN-1 V3.0 is available in a lot of different languages. Most of
    them are fully compatible and can be installed everywhere in the world,
    mono- and multilingually.
    
    So, if you have a customer at some place in the world where you don't
    know how to get a specific language kit for ALL-IN-1, don't tell the 
    customer "we can't"!  Send a mail to Peter Hanspach at FRO 
    (PAULUS::HANSPACH) for help.
    
    Current list of fully supported languages:
        Danish
    	Dutch
    	English
    	Finnish
    	French
    	German
    	Italian
    	Norwegian
    	Portuguese    
    	Spanish
    	Swedish
    	
    		
    		Stefan