Error

Value	Description
mailAbort	The Abort method was called. FATAL.
mailAddressInUse	Address already in use. Only one usage of each socket address (protocol/IP address/port) is normally permitted. This error occurs if an application attempts to bind() a socket to an IP address/port that has already been used for an existing socket, or a socket that wasn't closed properly, or one that is still in the process of closing. For server applications that need to bind() multiple sockets to the same port number, the ReuseAddress property can be used. FATAL.
mailAddressNotAvailable	Cannot assign requested address. The requested address is not valid in its context. Normally results from an attempt to bind() to an address that is not valid for the local machine. This may also result from connect(), sendto(), WSAConnect(), WSAJoinLeaf(), or WSASendTo() when the remote address or port is not valid for a remote machine (for example, address or port 0). FATAL.
mailAttachUuencode	Only (uuencoded) files may be attached to this non-MIME message.  Consider using MIME or putting all text in the Message.Data property area.
mailAuthentication	Authentication with the server failed. FATAL.
mailBadConfigItem	Invalid Configuration Item
mailBadDataType	Cannot create the requested data type or format.
mailBadRecipient	Mail Recipient Not Accepted.
mailBadSender	Sender address not accepted.
mailBlocked	User thread is blocking in another method. INFO.
mailCompile	An error occurred while compiling
mailConnected	A connection already exists
mailConnectionAborted	Software caused connection abort. An established connection was aborted by the software in your host machine, possibly due to a data transmission timeout or protocol error. FATAL.
mailConnectionRefused	Connection refused. No connection could be made because the target machine actively refused it. This usually results from trying to connect to a service that is inactive on the foreign host (for example,. one with no server application running). May also be generated by a Daemon that refuses a connection because its resources have been exhausted. FATAL.
mailConnectionReset	Connection reset by peer. An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, or the remote host used a "hard close" (see Abort method) on the remote socket. This error may also result if a connection was broken due to keep-alive activity detecting a failure while one or more operations are in progress. Operations that were in progress fail with ptNetworkReset. Subsequent operations fail with ptConnectionReset. FATAL.
mailDuplicateMessage	Message object already exists in collection.
mailError	Unexpected general error. FATAL.
mailFile	Error accessing local file storage. FATAL.
mailFileOpen	Unable to open file.
mailFileOperation	A file operation (such as size) had failed.
mailFileRead	A file read error has caused the operation to fail.
mailFileWrite	A file write error has occurred. Check disk free space.
mailFormatError	The server was unable to interpret the query.
mailHeader	Occurs when a proper termination (usually a CRLFCRLF) is not found in the header.
mailHostNotFound	Host not found. No such host is known. The name is not an official hostname or alias, or it cannot be found in the database(s) being queried. This error may also be returned for protocol and service queries, and means the specified name could not be found in the relevant database. FATAL.
mailHostUnreachable	Remote host does not exist
mailHttpInvalidUrl	The Url is unspecified or invalid.
mailInvalidMailAddress	The Email address specified was not valid.
mailInvalidMessageHeader	A recipient, from, and subject are needed for a valid message header.
mailInvalidParam1	Parameter #1 is invalid. INFO.
mailInvalidParam2	Parameter #2 is invalid. INFO.
mailInvalidParam3	Parameter #3 is invalid. INFO.
mailInvalidParam4	Parameter #4 is invalid. INFO.
mailInvalidProperty	Invalid property assignment. INFO.
mailInvDecodeType	An invalid or unsupported Decode Type was specified.
mailMsgObjRead	An error has occurred while reading data from the Message object. Verify the Message object contents.
mailNetworkDown	Network is down. A socket operation encountered a dead network. This could indicate a serious failure of the network system (for example,. the protocol stack that the Winsock DLL runs over), the network interface, or the local network itself. FATAL.
mailNetworkReset	Network dropped connection on reset. The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress. FATAL.
mailNetworkUnreachable	Network is unreachable. A socket operation was attempted to an unreachable network. This usually means the local software knows no route to reach the remote host. FATAL.
mailNoAccess	The user does not have the proper permissions
mailNoAuthMech	No authentication mechanism was found in the server's advertised capabilities, a secure connection may be required.
mailNoBufferSpace	No buffer space available. An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full. FATAL.
mailNoCertificate	There was an error in creating credentials.
mailNoData	Valid name, no data record of requested type. The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for. The usual example for this is a hostname -> address translation attempt which uses the DNS, and an MX record is returned but no A record - indicating the host itself exists but is not directly reachable. FATAL.
mailNoHeader	The message is invalid because the header was not found.
mailNoMemory	There was not enough memory available to complete the operation.
mailNoMessageHeader	The message does not contain a valid header.
mailNoRecipientsFound	The message header does not contain any (valid) recipients (To).
mailNoRecovery	This is a non-recoverable error. This indicates some sort of non-recoverable error occurred during a database lookup. This may be because the database files (for example, BSD-compatible HOSTS, SERVICES or PROTOCOLS files) could not be found, or a DNS (Domain Name Server) request was returned by the server with a severe error. FATAL.
mailNoSecurity	Secure communications is not available on this machine.
mailNotConnected	Socket is not connected. A request to send or receive data was disallowed because the socket is not connected or allocated. Any other type of operation might also return this error. FATAL.
mailNotFound	The name referred to in the query does not exist.
mailNotImplemented	The server does not support the request type of query.
mailNotInitialized	Network interface could not be initialized. FATAL.Host not found. No such host is known. The name is not an official hostname or alias, or it cannot be found in the database(s) being queried. This error may also be returned for protocol and service queries, and means the specified name could not be found in the relevant database. FATAL.
mailNotInSpoolMode	Method not allowed when spool mail mode is active.
mailNotMessageObject	The passed object is not a Message object.
mailNotPartObject	The operation requested requires an object of type Part.
mailOk	Ok
mailOnlyInSpoolMode	The DeSpool Method is only available when mail spooling is enabled.
mailOperationRefused	The server refused to perform the specified operation.
mailOptionNotSupported	The specified socket option is not supported by the system. INFO.
mailPartInStructure	The Part to Add already exists in this structure.
mailProtocol	Unexpected protocol error. FATAL.
mailServerError	There was a failure on the server.
mailSocks4DifferentUserID	The SOCKS4 server rejected the connection because the client program and identd report different user-ids
mailSocks4NoAcceptableMethods	The SOCKS5 server will not accept any of the requested methods
mailSocks4NoIdentd	The SOCKS4 server rejected the connection because it was unable to connect to identd on the client
mailSocks4RequestRejected	The SOCKS4 server rejected the connection (No reason given)
mailSocks5AddressTypeNotSupported	The SOCKS5 server reported that the address type is not supported
mailSocks5AuthFailed	The SOCKS5 server rejected the connection because authorization failed
mailSocks5CommandNotSupported	The SOCKS5 server reported that the command is not supported
mailSocks5ConnectionRefused	The SOCKS5 server reported that the host connection was refused
mailSocks5HostUnreachable	The SOCKS5 server reported that the host was unreachable
mailSocks5NetworkUnreachable	The SOCKS5 server reported that the network was unreachable
mailSocks5NoRuleSet	The SOCKS5 server reported that the connection was not allowed by the ruleset
mailSocks5ServerFailure	The SOCKS5 server reported a general failure
mailSocks5TTLExpired	The SOCKS5 server reported that the TTL has expired
mailTimeout	Timed out. A connection attempt failed because the connected party did not properly respond after a period of time, or an established connection failed because connected host has failed to respond. Alternatively, a blocked method failed to return within the period specified by the Timeout property. FATAL.
mailTryAgain	Non-authoritative host not found. This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server. A retry at some time later may be successful. FATAL.
mailUseMimeEncode	mailUseMimeEncoding must be Always, Never, or Smallest

Description

ErrorConstants description.

Some environments, such as IIS Active Server Pages, do not support event handling. In this case the application must rely on blocking and the Error object that is returned to the container when an error condition occurs.

Note  See the appropriate method and property description for a list of errors that may be generated.

Pop Object  | Pop Members