I saw in Gemini where this issue was verified and fixed! in this current release 05.04.02(66)

Gentlemen I can verify that Three (count'em 3) of my clients 05.04.02 (66) sites, 2 clean installs and 1 upgrade are throwing these errors with this same problem.

And yet as they are thrown this error and sent away in shame I look in the user accounts and low and behold they are in there. They get no verification email and the client gets no users.

Here is the exception;

ModuleId: -1
ModuleDefId: -1
FriendlyName: User Registration
ModuleControlSource: DesktopModules/Admin/Security/ManageUsers.ascx
AssemblyVersion: 5.4.2
PortalID: 0
PortalName: xxx
UserID: -1
UserName:
ActiveTabID: 39
ActiveTabName: Home
RawURL: /Register.aspx?ReturnUrl=http%3a%2f%2fwww.xxx.com%2fHome.aspx
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer: http://www.xxx.com/Register.aspx?Retu...
UserAgent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.70 Safari/533.4
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: f6c812c2-3346-409d-aefc-7e74e89a923a
InnerException: Mailbox unavailable. The server response was: <xxx@yahoo.com> No such user here
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Net.Mail.SmtpTransport.SendMail
StackTrace:
Message: DotNetNuke.Services.Exceptions.ModuleLoadException: Mailbox unavailable. The server response was: <xxx@yahoo.com> No such user here ---> System.Net.Mail.SmtpFailedRecipientException: Mailbox unavailable. The server response was: <xxx@yahoo.com> No such user here at System.Net.Mail.SmtpTransport.SendMail(MailAddress sender, MailAddressCollection recipients, String deliveryNotify, SmtpFailedRecipientException& exception) at System.Net.Mail.SmtpClient.Send(MailMessage message) at DotNetNuke.Services.Mail.Mail.SendEmail(String fromAddress, String senderAddress, String toAddress, String subject, String body) at DotNetNuke.Services.Mail.Mail.SendMail(UserInfo user, MessageType msgType, PortalSettings settings) at DotNetNuke.Entities.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 ---

So forgive the pissed off tone but I have been 18 hours trying to fix this with no results except to go to my clients tomorrow and figure something else out. A lot of money down the drain. I doubt I get any responses from here. But I can dream though.

If anyone from the core team is reading this, the big money site I rolled out threw this error out to 12 of the 21 first registrants untill I got the yellow config screen of death. Sporatic, so this was not a bad email or smtp setup because some registrations made it and some were sent to code hell.

Is there anyone in this forum with expert knowledge of what the last known release was before this problem appeared? And I would need you to bet your years wages your right.