Quick Tour

Product Info

  Freeware eMail CRM Maximize the life-time value of your clients and getting them to smile at you Art of eMail CRM Applying minimum efforts for maximum result, at the shortest time? emails eMail Bolts & Nuts Interesting emails stuff that you should  know eMail Broadcast FAQ's eMail Marketing Tips
Great email strategies to help you increase sales
Extension to the SMTP service RFC codes
Returning Enhanced Email Error Codes to provide more
informative explanations of email error conditions...

RFC defined ESMTP Status Error Codes
ESMTP Status Error Codes Command Group
Definition of extension to the SMTP service RFC-821
Winsock Error Codes
Mail Object Error Message

Network Working Group, Request for Comments: RFC 2034 www.cis.ohio-state.edu/cgi-bin/rfc/rfc2034.html
Category: Standards Track, N. Freed, Innosoft, Oct 1996

Page 1

SMTP Service Extension for

Returning Enhanced Error Codes

Status of this Memo

This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1)
www.csi-ohio-state.edu/cgi-bin/rfc/stdlist.htm#s1 for the standardization state and status of this protocol.
Distribution of this memo is unlimited.

1 Abstract

eMail Bolts & Nuts FAQ's
How to manage and clean bounced or undelivered emails? Understand why emails get bounced
How to use your desktop PCs as an email server and bypass your ISP email server, a simple process using a free mail server program
How to test your message and see if it gets deleted by broad based anti-spam filters?
A one page email course. Everything you wanted to know about emailing in a "nut shell"
Quick guide to: dig finger traceroute ping whois nslookup IP block FTP SMTP relay TCP/IP Port
How to embed email tracking code into your email? Invisible counters, codes, scripts to track viewer
Send HTML or TEXT email using formatted HTML email, you can send an entire webpage
How to embed images into HTML email for faster emailing? Prevent displaying linked-site in recipient email client status bar
RFC defined ESMTP, SMTP Status Email Error Codes? These codes are used to provide informative explanations of error conditions
How email works?  Delivery of each email is done
by your ISP mail server, first establishing a conversation through your recipient port 25
Some spiders visit site after site, collecting email addresses and controlling these rogue spiders spam bots or email harvesters with robot.txt
About TCP/IP and mail server port numbers? It is a number between 1 and 65535 which identifies to the receiving computer what function you want to perform

This memo defines an extension to the SMTP service RFC-821www.cis.ohio-state.edu/cgi-bin/rfc/rfc0821.html
RFC- 1869] whereby an SMTP server augments its responses with the enhanced mail system status codes defined in RFC 1893 

These codes can then be used to provide more informative explanations of error conditions, especially in the context of the delivery status notifications format defined in RFC 1894

2 Introduction

Although SMTP is widely and robustly deployed, various extensions have been requested by parts of the Internet community. In particular, in the modern, international, and multilingual Internet a need exists to assign codes to specific error conditions that can be translated into different languages.

RFC 1893 www.cis.ohio-state.edu/cgi-bin/rfc/rfc1893.html defines such a set of status codes and RFC 1894 www.cis.ohio-state.edu/cgi-bin/rfc/rfc1894.html defines a mechanism to send such coded material to users.

However, in many cases the agent creating the RFC 1894 delivery status notification is doing so in response to errors it received from a remote SMTP server.

As such, remote servers need a mechanism for embedding enhanced status codes in their responses as well as a way to indicate to a client when they are in fact doing this.

This memo uses the SMTP extension mechanism described in RFC 1869 www.cis.ohio-state.edu/cgi-bin/rfc/rfc1869.html define such a mechanism.

