Conference iosg::all-in-1_v30

re: -1

>
>        The users are using Pathworks on the PC to log onto their ALL-IN-1 
>system, but this should not make any difference, as they are not using 
>Desktop. I also do not think they are using Personal Assistant, but I will 
>check up on this.
>

Julie,

I don't pretend to be qualified to answer, but I have personally experienced 
this behavior which may help you isolate the "problem".

I first encountered this when we got TeamLinks working with our regional 
ALL-IN-1 IOS V3.0 server.  What I noticed when I left the TeamLinks, after an 
active session of reading messages, deleting some, and moving others, is the 
very scenario you describe.  Those messages which I had READ in the INBOX were 
still in the INBOX tagged READ.  I don't really see this as a problem but 
rather a feature for the TeamLinks user, but it's not my intend to begin a 
rathole on this subject.

So several days later, in a gesture of good corporate citizenship (and to 
avoid "Document Quota H*ll") I did and EW to empty my WASTEBASKET.  I'm doing 
this from a terminal window into the IOS system.  I get back a message from EW 
saying something like "these messages could not be deleted from your 
WASTEBASKET".  After some head scratching I came to the conclusion (see the 
light bulb going off) that these are items that I deleted from TeamLinks.  I 
confirmed this with another test and got the same results.  

I was able to delete these items by clicking on the Empty Wastebasket icon in 
TeamLinks.  The items were then removed from the WASTEBASKET.  After some 
thought I don't really see this scenario as a problem but rather a feature.  

I don't know if this helps, but if your customer is doing TeamLinks it sure 
would point to consistent product behavior even though yours is a V2.4 IOS 
environment.

Hope this helps, and please post the resolution here.

THANKS!!

Rick

    Thanks for the reply,
    
    	The customer does not have Teamlinks installed on their system, and
    he does not know of any other assets that he has which would affect
    mail. He also does not use Desktop - does anyone else have any other
    ideas??
    
    	Thanks,
    
    		Julie

Julie,

Is there anything else either 'special' or wrong with the message? In trying 
to narrow down the possibilities I remember that the code had to do 5 things 
when finishing read/unread (though I can't remember in which order they get 
done!):

	Decrement the newmail count
	Change status to READ
	Refile to READ folder
	Execute attached function
	Check for (and execute) read receipt request.

Any of those give you a hint? Do 4 out of the 5 work correctly?

grahame

    .0 presumably contains a typo I hope where it says the message is
    UNSENT in the INBOX
    
    It should of course be UNREAD or have I been away too long??
    
    GASH is wise not to remember which order the five tasks are done since
    they are actually done in a different order depending on whether you
    are reading, printing or deleting whilst reading an unread mail message
    though he did name all 5 tasks correctly - what is it they say about
    old mail developers? - no don't answer that.
    
    
    Regards,
    
    Andrew.D.Wicks

    Yes, the mail did arrive with status UNREAD
    
    What order takes place on reading??
    
    	Thanks,
    		Julie

    Julie,
    
    Change status from NOTED to READ (change from UNREAD done earlier)
    Refile message from INBOX to READ folder
    Decrement Unread Mail Count
    Dispatch Read Receipt 
    Perform Attached function
    
    Regards,
    
    Andrew.D.wicks 

    Apparently, the only thing that did not happen was 
    
    Refile message from INBOX to READ folder
    
    The message was nothing strange and only happened once.  However
    the user wants an answer as to why it happened.  Any ideas?
    
    Thanks

Refiling a message will involve deleting a DOCDB record, and writing a new 
one. Is it possible that, at that time, there wasn't enough space to extend 
the DOCDB?

g

    Or see the recent note that discusses a failure of the MAIL POSTFUN
    which results in the message remaining in the INBOX. (In the case
    listed it was that the TM system could not locate the meeting attendee
    on a reply to a meeting notice).
    
    Rick

    My customer is also convinced that they have read normal messages that
    do NOT get re-filed correctly to the READ folder, and instead remain in
    the INBOX. 
    
    Re-creating the situation is impossible, so nothing gets done... and
    then a week or so later the same thing happens again. 
    
    (Using ALL-IN-1 V3.0 + the .01A patch or whatever it is called.)
    
    Maybe there is enough happening to make it worth investigating??- maybe
    at DOCDB File Extend time??
    
    Customer thinks it might be:
    	while reading :- Gold I, choose another document (RN or similar),
    then Exit Screen out of this document.... and pressing Exit Screen once
    too many times leaves the document in the INBOX.
    But re-trying this causes no problems. 
    
    Cheers, Chris