Ticket #86 (assigned enhancement)

Opened 2 years ago

Last modified 2 years ago

validate email module

Reported by: chrisbraybrook Assigned to: chrisbraybrook (accepted)
Priority: critical Milestone: Future / Unassigned
Component: module Version: gbm-0.1-beta
Severity: Keywords:
Cc:

Description

a module designed to require users to re-validate their registered e-mail addresses. for use primarily in the case where we already have a lot of users without valid e-mail addresses in the system.

this module would lock the user's account until they input a valid e-mail address and verify it with the validation key sent to said address.

a companion module should also be written to run as a cron job every month or so, requiring that those who haven't validated their e-mail in 6 months do so.

note: any change to the e-mail address on a user's account should prompt a verification.

Attachments

email_validation.patch (15.3 kB) - added by chrisbraybrook on 02/18/07 13:17:25.
email validation patch (build 1)

Change History

12/11/06 18:23:35 changed by chrisbraybrook

  • version set to gbm0.1-beta.

12/18/06 20:47:49 changed by chrisbraybrook

  • status changed from new to assigned.

i will not write the companion cron job module at this time, however, it seems important that we get valid e-mail addresses in the database. beginning research into this module.

02/11/07 20:20:31 changed by chrisbraybrook

implementing this is no small task. users will be able to access this module either from the link provided them in the e-mail they receive, or by accessing the link in their "Edit Profile" module.

I am currently considering some security additions to the edit profile module so that someone cannot validate their e-mail address and then change it to something that doesn't exist or is not correct.

02/18/07 00:26:26 changed by anonymous

  • priority changed from major to critical.

02/18/07 11:37:10 changed by chrisbraybrook

The patch file I am attaching to this ticket will provide basic implementation for email validation, and require that the user validate their e-mail address when they change it in the edit_profile module.

However, it does require some changes to core functions and other modules, and is as yet a bit sloppy. Regardless, it does work.

(follow-up: ↓ 8 ) 02/18/07 12:56:55 changed by brad

You may want to reconsider the cron issue. To me it edges over into possible spam. My alternative suggestion would be to have a way to lock an unvalidated user account after a certain period of time. That way the only users you're going to bother with validation are those that have *not* abandoned their account.

02/18/07 13:17:25 changed by chrisbraybrook

  • attachment email_validation.patch added.

email validation patch (build 1)

02/18/07 13:57:35 changed by chrisbraybrook

  • milestone changed from gbm 0.1-beta to Future / Unassigned.

with this patch, we can implement email validation. I am reassigning the integration of this patch into the core project for a later date.

(in reply to: ↑ 6 ) 03/15/07 17:01:05 changed by chrisbraybrook

Replying to brad:

You may want to reconsider the cron issue. To me it edges over into possible spam. My alternative suggestion would be to have a way to lock an unvalidated user account after a certain period of time. That way the only users you're going to bother with validation are those that have *not* abandoned their account.

Hmmmm...a good point, which also lends towards cleaning up the database of users whose accounts have been locked for more than a certain period of time. (Like 2 months or so.)

(Yes, I only just saw this now.)


Add/Change #86 (validate email module)




Change Properties
Action