New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

The Community Blog is a personal opinion of community members and by no means the official standpoint of DNN Corp or DNN Platform. This is a place to express personal thoughts about DNNPlatform, the community and its ecosystem. Do you have useful information that you would like to share with the DNN Community in a featured article or blog? If so, please contact .

The use of the Community Blog is covered by our Community Blog Guidelines - please read before commenting or posting.

DotNetNuke Tips and Tricks #14: Testing Emails in a Dev Environment

DotNetNuke Tips and Tricks There are many times when doing DotNetNuke development that your module needs to send emails.  You often have emails that need to go out to several different addresses i.e. an email to the user, one to the system administrator and maybe one to a fulfillment partner.  You frequently have different emails that get sent based on specific configuration settings or that change based on the role of the user.

When developing for DotNetNuke I often create a custom installation devoted to the module under development.  In the past I have not always had an easy method for configuring the SMTP server so that I could trap all the emails being sent out from the system.  I would try to set all the emails to one of my many email addresses and set my SMTP settings to use one of my production email servers.  The problem with my previous approach is that I often missed emails.  Unless all the emails are directed to my personal email accounts, I had no way to trap the emails on my dev box to make sure they were correct.  My previous method also did not make it easy to follow the entire email workflow.

All of these problems were solved recently when I discovered a simple little application called Papercut after reading a blog from Scott Watermasysk.   Papercut provides a nice GUI that allows me to actually view the raw email content, the text content and an HTML view where appropriate.  Neptune is not as nice in this  The added bonus with Papercut, is that I can also forward emails to whatever email address I wish.


Now whenever I configure a new DotNetNuke test instance, I just set the SMTP server to localhost and startup Papercut.  Every email is trapped and ready for me to inspect.  When I think everything is working correctly, I can forward the appropriate emails off to my Marketing director for final approval.  At no time did I clutter my inbox or worry about customers inadvertently receiving test emails.

While doing some research for this post, I also found another solution called Neptune which also traps emails during development.  It works a bit differently and is designed for integration into the development environment with interfaces exposed for automated unit testing.  You can trigger an email to be sent and then programmatically inspect the actual email that was sent.

Being able to easily inspect and test emails will greatly improve your email handling code.  Tools which simplify this task make it more likely that you will run through more scenarios without worrying about filling your inbox or being worried about sending inadvertent emails to customers.  This is a good thing.  I will definitely be using both of these tools on all my future DotNetNuke development work.

Technorati Tags: ,,,


Comment Form

Only registered users may post comments.


Aderson Oliveira (22)
Alec Whittington (11)
Alessandra Davies (3)
Alex Shirley (10)
Andrew Hoefling (3)
Andrew Nurse (30)
Andy Tryba (1)
Anthony Glenwright (5)
Antonio Chagoury (28)
Ash Prasad (37)
Ben Schmidt (1)
Benjamin Hermann (25)
Benoit Sarton (9)
Beth Firebaugh (12)
Bill Walker (36)
Bob Kruger (5)
Bogdan Litescu (1)
Brian Dukes (2)
Brice Snow (1)
Bruce Chapman (20)
Bryan Andrews (1)
cathal connolly (55)
Charles Nurse (163)
Chris Hammond (213)
Chris Paterra (55)
Clint Patterson (108)
Cuong Dang (21)
Daniel Bartholomew (2)
Daniel Mettler (181)
Daniel Valadas (48)
Dave Buckner (2)
David Poindexter (12)
David Rodriguez (3)
Dennis Shiao (1)
Doug Howell (11)
Erik van Ballegoij (30)
Ernst Peter Tamminga (80)
Francisco Perez Andres (17)
Geoff Barlow (12)
George Alatrash (12)
Gifford Watkins (3)
Gilles Le Pigocher (3)
Ian Robinson (7)
Israel Martinez (17)
Jan Blomquist (2)
Jan Jonas (3)
Jaspreet Bhatia (1)
Jenni Merrifield (6)
Joe Brinkman (274)
John Mitchell (1)
Jon Henning (14)
Jonathan Sheely (4)
Jordan Coopersmith (1)
Joseph Craig (2)
Kan Ma (1)
Keivan Beigi (3)
Kelly Ford (4)
Ken Grierson (10)
Kevin Schreiner (6)
Leigh Pointer (31)
Lorraine Young (60)
Malik Khan (1)
Matt Rutledge (2)
Matthias Schlomann (16)
Mauricio Márquez (5)
Michael Doxsey (7)
Michael Tobisch (3)
Michael Washington (202)
Miguel Gatmaytan (3)
Mike Horton (19)
Mitchel Sellers (40)
Nathan Rover (3)
Navin V Nagiah (14)
Néstor Sánchez (31)
Nik Kalyani (14)
Oliver Hine (1)
Patricio F. Salinas (1)
Patrick Ryan (1)
Peter Donker (54)
Philip Beadle (135)
Philipp Becker (4)
Richard Dumas (22)
Robert J Collins (5)
Roger Selwyn (8)
Ruben Lopez (1)
Ryan Martinez (1)
Sacha Trauwaen (1)
Salar Golestanian (4)
Sanjay Mehrotra (9)
Scott McCulloch (1)
Scott Schlesier (11)
Scott Wilkinson (3)
Scott Willhite (97)
Sebastian Leupold (80)
Shaun Walker (237)
Shawn Mehaffie (17)
Stefan Cullmann (12)
Stefan Kamphuis (12)
Steve Fabian (31)
Steven Fisher (1)
Timo Breumelhof (24)
Tony Henrich (3)
Torsten Weggen (3)
Tycho de Waard (4)
Vicenç Masanas (27)
Vincent Nguyen (3)
Vitaly Kozadayev (6)
Will Morgenweck (40)
Will Strohl (180)
William Severance (5)
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out