On 8/4/24 03:35, Дилян Палаузов wrote:
Then I get a site, partially in English, partially localized. It is in my domain at address /mm3/accounts/confirm-email/ , and states:
Messages: Confirmation of email address sent to ...@yahoo.com Menu: Entrance \r\n New registration
Confirm your email address:
We have sent an email to you for verification. Follow the link provided to finalize the signup process. If you do not see the verification email in your main inbox, check your spam folder. Please contact us if you do not receive the verification email within a few minutes.
I'm not certain, but it looks like you are signing in to a new account and django-allauth is creating the account with the address from yahoo and is asking you to confirm.
I have indeed received an email, which states: New signin from … Hi, Your Yahoo account … was just used to sign in on …. If you did this, you’re all set. If not, please use this link to stop sharing, and create a new password. Have a great day! Thanks,Yahoo
So, the /account/confirm-email states I have received an email for verification, but the email sent says no verification is needed, I am all set up.
Any idea what can I improve?
This appears to be a glitch in the new account verification process. In any case, it's a django-allauth issue, not a Mailman issue.
Once you have gone through this dance, what happens the next time you sign in via Yahoo.
In addition https://gitlab.com/mailman/mailman-suite/-/blob/master/mailman-suite_project... suggests adding in settings.py:
SOCIALACCOUNT_PROVIDERS = {'openid': {'SERVERS': [dict(id='yahoo', name='Yahoo', openid_url='http://me.yahoo.com')]}}
which I have not done. That is, I do not use the “openid” provider, but the “yahoo” provider. Do I have to use the OpenID provider when using Yahoo?
I don't think it would matter.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan