Ref: 17300009
Title: Cause and Fix for 3+Mail 1.3.2 Errors 493, 494, 613, and 607
date: 4/13/90

Copyright 3Com Corporation, 1991.  All rights reserved.

If you see errors 493, 494, 613, or 607, it is probably due to
corrupt data on the Mail server.

When an admin user performs a 3M DIRM command to access a Mail
server with corrupt data, an "Internal Error -493" is issued at the
netstation and "3Mail error -494" is logged in the STATUS.LOG file.
The exact message in the STATUS.LOG file is

 3Mail 9999 MA_MSERR MS error: p: 1, error:-494

The error ranges from "p: 1" to p: 4."  This error message is closely
followed in the STATUS.LOG file by the messages "3Mail error -607" and
"3Mail error -613."

"Internal Error -493" is produced when 3+Mail cannot correlate the
quantity or quality of unretrieved mail files with the 3+Mail statistics
used to keep track of those files.  It may appear after the mail information
for one particular user is listed, but that does not necessarily mean that
the problem is in that user's mail data.  The failure may have occurred in
deleting mail for a user prior to that user.  If the problem is due to data
corruption, it will persist after moving the \3Plus\3Mail\MBXS file and all
user mail subdirectories to another server.

To correct the problem that causes "Internal Error -493,"  have all active
users retrieve their mail, and make sure that all mail for inactive users is
deleted.

An "Internal Error -613" results from deleting a user from the 3+Name
service without first retrieving his outstanding mail messages.  As a
result, the 3+Name server cannot identify the user.

When deleting a user, first use 3M DELM to empty the user's 3+Mail server
inbox of all outstanding mail.  Then remove the user from the 3+Mail
server, which will update the NS_DOM file.  All 3+Mail messages must be
retrieved or deleted before removing a user from the 3+Name service in order
to keep the 3+Name service synchronized with the 3+Mail service.
