Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

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!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Email Bug in 7.2.0 causing major issuesEmail Bug in 7.2.0 causing major issues
Previous
 
Next
New Post
1/24/2014 3:03 PM
 

that confirms that this is a different bug as the bug that was fixed was also an issue in 7.1.2. Taking a look at the code, the main difference introduced between 7.1.2 and 7.2.0 with the sendmail method was that the method was updated to do additional validation - in 7.1.2 only the first (bolded) check occurs, from 7.2.0 all 4 checks occur. This would suggest some issue with one of the 3 fields. Beforehand we always used the 4 host settings, but now we allow users to pass in different values so perhaps the issue is that your code calls a method passing one of those values (i.e a new smtpserver/smtpauthentication/smtpusername/smtppassword) -and the code (incorrectly) ignored those values in 7.1.2, but now (correctly) tries to use them in 7.2.0/7.2.1 - and one of them is causing an issue. It would be good to get the full stack trace from the admin->event viewer to see if it contains any useful data.

  //SMTP server configuration

            if (string.IsNullOrEmpty(smtpServer) && !string.IsNullOrEmpty(Host.SMTPServer))

            {

                smtpServer = Host.SMTPServer;

            }


            if (string.IsNullOrEmpty(smtpAuthentication) && !string.IsNullOrEmpty(Host.SMTPAuthentication))

            {

                smtpAuthentication = Host.SMTPAuthentication;

            }

            if (string.IsNullOrEmpty(smtpUsername) && !string.IsNullOrEmpty(Host.SMTPUsername))

            {

                smtpUsername = Host.SMTPUsername;

            }

            if (string.IsNullOrEmpty(smtpPassword) && !string.IsNullOrEmpty(Host.SMTPPassword))

            {

                smtpPassword = Host.SMTPPassword;

            }


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
1/30/2014 3:59 PM
 
Hello,

We have been using the following SendMail overload for about the last 7 years without any issues, however with the release of DNN 7.2.0 our customers are no longer able to send emails from their online stores:

emailResult = DotNetNuke.Services.Mail.Mail.SendMail(bi.SendFromEmail, customer.Email, "", emailSmithUserSubject, emailSmithUserBody, "", "html", smtpServer, smtpAuth, smtpUserName, smtpPassword);

Is this particular SendMail overload call not supported anymore? If not, please reply with the correct SendMail call that we should be using.

Thank you.


Kevin Carlson
Project Manager
Smith Consulting
DotNetNuke Consulting, DotNetNuke Store and DNN Ecommerce
 
New Post
1/30/2014 4:02 PM
 
Hello,

We have been using the following SendMail overload for about 7 years now without any issues however with the release of DNN 7.2.0 our customers are no longer able to send emails from their online stores.

emailResult = DotNetNuke.Services.Mail.Mail.SendMail(bi.SendFromEmail, customer.Email, "", emailSmithUserSubject, emailSmithUserBody, "", "html", smtpServer, smtpAuth, smtpUserName, smtpPassword);

Is this particular SendMail call not supported anymore? If not, please reply with the correct SendMail call that we should be using.

Thank you

Kevin Carlson
Project Manager
Smith Consulting
DotNetNuke Consulting, DotNetNuke Store and DNN Ecommerce
 
New Post
1/30/2014 4:03 PM
 
cathal connolly wrote:

that confirms that this is a different bug as the bug that was fixed was also an issue in 7.1.2. Taking a look at the code, the main difference introduced between 7.1.2 and 7.2.0 with the sendmail method was that the method was updated to do additional validation - in 7.1.2 only the first (bolded) check occurs, from 7.2.0 all 4 checks occur. This would suggest some issue with one of the 3 fields. Beforehand we always used the 4 host settings, but now we allow users to pass in different values so perhaps the issue is that your code calls a method passing one of those values (i.e a new smtpserver/smtpauthentication/smtpusername/smtppassword) -and the code (incorrectly) ignored those values in 7.1.2, but now (correctly) tries to use them in 7.2.0/7.2.1 - and one of them is causing an issue. It would be good to get the full stack trace from the admin->event viewer to see if it contains any useful data.

  //SMTP server configuration

            if (string.IsNullOrEmpty(smtpServer) && !string.IsNullOrEmpty(Host.SMTPServer))

            {

                smtpServer = Host.SMTPServer;

            }


            if (string.IsNullOrEmpty(smtpAuthentication) && !string.IsNullOrEmpty(Host.SMTPAuthentication))

            {

                smtpAuthentication = Host.SMTPAuthentication;

            }

            if (string.IsNullOrEmpty(smtpUsername) && !string.IsNullOrEmpty(Host.SMTPUsername))

            {

                smtpUsername = Host.SMTPUsername;

            }

            if (string.IsNullOrEmpty(smtpPassword) && !string.IsNullOrEmpty(Host.SMTPPassword))

            {

                smtpPassword = Host.SMTPPassword;

            }

 

Hello,

We have been using the following SendMail overload for about 7 years now without any issues however with the release of DNN 7.2.0 our customers are no longer able to send emails from their online stores.

emailResult = DotNetNuke.Services.Mail.Mail.SendMail(bi.SendFromEmail, customer.Email, "", emailSmithUserSubject, emailSmithUserBody, "", "html", smtpServer, smtpAuth, smtpUserName, smtpPassword);

Is this particular SendMail call not supported anymore? If not, please reply with the correct SendMail call that we should be using.

Thank you

Kevin Carlson
Project Manager
Smith Consulting
DotNetNuke Consulting, DotNetNuke Store and DNN Ecommerce
 
New Post
1/30/2014 7:05 PM
 

all of the existing signatures are still supported (we dont change signatures, only obsolete calls and forward their requests onto new signatures). Based on this and the other report clearly some other change has affected you - I posted code earlier where we added additional validation to 3 values, and I think this is it i.e. your code calls:

emailResult = DotNetNuke.Services.Mail.Mail.SendMail(bi.SendFromEmail, customer.Email, "", emailSmithUserSubject, emailSmithUserBody, "", "html", smtpServer, smtpAuth, smtpUserName, smtpPassword);

perhaps smtpServer, smtpAuth, smtpUserName or smtpPassword contains "bad" values. Before 7.2.0 these were ignored as sendmail always used the Host values - we noticed this was wrong and now use the values passed in the call (if they're not empty) i.e. if your smtpUsername was actually "somefakenamethatdoesntexist" older versions such as 7.1.2 would have used the Host.SMTPUsername but 7.2.0 and above ""somefakenamethatdoesntexist" (which is correct application behaviour i.e. the issue is in the calling code not DNN)


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Email Bug in 7.2.0 causing major issuesEmail Bug in 7.2.0 causing major issues


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out