javax.mail.SendFailedException

private static void fetchConfig() {
InputStream input = null;
try {
//If possible, one should try to avoid hard-coding a path in this
//manner; in a web application, one should place such a file in
//WEB-INF, and access it using ServletContext.getResourceAsStream.
//Another alternative is Class.getResourceAsStream.
//This file contains the javax.mail config properties mentioned above.
input = new FileInputStream( "C:\\Temp\\MyMailServer.txt" );
fMailServerConfig.load( input );
}
catch ( IOException ex ){
System.err.println("Cannot open and load mail server properties file.");
}
finally {
try {
if ( input != null ) input.close();
}
catch ( IOException ex ){
System.err.println( "Cannot close mail server properties file." );



here is the error:

Cannot open and load mail server properties file.
Cannot send email. javax.mail.SendFailedException: Sending failed;
nested exception is:
class javax.mail.MessagingException: Could not connect to SMTP host: localhost, port: 25

i want to make a simple email program so i find some code but i get errors.
C:\\Temp\\MyMailServer.txt <<<==== i dont know mail server config but he mention about an "....alternative is Class.getResourceAsStream." how do i implement Class.getResourceAsStream and get rid of the above errors? tnx

Those errors are next to useless.
You must print the stack trace, otherwise how on earth do you know where that exception was thrown from?

Anyway, presuming it's your file, does it exist at the location you've given?

sorry its not my file and i dont know the content of MyMailServer.txt, i just found the code on the net i tried to explore it hoping i would learn something but it doesnt run since a file is missing.. im looking for a simple java program that could send email.. i think i should look more.. tnx

If this "C:\\Temp\\MyMailServer.txt" doesn't exist then that code will fail.

If you're going to borrow code and try and build something from this borrowed code you really need to know the language beforehand...and be able to spot when code has been badly written.