User registration problems should be fixed

Post a reply

Smilies
:D :) :( :o :shock: :? 8) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :wink: :!: :?: :idea: :arrow: :| :mrgreen: :angel: :angry: :beer: :bfg: :chaingun: :cheers: :blergh:
View more smilies

BBCode is ON
[img] is ON
[url] is ON
Smilies are ON

Topic review
   

If you wish to attach one or more files enter the details below.

Maximum filesize per attachment: 1.5 MiB.

Expand view Topic review: User registration problems should be fixed

Re: User registration problems should be fixed

by Rachael » Thu Nov 05, 2009 16:07

Updated - again.

Re: User registration problems should be fixed

by baghead » Thu Oct 08, 2009 18:32

PHP's mail() function sucks; it can't do any kind of authentication. Pear's Mail class is much better. You can use it to send outgoing mail from any gmail account using smtp.gmail.com on port 587, it will almost never go into spam. I'm not sure if you have it available to you, but if so it's definitely worth switching, even if it requires some tiny changes to the code.

Re: User registration problems should be fixed

by Firebrand » Sat Sep 19, 2009 20:00

The email problem seems to be a bug in the current release of PHPbb as noted here:
http://www.phpbb.com/bugs/phpbb3/46725

User registration problems should be fixed

by Rachael » Fri Sep 18, 2009 20:29

Since the move, DRD Team seems to have been plagued with different problems relating to user registration. Two problems appear to have caused this:
  1. The php mail() function was not working. It may have been due to the sendmail configuration on this host - however, I may simply resort to using an external SMTP server instead. The problem is solved for now - it sends mail, but it will most likely be marked as "spam" - I am not positive how I will resolve that.
  2. The register function itself did not permit registrations - at all. The method that was previously used to verify clients was broken during the move - and I am not yet quite sure how to fix it. It has been temporarily disabled, though.
  3. Additionally, CAPTCHA settings have also changed. It should be much more readable now - I figure it's safe to loosen this up quite a bit due to the other verification that is in place.
If there are any further issues, please contact me on ZDoom or Skulltag.

Top