A client has been using IIS v6 SMTP over Windows 2008 R2 for many years to send out automated server notifications. Their apps use Blat to send through localhost with no authentication. Email seems to go out directly from that system with a masquerade FQDN that is the same as their actual email server. Only their staff email (Outlook, etc) goes through the real SMTP server.
We're migrating most functionality to a new Windows 2016 server and I need to ensure all email automation is working correctly. I'm concerned that remote servers that check SPF or DKIM or other certification will either bounce or silently trash emails from this server. I believe the number of remote servers doing this is quite likely to increase over time.
But I have not found what I expected to be an outcry from admins about issues like this, only the occasional old questions about how to relay to GMail or some other server. I do not see a folder full of bounces. And I get emails from this server - unfiltered by my third-party email host.
So my fears don't seem to match with reality and I can't justify a recommendation to change the setup on their new system. That's fine, I don't have an agenda, I'm really looking to ensure that things just work, regardless of how it works.
1) Am I correct that recipient servers could/will/should be filtering these outbound notifications, and the intended recipients might not even be getting their emails?
2) Is it better to just use a "real" SMTP server like Exchange or Postfix?
3) Is there any downside to continue using Blat, with Basic Authentication into localhost, and continuing to use IIS SMTP to send email from their v2016 server?