Direkt zum Inhalt

No E-Mail Notification after successful Backup

Thread needs solution

Hello,

after my Backup was created successfully, I'm getting the following error (I replaced the email addresses with ****):

Befehl 'E-Mail wird gesendet' ist fehlgeschlagen.
Zusätzliche Info: 
--------------------
Fehlercode: 61
Module: 309
Zeileninfo: 4a8728dc8a1c9510
Felder:  $module : mms_vs_44421
Nachricht: Befehl 'E-Mail wird gesendet' ist fehlgeschlagen.
--------------------
Fehlercode: 22
Module: 309
Zeileninfo: 8d165e86fb8195f7
Felder:  TraceLevel : 1, $module : email_commands_addon_vs_44421
Nachricht: TOL: Failed to execute the command. Dieser Befehl versendet E-Mails.
--------------------
Fehlercode: 32
Module: 335
Zeileninfo: da7e497cf4160e20
Felder:  $module : email_commands_addon_vs_44421
Nachricht: Senden der Nachricht von '****@*****' an '*****@*****;*****@*****' fehlgeschlagen (SMTP 'smtp.1und1.de:25').
--------------------
Fehlercode: 15
Module: 335
Zeileninfo: da7e497cf4160e00
Felder:  $module : email_commands_addon_vs_44421
Nachricht: Beim Lesen vom Socket ist ein fataler Fehler aufgetreten.
--------------------

I run 3 different backup jobs and the e-mail notification works for the other 2. All 3 jobs use the same e-mail parameter, I only changed the sender adresses between all jobs. Sending a test e-mail always works for this backup job.

I tried different things to find a solotion: 
Selected different sender addresses, backup times, created a complete new job, cloned from the working jobs etc. Nothing worked...

I need help to understand this error messages above.

0 Users found this helpful

Hello Norbert,

This type of error is usually returned when the SMTP server rejects the Agent connection (before authentication) and the Agent receives an empty reply.  The can happen, of example, of the IP of Acronis Agent is declined by SMTP server or firewall along the way.

Please consult with your network or SMTP administrator to make sure that nothing is blocking requests from the one Agent IP that is failing the notification. Also, if you have a whitelist, make sure that Agent is listed.

Basically, this Agent cannot see the SMTP server correctly and since the other agents work, this is probably a network issue (routing, firewall, etc). You can also try using something like Wireshark to look at the SMTP traffic packets and find where they are being rejected.