Failed to send e-mail notification.

This is a known bug. There a several threads covering potential work-arounds. However, for some it's SOL until they fix it. Note:it used to work in 2011.

If the backup was good but no notification after a good test, this could indicate no internet connection.

That was my first check and yes I did have a good connection at all times.
I have two backups on acronis one being a full backup of the c:drive and another only a certain files they both have the same email settings and both tested OK.
when it does a full backup I do get an email notification but not on the file backup.
I'm just wondering why it does for one and not the other.

Well I can concur that e-mail does not get sent on every occasion. I have a scheduled (at system startup) task and the log shows that the e-mail was sent successfully but no e-mail EVER arrives. I can edit the task and send a test e-mail and that turns up OK. but I NEVER get one when the task runs either on schedule or when run manually.

This is a file based task and that may have something to do with it as all partition based tasks seem OK.

So ATIH lies about its ability to send e-mail it says it has done it but it has not.

I want better and more accurate logging 3 years and still waiting on this one.
I want ATIH to do what it says on the tin correctly ALL the time.

==> This is a known bug. There a several threads covering potential work-arounds. However, for some it's SOL until they fix it. Note:it used to work in 2011.

I'll repeat for those who did not get it. This is a widely reported bug. It may work for you, but if it does not, there is not much you can do until Acronis fixes the code. Period.

I worked it with the U1-beta folks from Acronis on this and about 9 other bugs. The process is: 1) Acronis gets you to run monitoring programs, collect logs, etc. 2) Everything clearly shows that that the eMails are not actually being sent, 3) Acronis then 'analyzes' the logs, and 4) never gets back to you. The new release comes out and it is not listed in the 'known issues' list. The process repeats until it is finally fixed in some future release. This happened with 6 of the bugs that I worked -- 3 were fixed in U1, the rest are clearly documented bugs, but not listed under 'known issues'.

I know this thread is old, but wanted to chime in. I installed ATIH 2012 build 7133 as an upgrade on a machine running 2011. Now the nightly File backup runs successfully and the log clearly states that Email notification was successfully sent. However no email ever arrives at its destination recipient. Notification setup is correct and worked for the backup in 2011, and when sending a Test message, it is delivered successfully to recipient.

So is this still an undocumented issue with build 7133?

Just curious.

JS.

James,
As best I know, all reports and users show this to be fixed via 7133. If the test works, I would check the incoming email carefully as to make sure it is not spam or filtered elsewhere. Try doing a email search inside the received emails --such as all within a specific date.

If the program indicates it to be sent, I would try to prove it correct before confirming there is still a problem. There still could be a problem but try to confirm either way. There does not seem to be any email issues with 2013 which is what I have installed.

James,
I have many customers running 2012 build 7133 and the email notifications from their systems come to my email account for review/monitoring. There seems to be no problems with the installed base of 2012 build 7133 customers I deal with concerning email notifications.

Thanks. I checked Outlook, ISP's SPAM & spam filters, ISP's webmail... you name it. Emails nowhere to be found.

I tried one last thing... Since this backup Job was created and scheduled in ATIH 2011, I went in under 2012 and edited the job, went to notifications setup, and did a "reset" to clear notifications. Saved the job, then re-opened it, entered all the email info again, tested send successfully, then saved.

So far, the next scheduled execution of the backup job successfully sent the email (according to the log) and the email was in fact received. Since this is a nightly job, we'll watch it for the next few days to see if it continues to send it OK.

I'll keep you posted.

JS.

Thanks for the update.

You're welcome. It just seemed strange that after installing the upgrade from 2011 to 2012, the job continued to run successfully every night, and the log always indicated the Email was successfully sent. For the first week or so, the emails were actually received, then just stopped coming... even though the logs still said they were sent.

Hopefully setting up notifications in the job from scratch will clear up anything that went haywire. We'll see.

I have another machine I recently upgraded to 2012, and then upgraded again to 2013 when it was released and haven't seen any issues with email on that one.

Usually, when a task fails or is suspect, my first act is to create a totally new task and see if the same issue occurs. I completely refrain from editing any task and will start over with a new one if changes are needed. Sometimes is take time and is painful but the a new task usually corrects any issues.

OK... Update... After resetting email notification and re-entering all email related info, test email worked, and for the first few days, email successfully sent entries appeared in the daily job log, and notification emails were actually received.

Now no emails are received again for the last few days in spite of the logs continuing to say email successfully sent.

Next option... delete the backup jobs and recreate them from scratch. But I hate to do this because I can't figure out how to create a new backup job and have it continue to manage the existing set of backup files (multiple fulls + incrementals with automatic cleanup)

There's no rhyme or reason to the email issue that I can detect. I think Acronis needs to revamp the whole email subsystem including better user control in setup of all sendmail parameters. SMTP Login account settings, ports, protocol, etc., need to be completely separate from email subject (which user should have some control over subject), sender address (I'd like to have the sender be "acronis@computername"), etc. They've had lots of user complaints on email functionality for at least the last few versions. Its rediculous they can't get it right. This is not rocket science. I've never had this kind of issue with other programs that provide a SMTP email interface.

JS.