Thanks you so much this helps me a lot. I've been searching few days back and I couldn't figure out. After watching this video my SMTP server was up and running.
It does work, but there must be a better way to use IIS to authenticate with the connector using a certificate and not the public IP since spamhaus will block all attempts if any of your machines in your network starts to send spam emails through this connector.
hi, thanks for sharing. Any help in how to do the same thing but securing communcation? Access > Require TLS encryption Currently onlye the final delivery is TLS encrypted, but not from the sender. I do already have a signed public certificate. Thanks
please im having small issue , after successful setup just as you xplained , i will send my email newsletter with a 3rd party app with the smtp configurations , it will send successful but wont be in the mailbox both inbox/spam,,,,,,,,,,,, pls help
Since there is no inbound NAT or port opening required, the example was not set up in a DMZ. However, you can set it up in a DMZ as long as the server can get outbound to Office 365 using SMTP (port 25) and the devices that need to access it can get to your server. Regardless of where it is, the IP you would enter in to the connector is the IP that the server is using to go OUTBOUND to the interent on port 25.
Thanks, so I think instead of going for DMZ , I can get one Static public IP NAT with the server private IP and then it will also be added to the connector in o365.. I hope I am right.
I am curious if SMTP relay will work for an old MFP/printer using TLS1.0 ? At 5:21 we checked the TLS encryption option, what version of TLS encryption will it use ?
I had a similar problem to you, following this video to the detail and emails wouldn't arrive, I read your comment about TLS and deactivate mine, and email started to work... idk if it's exactly the problem you had but I hope it help you somehow
When set up correctly (like the video shows), you can email internally and externally. As always, O365 is not intended to be a blast emailing solution, so it should only be used for things like helpdesk ticketing systems, scanners, etc.
Thank you so much. it is very helpful. But all mails are showing as delivered in IIS logs code 250. Not in the queue folder also. But mails are not received. Please help
This tutorial is no longer current. If you follow these steps as they are laid out here, don't expect it to work, especially if your IIS Mail server is hosted in Azure. (Outbound connections on port 25 blocked for the vast majority of subscriptions out there) If anyone knows of an updated tutorial please post a link. Thanks!
Please I need a little guide. I have successfully set up the smtp relays following your instruction step by step and everything is now fine. But when I tried to connect the ip address for server to my heart sender and it refused to connect. I need to know if there is any other sender app I can use to send messages that will connect with that server ip.
Yes, you can. You're still under the restrictions of outgoing spam limitations with Office 365, but it works fine for normal emails like scans, helpdesk tickets, etc. If you're doing blasts, it's probably best to use a 3rd party service designed for that...
Thanks you so much this helps me a lot. I've been searching few days back and I couldn't figure out. After watching this video my SMTP server was up and running.
WOW EXCELLENT! - I did it as you explained and it works perfectly
Hi,
Is this connection using modern authentication? since basic will be disable by MS.
Thank you,
It does work, but there must be a better way to use IIS to authenticate with the connector using a certificate and not the public IP since spamhaus will block all attempts if any of your machines in your network starts to send spam emails through this connector.
Hi,
I have a problem
I did all the step by step but no emails arrive.
they stay in the queue
What I can do?
thanks for your answer
Great video. But they moved the "Connection filtering" from the classic interface
Thank you so much excellent video keep going with new videos 😊
Thanks a lot, very detailed and helpful info!
Excellent explanation. Informative video
This video is a life saver! Thanks
Great video, Tom. Do you have to do anything under Domains for the virtual server?
Great guide. Thank you. 👍
Thanks, it's Very helpful!
Well done. Thanks for sharing
Man!!! you've saved me!!
hi, thanks for sharing.
Any help in how to do the same thing but securing communcation?
Access > Require TLS encryption
Currently onlye the final delivery is TLS encrypted, but not from the sender.
I do already have a signed public certificate.
Thanks
Hi,
I have set up the SMTP server and noticed that we can send from any non-domain email address? How do we stop that?
please im having small issue , after successful setup just as you xplained , i will send my email newsletter with a 3rd party app with the smtp configurations , it will send successful but wont be in the mailbox both inbox/spam,,,,,,,,,,,, pls help
Very helpful thank you.
THANK YOU!!!!!!!!!!!!!!!!!!!!!
Great, Thank you..
Thanks bro
Dose this work if you get dynamic IP from ISP
as soon as the ip changes from your isp it will break
Can you confirm if this server was setup in DMZ or this server private IP address was natted with Public IP address ?
Since there is no inbound NAT or port opening required, the example was not set up in a DMZ. However, you can set it up in a DMZ as long as the server can get outbound to Office 365 using SMTP (port 25) and the devices that need to access it can get to your server. Regardless of where it is, the IP you would enter in to the connector is the IP that the server is using to go OUTBOUND to the interent on port 25.
Thanks, so I think instead of going for DMZ , I can get one Static public IP NAT with the server private IP and then it will also be added to the connector in o365.. I hope I am right.
I am curious if SMTP relay will work for an old MFP/printer using TLS1.0 ?
At 5:21 we checked the TLS encryption option, what version of TLS encryption will it use ?
I had a similar problem to you, following this video to the detail and emails wouldn't arrive, I read your comment about TLS and deactivate mine, and email started to work... idk if it's exactly the problem you had but I hope it help you somehow
@@AVDYNAMICS777 my smtp relay suddenly stopped working. Is it related to tls and how did you deactivate it?
@@AVDYNAMICS777 did u get blocked by spam hause?
@@tawchaentertainment1488 huh?
Can you please confirm that on Premises SMTP Relay will send mail only to the Office 365 or to any other Domain on the Internet ?
When set up correctly (like the video shows), you can email internally and externally. As always, O365 is not intended to be a blast emailing solution, so it should only be used for things like helpdesk ticketing systems, scanners, etc.
Thank you so much. it is very helpful. But all mails are showing as delivered in IIS logs code 250. Not in the queue folder also. But mails are not received. Please help
This tutorial is no longer current. If you follow these steps as they are laid out here, don't expect it to work, especially if your IIS Mail server is hosted in Azure. (Outbound connections on port 25 blocked for the vast majority of subscriptions out there) If anyone knows of an updated tutorial please post a link.
Thanks!
1000 STARS to you man. Really this video was my final hope and it really worked for SAGE app. THanks a ton
Azure VMs have port 25 outbound blocked. Would this work o poert 587 also?
Please I need a little guide. I have successfully set up the smtp relays following your instruction step by step and everything is now fine. But when I tried to connect the ip address for server to my heart sender and it refused to connect. I need to know if there is any other sender app I can use to send messages that will connect with that server ip.
i did step by step adn chek again but for some reason de mails go to "badmail" folder :((( any idea?
does this still work? TLS will be deactiveted from M365 or isnt active anymore. Does this still work with OAuth 2.0?
I would like to know as well since they are going to disable basic authentication.
Thank you, very helpful. Are you able to send to external mailboxes are not Office 365 and are not part of your tenancy?
Yes, you can. You're still under the restrictions of outgoing spam limitations with Office 365, but it works fine for normal emails like scans, helpdesk tickets, etc. If you're doing blasts, it's probably best to use a 3rd party service designed for that...
Worked perfectly for me! You are the man
Great coverage on this topic!
Worked a treat....thanks
Fantastic - thanks!!!
best of the best!
Very helpful!