SMTP error codes 213
sujit
I am getting error code 213 from SMTP server. What does it mean?
I gone through some material on web and it looks like
2 - first digit- indicates success
1- second digit - indicates informational message
3 - third digit - Not too sure what does it mean
From web I got refs for other error codes like
200 (nonstandard success response, see rfc876)
211 System status, or system help reply
214 Help message
220 <domain> Service ready
221 <domain> Service closing transmission channel
250 Requested mail action okay, completed
251 User not local; will forward to <forward-path>
But nothing for error code 213.
Can anyone help me with
1. Understanding what RFC is implemented by my SMTP implementer
2. Is there any RFC which specifies and describes 213 as some
meaningful error code. If yes what is RFC number?
Can i safely ignore this smtp error code without any issues. Can i
code something like
if ( smtp_error_code%100==2 )
//ignore error
else
//do some error handling
Is such kind of code normal protocol when you are sending emails
programmatic by using smtp?
Thanks
-Sujit
Barry Margolin
<0732b2a9-1b73-42fd...@j20g2000vbp.googlegroups.com>,
sujit <sujitku...@gmail.com> wrote:
> Hi,
>
> I am getting error code 213 from SMTP server. What does it mean?
>
> I gone through some material on web and it looks like
> 2 - first digit- indicates success
> 1- second digit - indicates informational message
> 3 - third digit - Not too sure what does it mean
>
> From web I got refs for other error codes like
> 200 (nonstandard success response, see rfc876)
> 211 System status, or system help reply
> 214 Help message
> 220 <domain> Service ready
> 221 <domain> Service closing transmission channel
> 250 Requested mail action okay, completed
> 251 User not local; will forward to <forward-path>
>
> But nothing for error code 213.
>
> Can anyone help me with
> 1. Understanding what RFC is implemented by my SMTP implementer
> 2. Is there any RFC which specifies and describes 213 as some
> meaningful error code. If yes what is RFC number?
It's not in RFC 5321, which is less than a year old, so I don't think
it's an officially recognized code.
Most SMTP replies include some human-readable text after the code. What
does it say?
--
Barry Margolin, bar...@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
*** PLEASE don't copy me on replies, I'll read them in the group ***
Gordon Burditt
*WHICH* SMTP server? It may identify itself (software package and
perhaps version) when you connect to it on port 25. In response
to what command? Or is this on initial connect?
Is there any human-readable text with the response?
>I gone through some material on web and it looks like
>2 - first digit- indicates success
>1- second digit - indicates informational message
>3 - third digit - Not too sure what does it mean
I haven't found anything referencing that code either. I do vaguely
recall some odd codes that I don't see any more (like "payment
required") which may exist only in superceeded RFCs. Or maybe I
remember incorrectly ever seeing it.
>From web I got refs for other error codes like
>200 (nonstandard success response, see rfc876)
>211 System status, or system help reply
>214 Help message
>220 <domain> Service ready
>221 <domain> Service closing transmission channel
>250 Requested mail action okay, completed
>251 User not local; will forward to <forward-path>
>
>But nothing for error code 213.
>
>Can anyone help me with
>1. Understanding what RFC is implemented by my SMTP implementer
WHICH implementor?
>2. Is there any RFC which specifies and describes 213 as some
>meaningful error code. If yes what is RFC number?
RFC1893 describes X.1.3 as "Bad destination mailbox address syntax",
but says it's only useful for permanent failures (e.g. 513), so
there shouldn't *be* a 213 code.
RFC5248 is supposed to be a collection of these status codes and
it's only a year old. 213 is not listed.
>Can i safely ignore this smtp error code without any issues. Can i
If it issues a response code it's generally throwing the ball back
in your court to DO something. You can ignore any error (first
digit of 2 is "success"), but you need to proceed with the next
step in sending a message.
Exim, for example, will issue a "250 OK" response after a "MAIL FROM"
command. It means "go ahead and send your "RCPT TO:" commands now.
>code something like
>if ( smtp_error_code%100==2 )
> //ignore error
>else
> //do some error handling
>
>Is such kind of code normal protocol when you are sending emails
>programmatic by using smtp?
You send a command, you get a response, then you send another command,
and get a response to that. You aren't supposed to send another command
*before* getting a response from the last command, unless you're using
PIPELINING. Some SMTP servers use that to filter spammers when they
send commands too soon.
There are a number of things a 213 message *might* mean:
213 Message is probably not a virus.
213 Message is probably not spam.
213 Authorized sender.
213 Message is probably not a chemical, biological, or nuclear weapon.
213 Message is not too large.
It would help to know what command it was a response to.