Here is my /mailamn/config/mailman-web/settings_local.py. I get an error message

curl http://172.19.199.3:8000/postorius/lists/ curl: (7) Failed connect to 172.19.199.3:8000; No route to host Please comment out all the lines that are not necessary.

MAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = '172.19.199.1' EMAIL_PORT = 25 USE_SSL = False

INSTALLED_APPS = ( 'hyperkitty', 'postorius', 'django_mailman3', # Uncomment the next line to enable the admin: 'django.contrib.admin', # Uncomment the next line to enable admin documentation: # 'django.contrib.admindocs', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'paintstore', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', #'django_mailman3.lib.auth.fedora', #'allauth.socialaccount.providers.openid', #'allauth.socialaccount.providers.github', #'allauth.socialaccount.providers.gitlab', #'allauth.socialaccount.providers.google', )

Same thing happens to me. If I comment out all the socialauth plugins, the web service doesnt work.

Are you using the docker-mailman installation method?

⁣Get BlueMail for Android ​

On Feb 16, 2021, 7:32 PM, at 7:32 PM, kwp.klein@gmail.com wrote:

Here is my /mailamn/config/mailman-web/settings_local.py. I get an error message

curl http://172.19.199.3:8000/postorius/lists/ curl: (7) Failed connect to 172.19.199.3:8000; No route to host Please comment out all the lines that are not necessary.

MAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = '172.19.199.1' EMAIL_PORT = 25 USE_SSL = False

INSTALLED_APPS = ( 'hyperkitty', 'postorius', 'django_mailman3', # Uncomment the next line to enable the admin: 'django.contrib.admin', # Uncomment the next line to enable admin documentation: # 'django.contrib.admindocs', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'paintstore', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', #'django_mailman3.lib.auth.fedora', #'allauth.socialaccount.providers.openid', #'allauth.socialaccount.providers.github', #'allauth.socialaccount.providers.gitlab', #'allauth.socialaccount.providers.google', )

---

Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

On 2/16/21 4:46 AM, Matthew Alberti wrote:

I think each plugin has to be configured separately, such as with an API key from each service.

For what it's worth, this list supports 4 Oauth2 providers, Google, Facebook, Github and Gitlab. 3 of these require stuff in Django's settings

SOCIALACCOUNT_PROVIDERS = {
    'google': {
        'SCOPE': ['profile', 'email'],
        'AUTH_PARAMS': {'access_type': 'online'},
    },
    'facebook': {
       'METHOD': 'oauth2',
       'SCOPE': ['email'],
       'FIELDS': [
           'email',
           'name',
           'first_name',
           'last_name',
           'locale',
           'timezone',
           ],
       'VERSION': 'v2.12',
    },
    'gitlab': {
        'SCOPE': ['read_user'],
    },
}

Additionly, each requires creation of an app with the provider and
addition of the app and its keys in the Django admin UI at
socialaccount/socialapp/. See
<https://django-allauth.readthedocs.io/en/latest/providers.html> for
more info on setting up specific providers.


-- 
Mark Sapiro <mark@msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

On 2/16/21 7:27 PM, kwp.klein@gmail.com wrote:

I want t disable all social account providers. I need an example and the name of the file.

I'm not certain this will do what you want,, but in your Django local settings (probably settings_local.py) put

SOCIALACCOUNT_PROVIDERS = {}

You can also remove

'allauth.socialaccount'

and any

'allauth.socialaccount.providers.*' from INSTALLED_APPS

and in the Dgango web admin interface under Social Accounts › Social applications, if any are listed, delete them.

-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

On 2/16/21 8:20 PM, Aaron Klein wrote:

This is my local_settings.py. The social account icons are not deleted.

you need to ensure that they are deleted from the Dgango web admin interface under Social Accounts › Social applications

2. I don't find the Social Accounts › Social applications. where I have to search?

It is in the Django web UI. Assuming you have something like

url(r'^django/', admin.site.urls),

in your urls.py, not commented, it wuoul be a url like

https://example.com/admin/socialaccount/socialapp/

-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

On 2/16/21 11:40 PM, Jörg Klein wrote:

I logged in in the Django Web. But the social buttons are still visible.

Select social application to change ADD SOCIAL APPLICATION 0 social applications

If you have removed them from Django as above and also set

SOCIALACCOUNT_PROVIDERS = {}

and removed the allauth.socialaccount.providers.* entries from INSTALLED_APPS in your Django settings, then I don't know what the problem is.

Actually just removing the allauth.socialaccount.providers.* entries from INSTALLED_APPS should be enough.

-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan