SMTP-code

Omschrijving

SMTP Code 4.2.0: Timeout communication problem encountered during transmission

This is a Novell GroupWise SMTP error generated by the sending mail server when communications problems occur during the transmission of the actual message between the sending and receiving mail servers.

Typical causes include:

• The receiving mail server’s anti-spam firewall does not like the sending mail server’s IP address or HELO command
• A physical communication problem with the network, switches, routers, firewall or internet line

SMTP Code 4.2.1 : Service not available – the sending email program should try again later

The mail transfer service is unavailable because of a transient event.

Typical causes include:

• The receiving mail server is currently unavailable but may be available later
• Too many concurrent SMTP connections from the sending to the receiving mail server

SMTP Code 4.2.2 : The recipient’s mailbox is over its storage limit

Typical causes include:

• The recipients mailbox is over the storage limit
• The message delivery directory on the receiving mail server is currently over a size limit imposed by the Network Administrator
• The email being sent is larger than the incoming email size limit in operation at the receiving mail server

SMTP Code 4.3.1 : The recipient’s mail server is experiencing a Disk Full condition

The receiving mail server is experiencing a Disk Full error condition, or an Out of Memory error condition

SMTP Code 4.3.2 : The recipient’s Exchange Server incoming mail queue has been stopped

This is an SMTP status response specific to Microsoft Exchange Server and indicates that the receiving mail server’s incoming mail queue has been stopped and cannot deliver any email messages at this time

SMTP Code 4.4.1 : The recipient’s server is not responding

This code emanates from the sending mail server when the receiving mail server is not responding. The sending mail server will automatically try again a number of times

SMTP Code 4.4.2 : The connection was dropped during connection

The sending mail server started delivering the message but the connection was broken during transmission.

Typical causes include:

• Any type of network related issue that could result in a connection being broken between the sending and receiving mail servers

SMTP Code 4.4.6 : The maximum hop count was exceeded for the message

Typical causes include:

• The message is looping internally on the sending mail server
• The message is looping internally between two local mail servers
• The message is looping between the sending and receiving mail servers

SMTP Code 4.4.7 : Your outgoing message timed out

Your outgoing message timed out because of problems with the receiving mail server that objected to your message

Typical causes include:

• There is a problem with the message header such as too many recipients
• There is a protocol timeout between the sending and receiving mail servers

SMTP Code 4.4.9 : Bad routing configuration

This code indicates that a temporary routing error occurred or that a bad routing configuration exists between the sending and receiving mail servers

Typical causes include:

• A Simple Mail Transfer Protocol (SMTP) connector is configured to use DNS without a smart host and is also configured to use a non-SMTP address space such as an X.400 address space.
• A message was sent to a recipient who was identified as a member of a routing group that was deleted.

SMTP Code 4.5.0 : Requested action not taken – the mailbox was unavailable at the remote end

The receiving mail server could not access the mailbox to deliver the message.

Typical causes include:

• A process on the receiving mail server is tidying up the mailbox
• The remote mailbox could be corrupt
• The remote mailbox could be stored on another server that is currently offline
• The network connection went down whilst sending
• The receiving mail server does not want to accept mail from the sending mail server for some reason (IP address, blacklisting, etc…)

SMTP Code 4.5.1 : Requested action aborted – Local error in processing

The action has been aborted by the receiving mail server due to some local problem or error on that server.

Typical causes include:

• Overloading on the receiving mail server from too many messages
• Error in relaying the message from the sending mail server due to a transient failure, e.g. DNS, Greylisting
• The message has been rejected by the receiving mail server because of anti-spam measures

SMTP Code 4.5.2 : Requested action not taken – insufficient storage

The receiving mail server’s disk system has run out of storage space, so the action had to be cancelled.

SMTP Code 4.6.5 : Code Page unavailable on the recipient server

This is an Exchange Server-specific error code.

Typical causes include:

• Conversion of an inbound SMTP failed because the code page that is specified in the message is not installed on the receiving mail server.
• This delivery status notification contains only the original message headers.
• None of the original content is provided

SMTP Code 4.7.1 : This is a local error with the sending mail server and is often followed with "Please try again later"

Typical causes include:

• Anti-spam or virus scanning software on the sending mail server has encountered a bad automatic update from the manufacturer
• A lack of memory on the sending mail server
• A hard-disk related problem on the sending mail server