eMail Bolts & Nuts FAQ's
The function of URL or Uniform Resource Locator?
A command for your email address, some mail clients may not be able to translate it into an email address
A standard client server protocol for receiving email. POP3 is use for retrieving Internet email from ISPs mail server...
Collections of important useful emails related sites? Free email stuff, real cool, give it a try
Advanced DNS (dig) for the DNS records of a host or domain showing all the DNS records
All about IP Addresses, DNS, Internet addressing. Serious stuff, perfect remedy if you can't sleep
Email history, email netiquette, improving email presentation, email with sound, pictures--give it a try
101 Email spam tracking and meaning of message header? 102 DejaNews the most powerful dedicated spam-tracker's tool 103 The spam tracker tools: Whois, nslookup, traceroute, dig 104 Spam tracking
Never use ISPs that hosts your web site to send out newsletter. If they cancel your account, you will lose all your web pages
Warning: If you publish an online newsletter or email to any opt-in list (including your own list), it is critical that you read this
The history of Spam starts with Monty Python's Flying Circus and Vikings singing Spam
A list of return error codes by Windows Sockets API returned by WSAGetLastErrorcall with descriptions
Meet The Kings of SPAM - You don't need rocket science to figure out how to send spam emails

Page 2

3 Framework for the Enhanced Error Statuses Extension

The enhanced error statuses transport extension is laid out as follows:

1)the name of the SMTP service extension defined here is
2)the EHLO keyword value associated with the extension is
3)no parameter is used with the ENHANCEDSTATUSCODES EHLO Keyword;
4)the text part of all 2xx, 4xx, and 5xx SMTP responses other than the 
initial greeting and any response to HELO or EHLO are prefaced with a 
status code as defined in RFC 1893. This status code is always
followed by one or more spaces.
5)no additional SMTP verbs are defined by this extension; and,
6)the next section specifies how support for the extension affects the
behavior of a server and client SMTP.

4 The Enhanced-Status-Codes service extension

Servers supporting the Enhanced-Status-Codes extension must preface the text part of almost all response lines with a status code. As in RFC 1893, the syntax of these status codes is  given by the ABNF:

        status-code ::= class "." subject "." detail
        class       ::= "2" / "4" / "5"
        subject     ::= 1*3digit
        detail      ::= 1*3digit

These codes must appear in all 2xx, 4xx, and 5xx response lines other than initial greeting and any response to HELO or EHLO. Note that 3xx responses are NOT included in this list.

All status codes returned by the server must agree with the primary response code, that is, a 2xx response must incorporate a 2.X.X code, a 4xx response must incorporate a 4.X.X code, and a 5xx response must incorporate a 5.X.X code.

Spam-tracking 103 WHOIS tool nslookup and traceroute freeware download
whois.internic.net or network solutions are network registries to find out contact info for current domain or IP address
nslookup a DNS tool that Perform forward and reverse DNS queries for the current address (this will usually give you the IP address of a hostname)
traceroute finds the route packets take between you and the selected address
Email in a "nut shell" a one page course about emailing. Everything you wanted to know about emailing.
How email works? Delivery of each email is done by your ISP mailserver establishing a conversation through (port 25) of your recipient mail server
Free2-Try 100% effective. The easiest way to Stop Spam getting into your PC. I recommend it. stop spam
Free eBook Sun Tzu Art of War Commanders without thoughtful strategy invite defeat.

Sun Tzu

Free eBook Great online Stealth Marketing strategies to help you increase sales email tips


Page 3

When responses are continued across multiple lines the same status code must appear at the beginning of the text in each line of the response.

Servers supporting this extension must attach enhanced status codes to their responses regardless of whether or not EHLO is employed by the client.

5 Status Codes and Negotiation

This specification does not provide a means for clients to request that status codes be returned or that they not be returned; a compliant server includes these codes in the responses it sends regardless of whether or not the client expects them.

 This is somewhat different from most other SMTP extensions, where generally speaking a client must specifically make a request before the extended server behaves any differently than an unextended server.

The omission of client negotiation in this case is entirely intentional: Given the generally poor state of SMTP server error code implementation it is felt that any step taken towards more comprehensible error codes is something that all clients, extended or not, should benefit from.

The use of this approach in this extension should be seen as a very special case. It MUST NOT be taken as a license for future SMTP extensions to dramatically change the nature of SMTP client-server interaction without proper announcement from the server and a corresponding enabling command from the client.

6 Usage Example
The following dialogue illustrates the use of enhanced status codes by a server:

S: <wait for connection on TCP port 25>
C: <open connection to server>
S: 220 dbc.mtview.ca.us SMTP service ready
C: EHLO ymir.claremont.edu
S: 250-dbc.mtview.ca.us says hello
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


