Error Messages

This table lists error and information messages the may appear on your i-Mail server log screen or system console. Use this guide to find out what the error means and how to resolve it.

System console messages are always preceded by the text - 'i-Mail: '

The remedy 'Refer other error codes to find the cause of the failure.' means that you will find errors earlier in the logs that have resulted in this error being shown.

Error	Cause	Remedy
i-Mail: Could not get server connection, exit code will assume 4.x for comatibility	NDS or bindery is either closed or corrupt	Fix the NDS or bindery
i-Mail: Trial period expired, shutting down engines	The i-Mail trial period has expired.	Purchase an i-Mail licence
i-Mail: System failure, shutting down dispatcher!	A critical error occured while i-Mail was reloading its configuration	Refer other error codes to find the cause of the shutdown.
i-Mail: Mail server has been forcibly shut down, some resources may not have been properly released.	During i-Mail shutdown 'CTRL-K' was pressed. Any resources that were waiting to be unloaded will be left to the system to clean up.	No action necessary
i-Mail: Error seeking to file start (filename)	During startup or system reload a file that i-Mail is using has become unusable due to volume dismount or physical disk error.	Ensure all i-Mail configuration files are healthy
i-Mail: filename initialization file has been corrupted	A line in an i-Mail config file is invalid. This can be due to disk corruption, manual modification of files, or the admin program failing during writing to disk.	Back up the configuration files, run admin to recreate the configuration files.
i-Mail: Error seeking into file filename	During startup or system reload a file that i-Mail is using has become unusable due to volume dismount or physical disk error.	Ensure all i-Mail configuration files are healthy
i-Mail: Failed to allocate memory while reading filename	During startup or system reload, the server could not provide sufficient memory for i-Mail to use.	Add more RAM to your server or unload NLMs that do not need to be running
i-Mail: Initialization Failed	During startup i-Mail had problems obtaining memory.	Add more RAM to your server or unload NLMs that do not need to be running
i-Mail: Interface Initialization Failed	During startup i-Mail had problems creating the user interface.	Check that your system has enough memory
i-Mail: Configuration Read Failed	During startup i-Mail had problems loading configuration information.	Refer other error codes to find the cause of the failure.
i-Mail: Could not open filename	During startup or system reload, the server could not find a required configuration file.	Make sure that the i-Mail directory and DAT files are in their correct place.
i-Mail: Failed to allocate memory while creating SMTP size indexes	During startup or system reload, the server could not provide sufficient memory for i-Mail to use.	Add more RAM to your server or unload NLMs that do not need to be running
i-Mail: Failed to start NetDB access engine	During startup i-Mail had problems starting a required process, normally due to lack of RAM.	Add more RAM to your server or unload NLMs that do not need to be running
i-Mail: Invalid registration key!	The imail.dat file contains a registration key that is incorrectly formatted	Re-run the admin program to fix the registration key
i-Mail: Invalid licence code!	The imail.dat file contains licence codes that are incorrectly formatted	Re-run the admin program to fix the licence codes
i-Mail: No global postmaster defined, use Admin to correct this problem	The imail.dat file does not contain a global postmaster.	The global postmaster needs to be entered on the general tab of the i-Mail admin program.
i-Mail: No primary domain defined, use Admin to correct this problem	The imail.dat file does not contain a primary domain.	The primary domain needs to be entered on the general tab of the i-Mail admin program.
i-Mail: Invalid licence key(1)	One of the licence codes is missing	Re-run the admin program to fix the licence codes
i-Mail: Invalid licence key(2)	The number of characters in one of the licence codes is wrong.	Re-run the admin program to fix the licence codes
i-Mail: Invalid licence key(3)	One or more of the licence codes has been entered incorrectly	Re-run the admin program to fix the licence codes. Ensure the licence key is entered exactly as shown, including case
i-Mail: Invalid licence key(4)	One or more of the licence codes has been entered incorrectly	Re-run the admin program to fix the licence codes. Ensure the licence key is entered exactly as shown, including case
i-Mail: Invalid licence key(5)	One or more of the licence codes has been entered incorrectly	Re-run the admin program to fix the licence codes. Ensure the licence key is entered exactly as shown, including case
i-Mail: Out of memory during licence check	During startup i-Mail had problems starting a required process, normally due to lack of RAM.	Add more RAM to your server or unload NLMs that do not need to be running
i-Mail: Could not check registration information, quitting	The licence codes are invalid	Re-run the setup program
i-Mail: Could not check registration information, quitting (1)	The licence codes are invalid	Re-run the setup program and ensure the system directly has been correctly entered
i-Mail: Please use the setup program distributed with this NLM	i-Mail files were copied rather that installed.	Re-run the setup program
i-Mail: Could not check registration information, please re-run setup	The i-Mail trial period has expired	Purchase an i-Mail licence
i-Mail: Trial period expired, quitting	The i-Mail trial period has expired	Purchase an i-Mail licence
i-Mail: Warning! Could not allocate memory for RestartBuffer	During system reload, the server could not provide sufficient memory for i-Mail to use.	Add more RAM to your server or unload NLMs that do not need to be running
i-Mail: Could not allocate memory for variable	The server could not provide i-Mail with enough memory for a required variable declaration.	Add more RAM to your server or unload NLMs that do not need to be running
i-Mail: Could not allocate memory for initialization	The server could not provide i-Mail with enough memory during startup.	Add more RAM to your server or unload NLMs that do not need to be running
i-Mail: Critical errors were reported during initialization, shutting down	One or more errors were reported that prevented i-Mail from starting up.	Refer other error codes to find the cause of the failure.
i-Mail: Memory failed for indexes, removing temporary index	The server could not provide i-Mail with enough memory for creating user indexes.	Add more RAM to your server or unload NLMs that do not need to be running
i-Mail: Failed to allocate memory for indexes	The server could not provide i-Mail with enough memory for creating user indexes.	Add more RAM to your server or unload NLMs that do not need to be running
i-Mail: Memory failure while compacting indexes	The server could not provide i-Mail with enough memory for creating user indexes.	Add more RAM to your server or unload NLMs that do not need to be running
Recipient name exceeds allowable limit	A message has been delivered with an e-mail address that exceeds 512 characters	Check that e-mail addresses in your system do not exceed 512 characters. Also check the imail spool directory for any messages that have been downloaded which may contain extra long addresses
No recipient in address field	An e-mail address has been provided that is blank	Check clients reply-to address is filled in
Recipient has unbalanced bracket sets	A client or message that has been downloaded has an address that has an extra < or >	Check that e-mail clients on your system do not contain these characters. Also check the imail spool directory for any messages that have been downloaded which may contain these characters
Recipient invalid	A client has an e-mail address that does not have the domain	Ensure clients e-mail and reply-to addresses are filled in correctly
'Failed to allocate memory' messages	The server could not provide i-Mail with enough memory.	Add more RAM to your server or unload NLMs that do not need to be running
Recipient name corrupted by rules	One or more replacement rules in admin has turned a valid e-mail address into a non-valid address.	Check and test your replacement rules
GetRecipientList Failed	Their was either a memory failure or a message downloaded from the internet has corrupt data.	Refer other error codes to find the cause of the failure.
Failed to get file details for filename	While scanning a file for its time and size information an error was reported that the file was not available.	Check that the server has rights to the volume and that the volume is mounted
No files have expired in safe directory	This is informational only	No action necessary
Failed to reset to beginning of message file	A file access failure occured during message scanning operation. The file has become damaged or unavailable while it was being read.	Check that the volume is mounted and that it is reliable with vrepair
Read from message file failed	A file access failure occured during message scanning operation. The file has become damaged or unavailable while it was being read.	Check that the volume is mounted and that it is reliable with vrepair
Reached message body without finding sender	A message was delivered that does not have a sender.	No action necessary, i-Mail will replace the sender name with the postmaster
File access failed during function	A file access failure occured during message scanning operation. The file has become damaged or unavailable while it was being read.	Check that the volume is mounted and that it is reliable with vrepair
Login name or password not set for auto print	The auto print function was started but no username or password has been defined	Enter a valid user and password for auto print in the printing tab of admin
Error found in auto queue name while attempting to print	A '/' character was not found in the queue name.	Enter the auto print queue in the format server/queue in the accounts tab of admin.
Error setting print message file to start	A file access failure occured during message scanning operation. The file has become damaged or unavailable while it was being read.	Check that the volume is mounted and that it is reliable with vrepair
No sender located for printing	A message was delivered that does not have a sender.	This will not affect the auto print
No message date found for printing	A message was delivered that does not have a date.	This will not affect the auto print
No subject line located for printing	A message was delivered that does not have a subject.	This will not affect the auto print
No message body found for printing	A message was delivered that does not have a body.	This will not affect the auto print
Create print job failed with code x	i-Mail could not create a file in the designated print queue.	The error code is the 'Base 10' NetWare error code. Look up the 'Base 16' code in the Novell manuals or contact Digital Integration
Object ID map failed with code x during print	i-Mail could not get the ID number of the print queue object.	Run DSRepair and see if there are any object ID problems. The error code is the 'Base 10' NetWare error code. Look up the 'Base 16' code in the Novell manuals or contact Digital Integration
Authenticate connection handle failed during auto print (x)	i-Mail could not authenticate the user supplied for logging in to print.	Check the user and password supplied for auto print and that the user has rights to the print queue
Auto print to server servername failed	i-Mail could not authenticate the user supplied for logging in to print.	Check the user and password supplied for auto print and that the user has rights to the print queue
Login failed for auto print, check printing setup in admin (x)	i-Mail could not authenticate the user supplied for logging in to print.	Check the user and password supplied for auto print and that the user has rights to the print queue
Context change failed, check printing setup in admin (x)	The context supplied for auto print is either inaccessible on this server or not correct.	Check the NDS context supplied for auto print The error code is the 'Base 10' NetWare error code. Look up the 'Base 16' code in the Novell manuals or contact Digital Integration
Failed to create context handle during auto print (x)	The auto print function could not get access to NDS.	Run DSRepair and check that NDS is open The error code is the 'Base 10' NetWare error code. Look up the 'Base 16' code in the Novell manuals or contact Digital Integration
Print job has been aborted	An error occurred that prevented i-Mail from printing.	Refer other error codes to find the cause of the failure.
Destination host undefined, check config	When connecting to an internet host i-Mail was supplied with a blank hostname or IP address.	Check that the outbound SMTP address is correct in admin
NetDB functions inactive, DNS call failed	The i-Mail NetDB access was disabled due to startup problems and i-Mail cannot resolve DNS names.	Check logs for any startup errors and reload i-Mail
Retrying DNS connection (attempt x) Retrying IP address connection (attempt x)	i-Mail failed to connect to an internet host and is retrying the connection.	No action necessary
Host name resolution failed for name	i-Mail could not convert an internet host name to an IP address.	Check that the server can 'Ping' the host. If not, and the host is definitely correct, restart the server to reset the NetDB tables
Failed to open socket with name	i-Mail either could not connect to an internet host or the host does not provide the services that i-Mail was trying to use	Check that the server can 'Ping' the host. If not, and the host is definitely correct, restart the server to reset the NetDB tables If the host can be pinged then ensure the appropriate services (POP or SMTP) are actually available. You may need to contact your service provider. Also check the TCP ports configured for access in i-Mail admin. the default POP port is 110 and the default SMTP port is 25
ip_address is a malformed address	An IP address provided in admin is incorrect	Check all IP addresses in i-Mail admin have been entered correctly for POP collectors, SMTP connectors and remote domains
Failed to connect socket to name	i-Mail was unable to establish a connection to the named host.	Check that the host can be pinged Refer other error codes to find the cause of the failure.
Warning, could not write to unsubscribe update file Warning, could not write to subscribe update file	A file access failure occured during updating a subscription list. The file has become damaged or unavailable while it was being used.	Check that the volume is mounted and that it is reliable with vrepair
Auto responder failed to create file	A file access failure occured while creating a response message.	Check that the volume is mounted and that it is reliable with vrepair
Auto responder activated with no responder in list! Responder activated was: list name	An auto responder is not valid	Check the auto responder in admin
Client exceeded conversation buffer size, closing link	A connected client has sent too more data than is acceptable for the current operation.	Check any clients that are having connection problems
Failed to open audit tracking file	A file access failure occured while creating a new audit log.	Check that the volume is mounted and that it is reliable with vrepair
Backup file copy system using 256 byte copy buffer	Memory is low on the server and the slow backup copy system has been used.	Add RAM to your server
Freeing hung POP collector [x]	A POP collector has not received any data for more than the configured timeout period.	Check the reliabilty of your internet link or increase the timeout value
Freeing hung SMTP connector [x]	As SMTP client has not sent any data for more than the configured timeout period.	Check the reliabilty of your internet link or increase the timeout value
Freeing hung client connector [x]	A POP or SMTP client has not sent any data for more than the configured timeout period.	Check any clients that are having connection problems or increase the timeout value
Freeing hung MX connector [x]	An MX record lookup has not received any data for more than the configured timeout period.	Check the reliabilty of your internet link or increase the timeout value
System failure, shutting down dispatcher & engines!	A critical error was reported during system reconfiguration which has forced i-Mail to shut down to prevent data loss.	Refer other error codes to find the cause of the failure.
iManager client password failed	An iManager client entered their password incorrectly.	Passwords for iManager are case sensitive. Re-enter the password and try again
iManager failed to authenticate user	The TCP/IP link between iManager and i-Mail failed during authentication.	Check the reliability of the TCP/IP link.
A password is required for remote management	No password has been entered in the general tab of admin for iManager, but the service is enabled	Enter a password for remote management or turn the service off
Retrying request to listen on socket for service type clients (Service types are: iManager, SMTP, POP)	i-Mail is waiting for the specified port to become available on the address specified for this service.	Check for any other software configured on the same IP address and port that this service is configured to use. If so, change the port number. Otherwise wait for the service to become available or restart the server
Failed to allocate socket for service type server process (Service types are: iManager, SMTP, POP)	The address or port was not available for this service to use.	Change the IP address or port for this service to use, or try restarting the server.
Service type local address is malformed (Service types are: iManager, SMTP, POP)	The IP address provided for this service is invalid	Provide the correct IP address
Retrying bind to socket for service (Service types are: iManager, SMTP, POP)	i-Mail is waiting for the specified port to become available on the address specified for this service.	Check for any other software configured on the same IP address and port that this service is configured to use. If so, change the port number. Otherwise wait for the service to become available or restart the server
Failed to bind to service type server socket (Service types are: iManager, SMTP, POP)	The address or port was not available for this service to use.	Change the IP address or port for this service to use, or try restarting the server.
Failed to listen on service type server socket (Service types are: iManager, SMTP, POP)	The address or port was not available for this service to use.	Change the IP address or port for this service to use, or try restarting the server.
Service type server is not able to accept connections (Service types are: iManager, SMTP, POP)	A connection to the server was rejected.	The server is either currently overloaded with TCP/IP connections or more that the maximum configured clients are currently connected
Failed to start service type thread (Service types are: iManager, SMTP, POP)	The service for a client process failed to start, most likely due to low memory.	Add more RAM to the server
Log file is not active No log file to export	An attempt was made to export the log without an active log file.	Configure and enable logging with i-Mail admin and reload the i-Mail NLM
Could not open log file for reading	A file access failure occured while reading the log file.	Check that the volume is mounted and that it is reliable with vrepair
Could not open export log file for writing	A file access failure occured while opening the export log file.	Check that the volume is mounted and that it is reliable with vrepair
Failed to reopen log file	After exporting the log file, a file access failure occured while reopening the log file.	Check that the volume is mounted and that it is reliable with vrepair
Excess length line detected in recipient list	An MSR or MSL file has been corrupted.	Check that the volume is mounted and that it is reliable with vrepair
Non address line found in recipient file	An MSR or MSL file has been corrupted.	Check that the volume is mounted and that it is reliable with vrepair
File read error while checking recipient file	A file access failure occured while reading an MSR or MSL file.	Check that the volume is mounted and that it is reliable with vrepair
ManagerCC address is invalid	The ManagerCC e-mail address entered in admin is invalid.	Fix the e-mail address
Warning: ManagerCC address must be on local or defined domain.	The ManagerCC e-mail address entered in admin is not a local domain.	Change the ManagerCC address to be local
ManagerCC failed to find user in local system	The ManagerCC e-mail address entered in admin does not exist.	Change the ManagerCC address to a valid e-mail address for your system
ManagerCC failed to create message file	A file access failure occured while creating the message for the ManagerCC address	Check that the volume is mounted and that it is reliable with vrepair
ManagerCC address type unidentified?	The ManagerCC e-mail address entered in admin does not exist.	Change the ManagerCC address to a valid e-mail address for your system
Invalid subscribe entry detected, check auto responders Invalid unsubscribe entry detected, check auto responders	A subscription lists is defined with no corresponding AutoCC entry.	If an AutoCC name has been removed or renamed, subscription lists need to be updated
Warning: failed to create LST file	A file access failure occured while creating a message flag.	Check that the volume is mounted and that it is reliable with vrepair
-ERR Memory or mailbox failure detected, quitting session	A mailbox was not available when a user tried to collect mail	Check that the users mailbox exists in the users directory
Communication failed with client	A mail client disconnected during a mail transaction.	Normally this is not a problem if a user has pressed cancel while retrieving mail, otherwise check the client configuration and/or try a new network card in the offending client PC
Read from disk failed during SendMessage	A file access failure occured while sending a message to the internet or another mail server.	Check that the volume is mounted and that it is reliable with vrepair
Write to socket failed during SendMessage	The TCP/IP link went down during sending a message to the internet or another mail server.	Check your internet link reliability
Warning: Failed to create safe file	A copy of downloaded mail could not be made either because the disk is not available or the i-Mail safe folder does not exist.	Ensure the safe folder exists in the i-Mail directory
[x] Host does not support TOP, attempting full download	A POP collector has been configured to skip large files, but to download their headers and the ISP does not support the TOP command which is required for this operation.	Ask your ISP if they can support this command or change your ISP
[x] Message download failed, error reported on RETR command	The ISP responded with an error command when i-Mail tried to retrieve a message from the internet.	Contact your ISP if the problem persists
[x] - POP Collect failed due to connection time out	During mail collection i-Mail did not receive data from the POP server for the specified timeout period.	Check the reliabilty of your internet link or increase the timeout value
Warning! Malformed IP address in SMTP size exception	An SMTP size exception configured in the POP/SMTP connectors tab of admin has an invalid IP address entry.	Fix the IP address
User or Password not set for pop collector, skipping	A POP collector has been configured without a password or user, both of these must be set. i-Mail does not support POP collection from an ISP without a password.	Set the user name and password for the POP collector
Deleted dead message: filename	During startup, i-Mail cleans up any files that were incomplete in the event of the server crashing or being reset during mail transactions.	No action necessary
[x] - Client has stopped sending data, closing session	While a client was sending data to i-Mail no data was received for the specified timeout period.	Check the reliabilty of your internet link or increase the timeout value
[x] - 1:File failure while writing message	The file that i-Mail was writing to while receiving data from a client is no longer accessible	Check that the volume is mounted and that it is reliable with vrepair
[x] - Error occurred while receiving data	While i-Mail was receiving mail from a client, the client disconnected.	Normally this is not a problem if a user has pressed cancel while sending mail, otherwise check the client configuration and/or try a new network card in the offending client PC
Illegal notify options found during return notification	A client has sent unknown return notification parameters with a message.	Check that your mail clients support the standard DSN delivery format
Return notification for local user failed - no local account	A client requested return notification to an invalid mailbox.	Check the mail client return notification options
Failed to create return notification message for local user	When creating a return notification message i-Mail could not access the file system.	Check that the volume is mounted and that it is reliable with vrepair
Failed to create return notification message for named remote domain	When creating a return notification message i-Mail could not access the file system.	Check that the volume is mounted and that it is reliable with vrepair
Failed to create return notification message for unnamed remote domain	When creating a return notification message i-Mail could not access the file system.	Check that the volume is mounted and that it is reliable with vrepair
Return recipient is invalid, notify message not sent	A client requested return notification to an invalid mailbox.	Check the mail client return notification options
Critical Error! Failed to read from disk during return notify	When creating a return notification message i-Mail could not access the file system.	Check that the volume is mounted and that it is reliable with vrepair
Mail failed, returning to sender	A message was undeliverable and is being returned to the sender.	If this occurs on all messages, check your account with your ISP and that your server is connecting properly to the internet. If the error is an isolated incident, check the recipient name for the message.
Failed to open original message list to return mail to sender	When attempting to return mail, the recipient list file no longer exists for i-Mail to determine who to send the message to.	Check that the volume is mounted and that it is reliable with vrepair
Failed to send message file, requeing	A message could not be delivered for some reason.	Refer other error codes to find the cause of the failure.
UID Lists have become unstable due to memory problems Shut down mail server as soon as possible and remedy	i-Mail is trying to use UID to leave messages at the ISP, however memory has become low and the tables cannot be stored.	Add RAM to the server
User attempted to send mail with size greater than allowed	A user tried to send a message that exceeds the maximum limit set in admin	No action necessary if this was intended
Disk failure storing message list for ETRN queue	The file system was not available when i-Mail tried to write a file.	Check that the volume is mounted and that it is reliable with vrepair
Client disconnected, terminating session	A client connected to the SMTP server but disconnected before sending any data.	Normally this is not a problem if a user has pressed cancel while sending mail, otherwise check the client configuration and/or try a new network card in the offending client PC
Failed to replicate incoming address, recipients will be affected	The server ran out of memory while i-Mail was replicating mail addresses.	Add RAM to the server
No members found in group, this recipient will return or fail	Mail was sent to a NetWare group that has no members.	No action necessary if this was intended
Failed to log in for user lookup, access will be denied	Either the user or password supplied in the UserLink tab of admin is invalid.	Provide correct details for i-Mail to log in to the server to access NDS information
Failed to create context handle during group replication	i-Mail could not get access to NDS.	Ensure NDS is running and that it is reliable with DSRepair
Originator invalid, check outbox files for corruption (.MSR & .MSL)	When attempting to send a message, i-Mail was unable to interpret the recipient list file, probably due to corruption.	Delete the offending MSR or MSL file and the associated MSG file. Check that the volume is reliable with vrepair
SMTP queue full, will re-process next run	While sending data, i-Mail had too many messages to send on the given internet link.	No immediate action necessary. The internet link speed may need to be increased if this problem persists.
Connection to host host name failed for host	When using direct connection to SMTP hosts i-Mail could not contact a host in the list provided by DNS, it will try the next one.	No action necessary
Cannot use SMTP host for ETRN, quitting session Host does not support ETRN, quitting session	An ETRN server defined does not provide ETRN services.	Contact your ISP to find out the correct ETRN host name
Message is too large for remote system	A message being sent to the internet is larger than the ISP will accept	Contact your ISP about size limitations
Send message failed, re-queueing for next processing run	While sending data the internet link stopped	Check the reliability of the internet link
(???) Remote SMTP host responded with bad syntax	The internet SMTP server that i-Mail is communicating with does not support a command that i-Mail sent.	If this happens once, the cause is probably a freak incident and no action is required. If the problem persists, contact your ISP and get them to examine their logs to determine the problem
Corrupt MSR/MSL file detected, saving message in BadMsgs folder	While attempting to send a message to the internet i-Mail found corruption in a recipient list file.	Resend the message Check that the volume is reliable with vrepair
Corrupt message file detected, moving to BadMsg folder (x)	While attempting to parse a message from the internet i-Mail found corruption.	Read the message from the badmsgs folder in a text editor such as notepad.
Warning: Bad message create failed, message may be lost! Failure copying file to bad message folder	i-Mail could not copy a message to the bad messages folder.	Check that the badmsgs folder exists and is accessible
EOF prematurely detected	While attempting to send a message to the internet i-Mail found corruption in a recipient list file.	Resend the message Check that the volume is reliable with vrepair
Warning: Mail forwarding configured to same maildrop!	A user account has been set to forward mail to itself.	Change the forward to address for the account
Failed to print message, disk or RAM failure	Printing failed for some reason.	Refer other error codes to find the cause of the failure.
Unable to add job to queue, check queue status	Printing failed for some reason.	Refer other error codes to find the cause of the failure.
Unable to connect to specified print queue, check configuration	Printing failed for some reason.	Refer other error codes to find the cause of the failure.
Warning: Forwarded user not found (name)	Forwarding has been set to a local user, but the user does not exist.	Change the forward to address
An error occurred while parsing a message in the spool queue	A problem occurred while a message downloaded from the internet was being interpreted.	Refer other error codes to find the cause of the failure.
Discarding duplicate message	Multiple messages have been downloaded from the internet which contain the same data. i-Mail discards duplicates if the dedupe option is on in the advanced tab of admin.	No action necessary
No users survived message parsing	No valid users were found in a message that was downloaded from the internet and it will be sent to the Postmaster or discarded as defined in admin.	No action necessary
Alias postmaster not found	i-Mail needed to find a PostMaster address to deliver mail and did not find one in the alias lists.	Create an alias PostMaster if i-Mail is being used as a mail server (as opposed to a router for GroupWise)
Failed to create remote recipient list for PostMaster Failed to queue message for remote PostMaster Failed to queue message for PostMaster Failed to create message file for remote PostMaster Failed to create message file for PostMaster	i-Mail could not access the file system when creating a message for the remote PostMaster.	Check that the volume is mounted and that it is reliable with vrepair
No PostMaster defined, moving message to bad message folder	A message could not be delivered to the PostMaster because none is defined.	Define a PostMaster alias or for remote domains set the postmaster on the general tab of admin
Failure copying file to PostMaster mailbox	i-Mail could not copy a message to the PostMaster mailbox .	Check that the PostMasters mailbox exists and is accessible
PostMaster mailbox storage failed, storing in BadMsgs folder	i-Mail could not copy a message to the PostMaster mailbox because it was not found and will store it in the badmsgs folder instead.	Check that the PostMasters mailbox exists and is accessible
Warning! Malformed IP address in POP security entry Warning! Malformed IP address in SMTP security entry Warning! Malformed IP address in Anti-Relay security entry	An IP address in the security tables is invalid.	Fix the IP addresses in admin
Invalid greeting from POP host, contact ISP if this continues	The first response from a server that i-Mail is connecting to is invalid. This may be due to an incorrect port setup or a problem at the ISP.	Check the ports in the TCP ports tab are correct, or contact your ISP.
Error while sending USER command	Your account at the ISP probably does not exist.	Contact your ISP.
Error while sending PASS command	You have entered an invalid password for connecting to your ISP POP server.	Reenter the password. Passwords are case sensitive. If this does not solve the problem, contact your ISP.
Error while sending STAT command	The POP server that i-Mail is connecting to does not understand this command.	Contact your ISP.
Host does not support LAST	A POP collector has been configured to use the LAST command but it is unsupported by the ISP.	Contact your ISP.
UID List is corrupt for host, resetting	Memory failure has cuased corruption in the UID lists.	Add more RAM to your server
Remote POP host does not support UIDL, disabling Remote POP host did not respond to UIDL command	The POP server that i-Mail is connecting to does not understand this command and i-Mail has been configured to leave mail at the server.	Contact your ISP.
Error while sending LIST command	The POP server that i-Mail is connecting to does not understand this command.	Contact your ISP.
POP server reported zero byte message, contact your ISP!	The ISP POP server reported that it has a message that has no size. i-Mail will not download 0 byte messages.	Contact your ISP.
Error opening temporary spool file	i-Mail could not create a file to download mail from the ISP.	Check that the volume is mounted and that it is reliable with vrepair
Removing partial message filename	Mail collection was interrupted and i-Mail is removing the portion of the message that was downloaded.	No action necessary
Error while sending NOOP command	The POP server that i-Mail is connecting to does not understand this command.	No action necessary
Error while sending DELE command	The POP server that i-Mail is connecting to does not understand this command.	Contact your ISP.
UID cleanup was avoided, freeing unused lists	A problem occurred during mail collection and the UID list may have become corrupt so it must be refreshed.	Refer other error codes to find the cause of the failure.
Some inconsistencies were corrected in system message	A system message supplied has some non- standard text in it. i-Mail automatically reformats the inconsistencies.	No action necessary
No DNS servers configured, MX lookup disabled	Send directly to host has been configured in admin but no DNS servers have been provided.	Enter valid DNS servers to the TCP Ports tab in admin
DNS server IP address is malformed	A supplied DNS IP address is invalid.	Fix the IP address
Failed to create socket for MX lookup to IP address Failed to connect to IP address for MX lookup MX lookup failed, could not connect to any configured DNS servers	A connection to the DNS server could not be established.	Check the IP addresses of the DNS servers are valid. Also check the reliability of your internet links.
MX lookup failed, domain name is illegal	A lookup was requested for an invalid domain.	Check the recipient address
Error occured while sending request to DNS server Error occured while receiving response from DNS server	The TCP/IP link stopped during an MX record lookup	Check the reliability of your internet links.
Unknown user user name attempted remote update	A user who does not have an account on the server attempted to update account details.	No action necessary
User user name attempted remote update but was rejected	A user who does not have the priveleged to update their account details attempted to update their account.	No action necessary
User user name attempted remote update but failed on password	A user attempted to update their account details but got their password wrong.	No action necessary
User %s selected invalid remote update option	A user attempted to update their account details but provided an option that is not valid.	Provide the user with the valid remote options
System update failed, system may be unstable	During system update a critical disk or memory failure occurred.	Refer other error codes to find the cause of the failure.
Sender of the e-mail was malformed, external recipients not replicated	An external activation of an AutoCC list was received, however the sender could not be interpreted so i-Mail will not allow replication to external addresses.	No action necessary
Failed to create redirect message recipient list Failed to create redirect message	A new message could not be created during AutoCC processing.	Check that the volume is mounted and that it is reliable with vrepair
Discarding unknown recipient e-mail address	During message parsing, e-mail addresses found that are not for the local system are discarded.	No action necessary
Domain is configured for unknown forwarding with no address!	A remote domain has been configured so that mail for unknown recipients will be forwarded but no name has been provided.	Supply a name for unknown recipient forwarding
Message file locked by filename	i-Mail is scanning the directories for mail to be processed, but this file is already being processed. This information shows in diagnostic logging mode only.	No action necessary
Mailscan failed login to server 'server name' Mailscan could not connect to server 'server name'	Mailscan has been configured to scan directories on another server but cannot log in.	Check the username and password for the mailscan entry and that the server is accessible from the i-Mail server by typing 'display servers'
Caution: Outbox directory changed during scanning	Files that i-Mail had listed in the outbox directory were removed by some other process.	Ensure no other programs interfere with the operation of i-Mail.
An error occurred while setting name space No useful long name spaces found, will use DOS names	i-Mail is informing that it will not use the long, NFS or OS/2 name space	No action necessary
NetNotify message was not sent, user is not logged in to this server	An attempt was made to notify a user that mail has arrived, however the user is not currently logged in to this server.	No action necessary
UserLink access denied to username UserLink user username denied access	A user attempted to access mail but was rejected due to restrictions in force.	No action necessary
Failed to create welcome message for username	A message could not be created for a new user due to problems with the file system.	Check that the volume is mounted and that it is reliable with vrepair
Could not create UserLink data file	A control file could not be created for a new user due to problems with the file system.	Check that the volume is mounted and that it is reliable with vrepair
Cannot create UserLink user, would exceed licence count	The UserLink count and the user count are at the licence limit.	Either remove users, remove entries from the UserLink registered table or purchase a higher licence count.
No mail store found for username	A user in the system has no mail store configured.	Ensure the user has a mail store entered in admin.
Directory username not found	A user exists in the i-Mail system but their mailbox does not.	Ensure the users mail store exists in the users directory
Dir failed for directory	i-Mail attempted to list the files in a directory but NetWare returned an error.	Check that the directory exists. Also check that the volume is mounted and that it is reliable with vrepair
Skipping zero byte message file	A zero byte file was found in a users mail directory.	Delete the message
Invalid queue format in AutoQueue entry, discarding entry	An auto print queue was invalid and will not be used.	Re-enter the print queue name properly.
Licence count exceeded, discarding name	While loading the users into the on-line database the user licence count was exceeded. Any extra accounts are discarded.	Remove some accounts or purchase a licence for more users.
This version of i-MailDS does not support unlimited user forwarding	The domains tab has a remote domain that is not set to 'Lookup recipients' and the licence count is not unlimited. This blind forwarding is only available in the unlimited user version of i-Mail.	Either turn on the 'Lookup recipients' for the remote domain or purchase an unlimited user licence.
Removing empty message file (x)	During startup i-Mail scans user directories for zero byte files and deletes them.	No action necessary
Failed to log in for user lookup, access will be denied	The user name or password supplied for UserLink to work is invalid.	Provide the correct user account details in the UserLink tab of admin
UserLink access user has not been configured	Either the user name or password has not been supplied for UserLink to work.	Provide the correct user account details in the UserLink tab of admin
Failed get NDS context handle during user lookup	i-Mail could not access NDS.	Ensure NDS is open and run DSRepair.
Failed change to context	The context supplied in the UserLink tab of admin cannot be accessed.	Check the UserLink context is correct. Run DSRepair.
NWDSAllocBuf returned x	An NDS call failed	Run DSRepair Check that your server has enough memory
Context notify cannot proceed without user, password and server	One of the details required for context sensitive broadcast notify has not been provided	Provide the details for context sensitive notify in the notify tab of admin
Could not login for context notify, check user and password NDS login details are not correct, userlink updates not allowed Could not log user name in to Directory Services NDS login details are not correct, userlink requests will fail	One of the details required for context sensitive broadcast notify is invalid	Provide the correct details for context sensitive notify in the notify tab of admin
Could not set context for notify, check notify settings	i-Mail could not access NDS.	Ensure NDS is open and run DSRepair.
Failed get NDS context handle during password check	i-Mail could not access NDS.	Ensure NDS is open and run DSRepair.
Could not set context context Check configuration for domain domain name	The context for the independant domain could not be set.	Check the context for the domain is available on this server Run DSRepair
Could not set context context Check UserLink default NDS context	The default context for UserLink could not be set.	Check the default context specified in the UserLink tab is available on this server Run DSRepair
*Failed get NDS context handle during password check	i-Mail could not access NDS.	Ensure NDS is open and run DSRepair.
i-Mail will not modify NDS attributes without valid user AND password	Either a username or password was not supplied in the UserLink tab for NDS access.	Provide the correct user account details in the UserLink tab of admin
Error occured while waiting for POP message	During POP mail collection the service providers POP server did not send a <cr><lf> pair to indicate that the message was ready to be received.	Contact your ISP and ask them to check the state of your POP mailbox
POP server did not send line feed?	The POP server that i-Mail is downloading from is supposed to send a carriage return and a line feed after each transaction. In this case the POP server only send the carriage return.	Contact your ISP and ask them to check the state of your POP mailbox
Rule converted recipient to nothing, resetting recipient	A recipient replacement rule converted an e-mail address into an invalid e-mail address.	Check the recipient rules and/or the message that caused the error. A user may have entered an e-mail address that is invalid.
Rule removed name, resetting recipient	A recipient replacement rule converted an e-mail address into an invalid e-mail address.	Check the recipient rules and/or the message that caused the error. A user may have entered an e-mail address that is invalid.
Rule removed domain, resetting recipient	A recipient replacement rule converted an e-mail address into an invalid e-mail address.	Check the recipient rules and/or the message that caused the error. A user may have entered an e-mail address that is invalid.