GUI Error - Email SMTP

ERROR

420

Timeout communication problem encountered during transmission. This is a Novell GroupWise SMTP error

• If you experience 420 errors only with specific recipient then it is quite likely that the recipient’s anti-spam firewall does not like your server.
• If you experience too many 420 errors with all email communications, then you have a physical communication problem somewhere.

421

<Server name> Service not available – the sending email program should try again later

• “Mail Server” in this case can be any of the mail servers on the message’s route – the sending server (your server), the ISP SMTP server, or the recipient’s mail server.
• The Mail transfer service is unavailable because of a transient event. SMTP reply 421 can be caused by many things but generally indicates that the mail server which returns this status code is currently unavailable but may be available later.
• Clearly, if you repeatedly receive an SMTP status 421 then the problem is no longer of a transient nature and you need to investigate or inform the relevant network administrator, ISP tech support, or the recipient.

422

The recipient’s mailbox is over its storage limit

• Either the recipient’s mailbox is over its storage limit or the message delivery directory (folder) on the recipient’s mail server is currently over a size limit imposed by the Network Administrator

431

The recipient’s mail server is experiencing a Disk Full condition

• The recipient’s mail server is experiencing a Disk Full error condition, or an Out of Memory (too many file handles) error condition (Microsoft Exchange).

432

The recipient’s Exchange Server incoming mail queue has been stopped

• This is an SMTP status response specific to Microsoft Exchange Server. It indicates that the recipient’s mail queue on their Exchange Server has been stopped (frozen), probably while the Network Administrator troubleshoots some problem.

441

The recipient’s server is not responding

• This is an error emanating from your server indicating that the recipient’s server is not responding. Your server will automatically try again a number of times – how many depends on how your server has been configured.

442

The connection was dropped during transmission.

• Your server started delivering the message but the connection was broken during transmission.

446

The maximum hop count was exceeded for the message

• The maximum hop count was exceeded for your message. The most likely cause of this error status code is that your message is looping internally on your server, internally between two of your organisation’s servers, or, sometimes, looping between your server and the recipient’s server.

447

Your outgoing message timed out.

• Your outgoing message timed out because of problems with the receiving server who objected to your message. Typically there is a problem with the message header (such as too many recipients, in most cases, or a protocol timeout between the two servers).

449

Routing error

• This is a Microsoft Exchange Server specific error code.

450

Requested action not taken – The mailbox was unavailable at the remote end.

• The server could not access the mailbox to deliver the message.

451

Requested action aborted – Local error in processing. / <IP_Address> has recently sent spam

• The action has been aborted by the ISP’s server. “Local” refers to the ISP’s server. This error is usually due to overloading at the ISP from too many messages or transient failures.

500

Syntax error, command unrecognised

• The last command sent by your server was not recognized as a valid SMTP or ESMTP command, or is not formatted in the way the server expected. This includes situations where the command is too long.

501

Syntax error in parameters or arguments

• The command was correct and recognised, but the parameters (the arguments, e.g. email address) were not valid.
• In the vast majority of cases SMTP Error 501 is caused by invalid email addresses.

502

Command not implemented

• The command or function issued by your mail server is valid but has not been activated (typically, it is not supported on this particular server).

503

Bad sequence of commands / This mail server requires authentication

• This error, particularly if repeated, can be indicative of communications problems, such as a noisy line, intermittent drops in network connections, etc...

504

Command parameter not implemented

• The command and parameter are both valid, but the parameter is not implemented on the ISP server, or an additional parameter or action is missing.

504 5.5.2 : Sender address rejected: need fully-qualified address

Put your Login/Username in the From field in Email Settings (example):

510

Bad Email Address

• Bad email address. This status code is generated by the sender’s local mail server.
• If the email was addressed internally, then it means that the addressee, as written in the email’s TO, CC, or BCC fields, does not exist in your organization’s email system.
• If the email was addressed externally, then the recipient’s email address was misspelt.

521

<domain> does not accept mail

530

Access denied

535

Email Username and Password not accepted

• Enter correct Username and Password for your Email in SETTINGS.

550

Requested action not taken: mailbox unavailable

551

User not local; please try <forward-path>

• If neither the sending mail address nor the recipient’s address are locally hosted by the server, then the ISP’s servers may refuse to relay the message on.

552

Requested mail action aborted: exceeded storage allocation

• The recipient’s mailbox has reached its maximum allowed size (this is often accompanied by a return mail from your ISP or mail server informing the sender of the email of just that situation).

553

Requested action not taken: mailbox name not allowed

• There is an invalid email address in the “To“, “CC”, or “BCC” field of the email message.

554

Message refused / Transaction failed

554 – message refused.

• The mail server was rejecting the address because it was bad. A transcription error allowed an relatively unnoticeable character into the address.

• Secureserver.net - Your access to this mail system has been rejected due to the sending MTA's poor reputation. If you believe that this failure is in error, please contact the intended recipient via alternate means.

554 – Transaction failed.

• Nowadays SMTP status 554 is in most cases returned when the recipient server believes your email is spam or your IP address or ISP server has been blacklisted on one or more.

• With Yahoo, on the other hand, this usually means the email address does not exist or has been disabled.

• With IBM’s Lotus Domino this is either a Domino bug or a Disk Full error.

Email SMTP server timeout

Wrong SMTP server address or port.

SMTP server is unreachable.

Check the settings and enter correct ones.