SMTP Notifications

---

Hi All, I was wondering if any can help.

I am trying to send email notifications however they are not coming through.

We are not reeiving the notifications from our Veeam Backup and Scan to emails from printer.
I have also tried testing via PowerShell script which does not work;

function sendMail{

Write-Host "Sending Email"

  #SMTP server name
$smtpServer = "Exchange Server IP Address"

    #Creating a Mail object
$msg = new-object Net.Mail.MailMessage

   #Creating SMTP server object
$smtp = new-object Net.Mail.SmtpClient($smtpServer)

    #Email structure
$msg.From = "Test@domain.com"
$msg.To.Add("waqas@domain.com")
$msg.subject = "Alert"
$msg.body = 

     #Sending email
$smtp.Send($msg)

}

#Calling function
sendMail

Direct emails are oming through fine, just not the notifications. I have tried rebooting the server to no avail and restarted the MS Information service.

Thanks

@Waqkas-Ahmed ,

Is your email server on-premises or are you using O365?

One simple solution might be to spin up a local smtp server. We do that for our printers here.

PowerShell does have a mail cmdlet, Send-MailMessage as well.

Mike

@Mike-Rodrick Thanks for the quick response.

We have an on prem Exchange Server 2010 as well as all users migrated to O365.

I have tried changing the SMTP info in Veeam and on the printer to point to smtp.office365.com but dosen't work.
The printer seems to complete the test email from the portal, however if a user scans they receive the following message 'The connection to the SMTP server was lost.'

Just to add, the SmtpReceive logs are as follows;

2020-01-17T14:56:28.577Z,FQDN\Default FQDN,08D79B5C6D0426EA,19,IPAddress:25,IPAddress:59145,<,MAIL FROM:<test@domain.com>,

TO:<TEST2@DOMAIN.com>,
2020-01-17T14:56:28.577Z,FQDN\Default FQDN,08D79B5C6D0426EA,23,IPAddress:25,IPAddress:59145,>,250 **2.1.5 Recipient OK,**

2020-01-17T14:56:34.054Z,FQDN\Default FQDN,08D79B5C6D0426EA,26,IPAddress:25,IPAddress:59145,*,Tarpit for **'0.00:00:05.461' due to 'DelayedAck',Delivered**



 2.6.0 <0f5fd9d9-267c-4bfe-86a4-713205f36aa2@FQDN.domain.local> **[InternalId=10459952] Queued mail for delivery,**

17T14:58:50.477Z,,08D79B5C6D042700,1,10.20.30.43:25,185.234.216.105:53854,>**,421 4.3.2 Service not available,**

@Waqkas-Ahmed ,

I don't have a lot of Exchange experience, maybe someone else will add some ideas.

Here is a link to Microsoft Docs that might help.
https://docs.microsoft.com/en-us/Exchange/mail-flow-best-practices/how-to-set-up-a-multifunction-device-or-application-to-send-email-using-office-3

Is domain.com a valid domain that the Exchange server is allowed to handle?

You should also research the Tarpit for **'0.00:00:05.461' due to 'DelayedAck' log entry.
Here are a couple of links that might be relevant...

https://social.technet.microsoft.com/Forums/en-US/2d2ff7d0-742e-452c-8bce-d930c9335bdb/receive-connector-message-tarpit-for-0000009675-due-to-delayedackdelivered

https://exchangegloves.blogspot.com/2012/11/tarpit-for-0000009675-due-to.html