• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1446
  • Last Modified:

Provide all possible statuses for javax.mail.SendFailedException i.e. "550 5.7.1 Unable to relay"

Hello,

Where can I get all possible exception statuses for javax.mail.SendFailedException class of Java Mail.

For example this would be one exception status:
javax.mail.SendFailedException: 553 5.1.2 Bad recipient format -- no domain specified

(and another mentioned in the title of this question)

Thank you,
0
ok_lilya
Asked:
ok_lilya
  • 7
  • 6
  • 2
1 Solution
 
CEHJCommented:
Probably from the source code ...
0
 
ok_lilyaAuthor Commented:
This is an MKS site...??
0
 
CEHJCommented:
Don't understand you comment... You need to look into the javax.mail sourcecode
0
Cloud Class® Course: MCSA MCSE Windows Server 2012

This course teaches how to install and configure Windows Server 2012 R2.  It is the first step on your path to becoming a Microsoft Certified Solutions Expert (MCSE).

 
CEHJCommented:
Another way would be to look at the sending protocols and find out their error codes:

http://www.networksorcery.com/enp/protocol/imap.htm
http://www.modemhelp.net/smtperrors/smtpserver.shtml
0
 
ok_lilyaAuthor Commented:
These links are not the ones for javax.mail

Also, I would love to look into javax.mail source code, but where do I get it from?
Thanks
0
 
CEHJCommented:
>>These links are not the ones for javax.mail

Those links are protocol-related, which is where the error codes come from in the first place

Source:

http://java.sun.com/products/javamail/FAQ.html#source
0
 
ok_lilyaAuthor Commented:
I got the source files, but I still don't know where I can get all the statuses.

For example,
I'm looking fo: 553 5.1.2 Bad recipient format -- no domain specified

But in the links that you sent 553 means: Requested action not taken: mailbox name not allowed

Thanks
0
 
CEHJCommented:
I'd just unzip the source and then do a find on those codes
0
 
objectsCommented:
> I got the source files, but I still don't know where I can get all the statuses.

Thats not the place to look, the errors are coming from the mail server you are connecting to and will varying when connecting to different servers. Have a look at the server you are using for a list of error codes.
0
 
ok_lilyaAuthor Commented:
Ok, thanks.
0
 
CEHJCommented:
That's simply untrue - the error messages may be somewhat different, but the codes should not change per protocol and that's the important thing. Can you explain

a. why you accepted that answer ok_lilya?
b. what action you're going to take based upon that answer?
0
 
ok_lilyaAuthor Commented:
CEHJ,

a. I accepted the answer because those errors are comming from the server and that is where I should look.
"I'd just unzip the source and then do a find on those codes" - the codes are not in the source.

b. I will look into the  serverto get the list of error codes.

I appreciate your help though,

Thanks.
0
 
CEHJCommented:
>>I accepted the answer because those errors are comming from the server

Of course they're coming from the server! The point is that servers implement protocols. If each one returned different error codes then they would not be implementing the protocol properly.
0
 
ok_lilyaAuthor Commented:
What you are saying is true, but it is not what I asked for. I asked:
"I got the source files, but I still don't know where I can get all the statuses."

to which you answered:
"I'd just unzip the source and then do a find on those codes"

The point is that you told me to look into source of java mail, which is not where it is at.

0
 
objectsCommented:
Thanks :)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 7
  • 6
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now