I have a whole thread over at DNN Forums that has not been resolved and I am lost - you can see the full thread here: http://www.dotnetnuke.com/Community...fault.aspx Basically, I do recieve emails for being notified of a new account being made and for the password request. What is strange is that in every single installation of DNN 5.4.4 I cannot send out a newsletter: http://www.mydomain.com/Admin/Newslet... The only thing this does is send me a SMTP test message... however on my only install of DNN 5.2.3 - all of the email functionality works... All of these sites are on the same server. All use the same SMTP settings. All of the DNN 5.4.4 Instances have issues sending an email from the Newletter Module. This seems to cause other issues - like my dynamic forms module from Data Springs does not send emails from forms that are created with it. Chirs... do you have any other ideas? I find it odd that DNN 5.2.3 works fine in the same duplicated environment and settings and DNN 5.4.4 does not. Let me kow your thoughts. Thanks!

Are there error messages? What are they? Or, does the mail just disappear?

Do you have access to the SMTP server? Its logs should be able to show you if the mail is being handed off from DotNetNuke and the disposition of the mail.

The error message I get from DNN Event Viewer is:

AssemblyVersion: 5.4.4
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL:
AbsoluteURL:
AbsoluteURLReferrer:
UserAgent:
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 12ab63c3-65f6-4bb4-b77c-de338b9da81a
InnerException: This operation returned because the timeout period expired. (Exception from HRESULT: 0x800705B4)
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Threading.ReaderWriterLock.AcquireWriterLockInternal
StackTrace:
Message: System.ApplicationException: This operation returned because the timeout period expired. (Exception from HRESULT: 0x800705B4) at System.Threading.ReaderWriterLock.AcquireWriterLockInternal(Int32 millisecondsTimeout) at DotNetNuke.Services.Scheduling.DNNScheduling.Scheduler.CoreScheduler.AddToScheduleQueue(ScheduleHistoryItem objScheduleHistoryItem)
Source:
Server Name: WEBSERV01

Also... from what my IT guy says... there are no error in the SMTP logs showing that anything is even being delivered from DNN.

There is something not right with DNN and our SMTP server. I had previously thought this was an issue specific to the latest version of DNN (5.4.4) but it might not be based on further investigation from Chris Hammond. However – every test I have done makes me believe that it is something specific to DNN… let me give a complete overview...

Here is the issue:

When testing the SMTP settings in DNN I can verify that I do receive an SMTP test message. This test works on every single DNN instance we have – it does not matter if I change the SMTP Auth. to Anonymous or Basic (Username and Password)…

However… when I test sending a newsletter out from DNN, all of the DNN 5.4.4 instances we use will state that they have successfully send a message. This is not the case… the only thing that comes through is another SMTP test message…

But… when I send a newsletter out with a version of DNN that is less than 5.4.4 – for example SND Rome or HSL which are on Version 5.2.3 they work fine - I get the Bulk Message report as I should...

  
How this was discovered?

a client needed some help with a form on their site after it was moved from DNN4 to DNN5 – Keep in mind that the move has nothing to do with the SMTP functionality as it is a problem on all 5.4.4 instances of DNN not just this particular instance...

After the form was created… trying to run tests came back with nothing… no emails. To verify the SMTP issues you first test it in the Host settings – then try sending a newsletter, which is outlined above…

As you can see it does not work…

What’s been done up to this point?

I have started a thread here and other DNN sites to see if anyone else is having this issues out there – There is one person here and Chris is hopefully looking into the issue, but has not been able to accurately recreate the same issue I am having here.

I have also sent this information to Data Springs (the module developer of the Dymanic Forms module… even through they can’t technically support DNN itself – this is affecting the functionality of their product…

What’s Strange?

Is that even though the newsletter module does not work on our company's website.. The contact form does (Dynamic Forms)… and we do get messages from that particular form in DNN 5.4.4?!

I have been researching and trying to chase this for a week with no solutions… There are also no errors in DNN’s event viewer that are specific to SMTP… my IT dept. says there are no issues or items in the SMTP logs that point to any type of error…

When it comes to DNN I am getting no errors at all… therefore it is becoming increasing difficult to find the answer to this.

Well, reading the entirety of the thread at DotNetNuke.com, it seems that you have the right people involved.  Chris Hammond is a certified good guy.  So, I will be awaiting your report on the change that was suggested.

I'll let you know the minute I figure this out - the word needs to be spread to help others that may run into this.

Seems to me that together with the permissions problem reported here in another thread ( All Users Page Permission Locked  ) this problem makes 5.4.4  a bit flakey.
I've suffered from the locked permissions on a fresh install - which I think I fixed by running some SQL published in the DNN forums. But I've also got a problem with email - users trying to register get no email, the registration process gives an error and the event log shows
InnerException: Object reference not set to an instance of an object.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: DotNetNuke.Services.Mail.Mail.SendMail
StackTrace:
Message: DotNetNuke.Services.Exceptions.ModuleLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Services.Mail.Mail.SendMail(UserInfo user, MessageType msgType, PortalSettings settings) at DotNetNuke.En ies.Modules.UserModuleBase.CompleteUserCreation(UserCreateStatus createStatus, UserInfo newUser, Boolean notify, Boolean register) at DotNetNuke.Modules.Admin.Users.ManageUsers.UserCreateCompleted(Object sender, UserCreatedEventArgs e) --- End of inner exception stack trace ---

However the user id is usable......

All very annoying and a huge waste of time........ especially as 5.4.4 was installed after some other problem with 5.2.3 made that version unusable with Active Social and SQL Server 2008.  

my pennyworth,
John

I upgraded a test site to 5.4.4 and I believe that I was able to verify a problem sending newsletters.

In my case, after sending the message it looks like my DotNetNuke crashes.  When the system recovers, I have this message:

[script removed]

Joe Craig, Patapsco Research Group Complete DNN Support