Ok, so this probably comes to no surprise to many of you. I remember running in to this problem when I was using BTS 2004. However, I thought that the community's cries would be answered with BTS 2006. I have not had a need for it until now, so I never checked, but again the ability to BCC using the SMTP Adapter does not exist. Fortunately, there are many ways to skin this cat. The first 2 that come to mind are:
- Create 2 separate email messages within BizTalk: 1 for your original recipients, and 1 for your BCC recipients
- Don't forget to tell them they received this as a BCC and list the original recipients.
- Yeah... won't end up biting you in the butt later on.
- Create a referenced assembly to manage your SMTP needs.
- Again, there are tons of SMTP DLLs floating around in the ether, but you can easily create your own with very little code. Depending how basic your needs are, you can accomplish it with very few lines of code.
using System.Net.Mail;
SmtpClient client = new SmtpClient("server");
using (MailMessage message = new MailMessage("from", "to", "subject", "Body"))
{
client.Send(message);
}But if your needs were that simple, you could just use the SMTP Adapter.
- Again, there are tons of SMTP DLLs floating around in the ether, but you can easily create your own with very little code. Depending how basic your needs are, you can accomplish it with very few lines of code.
Anyway, I whipped up some code that would handle my needs. I did not need to support attachments, although it shouldn't be too difficult to modify my code to include them.
Essentially, I created 2 classes: SMTPHelper and SMTPMessage.
SMTPMessage contains the necessary property values used to send an email.
SMTPHelper contains a single method (SendMail) that accepts a SMTPMessage parameter. SendMail uses the values within the SMTPMessage object to create SmtpClient and MailMessage objects and perform the necessary actions to deliver the email. Basic error handling is included, but can surely be expanded upon.
Within BizTalk, I created a variable called smtpMessage of type BAJ.Utilities.SMTPMessage. Inside my orchestration, I placed the following code within an expression shape.
smtpMessage = new BAJ.Utilities.SMTPMessage();
smtpMessage.SMTPServer = smtpServer;
smtpMessage.FromAddress = smtpFromAddress;
smtpMessage.FromName = smtpFromName;
smtpMessage.ToList = strToList;
smtpMessage.CCList = "";
smtpMessage.BCCList = strBCCList;
smtpMessage.Subject = "[enter subject here]";
smtpMessage.Body = "[enter message here]";
smtpMessage.IsHTML = true;
smtpMessage.Priority = System.Net.Mail.MailPriority.Normal;BAJ.Utilities.SMTPHelper.SendMail(smtpMessage);
In my process, smtpServer, smtpFromAddress, and smtpFromName are all string variables whose values are stored as AppSettings.
Here is the code for my SMTPHelper class: SMTPHelper.zip
No comments:
Post a Comment