|
코드 |
상세코드 |
오류 |
설명 |
문제해결 가이드 |
|
500 |
5.5.1 |
Command unrecognized |
The SMTP command currently used was unrecognized or is not supported by the SMTP service. |
Review the syntax of the last command and try again.
Another possibility is that you are trying to use telnet and the telnet connection to your server is not allowed. Check the settings in administration console: Mail service -> Security -> Advanced. |
|
501 |
5.5.2 |
Domain name required |
Sender has no domain specified (usually in MAIL FROM). |
Specify the senders' domain name and try again.
The problem will be with user's e-mail client, not your server. The e-mail client configuration is probably not supplied with a domain name. |
|
501 |
5.5.2 |
Unbalanced |
SMTP session syntax invalid (usually unbalanced brackets). |
Check the syntax of the last command and the configuration of corresponding .dat files. |
|
501 |
5.5.4 |
Syntax error in parameters scanning |
Common syntax error. You probably mis-typed last command or last string is invalid. |
Check the syntax of the last command. |
|
501 |
5.5.1 |
HELO/EHLO requires domain address |
Usually when there was blank or invalid string sequence after HELO/EHLO command. |
Retry the SMTP greeting with correct HELO/ELHO command. |
|
501 |
5.0.0 |
Authentication canceled
|
The process of authentication was canceled for any reason. |
Restart the authentication process by using proper command. |
|
501 |
5.7.0 |
Authentication failed |
The username/password combination provided during authentication was invalid. |
Reenter both the username and the password and authenticate again.
|
|
501 |
5.7.1 |
Permission denied |
You are not authorized to send. |
Result of "Reject if originator's IP has no rDNS" or "Reject if SMTP AUTH is different from sender".
Check the authentication in email client.
Be sure the options are NOT checked in administration console, or:
Put the local IP range and your e-mail client IP in the "Relaying from" box, or:
Create a Bypass for this IP/host. |
|
502 |
5.5.1 |
Sorry, we do not support this operation |
This operation is not allowed. |
You can allow/disable particular operations and commands from the administration console: Mail Service - > Security -> Advanced. |
|
503 |
5.5.1 |
Incorrect command sequence |
A supported command was used in invalid order. For example command RCPT TO used before MAIL FROM or DATA command used when RCPT TO command was not accepted. |
Solution depends on the context in which this error occurred. Check the last few commands sequence. |
|
503 |
5.5.1 |
Authentication already done |
Error occurs by re-authentication. |
|
|
503 |
5.5.1 |
HELO/EHLO command required |
Greeting error. HELO/EHLO command is required by the server. |
You have to use HELO or EHLO command. You can deactivate this option in administration console, or create a Bypass: Mail Service - > Security -> Advanced. |
|
503 |
5.5.1 |
HELO/EHLO already specified |
Greeting used again. |
|
|
504 |
5.7.6 |
Unrecognized authentication type |
Invalid authentication type. Incorrect or none type of AUTH specified. |
Use the command AUTH with proper authentication type. |
|
530 |
5.7.1 |
Authentication required [AUTH] |
Authentication with command AUTH is required. |
Use AUTH command (SMTP Server requires authentication) or disable this authentication type in administraton console. |
|
550 |
5.7.1 |
We do not relay |
Server is not open for relay. |
Refer to this FAQ. |
|
550 |
5.7.1 |
We do not relay, account limits apply |
|
Check the account limits for the particular user account, its domain and on the server level. |
|
550 |
5.7.1 |
You have rights to send mail to local domains only |
The user who gets this error is allowed to send mail only to local domains. |
Disable this option in the administration console: Management -> [User] -> Options -> User can send mail to local domains only. |
|
550 |
5.7.1 |
Access not allowed |
1) Server blocked access by a blacklist filter, or
2) Reject if originator's domain is local and not authorized option turned on. |
1) Review server black list filter settings or set a bypass file.
2) Local users have to authorize themselves so if they do not have this set up in their e-mail clients and you turned this on they are not allowed to send. |
|
550 |
5.7.1 |
Access to not allowed by rules |
1) Server blocked user access by a blacklist filter/rule, or
2) Server blocked access from the originating server by HELO/EHLO Filter. |
1) Review server black list filters and user rules or set a bypass item.
2) Whitelist the originating server in HELO/EHLO filter, or remove it from blacklist, or create a Bypass. |
|
550 |
5.7.1 |
Permission denied |
|
|
|
550 |
5.1.1 |
Unknown local user |
|
|
|
550 |
5.1.1 |
Unknown user; rejecting |
Unknown user account. The recipient is not local, thus reject the message. |
Behavior and the treatment of messages coming to unknown user accounts can be set from administration console: Management > [Domain] > Unknown Account. |
|
551 |
5.1.1 |
No such user found |
User account is not local. |
|
|
551 |
5.1.1 |
No such mailing list found |
Mailing list is not local. |
|
|
552 |
5.5.3 |
Too many recipients |
The number of recipients exceeds the maximum of allowed recipients. |
Older versions of Merak Mail Server used to follow RFC and had maximum of recipients set to 100. If you need more recipients or use mailing lists, upgrade to the latest version (adds support for unlimited number of recipients). |
|
554 |
5.3.4 |
Message size exceeds fixed maximum message size |
Too many data was sent by the user. User account has an amount limitation. |
You can increase or disable amount limit from administration console - user account management - Limits tab. Make sure all 3 levels (server, domain and user) are set to 0 (stands for unlimited). |
|
554 |
5.7.1 |
Message cannot be accepted, virus found |
Virus was found in the message body or in the message attachment. |
If you think the attachment is not harmless (false positive), try to alter the configuration of the anti-virus engine (Quarantine instead of Reject), or create a Bypass entry. |
|
554 |
5.7.1 |
Message cannot be accepted, content filter rejection |
Content filter applied and the message was rejected. |
Review the content filter settings in administration console. |
|
554 |
5.7.1 |
Message cannot be accepted, spam filter rejection |
Message is probably spam. |
If you think this message is spam (false positive), try to alter the configuration of the anti-spam engine, index the message by Bayesian or create a blacklist entry. |
|
554 |
5.7.1 |
Message cannot be accepted, spam rejection |
Message is probably spam. |
If you think this message is not spam (false positive), try to alter the configuration of the anti-spam engine, index the message by Bayesian or create a whitelist entry. |
|
|
|
Message deleted by filter |
|
Alter your content filters configuration. |
|
|
|
Message challenged by filter |
|
If you do not want to use Challenge Response, you can deactivate it in your anti-spam settings (Trust tab in older versions, now Quarantine node). |
|
554 |
5.2.2 |
|
Maximum mailbox size exceeded. |
Review settings of Limits on server / domain / user level. |
|
554 |
5.3.1 |
|
Maximum message size exceeded. |
Review settings of Limits on server / domain / user level. |
|
554 |
5.7.1 |
Message cannot be accepted, filter rejection |
The message was rejected. |
Check your filter settings and configuration. |
The IceWarp SSL Certificate Process.pdf
