Chad, from your error message, I'd assume that send mail is unable to obtain the culture of the current thread, used for compiling a regex. are you sending sync or asynchronously in a background thread (w/o portal context and culture)?

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN

Hi Sebastian - Well if you look at the error itself its coming from the email functions. Within the email functions there is some code:

From mail.vb
If (HtmlUtils.IsHtml(body)) Then
 emailMessage.IsBodyHtml = True
End If

And this code calls this code (from htmlutils.vb):
Public Shared Function IsHtml(ByVal text As String) As Boolean

            If (String.IsNullOrEmpty(text)) Then
                Return False
            End If
            Return HtmlDetectionRegex.IsMatch(text)

        End Function


This is where the error is coming from.... If its related to the culture I am not sure what we can change about that (we don't pass in the culture into the DNN email functions). We are using the same DNN email functions we have for a very long time in all of our modules... This only started happening recently though.

A few comments:  I did check the 5.5 source code and there is still this same code calling this RegEx issue. There could be other code somewhere else which would stop the problem that I am not aware of but basically this code is causing the problem is still in 5.5 from what I can tell.

I also checked 5.4.2 source code and the function was changed/is different:
Public Shared Function IsHTMLMail(ByVal Body As String) As Boolean
            Return System.Text.RegularExpressions.Regex.IsMatch(Body, "<[^>]*>")
        End Function

There is still the call /reference within 5.4.2 mail.vb
If (HtmlUtils.IsHtml(body)) Then
                emailMessage.IsBodyHtml = True
            End If

Even tough this same reference isn't in 5.2.3 of the mail.vb file or anything. So... There have clearly been some changes recently and we have had many reports of this with and without our modules. Actually the very first post of this thread was related to the main Admin/Newsletters having the same problem. 

Let me know if you have any other ideas... this seems to be affecting my of our clients.

-Chad

Hi all,

I comming over it now on DNN 5.5.0(532).  This version included some other fixes and I descript now the problem on this Build.  There are different thinks I would try to descript.

1. To the Newsletter.ascx.vb was added the SMTP Configuration Test to testing the connection on sending the newsletter to meke it easier to support and make sure the SMTP is configured well on the Host settings.  But this makes no sense for me about the SMTP Configuration Test Mail is sending with other credencety (i.e it is send as host not as admin) as the newsletter if self.  So this email is send also if you could not receive the newsletter and the Newsletter sending report.  Without the Newsletter sending report you don't get any error report on sending Newsletters.  Tis discript way you get the "Dotnetnuke: SMTP Configuration Test" email sending a newsletter.
2. The SMTP Server Configuration

   There are diffent needs between a developer and a Adminsitrator.  The Mailserver administrator want make his Mailserver very secure, so if he enabled
   
   "Reject mail if sender address is from a invalid domain" no email addresses want be accepted from the SMTP server that is outside the domain as you have setup on the Host SMTP Settings (SMTP Username).  This meen if your SMTP Username on Host - SMTP Settings is user1@domain1.com and you try to send a Nwesletter created from an user with it email address user2@domain2.com this want not work -  Newsletter did NOT delivered.
   
   Enabled the "Authenticated senders must be use a valid sender address" checks if the email address realy exists.  This meen if you used a Email address that not real exist on a Mail server the Email want not accepted from the Mail server and the Newsletter or Notification want not be delivered.
   
   Only way for both szenarious to become those messages to be delivered is to add a Sender Header to the Message (this had then done on DNN code). But this had also some restrictions about this is a standard practice that used from spammers, and so the email could be added or filtered as a spam!  Otherside I never have seen a message with the Sender header filtered as spam, and I using Outlook and on the Mail server a Spam filter service from spamhouse.org.  The Newsletter did not use Sender header on the Email headers.  
   
   Now the problem is you get the SMTP Config Test but not the Sendreport of the Newsletter and not the Newsletter, this makes it hard to understand non developers to know what is wrong.  The problem is that the user who creates the newsletter have his email address not on the same domain as you have setup on the SMTP settings.  This issue want also be gone on Portals where the administrator account have it email address not on the same domain as you have configured on the host settings. 
   The solution is at time to disable both upper reported restrictions on your email server.

3. Using SMTP settings for multible Portals

At time it is a need that the Administrator of each portal you created on DotNetNuke have it Email Account on the same Email server as you Configured on the SMTP Configuration on Host if you using a auth-smtp server.  Without this you want not be able to send any email to your SMTP server.  This happens about the Notification used also the Sender Header and the value is set to the Portal Administrator you have setup on the Site Settings.  Otherwise it could work if you disable both upper reported features on your SMTP server.

---

Regards

Matthias

DNN MVP

www.aarsys.de

Metro7 Skin

ShoutCastStats Module for DNN