<p>In a .net system I'm building, there is a need for automated e-mail notifications. These should be editable by an admin. What's the easiest way to do this? SQL table and WYSIWIG for editing?</p>

<hr>

<p>The queue is a great idea. I've been throwing around that type of process for awhile with my old company.</p>

[{'answer_id': 6212, 'author': 'Adam Haile', 'author_id': 194, 'author_profile': 'https://Stackoverflow.com/users/194', 'pm_score': 0, 'selected': False, 'text': "<p>Are you just talking about the interface and storage, or the implementation of sending the emails as well?</p>\n\n<p>Yes, a SQL table with FROM, TO, Subject, Body should work for storage and, heck, a textbox or even maybe a RichText box should work for editing.</p>\n\n<p>Or is this a web interface?</p>\n\n<p>For actually sending it, check out the System.Web.Mail namespace, it's pretty self explanatory and easy to use :)</p>\n"}, {'answer_id': 6213, 'author': 'palehorse', 'author_id': 312, 'author_profile': 'https://Stackoverflow.com/users/312', 'pm_score': 3, 'selected': True, 'text': "<p>From a high level, yes.  :D  The main thing is some place to store the templates.  A database is a great option unless you're not already using one, then file systems work fine.</p>\n\n<p>WSIWIG editors (such as fckeditor) work well and give you some good options regarding the features that you allow.</p>\n\n<p>Some sort of token replacement system is also a good idea if you need it.  For example, if someone puts %FIRSTNAME% in the email template, the code that generates the email can do some simple pattern matching to replace known tokens with other known values that may be dynamic based on user or other circumstances.</p>\n"}, {'answer_id': 6228, 'author': 'Vaibhav', 'author_id': 380, 'author_profile': 'https://Stackoverflow.com/users/380', 'pm_score': 1, 'selected': False, 'text': '<p>I am thinking that if these are automated notifications, then this means they are probably going out as a result of some type of event in your software. If this is a web based app, and you are going to have a number of these being sent out, then consider implementing an email queue rather than sending out an email on every event.</p>\n\n<p>A component can query the queue periodically and send out any pending items.</p>\n'}, {'answer_id': 7576, 'author': 'Mark Glorie', 'author_id': 952, 'author_profile': 'https://Stackoverflow.com/users/952', 'pm_score': 0, 'selected': False, 'text': '<blockquote>\n  <p><a href="https://stackoverflow.com/questions/6210/e-mail-notifications#6212">Adam Haile</a> writes:</p>\n  \n  <blockquote>\n    <p>check out the System.Web.Mail namespace</p>\n  </blockquote>\n</blockquote>\n\n<p>By which you mean System.Net.Mail in .Net 2.0 and above :)</p>\n'}, {'answer_id': 7587, 'author': 'Community', 'author_id': -1, 'author_profile': 'https://Stackoverflow.com/users/-1', 'pm_score': 0, 'selected': False, 'text': '<p>How about using the new Workflow components in .NET 3.0 (and 3.5)? That is what we use in combination with templates in my current project. The templates have the basic format and the tokens are replaced with user information.</p>\n'}]
['https://Stackoverflow.com/questions/6210', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/721/']