Page 4

S: 551 5.7.1 Select another host to act as your forwarder
S: 354 Send message, ending in CRLF.CRLF
C: .
S: 250 2.6.0 Message accepted
S: 221 2.0.0 Goodbye

The client that receives these responses might then send a nondelivery notification of the general form:

Date: Mon, 11 Mar 1996 09:21:47 -0400
From: Mail Delivery Subsystem <mailer-daemon@ymir.claremont.edu> Subject: Returned mail
To: <ned@ymir.claremont.edu>
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status; boundary="JAA13167.773673707/YMIR.CLAREMONT.EDU"

      content-type: text/plain; charset=us-ascii
         ----- Mail was successfully relayed to
               the following addresses -----
-- The following addresses had delivery problems --
        (Mailbox "nosuchuser" does not exist)
        (Forwarding to remote hosts disabled)
      content-type: message/delivery-status

Reporting-MTA: dns; ymir.claremont.edu

Original-Recipient: rfc822;mrose@dbc.mtview.ca.us
Final-Recipient: rfc822;mrose@dbc.mtview.ca.us
Action: relayed
Status: 2.1.5 (Destination address valid)
Diagnostic-Code: smtp;
250 Recipient <mrose@dbc.mtview.ca.us> ok
Remote-MTA: dns; dbc.mtview.ca.us


Page 5

Original-Recipient: rfc822;nosuchuser@dbc.mtview.ca.us Final-Recipient: rfc822;nosuchuser@dbc.mtview.ca.us
Action: failed
Status: 5.1.1 (Bad destination mailbox address)
Diagnostic-Code: smtp;
550 Mailbox "nosuchuser" does not exist
Remote-MTA: dns; dbc.mtview.ca.us

Original-Recipient: rfc822;remoteuser@isi.edu
Final-Recipient: rfc822;remoteuser@isi.edu
Action: failed
Status: 5.7.1 (Delivery not authorized, message refused) Diagnostic-Code: smtp;
551 Forwarding to remote hosts disabled
Select another host to act as your forwarder
Remote-MTA: dns; dbc.mtview.ca.us

      content-type: message/rfc822

[original message goes here]


Note that in order to reduce clutter the reporting MTA has omitted enhanced status code information from the diagnostic-code fields it has generated.

7 Security Considerations

Additional detail in server responses axiomatically provides additional information about the server. It is conceivable that additional information of this sort may be of assistance in circumventing server security. The advantages of provides additional information must always be weighed against the security implications of doing so.


Page 6

8 References

[RFC-821] www.cis.ohio-state.edu/cgi-bin/rfc/rfc0821.html
Postel, J., "Simple Mail Transfer Protocol", RFC 821 August, 1982. (August, 1982).

[RFC-1869] www.cis.ohio-state.edu/cgi-bin/rfc/rfc1869.html
Rose, M., Stefferud, E., Crocker, C., Klensin, J., Freed, N., "SMTP Service Extensions", RFC 1869, November, 1995.

[RFC-1893] www.cis.ohio-state.edu/cgi-bin/rfc/rfc1893.html
Vaudreuil, G., "Enhanced Mail System Status Codes", RFC 1893, January, 1996.

[RFC-1894] www.cis.ohio-state.edu/cgi-bin/rfc/rfc1894.html
Moore, K., Vaudreuil, G., "An Extensible Message Format for Delivery Status Notifications", RFC 1894, January, 1996.

9 Author Address
Ned Freed, Innosoft International, Inc., 1050 East Garvey Avenue South , West Covina, CA 91790 USA, tel: +1 818 919 3600, fax: +1 818 919 3614, email: ned @ innosoft.com



Can't find
what you want?

Try Google...







Suggestions or feed-back, please drop us a note  |  eMail CRM Freeware  | This site>>eMail Bolts & Nuts

Home | Guest Book | Refund Policy | Privacy Policy | Contact Us | Support | Purchase | Product Info | Quick Tour

Minute WisdomSun Tzu Art of War | Useful Sites | eMail Broadcast FAQ's | Art of eMail CRM | eMail Marketing Tips