You really can't possibly be so special that none of this stuff will work for you. And if it doesn't work, there are relay services specifically built for this stuff, like SendGrid. It's the number one email platform in the world. If it's that time sensitive it shouldn't be going through email in the first place.Įxchange 365 will have to prove its reliability, consistency, and speed to us before we trust it enough to use it as an off-net hosted general mail relay. How old is this code? And if you're talking about on the email side, it's email. ![]() You're scanning cannot be that special, every time I see a company that thinks like this it's always because they think they're special and that's "always the way they've done it."Īlso, we want to use a local smart relay for queuing application-generated email to customers/B2B-partners, to minimize submission latency.Īre you talking about within the application? We've got tons of apps using relaying through Office 365 with no noticeable difference. If only there were some other vendors that offer more robust spam filtering options for outbound email? Like Mimecast, or ProofPoint, or Barracuda, Email Laundry, or literally any spam filter on the market. And that's not even bringing up memory safety. Not to mention a large part of that difference is likely due to grep relying on libc, while ripgrep has to bundle its own runtime. saved search notifications, billing notifications, requested reports, etc)Īnd must also filter/scan outbound messages before they leave our network.Įxchange 365 doesn't offer us what we need for the type of filtering/scanning we do. Making that tradeoff in exchange for significantly improved performance seems reasonable. We have systems that generate messages to corporate recipients, external customers and B2B partners (e.g. Is this possible? Has someone done this before? We're diligent about not using catchalls/wildcards for any of our corporate email domains. We also won't rule out doing some sort of cached "valid local addresses" database (in mysql, for instance) on the relay system itself, generated on a schedule by querying AD/LDAP for all our active+valid email addresses. I'd like to try to implement a filter that can query our local domain controllers (via ldap) for the existence of a valid recipient address, during a mail submission transaction, if the recipient address' domain falls within our list of "local exchange-hosted domains" (this list will likely be static, so i can define it in the exim config), and if it can't find a valid email address/alias in AD/LDAP, immediately report an undeliverable error to the submitting client. The only hangup is that production systems generating mail won't necessarily see "undeliverable/no-such-recipient" errors during the submission to the relay, if the relay is just configured to be a simple forwarder. This means my internal hosts no longer have a local smtp relay, so I'm building a couple in an HA cluster using Exim. ![]() My corporate overlords have decided running Exchange on-site is no longer economical/practical, and shifting our organization's corporate mail to 365.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |