SMTP notifications not working

[Fernando_Vinan-]

After my upgrade from v10 to v11 my notifications to the local SMTP service (on the same server) have stopped and it appears BE is simply dropping the connection for no good reason. The logs from my mail server MDaemon are:

Thu 2007-05-17 08:44:39: ----------
Thu 2007-05-17 08:44:43: [2:1] Session 2; child 1; thread 6072
Thu 2007-05-17 08:44:43: [2:1] Accepting SMTP connection from [127.0.0.1:1411]
Thu 2007-05-17 08:44:43: [2:1] --> 220-mydomain.com ESMTP MDaemon 9.6.0l; Thu, 17 May 2007 08:44:43 +0100
Thu 2007-05-17 08:44:43: [2:1] --> 220-*
Thu 2007-05-17 08:44:43: [2:1] --> 220-* This site does not authorise the use of its proprietary computers
Thu 2007-05-17 08:44:43: [2:1] --> 220-* and computer network to accept, transmit or distribute unsolicited
Thu 2007-05-17 08:44:43: [2:1] --> 220-* bulk email from the Internet.
Thu 2007-05-17 08:44:43: [2:1] --> 220-*
Thu 2007-05-17 08:44:43: [2:1] --> 220-* Failure to abide by the above statement will result in your server
Thu 2007-05-17 08:44:43: [2:1] --> 220-* being permanently banned from connecting in the future.
Thu 2007-05-17 08:44:43: [2:1] --> 220-*
Thu 2007-05-17 08:44:43: [2:1] --> 220-* Please report any other problems to postmaster@mydomain.com
Thu 2007-05-17 08:44:43: [2:1] --> 220 *
Thu 2007-05-17 08:44:43: [2:1] <-- EHLO homer
Thu 2007-05-17 08:44:43: [2:1] --> 250-mydomain.com Hello homer, pleased to meet you
Thu 2007-05-17 08:44:43: [2:1] --> 250-ETRN
Thu 2007-05-17 08:44:43: [2:1] --> 250-AUTH LOGIN CRAM-MD5
Thu 2007-05-17 08:44:43: [2:1] --> 250-8BITMIME
Thu 2007-05-17 08:44:43: [2:1] --> 250-STARTTLS
Thu 2007-05-17 08:44:43: [2:1] --> 250 SIZE
Thu 2007-05-17 08:44:43: [2:1] <-- MAIL FROM: <backupexec@mydomain.com>
Thu 2007-05-17 08:44:43: [2:1] --> 250 <backupexec@mydomain.com>, Sender ok
Thu 2007-05-17 08:44:43: [2:1] <-- RCPT TO: <fred@mydomain.com>
Thu 2007-05-17 08:44:43: [2:1] Error writing to socket
Thu 2007-05-17 08:44:43: [2:1] *  Winsock Error 10053 Connection abort.
Thu 2007-05-17 08:44:43: [2:1] SMTP session terminated (Bytes in/out: 453/663)
Thu 2007-05-17 08:44:43: ----------
Thu 2007-05-17 08:45:28: [3:1] Session 3; child 1; thread 5880
Thu 2007-05-17 08:45:28: [3:1] Accepting SMTP connection from [127.0.0.1:1425]
Thu 2007-05-17 08:45:28: [3:1] --> 220-mydomain.com ESMTP MDaemon 9.6.0l; Thu, 17 May 2007 08:45:28 +0100
Thu 2007-05-17 08:45:28: [3:1] --> 220-*
Thu 2007-05-17 08:45:28: [3:1] --> 220-* This site does not authorise the use of its proprietary computers
Thu 2007-05-17 08:45:28: [3:1] --> 220-* and computer network to accept, transmit or distribute unsolicited
Thu 2007-05-17 08:45:28: [3:1] --> 220-* bulk email from the Internet.
Thu 2007-05-17 08:45:28: [3:1] --> 220-*
Thu 2007-05-17 08:45:28: [3:1] --> 220-* Failure to abide by the above statement will result in your server
Thu 2007-05-17 08:45:28: [3:1] --> 220-* being permanently banned from connecting in the future.
Thu 2007-05-17 08:45:28: [3:1] --> 220-*
Thu 2007-05-17 08:45:28: [3:1] --> 220-* Please report any other problems to postmaster@mydomain.com
Thu 2007-05-17 08:45:28: [3:1] --> 220 *
Thu 2007-05-17 08:45:28: [3:1] <-- EHLO homer
Thu 2007-05-17 08:45:28: [3:1] --> 250-mydomain.com Hello homer, pleased to meet you
Thu 2007-05-17 08:45:28: [3:1] --> 250-ETRN
Thu 2007-05-17 08:45:28: [3:1] --> 250-AUTH LOGIN CRAM-MD5
Thu 2007-05-17 08:45:28: [3:1] --> 250-8BITMIME
Thu 2007-05-17 08:45:28: [3:1] --> 250-STARTTLS
Thu 2007-05-17 08:45:28: [3:1] --> 250 SIZE
Thu 2007-05-17 08:45:28: [3:1] <-- MAIL FROM: <backupexec@mydomain.com>
Thu 2007-05-17 08:45:28: [3:1] --> 250 <backupexec@mydomain.com>, Sender ok
Thu 2007-05-17 08:45:28: [3:1] <-- RCPT TO: <fred@mydomain.com>
Thu 2007-05-17 08:45:28: [3:1] Error writing to socket
Thu 2007-05-17 08:45:28: [3:1] *  Winsock Error 10053 Connection abort.
Thu 2007-05-17 08:45:28: [3:1] SMTP session terminated (Bytes in/out: 453/663)
Thu 2007-05-17 08:45:28: ----------

