Would you be able to provide a full stack trace of the connection exception.
Also, while I assume you are providing the correct connection properties (i.e., host,port etc) I would still recommend to check the they are correct, but in any event the full stack trace would definitely help and you cn find it the the wifi app logs.


On Nov 15, 2016, at 4:07 AM, Gadiputi, Sravani <> wrote:

Thank you for your reply.
My requirement is , I just try to send/copy the 3 different files from source to destination through Nifi, and these jobs runs weekly once.
So I wanted to know which file is successfully moved through email.
In this process, I have configured putemail for each flow. There are hardly 3 notifications only.
Though files have been moved to destination, we could not receive the notifications properly and giving the below error.
Please suggest.
From: Jeff [] 
Sent: Tuesday, November 15, 2016 1:25 PM
Subject: Re: Nifi- PutEmail processor issue
Hello Sravani,
Could it be possible that the SMTP server you're using is denying connections due to the volume of emails your flow might be sending?  How many emails are sent per flow file, and how many emails do you estimate are sent per minute?
If this is the case, you can modify your flow to aggregate flowfiles with a processor like MergeContent so that you can send emails that resemble a digest, rather than a separate email for each flowfile that moves through your flow.
On Mon, Nov 14, 2016 at 11:59 PM Gadiputi, Sravani <> wrote:
I have used PutEmail processor in my project to send email notification for successful/failure copying of a files.
Each file flow having corresponding PutEmail to send  email notification to respective recipients.
Here the issue is, sometimes email notification will send to respective recipients successfully  for successful/failure job.
But sometimes for any one specific job email notification will not be send to recipients though job is successful, due to  below error.
Could not connect to SMTP host Connection timed out
Could you please suggest me how we can overcome this error.

This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.