Home/ Questions/Q 6189925
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-24T02:29:46+00:00

I have many applications across an enterprise environment and they all use different methods

  • 0

I have many applications across an enterprise environment and they all use different methods of sending emails. Some send directly through an exchange server, some queue up locally in an SMTP queue and others call a a web service that then sends the email.

I’m trying to decide on the best way to get guaranteed delivery of emails. If our Exchange server goes down, then the applications that send to it directly can no longer send emails, also any emails sent during the down time never get anywhere. I would also like to implement a universal templating solution that all applications can share.

Are there any pre-built solutions to this problem, or do you have an insight on how to handle this issue?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    We solved this by creating a web service that sends all our emails. This web service uses the 

    System.Net.Mail.SmtpDeliveryMethod.PickupDirectoryFromIis

    setting, which essentially saves the files to a spot on the disk, tries to send them via the main SMTP server, and if the server is unavailable, they sit in the directory until it BECOMES available.

    Guaranteed delivery, as long as the web service is up. Since we have redundancy checks in place, this is almost never an issue. If it is, we treat it as an error in code and handle it.

    edit – added

    I forgot to mention that XSS is a concern even in an email, so be sure to use something like the Microsoft.Security.AntiXss library, which contains functions like GetSafeHtmlFragment to strip out potentially dangerous scripts before outputting html to an email.

    http://msdn.microsoft.com/en-us/security/aa973814.aspx

    http://msdn.microsoft.com/en-us/library/aa973813.aspx

    • 0