title: django-rest-auth: What is the email verification for and how can I let the user activate the account correctly?
body: <p>I might misunderstand something. <code>django-rest-auth</code> provides <code>RegisterView</code> and an email is supposed to be sent to the user's email after user sign up. However, I've noticed the user is registered with <code>is_active=True</code> even before the user confirm the email. Then, what is the email verification for? Do I have to override something and create the user with <code>is_active=False</code> when the user register with a site? And if so, how can I achieve it properly? I'm having trouble with it.</p>
  
  <p>Here is what I did.</p>
  
  <p><code>urls.py</code></p>
  
  <pre><code>path('api/v1/rest-auth/registration/', include('rest_auth.registration.urls')),
  </code></pre>
  
  <p><code>serializers.py</code></p>
  
  <pre><code>from rest_auth.registration.serializers import RegisterSerializer
  
  class CustomRegistrationSerializer(RegisterSerializer):
  
      def save(self, request):
          user = super(CustomRegistrationSerializer, self).save(request)
          user.is_active = False
          return user
  </code></pre>
  
  <p><code>settings.py</code></p>
  
  <pre><code>REST_AUTH_REGISTER_SERIALIZERS = {
  'REGISTER_SERIALIZER': 'appname.serializers.CustomRegistrationSerializer',
  }
  </code></pre>
  
  <p>and here is an error I encountered.</p>
  
  <blockquote>
    <p>File "rest_auth/registration/views.py", line 46, in dispatch
        return super(RegisterView, self).dispatch(*args, **kwargs)</p>
    
    <p>File "/rest_framework/views.py", line 495, in dispatch
        response = self.handle_exception(exc)</p>
    
    <p>File "rest_framework/views.py", line 455, in handle_exception
        self.raise_uncaught_exception(exc)</p>
    
    <p>File "rest_framework/views.py", line 492, in dispatch
        response = handler(request, *args, **kwargs)</p>
    
    <p>File "rest_framework/generics.py", line 192, in post
        return self.create(request, *args, **kwargs)</p>
    
    <p>File "rest_auth/registration/views.py", line 65, in create
        user = self.perform_create(serializer)</p>
    
    <p>File "rest_auth/registration/views.py", line 81, in perform_create
        None)</p>
    
    <p>File "allauth/account/utils.py", line 183, in complete_signup
        signal_kwargs=signal_kwargs)</p>
    
    <p>File "/allauth/account/utils.py", line 133, in perform_login
        return adapter.respond_user_inactive(request, user)</p>
    
    <p>File "allauth/account/adapter.py", line 454, in respond_user_inactive
        reverse('account_inactive'))</p>
    
    <p>File "django/urls/resolvers.py", line 622, in _reverse_with_prefix
        raise NoReverseMatch(msg)
    django.urls.exceptions.NoReverseMatch: Reverse for 'account_inactive' not found. 'account_inactive' is not a valid view function or pattern name.</p>
  </blockquote>
  
  <p>I'd like to hear how people who are using <code>django-rest-auth</code> handle with registration.
  Anyone have used <code>django-rest-auth</code> and coule give me tips?</p>