Reply codes grouped by command
Command
Code
Description
connect |
|
220 |
<domain> Service ready |
|
421 |
<domain> Service not available, closing transmission channel |
HELO |
|
250 |
Requested mail action okay, completed |
|
500 |
Syntax error, command unrecognised |
|
501 |
Syntax error in parameters or arguments |
|
504 |
Command parameter not implemented |
|
521 |
<domain> does not accept mail [rfc1846] |
|
421 |
<domain> Service not available, closing transmission channel |
EHLO |
|
250 |
Requested mail action okay, completed |
|
550 |
Not implemented |
|
500 |
Syntax error, command unrecognised |
|
501 |
Syntax error in parameters or arguments |
|
504 |
Command parameter not implemented |
|
421 |
<domain> Service not available, closing transmission channel |
MAIL |
|
250 |
Requested mail action okay, completed |
|
552 |
Requested mail action aborted: exceeded storage allocation |
|
451 |
Requested action aborted: local error in processing |
|
452 |
Requested action not taken: insufficient system storage |
|
500 |
Syntax error, command unrecognised |
|
501 |
Syntax error in parameters or arguments |
|
421 |
<domain> Service not available, closing transmission channel |
RCPT |
|
250 |
Requested mail action okay, completed |
|
251 |
User not local; will forward to <forward-path> |
|
550 |
Requested action not taken: mailbox unavailable |
|
551 |
User not local; please try <forward-path> |
|
552 |
Requested mail action aborted: exceeded storage allocation |
|
553 |
Requested action not taken: mailbox name not allowed |
|
450 |
Requested mail action not taken: mailbox unavailable |
|
451 |
Requested action aborted: local error in processing |
|
452 |
Requested action not taken: insufficient system storage |
|
500 |
Syntax error, command unrecognised |
|
501 |
Syntax error in parameters or arguments |
|
503 |
Bad sequence of commands |
|
521 |
<domain> does not accept mail [rfc1846] |
|
421 |
<domain> Service not available, closing transmission channel |
DATA |
|
354 |
Start mail input; end with <CRLF>.<CRLF> |
|
451 |
Requested action aborted: local error in processing |
|
554 |
Transaction failed |
|
500 |
Syntax error, command unrecognised |
|
501 |
Syntax error in parameters or arguments |
|
503 |
Bad sequence of commands |
|
421 |
<domain> Service not available, closing transmission channel |
received data |
|
250 |
Requested mail action okay, completed |
|
552 |
Requested mail action aborted: exceeded storage allocation |
|
554 |
Transaction failed |
|
451 |
Requested action aborted: local error in processing |
|
452 |
Requested action not taken: insufficient system storage |
RSET |
|
200 |
(nonstandard success response, see rfc876) |
|
250 |
Requested mail action okay, completed |
|
500 |
Syntax error, command unrecognised |
|
501 |
Syntax error in parameters or arguments |
|
504 |
Command parameter not implemented |
|
421 |
<domain> Service not available, closing transmission channel |
SEND |
|
250 |
Requested mail action okay, completed |
|
552 |
Requested mail action aborted: exceeded storage allocation |
|
451 |
Requested action aborted: local error in processing |
|
452 |
Requested action not taken: insufficient system storage |
|
500 |
Syntax error, command unrecognised |
|
501 |
Syntax error in parameters or arguments |
|
502 |
Command not implemented |
|
421 |
<domain> Service not available, closing transmission channel |
SOML |
|
250 |
Requested mail action okay, completed |
|
552 |
Requested mail action aborted: exceeded storage allocation |
|
451 |
Requested action aborted: local error in processing |
|
452 |
Requested action not taken: insufficient system storage |
|
500 |
Syntax error, command unrecognised |
|
501 |
Syntax error in parameters or arguments |
|
502 |
Command not implemented |
|
421 |
<domain> Service not available, closing transmission channel |
SAML |
|
250 |
Requested mail action okay, completed |
|
552 |
Requested mail action aborted: exceeded storage allocation |
|
451 |
Requested action aborted: local error in processing |
|
452 |
Requested action not taken: insufficient system storage |
|
500 |
Syntax error, command unrecognised |
|
501 |
Syntax error in parameters or arguments |
|
502 |
Command not implemented |
|
421 |
<domain> Service not available, closing transmission channel |
VRFY |
|
250 |
Requested mail action okay, completed |
|
251 |
User not local; will forward to <forward-path> |
|
550 |
Requested action not taken: mailbox unavailable |
|
551 |
User not local; please try <forward-path> |
|
553 |
Requested action not taken: mailbox name not allowed |
|
500 |
Syntax error, command unrecognised |
|
501 |
Syntax error in parameters or arguments |
|
502 |
Command not implemented |
|
504 |
Command parameter not implemented |
|
421 |
<domain> Service not available, closing transmission channel |
EXPN |
|
250 |
Requested mail action okay, completed |
|
550 |
Requested action not taken: mailbox unavailable |
|
500 |
Syntax error, command unrecognised |
|
501 |
Syntax error in parameters or arguments |
|
502 |
Command not implemented |
|
504 |
Command parameter not implemented |
|
421 |
<domain> Service not available, closing transmission channel |
HELP |
|
211 |
System status, or system help reply |
|
214 |
Help message |
|
500 |
Syntax error, command unrecognised |
|
501 |
Syntax error in parameters or arguments |
|
502 |
Command not implemented |
|
504 |
Command parameter not implemented |
|
421 |
<domain> Service not available, closing transmission channel |
NOOP |
|
200 |
(nonstandard success response, see rfc876) |
|
250 |
Requested mail action okay, completed |
|
500 |
Syntax error, command unrecognised |
|
421 |
<domain> Service not available, closing transmission channel |
QUIT |
|
221 |
<domain> Service closing transmission channel |
|
500 |
Syntax error, command unrecognised |
TURN |
|
250 |
Requested mail action okay, completed |
|
502 |
Command not implemented |
|
500 |
Syntax error, command unrecognised |
|
503 |
Bad sequence of commands |
相关推荐
### SMTP Server状态码详解 #### 引言 在IT领域,特别是网络管理和电子邮件服务中,了解SMTP(简单邮件传输协议)服务器状态码至关重要。当邮件发送或接收出现问题时,这些状态码可以帮助技术人员快速定位问题所在...
Error-Correcting Codes, by Professor Peterson, was originally published in 1961. Now, with E. J. Weldon, Jr., as his coauthor, Professor Peterson has extensively rewritten his material. The book ...
为此,纠错码(Error-Correcting Codes, ECC)作为一项关键的技术手段,在减少数据传输过程中的错误方面发挥着基础性的作用。本书《代数编码在数据传输中的应用》由伊利诺伊大学厄巴纳-香槟分校电气与计算机工程系...
github-recovery-codes.txt
在这个名为"C++ Codes"的压缩包中,可能包含了各种C++编程的示例代码、练习项目或库,涉及了C++的多个方面,例如基础语法、类与对象、模板、异常处理、STL(标准模板库)等。 **C++基础语法** C++的基础语法包括...
### SMD-Codes:主动型SMD半导体组件的标记代码 #### 概述 随着电子产品技术的不断进步和发展,表面贴装技术(Surface Mount Technology,简称SMT)因其体积小、重量轻、易于自动化组装等优点,在电子产品的设计与...
- **克尔多克码(Kerdock Codes)**与**预备拉塔码(Preparata Codes)**:这两类码具有良好的非线性性质,适合于某些特定的应用场景。 - **自对偶码(Self-Dual Codes)**:这类码具有独特的数学性质,在编码理论中占有...
### 低密度奇偶校验码 (Low Density Parity Check Codes) #### 概述 低密度奇偶校验码(Low Density Parity Check Codes,简称LDPC码)是一种高效的线性错误校正码,最初由罗伯特·G·加拉格尔(Robert G. ...
标题中的“MATLAB Codes for Finite Element Analysis”表明这是一个关于使用MATLAB进行有限元分析的资源。有限元分析(Finite Element Analysis, FEA)是一种数值计算方法,常用于工程领域,如结构力学、流体力学等...
Cracking Codes with Python: An Introduction to Building and Breaking Ciphers (True PDF)
【描述】"fk fk2_codes 2_codes fk2_codes fk2_codes fk2_codes fk2_codes fk2_codes"看起来像是重复的关键词,"fk"可能是缩写,可能是开发者的名字、项目代号或者是某种编程概念的简写。"2_codes"可能表示第二版...
codes for collaborative filtering, which enables us to efficiently make recommendations with time complexity that is independent of the total number of items. We propose to construct binary codes for ...
3. Visual C++ source codes:这部分可能包含用C++编写的示例代码,展示了如何在C++项目中集成和使用这个SMTP库。这对于C++开发者来说是非常有价值的,因为他们可以直接参考这些代码来快速上手。 4. Visual C# ...
错误校正码(Error-Correcting Codes, ECC)是信息理论中的一个基础概念,它们在数字通信和存储领域扮演着至关重要的角色。为了确保数据在传输或存储过程中遭受干扰时,接收方能够准确还原发送方的信息,错误校正码...
涡轮码(Turbo Codes)是一种纠错编码技术,它在通信和存储系统中扮演着重要的角色,因其接近香农极限的性能而闻名。MATLAB是一个强大的数学计算软件,广泛用于科学计算、工程仿真以及信号处理等领域。在这个"turbo ...
《Variable-length Codes for Data Compression》是一本关于数据压缩领域中变长编码技术的专业书籍。本书由David Salomon教授撰写,详细介绍了各种变长编码算法及其在实际数据压缩场景中的应用。 #### 什么是变长...
错误纠正编码(Error-Correcting Codes,ECC)是通信和数据存储领域中至关重要的技术,旨在检测并修复数据传输或存储过程中可能出现的错误。《Fundamentals of Error-Correcting Codes》这本书由W. Cary Huffman撰写...