The sender is always the same in all my examples.  In some it works and in others it doesn't work depending on the email address in the TO field.

I'll just switch up to a non-DNN send function and see how that works.

FYI: .net simply passes the mail to an smtp server. Some smtp servers reject messages that don't have a to & from & subject & body, some may reject messages that are not sent from the actual from domain (relay), some perform a dns check on the sender's email address, and some may perform blacklist checks as well.

In addition, the receiving server my reject the message if the email account is invalid, the originating domain is blacklisted, or even if the mailbox is full.

Have you tested sending and receiving to this particular address using the same smtp server with a standard email client?

Just a thought...

DotNetNuke.Services.Mail.Mail.SendMail("programmer@mysite.com", OurUserInfo.Email, "", "Access Denied", EmailBody, "", "HTML", "", "", "", "")

The only way to really test your example is to issue multiple sends.

DotNetNuke.Services.Mail.Mail.SendMail("programmer@mysite.com", "email1@mysite.com, "", "Subject1", "Body1", "", "HTML", "", "", "", "")DotNetNuke.Services.Mail.Mail.SendMail("programmer@mysite.com", "email2@mysite.com, "", "Subject2", "Body2", "", "HTML", "", "", "", "")

If both emails are received, then something else in your code or your data is causing the problem. Like I mentioned, some servers will reject messages with an empty email, subject or body. The code you provided does not test for or ensure actual values per userID.

I hope this is of some help to you.