News for hackers. Stuff that matters.
Re:Show HN: Mailready – meet the new email deliverability st... by a_subsystem on Tuesday January 30, 2024 @02:42PM (#39194676)
Our domain checks out because we use O365. However, we have an old Exchange server sending out via SMTP. We're not sure what the best path forward is for us. Do we change our apps to route through O365? Will probably take days for that. We have in house custom apps that use it heavily. Anyone have good resources on what we should do?
Re:Show HN: Mailready – meet the new email deliverability st... by dashgreen on Tuesday January 30, 2024 @02:48PM (#39194748)
With the appropriate configuration, your SMTP server could relay to O365, just acting as a forwarder, you don't necessarily have to remove the server. This is very common in use-cases for old devices that barely support SMTP authentication, never mind TLS!
Re:Show HN: Mailready – meet the new email deliverability st... by technion on Tuesday January 30, 2024 @07:37PM (#39198122)
There's an oss dikim signing transport plugin for on prem exchange that has become somewhat a standard in this space.

https://github.com/Pro/dkim-exchange/releases