As many Adept Sysops realise, when a user logs on and has personal mail
waiting he must read that mail whilst logged on before the indexes clear.
Even if the user includes those personal messages in an off-line mail packet
he is still prompted that there are X number of personal messages to be read
until such time as s/he reads them whilst logged on.

After reading Adept's docs and noting that Steven has stated this bug won't be
fixed before the release of V1.0 I decided something had to be done.  My
solution is fairly elegant and works by simply deleting the personal mail
index after the user logs off.  It does not affect any other mail index
such as off-line mail LMR's but the down side is that if the user decides not
to read his mail whilst logged on then the index is lost and only *new*
personal messages are listed next time he calls (however, the actual messages
are not lost).  After careful thought I decided this was a much better option
than currently available and was unlikely to affect *any* of my users.  The
indexes affected are stored in adept's PERSONAL_MAIL directory.

Ok, so now the solution...  Copy the following text (between dotted lines)
into your ATEND.CMD file.  It doesn't seem to matter whereabouts in the file
you place this and I have mine after the section which handles Julie's Caller
script.  Please note this script only works for remote callers as I figured
most Sysops would logon locally and *actually* read any messages for them...

------------------------------------------------------------------------
CALL RxFuncAdd "SysLoadFuncs","REXXUTIL","SysLoadFuncs"
CALL SysLoadFuncs

ARG Line

UserName = AdeptGetVar(Line,1)
UserNameFile = 'Personal_Mail/' || UserName || ' '

IF STREAM(UserNameFile,'c', 'query exist')<>' ' THEN DO
    rc = SysFileDelete(UserNameFile)
END
-------------------------------------------------------------------------

And that's all there is to it...   This works for me, has been tested with
remote guinea pigs (oops, users) and has not caused any problems.  However, if
you run this as a *.cmd called whilst the user is still on line then it *will*
bring Adept down totally.  Only use this from within the ATEND.CMD file - you
have been warned...

Rgrds,

Jon

--- AdeptXBBS v0.96.00wb
 * Origin: Galaxy 10 - Plain sailing with OS/2 - (01621) 850032 (2:257/88)