How to make email_field as readonly from different table

Hello dear Django community,
I am new to this wonderful framework and currently within the learning curve of how to handle custom user models.

I have the following model in my accounts app:

class BlogUser(AbstractBaseUser, PermissionsMixin):
    username_validator = UnicodeUsernameValidator()

    username = models.CharField(
            "Required. 150 characters or fewer. Letters, digits and @/./+/-/_ only."
            "unique": _("A user with that username already exists."),
    is_active = models.BooleanField(default=True)
    is_admin = models.BooleanField(default=False)

    objects = BlogUserManager()

    USERNAME_FIELD = 'username'
    REQUIRED_FIELDS = ['password', ]

And here is a snippet from another app with a profile model extension to the user model:

from django.contrib.auth import get_user_model

class Author(models.Model):
    user_id = models.OneToOneField(get_user_model(), on_delete=models.PROTECT)
    name = models.CharField(max_length=512)
    email = models.CharField(max_length=512, unique=True)
    author_page_text = models.TextField(default='', blank=True)
    author_page_text_html = models.TextField(default='', blank=True)
    author_picture_url = models.CharField(max_length=512, blank=True)

It plays nice with the admin app so far, but it does not play well with the django auth app, which wants to read the email from the EMAIL_FIELD in the user model when submitting a reset password form for example.
I would like to give it the email from the one to one profile model.
Would there be a way to make this happen?

Thank you for your time and knowledge!

First, Mixins must be listed before the base class in class definitions. You’ll want to fix your BlogUser class definition.

Why do you want to use the email field from the User profile model? I really suggest that you add an email field to your BlogUser model and use it. (And no, unless you’re willing to do a lot of otherwise unnecessary work, it’s not going to work with a “non-local” email field.)

First, Mixins must be listed before the base class in class definitions. You’ll want to fix your BlogUser class definition.

Thank you for pointing that out! Will be fixed immediately.

Good to know that there’s not an easy solution for what I wanted to do there. I’ll follow the advise and put the email field into the BlogUser table.
The reason was that the code that I want to integrate in Django expects the email field in the other table, but I could probably merge them or double the field.