Todos os códigos de erros SMTP - Mail Delivery System - PDF

Todos os códigos de erros SMTP - Mail Delivery System Este documento faz parte do artigo sobre erros de Mail Delivery System encontrado no site Dicas para Computad. O texto iginal deste arquivo em PDF

Please download to get full document.

View again

of 20
All materials on our website are shared by users. If you have any questions about copyright issues, please report us to resolve them. We are always happy to assist you.


Publish on:

Views: 166 | Pages: 20

Extension: PDF | Download: 0

Todos os códigos de erros SMTP - Mail Delivery System Este documento faz parte do artigo sobre erros de Mail Delivery System encontrado no site Dicas para Computad. O texto iginal deste arquivo em PDF foi elabado pela AnswersThatWk. 101 Cannot open connection SMTP Err 101 : Typically your SMTP server program is unable to even start an SMTP session. Typical replies will be SMTP Err 101, Err opening connection SMTP Err 101, cannot open SMTP stream. (also called SMTP Err 1.0.1) All SMTP Err 101 errs usually point to a configuration problem, such as an increctly spelt SMTP server, an IP address that does not exist, an SMTP pt that does not exist which the recipient will not accept SMTP connections on, some other process is already using the default SMTP pt, pt Connection refused (also called SMTP Err 1.1.1) SMTP Err 111 :Typically from Linux based systems such as SquirrelMail and Mailman. The message will usually go like this : Connection refused, 111 Can t open SMTP stream. All SMTP Err 111 errs usually point to an inability of your server to communicate with the remote SMTP server (either the recipient s SMTP server your ISP s SMTP server) to a Linux/SMTP software configuration problem, typically /etc/hosts not being wld readable, a newly installed reconfigured firewall preventing connection to the remote SMTP server, increct hostnames and/ domains (e.g. does your sending hostname match your IP address in a reverse lookup?), exim not running. Telnet and logs should help you home in on the problem. 211 System Status message System Help Reply (also called SMTP Err 2.1.1) SMTP Err 211 : SMTP status 211 prefaces a message about the Mail Server status a System Help reply to the user requesting help infmation. You might f 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. 214 Help Reply message (also called SMTP Err 2.1.4) SMTP Err 214 : SMTP status 214 is usually in reply to the HELP command. It displays infmation about the server, usually a URL to the FAQ page of the SMTP software running on the server. As a result this err is nmally called a reply, as in SMTP Reply Server Name service is running (also called SMTP Err 2.2.0) SMTP Status 220 : This is nmally the first message you will get back from the server. It means the mail service is running (ie. your mail server is running). It will nmally contain a welcome message and/ the title of the SMTP software and, sometimes, the version number of the mail server software. SMTP Reply 220 is effectively a Hi There, I have just this second finished starting up I am ready to go and at your command infmational message. Page 2 of 25 221 The domain service is closing the transmission channel SMTP Err 221 : The server is ending the mail session it is closing the conversation with the ISP as it has no me mail to send in this sending session. (also called SMTP Err 2.2.1) SMTP Status 221 is often misconstrued as an err condition, when it is in fact nothing of the st. The mail server is simply telling you that it has processed everything it was given in this particular session, and it is now going back into waiting mode. Because SMTP status 221 is often misinterpreted, with some mail servers the Netwk Administrats have changed the default text of SMTP Reply 221 to something me meaningful and less alarming. F example, a typical SMTP reply 221 might say 221 Goodbye 221 Closing connection, the most irritating one we ve seen 221 Bye, Arrrgghh can you blame anyone f thinking there might be a problem? Of course not! So some Netwk Administrats are these days being quite imaginative by changing the default text of SMTP reply 221 to me user friendly messages like : 221 Thank you f your business (I love that one!), 221 All messages processed successfully in this session, SMTP connection is closing. 250 Requested mail action OK completed (also called SMTP Err 2.5.0) 251 User not local will fward (also called SMTP Err 2.5.1) SMTP Status 250 : The mail server has successfully delivered the message! This is the best SMTP reply (250) to receive - your message has been accepted and transmitted OK! Yippee. 250 is effectively a status code rather than an err code there is no such thing as an SMTP err 250. SMTP Status 251 : The account is not local to the ISP server but the ISP server will accept the and will fward it (the server will RELAY your message, this is the most common action f ISP Mail servers the recipient will see your ISP in the mail header as one of the first hops on the way to the recipient s system). SMTP Err 251 is therefe me of an infmational message f technicians tracking how a message reached its destination. Page 3 of 25 252 Cannot VRFY (verify) the user the server will accept the message and attempt to deliver it (also called SMTP Err 2.5.2) SMTP Status 252 : The user account appears to be valid but could not be verified, however the server will try do deliver the message. There are sometimes circumstances where an address appears to be valid but cannot be verified as definitely valid during the SMTP session between the sending server (your server) and the next server to accept your message. This can happen f example in very large cpation where the first receiving server might only be an exchanger server, a gateway server to the eventual server which holds the user mailboxes and which can verify if the intended recipient exists in that ganization. When this happens the gateway server will reply with an SMTP Err 252 telling your sending server that it cannot verify the user part of the address, that the domain part is OK, and that it will fward your to a server which can do the checking and eventually deliver to the user mailbox if it exists. 354 Start mail input end with CRLF . CRLF ,, as a less cryptic description FROM and TO infmation received, now please provide message body and mark its end with CRLF . CRLF SMTP Err 354 : This is nmally in response to the DATA command. The server has received the From and To infmation and is now asking f the Message Body, the main part of the message which should be ended by two blank lines separated by a dot (period). Therefe, on receiving an SMTP Reply 354 the sending server should send the body of the message to the receiving server and indicate the end of the message body with CRLF . CRLF (note the full stop between the two Carriage_Return-Line_Feed s). (also called SMTP Err 3.5.4) Page 4 of 25 420 Timeout communication problem encountered during transmission. This is a Novell GroupWise SMTP err (also called SMTP Err 4.2.0) SMTP Err 420 :In our experience only Novell GroupWise servers use this err (we use GroupWise!). You will get a GroupWise GWIA (GroupWise Internet Agent) 420 TCP Write Err 420 TCP Read Err if there are communication problems during transmission of the actual message after the sending and receiving servers have actually connected. A small number of 420 SMTP errs is nmal as occasional peaks of Internet usage may delay the transmission of an with attachment so much that a timeout occurs. When a timeout occurs on a GWIA send, the message is queued up in the Domain \WPGATE\DEFER directy f processing at a later time (as defined in ConsoleOne GWIA.CFG). If you experience 420 errs only with specific recipient then it is quite likely that the recipient s antispam firewall does not like your server, your server s external IP address, that your server s HELO command uses an outbound identification that does not match your server s external IP address (check that your sending domain s DNS is set up crectly). In an ideal wld a well behaved recipient server should really be issuing your GroupWise server with a 554 err rather than timing out and causing the GroupWise GWIA to fault with a 420 err. If you experience too many 420 errs with all communications, then you have a physical communication problem somewhere. This could be your server s netwk card, the netwk point that your server is plugged into, your switch(es), your router(s), your firewall, your Internet line problems caused by routers with different MTU sizes is a classic issue. Unless the logs of all those various problem points can give you an instant answer, the only way you will get to the bottom of the problem is to use a packet tracing and inspection program like Ethereal Wireshark, its success, if you re running GroupWise on a Windows Linux server; on NetWare your only choice is PacketScan which you cangethere In the final analysis, if the tracing of packets, and the changing of hardware does not help then do not discount a slightly faulty hard disk being the cause of all your problems (even if your RAID controller your hard disk testing software does not detect any problem!). Page 5 of 25 421 Server name Service not available the sending program should try again later SMTP Err 421 :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. The SMTP service /server you use has a limit on the number of concurrent SMTP streams your server can use F example, the server administrat may have stopped the mail service to troubleshoot a problem, the mail server is right in the middle of rebooting, the mail server is currently processing too many incoming messages incoming requests, etc... Note : 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, the recipient s mail server. (also called SMTP Err 4.2.1) Clearly, if you repeatedly receive an SMTP status 421 then the problem is no longer of a transient nature and you need to investigate infm the relevant netwk administrat, ISP tech suppt, the recipient. -- SMTP Response 421 can also be received as a result of your message server sending an where the total number of TO, CC, and BCC users results in a number of simultaneous SMTP connections that is in excess of the number of connections your ISP SMTP service allows. A typical err message f this situation would be : 421 Too many concurrent SMTP connections from this IP address; please try again later. Typically, when this happens your server will have sent some of the messages (note that f all servers, each sent by a user always gets broken down into individual separate s to each of the recipients in the TO, CC, and BC fields), and will automatically retry a little later to send the remaining messages. 422 The recipient s mailbox is over its stage limit The size of the message exceeds the recipient s size limits f incoming s SMTP Err 422 : Either the recipient s mailbox is over its stage limit the message delivery directy (folder) on the recipient s mail server is currently over a size limit imposed by the Netwk Administrat (e.g. possibly as a result of the mail server having been down f some time, having been repaired, and currently in the process of collecting thousands of queued up messages). However, SMTP response 422 can also be received if the being sent is larger than the incoming s size limit in operation at the recipient s mail server (particularly when that recipient s mail server is Exchange Server). (also called SMTP Err 4.2.2) 431 The recipient s mail server is experiencing a Disk Full condition (also called SMTP Err 4.3.1) SMTP Err 431 :The recipient s mail server is experiencing a Disk Full err condition, an Out of Memy (too many file handles) err condition (Microsoft Exchange). Page 6 of 25 432 The recipient s Exchange Server incoming mail queue has been stopped SMTP Err 432 :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 Netwk Administrat troubleshoots some problem. (also called SMTP Err 4.3.2) 441 The recipient s server is not responding (also called SMTP Err 4.4.1) SMTP Err 441 : This is an err 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. (also called SMTP Err 4.4.2) SMTP Err 442 :Your server started delivering the message but the connection was broken during transmission. This may be an unusual transient err however, if it keeps happening you should investigate possible problems with your server s netwk card, your Internet routers, processes hogging the resources of your server, and anything else which could result in a netwk connection being broken. 446 The maximum hop count was exceeded f the message (also called SMTP Err 4.4.6) SMTP Err 446 :The maximum hop count was exceeded f your message. The most likely cause of this err status code is that your message is looping internally on your server, internally between two of your ganisation s servers,, sometimes, looping between your server and the recipient s server. 447 Your outgoing message timed out. (also called SMTP Err 4.4.7) SMTP Err 447 :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, a protocol timeout between the two servers). 449 Routing err (also called SMTP Err 4.4.9) SMTP Err 449 : This is a Microsoft Exchange Server specific err code. As per Microsoft s documentation this err code is returned when either of the following conditions occurs : an SMTP connect is configured to use DNS without a smart host and also uses a non-smtp address space (e.g. X.400), A message was sent to a recipient who was identified as a member of a routing group that was deleted. Microsoft recommends using the WinRoute tool to troubleshoot this err (Microsoft Knowledgebase article ) Page 7 of 25 450 Requested action not taken The mailbox was unavailable at the remote end. A secondary SMTP err code may follow 450 to refine the reason f the failure to transmit the message, e.g. SMTP Err 450 (also called SMTP Err 4.5.0) SMTP Err 450 : The server could not access the mailbox to deliver the message. This could be caused by a process on the remote server tidying up the mailbox, the remote mailbox could be crupt, the remote mailbox may be sted on another server which is currently offline, the netwk connection went down while sending, the remote mail server does not want to accept mail from your server f some reason (IP address, blacklisting, etc..). In general SMTP Err 450 is a transient err at the remote end (the destination), at one of the routers servers en route to the remote end, and should induce your mail server to retry after it s preset retry interval. Example of an SMTP Err 450 reply message : 450 Please try again later, a classic Novell GroupWise 450 status message : The message that you sent has been delayed. The reason given f the delay: 450 Host down ( SMTP Err 450 is often followed by a second SMTP err code to refine the reason f the not reaching its destination. F example : SMTP Err Msg Size greater than allowed by Remote Host. When that is the case and If the err message is not as clearly wded as in this example, then simply search this document f the secondary err code. In this case searching this document f SMTP Err 523 SMTP Err would yield an explanation identical to the wding above. Page 8 of 25 451 Requested action abted Local err in processing. Requested action delayed Local problem IP_Address has recently sent spam (also called SMTP Err 4.5.1) SMTP Err 451 : The action has been abted by the ISP s server. Local (Local Problem, Local Err) refers to the next server that your message will go through after leaving your server, typically your ISP s server, the SMTP relaying service you are using,, if your mail server is sending directly to the destinations, the destination mail server. This err is usually due to overloading at your ISP your SMTP relaying service from [temparily] too many messages some other similar transient failure.typically some [hopefully] tempary event prevents the successful sending of the message. The next attempt to send by your server may prove successful. If this err keeps occurring to the point that it has effectively lost its transient nature and has become... frequent (!!), then the problem is at your end and you should check your own mail server (if you out of a cpate netwk), communications on your side (router, server netwk card), infm your ISP if your mail server relays through your ISP if you are a home user ing out through Outlook, Outlook Express, Windows Mail, similar program. Examples of typical SMTP Err 451 return messages : SMTP err 451 Unable to complete command, DNS not available timed out 451 Domain of sender address does not resolve 451 Err getting LDAP results in map, Greylisting in action, please come back in 00:02:00 [minutes] The message that you sent has been delayed. The reason given f the delay : 451 Tempary local problem - please try later.. -- With the iginal SMTP standards having been invented befe spam became the scourge of the Internet, there are no SMTP err codes dedicated to anti-spam errs. As a result, SMTP Err 451 is now increasingly also used to indicate that a message has been rejected by the remote server because of anti-spam measures. A typical err might be, f example : SMTP err from remote mail server after end of data, host host_address : 451 ip_address has recently sent spam. If you are not a spammer, please try later.. If all anti-spam related SMTP 451 errs are as descriptive as the one above, then the err itself will tell you what you need to do. As a general rule, however, you will most times need to take some measures to have either your server, your ISP s server, taken off some Internet blacklist used by the recipient. Page 9 of 25 452 Requested action not taken Insufficient stage. (also called SMTP Err 4.5.2) SMTP Err 452 : The ISP server s disk system has run out of stage space, so the action had to be cancelled. Unless you are with an ISP which is so slack that they have not implemented Disk Full Alerts, this err usually indicates that your ISP s mail server is overloaded from too many messages. This can happen even to the best ISPs when, f example, there have been problems and none of the ISP s customers could send mail; as soon as the problems are fixed there is almost always a situation where thousands of users and ganizations are trying to send mail all at the same time, and those numbers can occasionally result in the ISP s mail servers hard disks temparily filling up, with SMTP Err 452 being the result. The next attempt to send by your server may prove successful. SMTP Err 452 : Most ISPs mail servers impose a maximum number of concurrent connections that client s mail servers can attempt to make, and they usually also have a limit on the number of messages that are sent per connection. With business customers these maximums are rarely reached, if ever. Nevertheless, If you have a lot of messages queued up, f example as a result of the connection to your ISP going down f a significant amount of time (and you have hundreds of users in your ganization, it happened just as you were about to send that large mailshot!), there could be a situation where the output of messages from your server goes over the maximum number of messages per connection allowed by your ISP. This is another case where the ISP s server may issue a 452 SMTP err. As above, the next attempt to send by your server may prove successful. SMTP Err 452 : This err can also be indicative of a problem on your own mail server. Here is an example of an SMTP 452 err : 452 Out of memy 465 Code Page unavailable on the recipient server (also called SMTP Err
Related Search
We Need Your Support
Thank you for visiting our website and your interest in our free products and services. We are nonprofit website to share and download documents. To the running of this website, we need your help to support us.

Thanks to everyone for your continued support.

No, Thanks