Jenkins email notification setup - company domain / james not working

3,522 views
Skip to first unread message

Sairam Sankaran

unread,
Jun 19, 2013, 3:49:59 PM6/19/13
to jenkins...@googlegroups.com

I am trying to setup email notification for my jenkins server for build failures.

Things I have tried:

1) Use my company smtp mail server with authentication - does not work. Connection refused. I am able to telnet from jenkins server machine.

2) Setup my own James mail server. SMTP server - localhost. Authentication - admin,admin. Port 25. I see that my SMTP server is running. - does not work. Connection refused. I am able to telnet from jenkins server machine.

3) Use my personal gmail account with authentication - Works!!!

I have followed other discussions on this topic but not got an answer.

Some say it may be a firewall issue but I am not sure how to overcome it.

Any suggestions are most welcome.


Notes:

Error message: javax.mail.MessagingException: Could not connect to SMTP host: localhost, port: 25; nested exception is: java.net.ConnectException: Connection refused: connect 

Thanks,

Sairam

k.thi...@comcast.net

unread,
Jun 19, 2013, 4:00:09 PM6/19/13
to jenkins...@googlegroups.com

Might sound weird, but have your tried your company mail server without using authentication?

 

And does it fail even when you try using the test checkbox and send an email from the config page?

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Sairam Sankaran

unread,
Jun 19, 2013, 4:02:36 PM6/19/13
to jenkins...@googlegroups.com
Yes. I have tried w/o authentication. I am unable to move past the config page because the test fails.
I think it needs authentication. Because when I tried it with gmail, it failed w/o authentication and worked when I supplied it.


Sairam


--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/rh9FK_IWgmo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-use...@googlegroups.com.

k.thi...@comcast.net

unread,
Jun 19, 2013, 4:07:48 PM6/19/13
to jenkins...@googlegroups.com

It shouldn't need it unless your environment requires it, which yours must.  Mine is set up without authentication.

 

You may have to work with your IT team to figure out why you are getting rejected.  The mail server might just be rejecting anything from the Jenkins server IP or at least something in that IP range.

Sairam Sankaran

unread,
Jun 19, 2013, 4:09:14 PM6/19/13
to jenkinsci-users
OK. I can understand if I am using my company mail server.

But do not understand why a mail server on the same Jenkins machine that I setup is not working.


Sairam

Scott Evans

unread,
Jun 19, 2013, 4:11:51 PM6/19/13
to jenkins...@googlegroups.com
If you're running Windows, do you have any sort of virus protection running on your jenkins server box that might be blocking outgoing emails, or possibly port 25 is being blocked on an outgoing request?  I assume when you say you can telnet to the email server machine that you're telnetting to port 25 and can get the email server to respond appropriately?  I've not set up a gmail relay, but does it require a different port than 25?  If so, that may be an indication that something is blocking your outbound communication on port 25.

Scott

Sairam Sankaran

unread,
Jun 19, 2013, 4:15:34 PM6/19/13
to jenkins...@googlegroups.com
Yes. I have anti-virus running on that machine.

And for gmail I used 465 for smtp port.

When I telnet to my localhost mail server, I do so on port 25. Looks like a possible issue. Do you have any suggestions on freeing that port?


Sairam

k.thi...@comcast.net

unread,
Jun 19, 2013, 4:22:21 PM6/19/13
to jenkins...@googlegroups.com
Try running netstat, I think with the -n option to see what is using that port.  It should list out the PID which you can check in task manager then.
Sent: Wednesday, June 19, 2013 3:15:34 PM
Subject: Re: Jenkins email notification setup - company domain / james not working

Sairam Sankaran

unread,
Jun 19, 2013, 4:39:51 PM6/19/13
to jenkinsci-users
Here is the output of netstat. Looks like the port 25 is listening for smtp


C:\>netstat -a | find "LISTENING"
  TCP    <my machine name>:smtp     <my machine name>.<my company domain>.com:0  LISTENING
  TCP    <my machine name>:pop3     <my machine name>.<my company domain>.com:0  LISTENING
  TCP    <my machine name>:nntp     <my machine name>.<my company domain>.com:0  LISTENING
  TCP    <my machine name>:epmap    <my machine name>.<my company domain>.com:0  LISTENING
  TCP    <my machine name>:microsoft-ds  <my machine name>.<my company domain>.com:0  LISTENING
  TCP    <my machine name>:1025     <my machine name>.<my company domain>.com:0  LISTENING
  TCP    <my machine name>:1234     <my machine name>.<my company domain>.com:0  LISTENING
  TCP    <my machine name>:2914     <my machine name>.<my company domain>.com:0  LISTENING
  TCP    <my machine name>:2915     <my machine name>.<my company domain>.com:0  LISTENING
  TCP    <my machine name>:ms-wbt-server  <my machine name>.<my company domain>.com:0  LISTENIN
  TCP    <my machine name>:4555     <my machine name>.<my company domain>.com:0  LISTENING
  TCP    <my machine name>:8080     <my machine name>.<my company domain>.com:0  LISTENING
  TCP    <my machine name>:8081     <my machine name>.<my company domain>.com:0  LISTENING
  TCP    <my machine name>:netbios-ssn  <my machine name>.<my company domain>.com:0  LISTENING
  TCP    <my machine name>:1036     <my machine name>.<my company domain>.com:0  LISTENING
  TCP    <my machine name>:5152     <my machine name>.<my company domain>.com:0  LISTENING

C:\>netstat -n | find "LISTENING"

C:\>netstat -an | find "LISTENING"
  TCP    0.0.0.0:25             0.0.0.0:0              LISTENING
  TCP    0.0.0.0:110            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:119            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1025           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1234           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:2914           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:2915           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:4555           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:8080           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:8081           0.0.0.0:0              LISTENING
  TCP    10.105.152.46:139      0.0.0.0:0              LISTENING
  TCP    127.0.0.1:1036         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:5152         0.0.0.0:0              LISTENING


Sairam
Reply all
Reply to author
Forward
0 new messages