i have bug on reset password link

Using Django The Admin
1

hello guys i’am got a big bug how fix it

i when type email address and click to django send reset password to send reset password link in console i get this

####################################################################

[30/May/2026 23:51:22] “GET /login/ HTTP/1.1” 200 1710
[30/May/2026 23:51:23] “GET /password-reset/ HTTP/1.1” 200 1350
Content-Type: text/plain; charset=“utf-8”
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: =?utf-8?b?2KjYp9iy24zYp9io24wg2q/YsNix2YjYp9qY2Ycg2K/YsQ==?=
127.0.0.1:8000
From: webmaster@localhost
To: ahmadcub9@gmail.com
Date: Sat, 30 May 2026 20:21:35 +0000
Message-ID: 178017249531.136945.18351584476362565960@silent-linux

2LTZhdinINiv2LHYrtmI2KfYs9iqINio2KfYstmG2LTYp9mG24wg2LHZhdiyINi52KjZiNixINiu
2YjYryDYsdinINio2LHYp9uMINin24zZhduM2YQg2LLbjNixINin2LHYs9in2YQg2qnYsdiv2Ycg
2KfbjNivCmFobWFkY3ViOUBnbWFpbC5jb20K2K/YsSDYtdmI2LHYqtuMINqp2Ycg2LTZhdinINiv
2LHYrtmI2KfYs9iqINmG2K/Yp9iv2Ycg2KfbjNivINin24zZhiDYp9uM2YXbjNmEINix2Kcg2YbY
p9iv24zYr9mHINio2q/bjNix24zYrwoKaHR0cDovLzEyNy4wLjAuMTo4MDAwL3Bhc3N3b3JkLXJl
c2V0L01nL2Q5ZjB4ei03YWI0Yjg4ZjQ2MTEzMWJlZjdiMTBiMzI4YzQ3OGM1ZS8gICAK

[30/May/2026 23:51:35] “POST /password-reset/ HTTP/1.1” 302 0
[30/May/2026 23:51:35] “GET /password-reset/done HTTP/1.1” 301 0
[30/May/2026 23:51:35] “GET /password-reset/done/ HTTP/1.1” 200 985

###########################################################

my link is encoded base64 django not auto decoding it
please help me :folded_hands:

2

Welcome @Ahmad-Coder-0 !

Please post your password reset view that is generating this, along with the template.

Also identify what version of Django and Python you are using, and if you are using any third-party libraries as part of this process.

Side Note: When posting code (or any other preformatted text, like your text above) here, enclose the code between lines of three backtick - ` characters. This means you’ll have a line of ```, then your code, then another line of ```. This forces the forum software to keep your code
properly formatted.

3

That’s not a bug, it’s a valid password reset email. Non-ASCII characters have to be encoded in email, and base64 is the most efficient Content-Transfer-Encoding when most of the characters are non-ASCII.

You can paste the encoded block into something like base64decode.org to see the text that would be displayed in an email app. The snippet I quoted above decodes to:

… دیده بگیرید
http://127.0.0.1:8000/password-reset/Mg/d9f0xz-7ab4b88f461131bef7b10b328c478c5e/

4

Yes, that’s right. The problem is that the text shouldn’t be displayed like this, the text should be decrypted.

5

I do not created view for this using CBV and my url is it

    path('password-reset/', AuthViews.PasswordResetView.as_view(success_url='done'),
         name='password_reset'),
    path('password-reset/done/', AuthViews.PasswordResetDoneView.as_view(),
         name='password_reset_done'),
    path('password-reset/<uidb64>/<token>/', AuthViews.PasswordResetConfirmView.as_view(),
         name='password_reset_confirm'),
    path('password-reset/complate/', AuthViews.PasswordResetCompleteView.as_view(),
         name='password_reset_complate'),

this all code project on my github

6

i found it I not wirte Farsi in password_reset_confim.html

but why?

7

It’s precisely what @medmunds described in his response above.

If you actually sent that email such that it was received and opened by a proper client, you would see that it is correct.

When I save that email to a file and then import it into Thunderbird, this is what I see:

image
image1037×495 40.9 KB

And if I run that text through Google translate, I get:

You have sent a password reset request to the following email:
ahmadcub9@gmail.com
Ignore this email if you did not request it

8

thank you very much
So if I send this to real emails, there’s no problem.

9

That’s correct.

You’re using Django’s “console” EmailBackend. It shows exactly what Django would transmit to an SMTP server to send the email. That includes all the encodings needed for email to be delivered properly. The user’s email client will decode everything at the receiving end, before showing it to the user.

Although this is behaving as expected, I agree it would (usually) be more helpful for the console EmailBackend to show the un-encoded version of the message. I’ve opened this new feature request to make that an option.