Протокол SMTP отвечает за отправку ваших сообщений. Если Вы получаете сообщение об ошибках SMTP, это означает, что ваши электронные письма не были отправлены. Вам необходимо знать, что вызвало эту проблему. Все коды SMTP состоят из трех цифр, например, 550, 221, 354, и т.д. Не все из них подразумевают некоторый тип ошибки. Чтобы понять значение кодов ошибок Вы должна знать, что каждая цифра (первая, вторая и третья) имеет собственное значение.
Первая цифра показывает Вам, если ваша команда была принята и обработана. Есть пять различных значений:
- Почтовый сервер принял команду, но еще не предпринимает никакого действия. Требуется подтверждающее сообщение.
- Почтовый сервер завершил задачу успешно без ошибок.
- Почтовый сервер понял запрос, но требует, чтобы дальнейшая информация завершила это.
- Почтовый сервер столкнулся с временным отказом. Если команда повторена без изменения. Попытайтесь снова, это может помочь!
- Почтовый сервер столкнулся с неустранимой ошибкой. Ваш запрос не может быть обработан.
Если вы видите коды начинающиеся с 4, и 5, это означает, что ваше сообщение не будут отправлено, пока Вы не устраните неисправность
Вторая цифра означает:
- Синтаксическая ошибка.
- Информационный ответ (например, к ЗАПРОСУ СПРАВОЧНОЙ ИНФОРМАЦИИ).
- Эта цифра относится к состоянию подключения.
- Эта цифра относится к состоянию почтового сервера.
Последняя цифра кода показывает подробности состояния передачи.
Вот список самых важных кодов ошибки SMTP:
421 Обслуживание не доступно, закрыт канал передачи (Это может быть ответом на любую команду, если обслуживание{служба} знает, что это должно закрыть)
450 Требуемые почтовые действия, не предприняты: почтовый ящик недоступен (например, почтовый ящик занят)
451 Требуемое действие прерывалось: ошибка в обработке
452 Требуемые действия, не предприняты: недостаточно системных ресурсов
500 Синтаксическая ошибка, неправильная команда (Это может включать ошибки типа слишком длинная командная строка)
501 Синтаксическая ошибка в параметрах или переменных
502 Несуществующая команда
503 Неправильная последовательность команд
504 Параметр Command, не осуществлен
550 Требуемые действия, не предприняты: почтовый ящик недоступен (например, почтовый ящик, не найден, нет доступа)
551 Пользователь не местный; попробуйте еще раз
552 Требуемые почтовые действия прервались: превышено распределение памяти
553 Требуемые действия, не предприняты: имя почтового ящика, недопустимо (например, синтаксис почтового ящика неправильный)
554 Передача данных не удалась
Другие коды, обеспечивающие Вас полезной информацией о том, что происходит с вашими сообщениями:
211 Статус системы, или система помогают ответу
214 Сообщение Справки (Информация относительно того, как использовать получатель или значение специфической ненормативной команды; этот ответ полезен только человеческому пользователю)
220 Готов к обслуживанию
221 Обслуживается заключительный канал передачи
250 Требуемые почтовые действия завершены
251 Пользователь не местный; сообщение переправлено
354 Начните ввод сообщения. Завершите ввод сообщения. (точка).
<<Вернутся назад, в раздел «Полезные статьи»
From Wikipedia, the free encyclopedia
This is a list of Simple Mail Transfer Protocol (SMTP) response status codes. Status codes are issued by a server in response to a client’s request made to the server.
Unless otherwise stated, all status codes described here is part of the current SMTP standard, RFC 5321. The message phrases shown are typical, but any human-readable alternative may be provided.
Basic status code[edit]
A «Basic Status Code» SMTP reply consists of a three digit number (transmitted as three numeric characters) followed by some text. The number is for use by automata (e.g., email clients) to determine what state to enter next; the text («Text Part») is for the human user.
The first digit denotes whether the response is good, bad, or incomplete:
- 2yz (Positive Completion Reply): The requested action has been successfully completed.
- 3yz (Positive Intermediate Reply): The command has been accepted, but the requested action is being held in abeyance, pending receipt of further information.
- 4yz (Transient Negative Completion Reply): The command was not accepted, and the requested action did not occur. However, the error condition is temporary, and the action may be requested again.
- 5yz (Permanent Negative Completion Reply): The command was not accepted and the requested action did not occur. The SMTP client SHOULD NOT repeat the exact request (in the same sequence).
The second digit encodes responses in specific categories:
- x0z (Syntax): These replies refer to syntax errors, syntactically correct commands that do not fit any functional category, and unimplemented or superfluous commands.
- x1z (Information): These are replies to requests for information.
- x2z (Connections): These are replies referring to the transmission channel.
- x3z : Unspecified.
- x4z : Unspecified.
- x5z (Mail system): These replies indicate the status of the receiver mail system.
Enhanced status code[edit]
The Basic Status Codes have been in SMTP from the beginning, with RFC 821 in 1982, but were extended rather extensively, and haphazardly so that by 2003 RFC 3463 rather grumpily noted that: «SMTP suffers some scars from history, most notably the unfortunate damage to the reply code extension mechanism by uncontrolled use.»
RFC 3463 defines a separate series of enhanced mail system status codes which is intended to be better structured, consisting of three numerical fields separated by «.», as follows:
class "." subject "." detail class = "2" / "4" / "5" subject = 1 to 3 digits detail = 1 to 3 digits
The classes are defined as follows:
- 2.XXX.XXX Success: Report of a positive delivery action.
- 4.XXX.XXX Persistent Transient Failure: Message as sent is valid, but persistence of some temporary conditions has caused abandonment or delay.
- 5.XXX.XXX Permanent Failure: Not likely to be resolved by resending the message in current form.
In general the class identifier MUST match the first digit of the Basic Status Code to which it applies.[1]
The subjects are defined as follows:
- X.0.XXX Other or Undefined Status
- X.1.XXX Addressing Status
- X.2.XXX Mailbox Status
- X.3.XXX Mail System Status
- X.4.XXX Network and Routing Status
- X.5.XXX Mail Delivery Protocol Status
- X.6.XXX Message Content or Media Status
- X.7.XXX Security or Policy Status
The meaning of the «detail» field depends on the class and the subject, and are listed in RFC 3463 and RFC 5248.
A server capable of replying with an Enhanced Status Code MUST preface (prepend) the Text Part of SMTP Server responses with the Enhanced Status Code followed by one or more spaces. For example, the «221 Bye» reply (after QUIT command) MUST be sent as «221 2.0.0 Bye» instead.[1]
The Internet Assigned Numbers Authority (IANA) maintains the official registry of these enhanced status codes.[2]
Common status codes[edit]
This section list some of the more commonly encountered SMTP Status Codes. This list is not exhaustive, and the actual text message (outside of the 3-field Enhanced Status Code) might be different.
— 2yz Positive completion[edit]
-
- 211 System status, or system help reply
-
- 214 Help message (A response to the HELP command)
-
- 220 <domain> Service ready
-
- 221 <domain> Service closing transmission channel
-
- 221 2.0.0 Goodbye [1]
-
- 235 2.7.0 Authentication succeeded [3]
-
- 240 QUIT
-
- 250 Requested mail action okay, completed
-
- 251 User not local; will forward
-
- 252 Cannot verify the user, but it will try to deliver the message anyway
— 3yz Positive intermediate[edit]
-
- 334 (Server challenge — the text part contains the Base64-encoded challenge) [3]
-
- 354 Start mail input
— 4yz Transient negative completion[edit]
«Transient Negative» means the error condition is temporary, and the action may be requested again. The sender should return to the beginning of the command sequence (if any).
The accurate meaning of «transient» needs to be agreed upon between the two different sites (receiver- and sender-SMTP agents) must agree on the interpretation. Each reply in this category might have a different time value, but the SMTP client SHOULD try again.
-
- 421 Service not available, closing transmission channel (This may be a reply to any command if the service knows it must shut down)
-
- 432 4.7.12 A password transition is needed [3]
-
- 450 Requested mail action not taken: mailbox unavailable (e.g., mailbox busy or temporarily blocked for policy reasons)
-
- 451 Requested action aborted: local error in processing
-
- 451 4.4.1 IMAP server unavailable [4]
-
- 452 Requested action not taken: insufficient system storage
-
- 454 4.7.0 Temporary authentication failure [3]
-
- 455 Server unable to accommodate parameters
— 5yz Permanent negative completion[edit]
The SMTP client SHOULD NOT repeat the exact request (in the same sequence). Even some «permanent» error conditions can be corrected, so the human user may want to direct the SMTP client to reinitiate the command sequence by direct action at some point in the future.
-
- 500 Syntax error, command unrecognized (This may include errors such as command line too long)
-
- 500 5.5.6 Authentication Exchange line is too long [3]
-
- 501 Syntax error in parameters or arguments
-
- 501 5.5.2 Cannot Base64-decode Client responses [3]
-
- 501 5.7.0 Client initiated Authentication Exchange (only when the SASL mechanism specified that client does not begin the authentication exchange) [3]
-
- 502 Command not implemented
-
- 503 Bad sequence of commands
-
- 504 Command parameter is not implemented
-
- 504 5.5.4 Unrecognized authentication type [3]
-
- 521 Server does not accept mail [5]
-
- 523 Encryption Needed [6]
-
- 530 5.7.0 Authentication required [3]
-
- 534 5.7.9 Authentication mechanism is too weak [3]
-
- 535 5.7.8 Authentication credentials invalid [3]
-
- 538 5.7.11 Encryption required for requested authentication mechanism[3]
-
- 550 Requested action not taken: mailbox unavailable (e.g., mailbox not found, no access, or command rejected for policy reasons)
-
- 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
-
- 554 Transaction has failed (Or, in the case of a connection-opening response, «No SMTP service here»)
-
- 554 5.3.4 Message too big for system [4]
-
- 556 Domain does not accept mail [5]
Example[edit]
Below is an example SMTP connection, where a client «C» is sending to server «S»:
S: 220 smtp.example.com ESMTP Postfix C: HELO relay.example.com S: 250 smtp.example.com, I am glad to meet you C: MAIL FROM:<bob@example.com> S: 250 Ok C: RCPT TO:<alice@example.com> S: 250 Ok C: RCPT TO:<theboss@example.com> S: 250 Ok C: DATA S: 354 End data with <CR><LF>.<CR><LF> C: From: "Bob Example" <bob@example.com> C: To: Alice Example <alice@example.com> C: Cc: theboss@example.com C: Date: Tue, 15 Jan 2008 16:02:43 -0500 C: Subject: Test message C: C: Hello Alice. C: This is a test message with 5 header fields and 4 lines in the message body. C: Your friend, C: Bob C: . S: 250 Ok: queued as 12345 C: QUIT S: 221 Bye {The server closes the connection}
And below is an example of an SMTP connection in which the SMTP Server supports the Enhanced Status Code, taken from RFC 2034:
S: 220 dbc.mtview.ca.us SMTP service ready C: EHLO ymir.claremont.edu S: 250-dbc.mtview.ca.us says hello S: 250 ENHANCEDSTATUSCODES C: MAIL FROM:<ned@ymir.claremont.edu> S: 250 2.1.0 Originator <ned@ymir.claremont.edu> ok C: RCPT TO:<mrose@dbc.mtview.ca.us> S: 250 2.1.5 Recipient <mrose@dbc.mtview.ca.us> ok C: RCPT TO:<nosuchuser@dbc.mtview.ca.us> S: 550 5.1.1 Mailbox "nosuchuser" does not exist C: RCPT TO:<remoteuser@isi.edu> S: 551-5.7.1 Forwarding to remote hosts disabled S: 551 5.7.1 Select another host to act as your forwarder C: DATA S: 354 Send message, ending in CRLF.CRLF. ... C: . S: 250 2.6.0 Message accepted C: QUIT S: 221 2.0.0 Goodbye {The server closes the connection}
References[edit]
- ^ a b c RFC 2034
- ^ «Simple Mail Transfer Protocol (SMTP) Enhanced Status Codes Registry». IANA. Retrieved December 20, 2018.
- ^ a b c d e f g h i j k l RFC 4954
- ^ a b RFC 4468
- ^ a b RFC 7504
- ^ RFC 5248
On webmail every user gets error «ERROR: Message not sent. Server replied: 354» while sending mails.
But mails are sent properly and reaches properly.
Can you tell me where is problem, and why it is occurred?
UPDATE: I found in some resources that this is not an error but standard information message. On the other side, it’s annoying. Can you tell me if it is a true, and if it is how can I avoid it?
Deesbek
2103 silver badges12 bronze badges
asked May 21, 2013 at 7:30
1
TL;DR:
Your webmail program is badly written and thinks that the response code 354 is an error, even though it isn’t.
Long answer:
This is what the SMTP conversation looks like (S = server, C = client)
S: 220 foo.com Simple Mail Transfer Service Ready
C: EHLO bar.com
S: 250-foo.com greets bar.com
S: 250-8BITMIME
S: 250-SIZE
S: 250-DSN
S: 250 HELP
C: MAIL FROM:<Smith@bar.com>
S: 250 OK
C: RCPT TO:<Jones@foo.com>
S: 250 OK
C: DATA
S: 354 Start mail input; end with <CRLF>.<CRLF>
C: Blah blah blah...
C: ...etc. etc. etc.
C: .
S: 250 OK
C: QUIT
S: 221 foo.com Service closing transmission channel
As you see, the code 354 means «OK, we’re done with the information about sender and recipient, now give me the actual mail». However, your webmail system has been coded to think that only response codes starting with a 2 means «succeeded», so it takes any other code to mean that there’s a problem. Whoever wrote the webmail program needs to go back and read RFC 5321 again and then fix the bug.
answered May 21, 2013 at 7:53
Jenny DJenny D
27.5k21 gold badges74 silver badges112 bronze badges
1
Hi I’m making a web application and need to send some e-mails. I’m using Laravel 5.6, and make the e-mail feature at localhost using Mailtrap to test it, worked fine. But when I put it on the server I got a weird error, like in the picture bellow.
I’ve configured the system to my host, Hostinger settings.
This is the config code in the .env file
MAIL_DRIVER=smtp
MAIL_HOST=mx1.hostinger.com.br
MAIL_PORT=587
MAIL_USERNAME=E_MAIL_HERE
MAIL_PASSWORD=PASSWORD_HERE
MAIL_ENCRYPTION=null
asked Oct 24, 2018 at 1:37
NathanNathan
972 silver badges8 bronze badges
1
I have faced the same issue.
Basically, I changed config/mail.php variable MAIL_FROM_ADDRESS to my actual email and it worked.
answered Apr 4, 2019 at 20:00
1
Code 354 is actually what Laravel expects, is not an error code. This is the SMTP server telling Laravel to proceed and send the body of the email. Note that this is what is expected, and not what you received.
Code 554 from a mail server indicates: «Transaction Failed», and you’ll note that this is what you actually got.
The reason this is failing is indicated further in the message: Error: no valid recipients.
Without further data I can’t tell why the recipient isn’t set properly on your production server.
A more complete list of codes can be found here: https://www.greenend.org.uk/rjk/tech/smtpreplies.html
answered Oct 24, 2018 at 1:51
hazhaz
1,50914 silver badges20 bronze badges
4
- If you have the
$message->from('anotheremail@mail.com')on your controller or anywhere defined, either remove it and just add theMAIL_FROM_ADDRESS="no-reply@test.com"to your.env. - Or you can add
$message->from('reply@test.com')anywhere you defined it, like in your controller for example.
I believe this happens when you are trying to put another from email address which is not part of your server or domain. Use the email you create on your server or Cpanel.
ahuemmer
1,4628 gold badges21 silver badges25 bronze badges
answered Mar 26, 2022 at 19:41
-
kalinga
- Posts: 40
- Joined: Wed Sep 06, 2006 6:18 am
- Location: Sri Lanka/Colombo
Reason: 354 Start mail input; end with <CRLF>.<CRLF
hello,
i have this error with ME 1.92 ST on Windows 2000 SP4 Server.
i see this msg time to time even with ME to ME mail transfers.
====
MailEnable: Message Delivery Failure.
The following recipient(s) could not be reached:
Recipient: [SMTP:log@XX.com]
Reason: 354 Start mail input; end with <CRLF>.<CRLF>
=======
why does ME SMTP take 354 reply as an error ????? this is really funny… does any one know why ?
-
eisi
- Posts: 27
- Joined: Thu Oct 17, 2002 12:58 am
Re: Reason: 354 Start mail input; end with <CRLF>.<
Post
by eisi » Thu Sep 07, 2006 8:31 am
Hello,
a year ago , we had the same problems with the Deutsche Telekom.
Mails to the Telekom are logged with the same error.
I think this problem is a faulty networkcard or a full/halfduplex problem in your network.
Regards,
Ingo
kalinga wrote:hello,
i have this error with ME 1.92 ST on Windows 2000 SP4 Server.
i see this msg time to time even with ME to ME mail transfers.
====
MailEnable: Message Delivery Failure.The following recipient(s) could not be reached:
Recipient: [SMTP:log@XX.com]
Reason: 354 Start mail input; end with <CRLF>.<CRLF>
=======why does ME SMTP take 354 reply as an error ????? this is really funny… does any one know why ?
-
kalinga
- Posts: 40
- Joined: Wed Sep 06, 2006 6:18 am
- Location: Sri Lanka/Colombo
Post
by kalinga » Thu Sep 07, 2006 11:46 am
Hi,
dont think is a network card issue as i have 2 servers both report the same error time to time.
what i cant understand is why does ME 354 reply as an error ? i think this is an error or a bug in the ME transport as i dont see any error when i use the MS SMTP as the outgoing and inbound SMTP.
i get this error in the local network with the fullowing setups
ME SMTP — > ME SMTP (LAN)
ME SMTP —-> POSTFIX SMTP (LAN)
-
eisi
- Posts: 27
- Joined: Thu Oct 17, 2002 12:58 am
Post
by eisi » Thu Sep 07, 2006 12:11 pm
Yes, but the normal logging looks like this one:
Helo
Mail From
Mail To
Data
Quit
Your logging looks like:
Helo
Mail From
Mail To
354 Start mail input; end with <CRLF>.<CRLF>
I dont now exacly why this happens, but i know that the Telecom had a faulty switch and after they changed this switch, the problem was solved.
Ingo
-
kalinga
- Posts: 40
- Joined: Wed Sep 06, 2006 6:18 am
- Location: Sri Lanka/Colombo
Post
by kalinga » Thu Sep 07, 2006 2:44 pm
well any normal smtp communication look like this
< 220 mail.XX.com ESMTP MailEnable Service, Version: 1.9— ready at 09/07/06 10:39:34
> HELO edit.XX.com
< 250 Requested mail action okay, completed
> MAIL FROM:<kalinga@XXX.net>
< 250 Requested mail action okay, completed
> RCPT TO:<abuse@XXX.lk>
< 250 Requested mail action okay, completed
> DATA
< 354 Start mail input; end with <CRLF>.<CRLF>
> From: kalinga@XXX.net
> To: abuse@XXX.lk
> Subject: SMTP Test
>
> If you received this, then the mail server is probably working.
> .
< 250 Requested mail action okay, completed
————
the < 354 Start mail input; end with <CRLF>.<CRLF> is the reply send by ME SMTP to the sending server as a reply to the DATA command.
as for RFC only 4XX and 5XX taken as error replys and 250 and 354 taken as OK
so im not sure why ME is taken the 354 reply as an error msg, when both been ME servers.
-
MailEnable
- Site Admin
- Posts: 4441
- Joined: Tue Jun 25, 2002 3:03 am
- Location: Melbourne, Victoria Australia
Post
by MailEnable » Thu Sep 07, 2006 3:04 pm
MailEnable does not consider 354 an error.
This:
Reason: 354 Start mail input; end with <CRLF>.<CRLF>
actually means that the 354 was the last valid command. This being the case it means that an error occured in the transmission of the message contents. This normally means that the MTU setting is incorrect for the server or there is a bad router in the mix.
The test is to manually use telnet to send a message to the remote server.
Then, send a very short message from mailenable. If the short message works, but larger ones do not, then you need to review the mtu settings of your server and (if possible) any routers between the two servers.
Regards, Andrew
-
paarlberg
- Posts: 1071
- Joined: Tue Mar 02, 2004 7:33 pm
- Location: Atlanta, GA, USA
Post
by paarlberg » Thu Sep 07, 2006 4:04 pm
If you are behind NAT on a Cisco router you will have to adjust the MTA. I had simialr issues at one point. I had to test in increments of 8 when lowering the MTU and I think the 3rd or 4th one worked.
I would look at the MTU as the root first. You can always change it back and it sholdn’t cause any issues with anything else.
-
kalinga
- Posts: 40
- Joined: Wed Sep 06, 2006 6:18 am
- Location: Sri Lanka/Colombo
Post
by kalinga » Thu Sep 07, 2006 4:47 pm
hi paarlbrg,
no both servers (ME) are on my LAN, i done use ME as the outgoing or incomming servers, for that i use linux gateways, i have this issue when ME transfer an mail form to a nother ME server on the same LAN, this happen only when there is a ZIP file or an attachment is there on the mail, but all of them are less then 500Kb.
so im thinking about setting up the system like this
ME —> MS SMTP —> MS SMTP —> ME
to transfer mail form and to ME servers in my LAN.
my only prb is why does ME take the and report the 354 as an error, clearly this is an bug on the SMTP of ME as it should NOT report the 354 reply as an error even if there was a data transfer error, it should re-try after some time.
-
kalinga
- Posts: 40
- Joined: Wed Sep 06, 2006 6:18 am
- Location: Sri Lanka/Colombo
Post
by kalinga » Thu Sep 07, 2006 4:54 pm
MailEnable wrote:MailEnable does not consider 354 an error.
The test is to manually use telnet to send a message to the remote server.
Then, send a very short message from mailenable. If the short message works, but larger ones do not, then you need to review the mtu settings of your server and (if possible) any routers between the two servers.
what MTU setting you recomend for ME servers that running on the same LAN ?
also to servers that runn on links slower then 512Kbps ?
-
paarlberg
- Posts: 1071
- Joined: Tue Mar 02, 2004 7:33 pm
- Location: Atlanta, GA, USA
Post
by paarlberg » Thu Sep 07, 2006 6:12 pm
I believe I used 1468 on mine. 1500 is most likley the default.
1500
1492
1484
1476
1468
etc…
-
kalinga
- Posts: 40
- Joined: Wed Sep 06, 2006 6:18 am
- Location: Sri Lanka/Colombo
Post
by kalinga » Fri Sep 08, 2006 5:31 am
i did a ping test with 1500 (for more then 1 hour) i did not get any errors, i have set the MTU to 1430 on both servers, let see how it goes….
-
kalinga
- Posts: 40
- Joined: Wed Sep 06, 2006 6:18 am
- Location: Sri Lanka/Colombo
Post
by kalinga » Fri Sep 08, 2006 9:44 am
well, its the same…. i get the error even after setting MTU in defrant setting
-
eisi
- Posts: 27
- Joined: Thu Oct 17, 2002 12:58 am
Post
by eisi » Fri Sep 08, 2006 9:50 am
Hi,
echo request/reply is nonrelevant for this problem.
If you have packetloss within your pings, you have much more trouble on your network 
Please tell me what hardware do you have:
Server1 Nic and operatingsystem
Server2 Nic and operatingsystem
Brand of switch or hub.
Ingo
kalinga wrote:i did a ping test with 1500 (for more then 1 hour) i did not get any errors, i have set the MTU to 1430 on both servers, let see how it goes….
-
kalinga
- Posts: 40
- Joined: Wed Sep 06, 2006 6:18 am
- Location: Sri Lanka/Colombo
Post
by kalinga » Fri Sep 08, 2006 10:01 am
server 1
Windows 2000 server SP4 + Uptodate
NIC — Broadcomm 440x 10/100
HUB — 3Com
server 2
Windows 2000 server SP4 + Uptodate
NIC — Broadcomm 440x 10/100
but there is no prb with this setup
(ME —> MS SMTP) ——-> (MS SMTP —> ME)
i have setup MS SMTP on the same system running on a def port and ME fwd the mail to MS SMTP then MS SMTP fwd the mail to the other servers MS SMTP.
had no prb so far….
what must be the prb ?
this error only happend when there is an attachment and multiple recipent on the same mail.
-
eisi
- Posts: 27
- Joined: Thu Oct 17, 2002 12:58 am
Post
by eisi » Fri Sep 08, 2006 10:09 am
Ok,
two ideas:
1. Do you use a virusscanner ? if yes, please disable and test again.
2. Is the 3com a hub or a switch ?
Ingo
What is SMTP?
SMTP stands for Simple Mail Transfer Protocol. This document provides the brief explanation about SMTP reply codes.
SMTP Error 101 : Cannot open connection
Typically your SMTP server or email program is unable to even start an SMTP session. Possible causes may be : incorrectly spelt SMTP server, invalid IP address, invalid SMTP port or some other process is already using the default SMTP port, port 25.
e.g. «SMTP Error 101, Error opening connection» -or- «SMTP Error 101, cannot open SMTP stream»
SMTP Error 211 : System Status message or System Help Reply
SMTP status 211 prefaces a message about the Mail Server status. You might for example issue a command to the mail server to display a list of commands you can use and the server replies with an SMTP Reply 211 followed by the list you requested.
SMTP Error 214 : Help Reply message
SMTP status 214 is usually in reply to the «HELP» command. It displays information about the server, usually a URL to the FAQ page of the SMTP software running on the server.
SMTP Status 220 : <Server Name> service is running
This is normally the first message you will get back from the server. It means the mail service is running . It will normally contain a welcome message and/or the title of the SMTP software and, sometimes, the version number of the mail server software.
SMTP Error 221 : The domain service is closing the transmission channel
The server is ending the mail session – it is closing the conversation with the ISP as it has no more mail to send in this sending session.
e.g. «221 Closing connection» -or- «221 Goodbye»
SMTP Status 250 : Requested mail action OK completed
The mail server has successfully delivered the message! This is the best SMTP reply to receive — your message has been accepted and transmitted OK !
SMTP Status 251 : User not local will forward to <forward-path>
The email account is not local to the ISP server but the ISP server will accept the email and will forward it.
SMTP Status 252 : Cannot VRFY (verify) the user – the server will accept the message and attempt to deliver it
The user account appears to be valid but could not be verified, however the server will try do deliver the message.
SMTP Error 354 : Start mail input end with <CRLF>.<CRLF>
This is normally in response to the DATA command. The server has received the From and To information and is now asking for the «Message Body», the main part of the message which should be ended by two blank lines separated by a dot (period).
SMTP Error 421 : <Server name> Service not available – the sending email program should try again later
The Mail transfer service is unavailable because of a transient event. It generally indicates that the mail server which returns this status code is currently unavailable but may be available later.
SMTP Error 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.
SMTP Error 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 error condition.
SMTP Error 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.
SMTP Error 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.
SMTP Error 442 : The connection was dropped during transmission.
Your server started delivering the message but the connection was broken during transmission. This may be an unusual transient error – however, if it keeps happening you should investigate possible problems which could result in a network connection being broken.
SMTP Error 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.
SMTP Error 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.
SMTP Error 449 : Routing error
This is a Microsoft Exchange Server specific error code. Possible causes may be : an SMTP connector is configured to use DNS without a smart host and also uses a non-SMTP address space (e.g. X.300), or A message was sent to a recipient who was identified as a member of a routing group that was deleted.
SMTP Error 450 : Requested action not taken – The mailbox was unavailable at the remote end.
In general SMTP Error 450 is a transient error at the remote end, and should induce your mail server to retry after it’s preset retry interval.
e.g. «450 Please try again later» -or- «SMTP Error 450 5.2.3 Msg Size greater than allowed by Remote Host»
SMTP Error 451 : Requested action aborted – Local error in processing.
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.
e.g. «SMTP error 451 Unable to complete command, DNS not available or timed out» -or- «451 Domain of sender address does not resolve»
SMTP Error 452 : Requested action not taken – Insufficient storage.
The ISP server’s disk system has run out of storage space, so the action had to be cancelled.Sometimes this error may raise if your ISP’s mail server is overloaded from too many messages.
e.g. «452 Out of memory»
SMTP Error 465 : Code Page unavailable on the recipient server
This is an Exchange Server-specific error code. This error is returned by the recipient’s server if the incoming email specifies a Code Page that is not installed on the recipient’s server.
SMTP Error 471 : This is a local error with the sending server and is often followed with «Please try again later»
This is always a local error with your own mail server.It is usually caused by anti-spam or virus scanning software on your server (the sending server) getting into problems through a bug in the software, or because of a bad automatic update from the antivirus/anti-spam manufacturer, because of lack of memory on your server, or because of hard disk problems.
SMTP Error 500 : Syntax error command not recognized.
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.
SMTP Error 501 : Syntax error in parameters or arguments (e.g. invalid email address)
The command was correct and recognised, but the parameters (the arguments, e.g. email address) were not valid. For example you try to use invalid email address as sender@domain.com and as «» is not allowed in email addresses.
e.g. «Remote host said: 501 Invalid Address»
SMTP Error 502 : Command not implemented.
The command or function issued by your mail server is valid but has not been activated.
SMTP Error 503 : Bad sequence of commands.
In the original standards SMTP Status 503 indicates that the commands have been sent in the wrong order, for example your mail server has sent the «Hello» command before sending the «Mail» command. This can often be caused by a drop in network connection just as your server was sending a command, resulting in the ISP’s server not receiving it and consequently not understanding the command that followed it.
SMTP Error 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. For example, an often encountered SMTP Error 504 is : «504 Need to authenticate first».
SMTP Error 510 : Bad Email Address
Bad email address. This status code is generated by the sender’s local mail server.
SMTP Error 511 : Bad Email Address
Bad email address. This error is similar to error 510 and as with error 510, this status code is generated by the sender’s local mail server.
SMTP Error 512 : The host server for the recipient’s domain name cannot be found (DNS error)
This SMTP reply code is received when one of the servers on the way to the destination is unable to resolve the domain name of a recipient email address.
e.g. «SMTP Error 550 5.1.2 Host unknown – host cannot be found»
SMTP Error 513 : Address type is incorrect (most mail servers)
This status code is received if the email addresses are not defined correctly from the sender’s mail server. The may happend due to if a user try to copy and paste the mail addresses from a web page without setting it to correct format. For example the address like receiver(at)domian.com is invalid and should be formated like receiver@domian.com before using.
e.g. «SMTP error 501 5.1.3 Invalid address» -or- «SMTP error 553 5.1.3 User address required !» -or- «SMTP error 501 5.1.3 Bad recipient address syntax»
SMTP Status 523 : The Recipient’s mailbox cannot receive messages this big
This error will be received when the total size of the message you have sent (ie: message + all of its attachments) exceeds the size limits on the Recipient’s server.
e.g. «SMTP Error 450 5.2.3 Message Size greater than allowed by Remote Host» -or- «SMTP Error 552 5.2.3 Data size exceeds maximum permitted» -or- «SMTP Error 552 5.2.3 Message exceeds maximum fixed size»
SMTP Error 550 : Requested actions not taken as the mailbox is unavailable.
SMTP Error 550 will be returned by many servers If the recipient email address simply does not exist on the remote side.
e.g. «550 Invalid recipient» -or- «550 User account is unavailable» -or- «550 No such user here»
SMTP Error 551 : User not local or invalid address – Relay denied.
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.
SMTP Error 552 : Requested mail actions aborted – Exceeded storage allocation.
The recipient’s mailbox has reached its maximum allowed size.
e.g. «552 sorry, mailbox user@somecompany.com is over quota temporarily (#5.1.1)»
SMTP Error 553 : Requested action not taken – Mailbox name invalid.
There is an invalid email address in the «To», «CC», or «BCC» field of the email message.
SMTP Error 554 : Transaction failed.
There was a permanent error trying to complete the mail transaction which will not be resolved by resending the message in its current form. Some change to the message and/or destination must be made for successful delivery.
Ниже перечислены сообщения об ошибках и коды ошибок, которые вы можете встретить при работе с Gmail и Google Workspace. Эти сообщения и коды помогают найти и устранить проблему с электронной почтой.
Чтобы обозначить источник ошибки, Gmail добавляет в конец сообщения один или оба из следующих фрагментов:
- gsmtp (Google SMTP): добавляется во все сообщения об ошибках;
- gcdp (Google Custom Domain Policies): добавляется в сообщения об ошибках, связанных с правилами, которые созданы администратором.
Например, сообщение 550 5.7.1 This message violates example.com email policy. – gcdp <sessionid> – gsmtp (Это сообщение нарушает политику example.com в отношении электронной почты. – gcdp <sessionid> – gsmtp) указывает, что ошибка связана с персонализированным правилом, созданным администратором.
Подробнее о сообщениях об ошибках SMTP…
Примечание. Ошибка 2014 связана с расширением браузера Chrome. По очереди отключите расширения Chrome, чтобы определить, какое из них вызывает ошибку. Сообщение об ошибке 2014: В системе произошла ошибка (2014). Повторите попытку.
Сообщения об ошибках протокола SMTP
| 421, «4.3.0». Временные неполадки в системе. Повторите попытку позже |
| 421, «4.4.5», Server busy, try again later. (Сервер занят. Повторите попытку позже.) |
| 421, «4.7.0», IP not in whitelist for RCPT domain, closing connection. (Соединение прервано, так как IP-адрес отсутствует в белом списке домена RCPT.) |
| 421, «4.7.0», Our system has detected an unusual rate of unsolicited mail originating from your IP address. To protect our users from spam, mail sent from your IP address has been temporarily blocked. For more information, visit Prevent mail to Gmail users from being blocked or sent to spam. (С вашего IP-адреса с необычной частотой поступают незапрашиваемые сообщения. Почта, отправляемая с вашего IP-адреса, временно заблокирована для защиты пользователей от спама. Дополнительная информация приведена в статье Как предотвратить блокировку почты, предназначенной пользователям Gmail, или ее отправку в папку «Спам».) |
| 421, «4.7.0», Temporary System Problem. Try again later. (Временные неполадки в системе. Повторите попытку позже.) |
| 421, «4.7.0», TLS required for RCPT domain, closing connection. (Соединение прервано, так как для домена RCPT требуется протокол TLS.) |
| 421, «4.7.0», Try again later, closing connection. This usually indicates a Denial of Service (DoS) for the SMTP relay at the HELO stage. (Соединение прервано. Повторите попытку позже. Эта ошибка обычно указывает на атаку типа «отказ в обслуживании» (DoS) для ретрансляции SMTP на этапе HELO.) |
| 450, «4.2.1», The user you are trying to contact is receiving mail too quickly. Please resend your message at a later time. If the user is able to receive mail at that time, your message will be delivered. For more information, visit Limits for sending & getting mail. (Пользователь, которому вы пытаетесь отправить письмо, получает почту слишком часто. Отправьте сообщение позже. Если к тому времени пользователь сможет получать почту, ваше письмо будет доставлено. Дополнительная информация приведена в статье Ограничения на отправку и получение писем.) |
| 450, «4.2.1», The user you are trying to contact is receiving mail at a rate that prevents additional messages from being delivered. Please resend your message at a later time. If the user is able to receive mail at that time, your message will be delivered. For more information, visit Limits for sending & getting mail. (Пользователь, которому вы пытаетесь отправить письмо, получает почту со скоростью, которая не позволяет доставлять ему дополнительные сообщения. Отправьте сообщение позже. Если к тому времени пользователь сможет получать почту, ваше письмо будет доставлено. Дополнительная информация приведена в статье Ограничения на отправку и получение писем.) |
| 450, «4.2.1», Peak SMTP relay limit exceeded for customer. This is a temporary error. For more information on SMTP relay limits, please contact your administrator or visit SMTP relay service error messages. (Превышено пиковое ограничение на ретрансляцию для клиента. Это временная ошибка. Чтобы получить подробную информацию об ограничениях, ознакомьтесь с этой статьей или свяжитесь с администратором.) |
| 451, «4.3.0», Mail server temporarily rejected message. (Почтовый сервер временно отклонил сообщение.) |
| 451, «4.3.0», Multiple destination domains per transaction is unsupported. Please try again. (Использование нескольких целевых доменов для одной операции не поддерживается. Повторите попытку.) |
| 451, «4.4.2», Timeout — closing connection. (Время ожидания истекло – соединение прервано.) |
| 451, «4.5.0», SMTP protocol violation, visit RFC 2821. (Нарушение протокола SMTP, см. RFC 2821.) |
| 452, «4.2.2», The email account that you tried to reach is over quota. Please direct the recipient to Clear Google Drive space & increase storage. (В аккаунте получателя закончилось свободное место. Предложите получателю ознакомиться с этой статьей.) |
|
452, «4.5.3», Domain policy size per transaction exceeded, please try this recipient in a separate transaction. |
| 452, «4.5.3», Your message has too many recipients. For more information regarding Google’s sending limits, visit Limits for sending & getting mail. (У вашего сообщения слишком много получателей. Дополнительная информация приведена в статье Ограничения на отправку и получение писем.) |
| 454, «4.5.0», SMTP protocol violation, no commands allowed to pipeline after STARTTLS, visit RFC 3207. (Нарушение протокола SMTP, после STARTTLS для потока запрещены другие команды, см. RFC 3207.) |
| 454, «4.7.0», Cannot authenticate due to temporary system problem. Try again later. (Не удалось выполнить аутентификацию из-за временных неполадок в системе. Повторите попытку позже.) |
| 454, «5.5.1», STARTTLS may not be repeated. (Запрещено повторять команду STARTTLS.) |
| 501, «5.5.2», Cannot Decode response. (Не удалось расшифровать ответ.) |
| 501, «5.5.4», HELO/EHLO argument is invalid. For more information, visit HELO/EHLO email error. (Недопустимый аргумент HELO/EHLO. Дополнительная информация приведена в статье Ошибка HELO/EHLO.) |
| 502, «5.5.1», Too many unrecognized commands, goodbye. (Слишком много нераспознанных команд.) |
| 502, «5.5.1», Unimplemented command. (Незадействованная команда.) |
| 502, «5.5.1», Unrecognized command. (Нераспознанная команда.) |
| 503, «5.5.1», EHLO/HELO first. (Сначала команда EHLO/HELO.) |
| 503, «5.5.1», MAIL first. (Сначала команда MAIL.) |
| 503, «5.5.1», RCPT first. (Сначала команда RCPT.) |
| 503, «5.7.0», No identity changes permitted. (Запрещены изменения идентификационных данных.) |
| 504, «5.7.4», Unrecognized Authentication Type. (Нераспознанный тип аутентификации.) |
| 530, «5.5.1», Authentication Required. For more information, visit Can’t sign in to your Google Account. (Необходима аутентификация. Дополнительная информация приведена в статье Не удается войти в аккаунт Google.) |
| 530, «5.7.0», Must issue a STARTTLS command first. (Сначала необходима команда STARTTLS.) |
| 535, «5.5.4», Optional Argument not permitted for that AUTH mode. (Для этого режима AUTH запрещен необязательный аргумент.) |
| 535, «5.7.1», Application-specific password required. For more information, visit Sign in using App Passwords. (Требуется пароль приложения. Дополнительная информация приведена в статье Как войти в аккаунт с помощью паролей приложений.) |
| 535, «5.7.1», Please log in with your web browser and then try again. For more information, visit Check Gmail through other email platforms. (Войдите через браузер и повторите попытку. Дополнительная информация приведена в статье Как настроить доступ к Gmail в сторонних почтовых клиентах.) |
| 535, «5.7.1», Username and Password not accepted. For more information, visit Can’t sign in to your Google Account. (Имя пользователя и пароль не приняты. Дополнительная информация приведена в статье Не удается войти в аккаунт Google.) |
| 550, «5.1.1», The email account that you tried to reach does not exist. Please try double-checking the recipient’s email address for typos or unnecessary spaces. For more information, visit Fix bounced or rejected emails. (Аккаунт электронной почты получателя не существует. Проверьте ещё раз, правильно ли указан адрес электронной почты и нет ли в нем пробелов. Дополнительная информация приведена в статье Что делать, если письмо отклонено.) |
| 550, «5.2.1», The email account that you tried to reach is disabled. (Аккаунт электронной почты получателя отключен.) |
| 550, «5.2.1», The user you are trying to contact is receiving mail at a rate that prevents additional messages from being delivered. For more information, visit Limits for sending & getting mail. (Пользователь, которому вы пытаетесь отправить письмо, получает почту со скоростью, которая не позволяет доставлять ему дополнительные сообщения. Дополнительная информация приведена в статье Ограничения на отправку и получение писем.) |
| 550, «5.4.5», Daily sending quota exceeded. For more information, visit Email sending limits. (Исчерпан дневной лимит на отправку сообщений. Дополнительная информация приведена в статье Ограничения в Google Workspace на отправку электронных писем из Gmail.) |
| 550, «5.4.5», Daily SMTP relay limit exceeded for user. For more information on SMTP relay sending limits please contact your administrator or visit SMTP relay service error messages. (Превышено суточное ограничение на ретрансляцию для клиента. Чтобы получить подробную информацию об ограничениях, ознакомьтесь с этой статьей или свяжитесь с администратором.) |
| 550, «5.7.0», Mail relay denied. (Почтовый ретранслятор запрещен.) |
| 550, «5.7.0», Mail Sending denied. This error occurs if the sender account is disabled or not registered within your Google Workspace domain. (Отправка почты запрещена. Эта ошибка возникает, если аккаунт отправителя заблокирован или не зарегистрирован в домене Google Workspace.) |
| 550, «5.7.1», Email quota exceeded. (Превышена квота электронной почты.) |
| 550, «5.7.1», Invalid credentials for relay. (Неверные учетные данные ретранслятора.) |
| 550, «5.7.1», Our system has detected an unusual rate of unsolicited mail originating from your IP address. To protect our users from spam, mail sent from your IP address has been blocked. Review Prevent mail to Gmail users from being blocked or sent to spam. (C вашего IP-адреса с необычной частотой поступают незапрашиваемые сообщения. Почта, отправляемая с вашего IP-адреса, заблокирована для защиты пользователей от спама. Подробную информацию читайте в статье Как предотвратить блокировку почты, предназначенной пользователям Gmail, или ее отправку в папку «Спам».) |
| 550, «5.7.1», Our system has detected that this message is likely unsolicited mail. To reduce the amount of spam sent to Gmail, this message has been blocked. For more information, visit Why has Gmail blocked my messages? (Это сообщение было классифицировано системой как вероятный спам и заблокировано в целях уменьшения количества спама, отправляемого в Gmail. Дополнительная информация приведена в статье Почему мои письма в Gmail заблокированы.) |
| 550, «5.7.1», The IP you’re using to send mail is not authorized to send email directly to our servers. Please use the SMTP relay at your service provider instead. For more information, visit ‘The IP you’re using to send email is not authorized…’. (IP-адрес, который используется для отправки почты, не имеет разрешения на отправку сообщений непосредственно на наши серверы. Используйте для отправки ретранслятор SMTP своего поставщика услуг. Дополнительная информация приведена в этой статье.) |
| 550, «5.7.1», The user or domain that you are sending to (or from) has a policy that prohibited the mail that you sent. Please contact your domain administrator for further details. For more information, visit Sorry, a policy is in place that prevents your message from being sent. (Для пользователя или домена, от которого или которому отправляются сообщения, установлено правило, запрещающее отправленную вами почту. Для получения дополнительной информации ознакомьтесь с этой статьей и обратитесь к своему администратору домена.) |
| 550, «5.7.1», Unauthenticated email is not accepted from this domain. (Почта без аутентификации от этого домена не принимается.) |
| 550, «5.7.1», Daily SMTP relay limit exceeded for customer. For more information on SMTP relay sending limits please contact your administrator or visit SMTP relay service error messages. (Превышено суточное ограничение на ретрансляцию для клиента. Чтобы получить подробную информацию об ограничениях, ознакомьтесь со статьей Сообщения об ошибках службы ретрансляции SMTP или свяжитесь с администратором.) |
| 550, «5.7.26», Unauthenticated email from domain-name is not accepted due to domain’s DMARC policy. Please contact the administrator of domain-name domain. If this was a legitimate mail please visit Control unauthenticated mail from your domain to learn about the DMARC initiative. If the messages are valid and aren’t spam, contact the administrator of the receiving mail server to determine why your outgoing messages don’t pass authentication checks. (Электронное письмо от [доменное имя] не прошло аутентификацию и запрещено правилами DMARC домена. Обратитесь к администратору домена. Если письмо запрещено по ошибке, ознакомьтесь со сведениями об инициативе DMARC в статье «Проблемы с проверкой подлинности сообщений из вашего домена» и обратитесь к администратору почтового сервера получателя, чтобы определить, почему ваши исходящие письма не проходят аутентификацию.) |
|
550, «5.7.26», «This message does not have authentication information or fails to pass authentication checks (SPF or DKIM). To best protect our users from spam, the message has been blocked. Please visit Prevent mail to Gmail users from being blocked or sent to spam for more information.» (Для этого письма нет информации о прохождении аутентификации (SPF или DKIM), или оно ее не прошло. Оно заблокировано, чтобы защитить наших пользователей. Более подробная информация приведена в статье «Как предотвратить блокировку почты, предназначенной пользователям Gmail, или ее отправку в папку «Спам».) |
| 550, «5.7.26», «This message fails to pass SPF checks for an SPF record with a hard fail policy (-all). To best protect our users from spam and phishing, the message has been blocked. Please visit Prevent mail to Gmail users from being blocked or sent to spam for more information.» (Это письмо не прошло проверки SPF для записи со строгими правилами (-all). Оно заблокировано, чтобы защитить наших пользователей от спама и фишинга. Более подробная информация приведена в статье «Как предотвратить блокировку почты, предназначенной пользователям Gmail, или ее отправку в папку «Спам».) |
| 552, «5.2.2», The email account that you tried to reach is over quota. (Для аккаунта электронной почты получателя превышена квота.) |
| 552, «5.2.3», Your message exceeded Google’s message size limits. For more information, visit Send attachments with your Gmail message. (Превышен максимально допустимый размер сообщения. Дополнительная информация приведена в статье Прикрепление файлов к письмам в Gmail.) |
| 553, «5.1.2», We weren’t able to find the recipient domain. Please check for any spelling errors, and make sure you didn’t enter any spaces, periods, or other punctuation after the recipient’s email address. (Не удалось найти домен получателя. Проверьте правильность адреса электронной почты получателя и убедитесь, что после него нет пробелов, точек и других знаков пунктуации.) |
| 554, «5.6.0», Mail message is malformed. Not accepted. (Сообщение электронной почты не принято, так как имеет недопустимый формат.) |
| 554, «5.6.0», Message exceeded 50 hops, this may indicate a mail loop. (Сообщение пересылалось более 50 раз, что может указывать на наличие почтового цикла.) |
| 554, «5.7.0», Too Many Unauthenticated commands. (Слишком много команд без аутентификации.) |
| 555, «5.5.2», Syntax error. (Синтаксическая ошибка.) |
Эта информация оказалась полезной?
Как можно улучшить эту статью?
- Remove From My Forums
-
Question
-
While analyzing my SmtpReceive logs in Exchange 2010 I am noticing that the return code:
354 Start mail input; end with <CRLF>.<CRLF>,
…does not always appear in a successful email transaction. I can confirm that the message was successfully sent, and delivered — but I’m curious why that ‘354’ return code is sometimes present, and sometimes not.
Can you please help me understand?
Thanks,
ND
Answers
-
That’s an interesting one I’ve not seen before.
From here:
http://tools.ietf.org/html/rfc18305. Examples
5.1 Simple Chunking
The following simple dialogue illustrates the use of the large
message extension to send a short psudo-RFC822 message to one
recipient using the CHUNKING extension:R: <wait for connection on TCP port 25>
S: <open connection to server>
R: 220 cnri.reston.va.us SMTP service ready
S: EHLO ymir.claremont.edu
R: 250-cnri.reston.va.us says hello
R: 250 CHUNKING
S: MAIL FROM:<Sam@Random.com>
R: 250 <Sam@Random.com>… Sender ok
S: RCPT TO:<Susan@Random.com>
R: 250 <Susan@random.com>… Recipient ok
S: BDAT 69 LAST
S: To:
<LF»>Sam@random.com<CR><LF>
S: Subject: This is a bodyless test message<CR><LF>
R: 250 Message OK, 69 octets received
S: QUIT
R: 221 Goodbye5.2 Pipelining Binarymime
The following dialogue illustrates the use of the large message
extension to send a BINARYMIME object to two recipients using the
CHUNKING and PIPELINING extensions:R: <wait for connection on TCP port 25>
S: <open connection to server>
R: 220 cnri.reston.va.us SMTP service ready
S: EHLO ymir.claremont.edu
R: 250-cnri.reston.va.us says hello
R: 250-PIPELINING
R: 250-BINARYMIME
R: 250 CHUNKING
S: MAIL FROM:<ned@ymir.claremont.edu> BODY=BINARYMIME
S: RCPT TO:<gvaudre@cnri.reston.va.us>
S: RCPT TO:<jstewart@cnri.reston.va.us>
R: 250 <ned@ymir.claremont.edu>… Sender and BINARYMIME ok
R: 250 <gvaudre@cnri.reston.va.us>… Recipient ok
R: 250 <jstewart@cnri.reston.va.us>… Recipient ok
S: BDAT 100000
OWA For SmartPhone
www.leederbyshire.com-
Marked as answer by
Saturday, November 9, 2013 5:11 AM
-
Marked as answer by