With and without authentication to exclude that.

I have plenty of other mail enabled services that talk just fine, and BackupExec had not had any issues for the last 5 years on this server until now with v11.

[quintar]

I experienced a very similar issue.  No notifications are being sent, however, when configuring them and using the TEST button, we do receive emails.
I had to update my 11d version to 7170, and then modify my existing jobs (change a setting and change it back) to 'refresh' the job, and since doing that, email notifications have been working for the last 2 weeks.

[Joseph_Wagner]

I am having this problem as well.  Were you able to fix it?

[Fernando_Vinan-]

No - tried making sure I was on 7170 (which Liveupdate refused to update to so had to download the full version - another backward step from Veritas days imho) and it makes no difference. Anyway, my problem was not that notifications were not being sent by BE, but that it sends them just fine only my local mail server cannot receive them.

I am also a member of the MDaemon beta team and when I posted to our mailing list, one other responded with having the same issue with their own clients in the same scenario - BE trying to mail a local mail server i.e. running on the same server as BE itself, fails. It seems that BE has a timing issue as using the same MDaemon server but from a different machine running BE works fine.

[Dominic_Moore]

Interesting. I started monitoring this thread because I almost never get email notifications. I also have MDaemon server but it is on different hardware (over gigabit LAN). There is also a thread SMTP Alert Issues with a log from a different server, so I don't think it's specific to MDaemon.

[Mark_H]

I have had that problem with BE right from version 9 on up...

I never receive the email alerts EXCEPT for the very first one after a reboot of the Backup server.  Every other alert after that never shows up.

On the bright side, its like an un-intentional notification system as I can tell when my backup servers at different clients restarted :)

[Backup_Exec_Gal]

HI All,

 We, too, are experiencing the same problem w/the SMTP notifications but w/one caveat.  We have four other servers all using BE 11d and the SMTP notification works fine on those four, but on this fifth one, no dice.  They're all configured to use the same address and the notification is enabled on both areas (Settings/Notifications and Selection List Notification) of the job's properties as well as the original configuration page.  We are perplexed as to why it works on our other servers, which all use the same account, but not this one.  I have verified that the notification information is the same as well.  Does anyone have any ideas?  I just tried the BE Utility and will wait until the next Backup runs to see what appears in the log.

 TIA!

BEG

[Backup_Exec_Gal]

An addendum to my previous message, the test always fails as well.

BEG

[DRice]

Anything on this yet?  I have tried EVERYTHING I can think of to get notifications via SMTP with no success.  I've upgraded to build 7170, tried with and without authentication, tried 3 different email accounts (work, aol, and pacbell.net) to see if it was just our mail server.  I have BE 9.1 on another server and it works just fine.

[Dominic_Moore]

I have one job that does email me on success. Others seem to generate a winsock error/connection abort at the mail server, with and without authentication enabled. Fully updated with LiveUpdate on Windows 2003 server.

I am investigating using a command line mailer as a post job command since BE is apparently not going to work.

Message Edited by Dominic Moore on 07-19-200703:08 PM

[D_B_5]

Make sure the Sender Name on the SMTP configuration screen is valid (or even try blank)  Putting something like no-reply@email.addy will not be recognized if it is not valid.

[Jorge_YV]

Hello all.

I'm still on this particulary problem.
Have tried everything, including what D B 5 said...

Any more ideas??

Thx.

[frankvl]

Jorge,

I had the same problem. When I read the post of D B 5, I realized that recently we changed our email setup of the domain to which the notification was sent so that all email first passes the virus and spam scanners of our internet provider. The sender in SMTP setup was a non-existent email address: amdinistrator@domain.local.

When I changed it to an existing email address, everything worked fine. So I suppose that the spamscanners of my provider scan for non-existent emailadresses?

Anyway, it worked for me.

grts,
frank