Skip to main content

A Django app for email verification.

Project description

Email-Verification for Django

Email verification for new signups or new user is a two step verification process and adds a layer for security for valid users.

verify_email is a django app that provides this functionality right of the bat without any complex implementation.

The app takes care of :

  • Settings user's is_active status to False.
  • Generate hashed token for each user.
  • Generate a verification link and sending it to user's email.
  • Recieve a request from verification link and verify for its validity.
  • Activating the user's account.

What you have to impliment is :

Note : The app is designed to be used right of the bat, however, further customizations options are also provided in Advance section below.


NOTE : Don't forget to activate virtual environment if you have one.

pip install Django-Verify-Email

Quick start

The steps to getting started is very simple. Like any other app, this can be installed easily by adding "verify_email" in your installed apps like:

Note : This documentation assumes that you already have a mail server configured for your project to send mails.

if Not, then your first step should be Step 0:

Step 0 :-

--- Bypass this step if you already have these things setup for your project. ---

In your :

EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend'
EMAIL_HOST_USER = os.environ.get('EMAIL_ID') 
EMAIL_HOST_PASSWORD = os.environ.get('EMAIL_PW')

DEFAULT_FROM_EMAIL = 'noreply<>'

Main steps...

Step 1 :-

Add "verify_email" to your INSTALLED_APPS setting like this:


Step 2 :-

Include the "verify_email" URLconf in your project like this:

urlpatterns = [
	path('verification/', include('verify_email.urls')),	


Step 3 :-

Apply migrations...

python migrate

Step 4 :-

For sending email from a signup form, in your import:

from verify_email.email_handler import send_verification_email

Now in the function where you are validation the form:


def register_user(request):
    if form.is_valid():

        inactive_user = send_verification_email(request, form)

Attention : "send_verification_email()" takes two arguments, requests and form in order to set user's active status.

The "inactive_user" that is returned by "send_verification_email()" contains a saved user object just like would do(with is_active status set as False), which you can further use to extract user information from cleaned_data dictionary, as shown below :


# Output :

The user is already being saved as inactive and you don't have to .save() it explicitly.

If anything goes wrong in sending the verification link email, the user will not be saved, so that user can try again.

At this point, you are good to go...

Start the development server and signup with an email and you should be getting an email on the entered email with the default template for account activation. (You can provide your own html template. see Advance Section)

Note : The app comes with default email templates which can be overriden. See Custom Email Templates

Verifying User's email :


That's right ! , you don't have to impliment any other code for validating user with their respective unique tokens and emails.

The app takes care of everything in background.

  • When user click on the verification link, it comes to :
    path('verification/', include('verify_email')),
    which you defined in your project's in step 2 above.
  • This pattern is further extended in this app's where it accepts encoded email and encoded hashed token from the verification link.
  • It then checks for user by that email.
  • If user exist, it then checks for token if it is valid for that user or not.
  • If the token is valid, it activates the user's account by setting is_active attribute to True and last_login to
  • If the token is alredy been redeemed or modified, you'll be redirected to a "verification failed" page.

This whole process from generating HMAC hashed token for each user to verifying it for a unique user, is abstracted within the app 😃.


Expiration of link and Resending emails :

The link, by default, does not expire until it has been used atleast once, however, you can change this behaviour by specifying the time as "EXPIRE_AFTER" in The variable can be set as :

  • By default the time is considered in seconds, so if you set "EXPIRE_AFTER" as integer, that will be considered in seconds.
  • You can specify time unit for large times, max unit is days.
  • Its very simple just suffix the "EXPIRE_AFTER" variable's value with a time unit from ["s", "m", "h", "d"]. (Keep in mind, the "m" here is minutes, not month)


  • If I have to make a link expire after one day, then I'd do:

    • EXPIRE_AFTER = "1d"
  • If I have to make a link expire after one hour, then I'd do:

    • EXPIRE_AFTER = "1h"
  • If I have to make a link expire after one minute, then I'd do:

    • EXPIRE_AFTER = "1m"

and so on... By default, if you do not specify a unit, it'll be considered in seconds.

Re-Sending Email

A user can request new verification link For a specific no. of times in case the previous one has expired. By default, a user can request new link two times which, obviously can be modified by you.

Set a "MAX_RETRIES" variable in specifying the no. of times a user is allowed to request new link.

After that no. is exceeded, the user will be automatically redirected on an error page showing that you have maxed out.

NOTE : This info is stored in database so you have to apply migrations (step 3) to use this feature.

Custom Email Templates :

The app is packed with default html templates to handle the web pages but if you want to provide your own template you can do it by setting an attribute in :

HTML_MESSAGE_TEMPLATE = "path/to/html_template.html"

VERIFICATION_SUCCESS_TEMPLATE = "path/to/success.html"

VERIFICATION_FAILED_TEMPLATE = "path/to/failed.html"
SUBJECT = 'subject of email'

# default subject is : Email Verification Mail

Inside Templates :

Custom HTML Message Template :

Two variables are passed in context dict of "HTML_MESSAGE_TEMPLATE" :

  • {{request}} : Which is the same request passed in to send_verification_email.
  • {{link}} : Which contains verification link

IMPORTANT : if you are using custom html message template for email that has to be sent to user, <u>provide a {{link}} as a template tag to contain verification link.</u>

You Must Pass This In Your Template . Otherwise the sent mail will not contain the verification link.

For Ex :

my_custom_email_message.html :

<div class="format-font" >
    <a href="{{link}}" class="my-button" >Verify</a>  # ----> The "link" variable is passed by the app's backend containing verification link.

----> "link" is a variable, that contains verification link, and is passed in html message template during sending the email to user.

Custom HTML Verification Success and Failed pages :

Success :

Two variables are passed in context dictionary of "VERIFICATION_SUCCESS_TEMPLATE" :

  • {{mgs}} : Which contains the message to be displayed on successful verification.
  • {{link}} : Which contains redirect link to login page.

In template :

<h1 style="text-align: center; color: white;">
    {{msg}}     # __--> message variable

<a href="{{link}}" class="btn btn-primary">     # __--> Link of login page

Failed :

Only "{{msg}}" is passed for failed msg in template.

In template :

<h1 style="text-align: center; color: white;">

Successful Verification :

After verification is successful, you might want to redirect the user to login page. You can do this in two ways :

  • 1 Redirect from success webpage. The user will be prompted to show success page with a button on it to navigate to Login page.
    LOGIN_URL = 'name of your login pattern'
    Note: This variable is also used by django.
  • 2 Redirect directly to login page without stopping at success message page. The user will be directly sent to login page, bypassing the success page.

Project details

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

Django-Verify-Email-1.0.8.tar.gz (30.6 kB view hashes)

Uploaded source

Built Distribution

Django_Verify_Email-1.0.8-py3-none-any.whl (32.5 kB view hashes)

Uploaded py3

Supported by

AWS AWS Cloud computing Datadog Datadog Monitoring Facebook / Instagram Facebook / Instagram PSF Sponsor Fastly Fastly CDN Google Google Object Storage and Download Analytics Huawei Huawei PSF Sponsor Microsoft Microsoft PSF Sponsor NVIDIA NVIDIA PSF Sponsor Pingdom Pingdom Monitoring Salesforce Salesforce PSF Sponsor Sentry Sentry Error logging StatusPage StatusPage Status page