Registration Verification Email Not Sent

(btw, these forums do not seem to work w/FF 4 or 5 - captcha never appears)

I have a site where I implemented URSP 2 years ago - all seemed to work fine.

Flash forward 2 years because the client stopped doing anything with the site and now is gung-ho to proceed... except now the User Registration page is not sending out the verification email. The page that it redirects to after a registration comes up, and the info in the form is entered into the database.

If a verified user goes to the "forgot password" page and requests a reminder email, that email gets sent fine.

Any help here is greatly appreciated!

Hunter

I would just like to second this that I have been having problems on the forums with Firefox 5. Sometimes the pages load and they are blank pages, reloading the page does nothing to correct the problem. But all seems to work correct in IE 9.

I just had to switch to Chrome to post this message.

Larry

the only real difference between the registration email and the verification eamil is the from address setting.

in the WA_Globals/WA_Globals.php file, what is set for:
$WAGLOBAL_Registration_Email_FROM

and what is set for:
$WAGLOBAL_Verification_Email_FROM


also what about the registration subject versus verification subject?


we are investigating the issues with different browsers, however, with Fire Fox 5 being in beta testing stages, we probably wont investigate that one to much till it is released.

the registration from and verification from addresses are set the same. I even created an account with that name on the email server just in case it was balking at an "unknown" user.

the verification global subject is:
$WAGLOBAL_Verification_Email_Subject = "(domain) Email Verification" ;

the registration global subject is:
$WAGLOBAL_Registration_Email_Subject = "Welcome to (domain)" ;

the FROM is:
$WAGLOBAL_Verification_Email_FROM = "noreply@(domain).com" ;
$WAGLOBAL_Registration_Email_FROM = "noreply@(domain).com" ;

obviously, I've used (domain) here in place of the actual domain info

we resolved this in a screen sharing session by clearing the bcc addresses.