Hello

I just upgraded to 5.6.1. from 5.6.0

Emails are not being sent from the optin module since the upgrade

The dnn logs indicate the email address is not a valid format.

Any ideas?

Hi Les,

This has been a problem because of some changes implemented in DNN 5.6.x as disccussed in this forum thread. Please follow Chad's comments on 1/26 at 9:11 a.m. and let us know if it clears the issue for you. Thanks!

http://www.datasprings.com/products.../aft/23380


Candace

Hello. I tried the documented fix, but I am still receiving the same error

AssemblyVersion: -1
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL:
AbsoluteURL:
AbsoluteURLReferrer:
UserAgent:
DefaultDataProvider:
ExceptionGUID:
InnerException: The email address (myemail) is not in a valid format.
FileName:
FileLineNumber: -1
FileColumnNumber: -1
Method:
StackTrace:
Message: System.ArgumentException: The email address (myemail) is not in a valid format.

Hi Les,

Can you please revisit the thread and check Marc Fuller's comments on 2/8 about a trailing space? Does his suggestion help you?

http://www.datasprings.com/products...380/afpg/2

Thanks!
Candace

Hi Candace. I checked for this. It still throws the same error. Any suggestions are appreciated

Let me refer this to our dev team for further review. Thanks!

Hi guys... I would maybe try a few things...
1. Copy/paste the exact regular expression you are trying to use.
2. Maybe go to host, host settings and click restart application
3. Please review the other posts and comments on this issue at http://www.datasprings.com/products...394/afpg/2
4. Let me know if you are running a single portal or if there are multiple portals, this might be referring to one portal and the setting is portal specific.

-Chad

Hi Chad. Im still receiving the same error, Ive reviewed all the posts related to this issue and reviewing all our settings.

Im getting really beat up that our client cannot send their messages. Any assistance is greatly appreciated.

thanks

I was having this same problem with my Data Springs module. My set up is a parent portal that is not using any DataSprings modules, and 2 child portals that are. I had changed the email regex in the 2 child portals, and still no joy. Finally, I tried changing the regex in the parent portal (which I shouldn't have had to do), and my emails started working.

Good luck - I hope that works for you.

Ok - an update. The fix I listed above helps some of the functions of some of my DataSprings modules, but it doesn't work for all functions. Unfortunately, the ones it isn't working for are the ones I need the most. Emails are still not being sent by the newsletter, although verification emails do get sent when a user opts in to a list.

Hi guys,

Ok. I believe I am starting to get enough information on this now to know what might be going on.

First - I should start by mentioning that I am under the impression after talking with some DNN Core folks that this regular expression will be changed in future versions back to how it worked prior to 5.6.1 (or something similar that fixes the problem) in 5.6.2. I am really hoping this as there is little we can do within our modules except make a patch that would maybe ignore the from name in the email (which you actually should be able to do anyway within the module by leaving the from name blank.

Second - The reason I think its working in some areas and not others is because this is a 'portal' setting where you can change the regular expression. Based on looking at the code I don't think that this 'portal setting' takes place on any modules/components that are using the DNN Scheduler. This is because the DNN scheduler runs in a stateless/portal less environment and therefore when its sends an email its not ever really looking at any individual portal setting (and the code that does this is in the DNN Core application and not something we can specify when sending the email).

So... The next steps I am imaging for clients running into this problem are:
1. Recompile the DNN Source Code and have the code changed back to use the previous regular expression. We will also look at doing this if we need to (we had to do something similar for 5.4.4 at one point) but we really don't want to be in the business of supporting the DNN framework itself and we would be able to do this for customers running on the DNN professional version.

2. Leave out the 'From Name' in applications that are still not sending email.

3. Await for the 5.6.2 DNN version which hopefully will fix this issue.


-Chad