Search results for "Postorius" - Mailman-users

Trying to configure a list (hosted)

by paul＠arenson.org

Is there a how to on how to configure a list? For example, using a hosted option, I see this menu: Subscription requests Held messages Users Templates Settings Mass operations Banned addresses Header filters And cling on settings, for example. I have already removed my list from the list of lists on the server since I want my website users to only see my list. They can either do that here https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… or here https://list.tokyoprogressive.org/accounts/signup/ I actually do not WANT people to join without being able to use the web interface because it is intended to be a discussion list. So the option to subscribe without creating an account. is confusing to me, which is why I prefer the latter. BUT...using a test of signing up myself (using 3 other email addresses I have), some using the subscription option and some using the bottom one (no account), all the email addresses end up in my members list and non end up in my non members list. (So I am wondering what a non member is. I had thought it was someone who signed up without registering (just name, no password), but if so i wonder why all 3 of my addresses end up in the members place. Lastly, I want to configure it as a discussion list. However, I do not see that option, which was clear in MAILMAN 2. (And I understand that if someone registers without making an account, I cannot set them myself to have an account enabling them to see the archives and post from the web? If it IS possible, that would be great, because the purpose of the archives in my case is to enable better discussions than if one has only to refer to their past emails.) That is about it for now, but I am stuck on this right now and a user manual for non techie people, if it exists, would be nice. I see one for list members but not administrators. Maybe I am looking in the wrong place? Thanks paul

6 years, 2 months

Re: Member Issue Discovered

by Allan Hansen

I agree that deleting, without an explicit request to do so, user-entered information is a violation of the user’s data This applies when the user has set up an account on the system. If he/she has never created an account, then I see no problem cleaning up the system when the user deletes the last subscription, as any remaining data presumably has been created by the server. Keeping that information on the server without the knowledge of the user is not right. Yours, Allan Hansen hansen(a)rc.org > On Nov 2, 2020, at 19:51 , Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > > Brian Carpenter writes: > >> This is in regard to our Affinity/Empathy UIs. I believe the issue >> [about data retention] that was raised originally in this >> thread/post still exists with Postorius/Hyperkitty. > > I don't speak *for* the Mailman team on this, but my *impression* from > these conversations is that we have a consensus on the team: deleting > the User data (authentication and profile) is a very big deal that > should be done only on explicit request, not as an automatic side > effect of other changes. We understand that others have a different > opinion, but we think that this is a difference of opinion, not a > mistake on either side. > > My own suggestion is that we *should* provide the *option* to delete > the User data, and prompt for it, when that User's last subscription > on the server is deleted. Note that there is a race condition where > the user deletes the second-to-last subscription and an admin then > deletes the last one. The user won't see the option, but the admin > will. I can see this as a bad outcome, depending on user's intent, > whether the admin deletes the User object or leaves it in place. > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

5 years

Re: Mixing Mailman 3 with AWS SES

by Ralph Weber

To close the loop on this topic... Comments received directly from one of the people who developed the AWS Marketplace kits for Mailman 3 and Mailman 4 have definitively established that AWS Mailman is *not* intended to interact with AWS SES when receiving email messages. AWS Mailman is designed to receive its email messages via Postfix. With many thanks to all those on this list who corroborated "Mailman and SES don't mix" mantra here, we are taking the advice received from so many sources and ending efforts to do the impossible. All the best, .Ralph On 3/20/2021 8:23 AM, Stephen J. Turnbull wrote: > Ralph Weber writes: > > > I am moving the website www.t10.org from a private/corporate VM to > > AWS EC2s. > > > > For many years, t10.org has had very happy results with using > > Mailman 2 for its email reflector, and I have no real concerns > > about moving to Mailman 3. My bugbear is the fact that I need the > > following mixed bag of incoming email addresses to work in concert > > with each other to receive and handle emails. > > > > > t10(a)t10.org (Primary Mailman Reflector) > > > chair(a)t10.org (Mailman Reflector to direct messages to the T10 > > > chair and his designates) > > * docs(a)t10.org (document posting mechanics - serviced by a small > > mountain of home-grown code code > > * bbs(a)t10.org (other publicly accessible services - serviced by > > code that recalls the days when everything as done on a Bulletin > > Board System, BBS) > > This isn't a Mailman question, to be frank. As Abhilash points out, > Mailman doesn't care about other mailboxes served by its host (unless > they conflict with list names or adinistrative addresses derived from > list names, which evidently yours do not). It's a question about the > mail service at AWS. I've not seen any documentation in our project > about setting up at AWS; I don't know anybody who has done so. (I > haven't looked for either though.) > > I took a quick look for AWS SES documentation. They don't seem to > have any real documentation online for the general public, only lists > of features. They also seem to be very focused on sending rather than > receiving. Much talk of how much mail you can send, bulk emailing, > statistics on responses, and the like. None about setting up for > incoming mail. > > Probably I could get access to online help if I signed up for a free > account, but that's above my pay grade. > > > My best guess is that the AWS Simple Email Service (SES) needs to > > sit in front of both Mailman and the home-grown code, > > I don't know if AWS provides an alternative Complicated Email Service, > but yes, something like SES is going to have to sit in front of the > various mailboxes. > > Mailman itself has a certain amount of capability to deal with the > main email protocols, but it is definitely not capable of replacing > the main mail server. For security reasons I would definitely advise > against any Mailman 3 presence directly on the Internet. It was > designed on the assumption that it would talk to the Internet via a > standard mail server, Postorius (for administration), and HyperKitty > (for mail archives)[1], and occasionally to admins logging in with shell > accounts. > > > All available evidence read to date > > URLs, please. As I wrote above, Amazon's documentation is at best not > very discoverable. > > > suggests that the default AWS installation > > Whose default installation of Mailman? AWS's? Typical 3rd party > configurations? > > > of Mailman 3 assumes that Mailman 3 is the *only* receiver of > > emails in the configuration. > > That's possible, but it's likely an artifact of the application -- I > would expect that many who host Mailman on AWS do so to isolate > Mailman from other services they provide. So it seems reasonable that > in many such installations Mailman is *the* service for that instance. > > But mail servers are designed to be many inputs, many outputs > services. If SES itself is as restricted as you fear, surely AWS > provides an alternative, more powerful mail service. I can imagine > quite a few restrictions, other than the backing application, on the > SES that Amazon *might* impose. But without access to documentation, > we can't say much. > > > Or... Hercules may have already cleaned the Augean Stables, and > > left behind a AWS Lambda function that can serve as a keystone > > puzzle piece for solving my dilemma. > > Good luck on that. I don't know of any, but that would be a quick > solution for you. I hope somebody here knows more. As evidenced by > Andrew's post, there are folks thinking about it, so maybe somebody's > actually tried -- anybody? Successes? Pitfalls to watch for? > > The other issue Andrew mentions could be important. Since Solar Winds > I'm seeing daily attempts to access my O365 server (nonexistent) from > AWS. Given the size of AWS, I think they probably actually do a good > job of keeping felonious behavior to a minimum[2], but a lot of folks > I know are happy to cut off huge netblocks until somebody they know > actually complains. :-( > > Footnotes: > [1] Or more precisely, some webservice providing those services > mediating between the Internet and Mailman sitting cozily behind a > firewall. > > [2] DigitalOcean, on the other hand, is accumulating blocked /24s, > and even /16s, at my firewall. But that's another story.

4 years, 7 months

Re: Docker Mailman3 installation frustration

by Danil Smirnov

Hi, This bug has filed and a couple of workarounds provided here: https://github.com/maxking/docker-mailman/issues/53 Danil 2017-07-13 0:04 GMT+03:00 <ccsmith(a)cetsi.com>: > I've been working on installing Mailman3 for several weeks now, with > limited success. I have tried various installation methods following > instructions on numerous different web pages. My experience has been that > the instructions are often conflicting and never complete. > > My best success has been with the Docker version, so that's what I'm going > to concentrate on here. > > I'm running Ubuntu 16.04 (under Citrix XenServer), with Apache httpd and > postfix. > > Following the instructions on https://asynchronous.in/docker-mailman/, I > did the following: > > * created the directories "/opt/mailman/core" and > "/opt/mailman/web", > * created "/opt/mailman/core/mailman-extra.cfg" and inserted the > suggested [mta] directives, > * inserted the "transport_maps", "local-recipient_maps", and > "relay_domains" entries in the /etc/postfix/main.cf file, > * created the necessary apache config files, > * cloned "https://github.com/maxking/docker-mailman", > * ran "docker-compose up -d" > > At this point, I am able to connect with Postorius. All of the text and > icons show up properly; all is well. It tells me (correctly) that "There > are currently no mailing lists." > > When I click on the "Login" link at the top right, the "Sign In" page > displays correctly. (Aside: Why do so many apps/sites have difficulty with > choosing between "login" and "sign in" and, in fact, use both terms? It can > really be off-putting to non-tech users... and me.) If I input an incorrect > login, I receive (correctly) the message "The username and/or password you > specified are not correct." However, if I input the correct sign-in, I > receive: "Server Error (500)". > > Running "sudo docker exec -it mailman-web cat ../mailman-web-data/logs/mailmanweb.log" > shows me: > > ERROR 2017-07-12 20:34:25,073 25 django.request Internal Server > Error: /accounts/login/ > Traceback (most recent call last): > File "/usr/local/lib/python2.7/site-packages/django/core/handlers/exception.py", > line 39, in inner > response = get_response(request) > ... more stuff ... > File "/usr/local/lib/python2.7/smtplib.py", line 747, in > sendmail > raise SMTPRecipientsRefused(senderrs) > SMTPRecipientsRefused: {u'pacetechadmin(a)cetsi.com': (451, '4.3.0 < > pacetechadmin(a)cetsi.com>: Temporary lookup failure')} > > On the Docker host (ubuntuServer2), /var/log/mail.log shows: > Jul 12 13:48:53 ubuntuServer2 postfix/smtpd[19931]: error: open > /opt/mailman/core/var/data/postfix_domains: No such file or directory > Jul 12 13:48:53 ubuntuServer2 postfix/smtpd[19931]: error: open > /opt/mailman/core/var/data/postfix_lmtp: No such file or directory > Jul 12 13:48:53 ubuntuServer2 postfix/smtpd[19931]: connect from > unknown[172.19.199.3] > Jul 12 13:48:53 ubuntuServer2 postfix/trivial-rewrite[19843]: > warning: regexp:/opt/mailman/core/var/data/postfix_domains is > unavailable. open /opt/mailman/core/var/data/postfix_domains: No such > file or directory > Jul 12 13:48:53 ubuntuServer2 postfix/trivial-rewrite[19843]: > warning: relay_domains: regexp:/opt/mailman/core/var/data/postfix_domains: > table lookup problem > Jul 12 13:48:53 ubuntuServer2 postfix/trivial-rewrite[19843]: > warning: relay_domains lookup failure > Jul 12 13:48:53 ubuntuServer2 postfix/trivial-rewrite[19843]: > warning: regexp:/opt/mailman/core/var/data/postfix_domains is > unavailable. open /opt/mailman/core/var/data/postfix_domains: No such > file or directory > Jul 12 13:48:53 ubuntuServer2 postfix/trivial-rewrite[19843]: > warning: relay_domains: regexp:/opt/mailman/core/var/data/postfix_domains: > table lookup problem > Jul 12 13:48:53 ubuntuServer2 postfix/trivial-rewrite[19843]: > warning: relay_domains lookup failure > Jul 12 13:48:53 ubuntuServer2 postfix/smtpd[19931]: NOQUEUE: > reject: RCPT from unknown[172.19.199.3]: 451 4.3.0 < > pacetechadmin(a)cetsi.com>: Temporary lookup failure; > from=<postorius(a)localhost.local> to=<pacetechadmin(a)cetsi.com> proto=ESMTP > helo=<mailman-web> > Jul 12 13:48:54 ubuntuServer2 postfix/smtpd[19932]: error: open > /opt/mailman/core/var/data/postfix_domains: No such file or directory > Jul 12 13:48:54 ubuntuServer2 postfix/smtpd[19932]: error: open > /opt/mailman/core/var/data/postfix_lmtp: No such file or directory > Jul 12 13:48:54 ubuntuServer2 postfix/smtpd[19932]: connect from > unknown[172.19.199.3] > Jul 12 13:48:54 ubuntuServer2 postfix/trivial-rewrite[19843]: > warning: regexp:/opt/mailman/core/var/data/postfix_domains is > unavailable. open /opt/mailman/core/var/data/postfix_domains: No such > file or directory > Jul 12 13:48:54 ubuntuServer2 postfix/trivial-rewrite[19843]: > warning: relay_domains: regexp:/opt/mailman/core/var/data/postfix_domains: > table lookup problem > Jul 12 13:48:54 ubuntuServer2 postfix/trivial-rewrite[19843]: > warning: relay_domains lookup failure > Jul 12 13:48:54 ubuntuServer2 postfix/trivial-rewrite[19843]: > warning: regexp:/opt/mailman/core/var/data/postfix_lmtp is unavailable. > open /opt/mailman/core/var/data/postfix_lmtp: No such file or directory > Jul 12 13:48:54 ubuntuServer2 postfix/trivial-rewrite[19843]: > warning: regexp:/opt/mailman/core/var/data/postfix_lmtp lookup error for > "root@localhost" > Jul 12 13:48:54 ubuntuServer2 postfix/trivial-rewrite[19843]: > warning: transport_maps lookup failure > Jul 12 13:48:54 ubuntuServer2 postfix/smtpd[19932]: NOQUEUE: > reject: RCPT from unknown[172.19.199.3]: 451 4.3.0 <root@localhost>: > Temporary lookup failure; from=<root(a)localhost.local> to=<root@localhost> > proto=ESMTP helo=<mailman-web> > Jul 12 13:48:54 ubuntuServer2 postfix/smtpd[19932]: disconnect > from unknown[172.19.199.3] ehlo=1 mail=1 rcpt=0/1 rset=1 quit=1 commands=4/5 > Jul 12 13:48:54 ubuntuServer2 postfix/smtpd[19931]: lost > connection after RSET from unknown[172.19.199.3] > Jul 12 13:48:54 ubuntuServer2 postfix/smtpd[19931]: disconnect > from unknown[172.19.199.3] ehlo=1 mail=1 rcpt=0/1 rset=1 commands=3/4 > > And /var/log/mail.err is filling up with: > Jul 12 13:48:53 ubuntuServer2 postfix/smtpd[19931]: error: open > /opt/mailman/core/var/data/postfix_domains: No such file or directory > Jul 12 13:48:53 ubuntuServer2 postfix/smtpd[19931]: error: open > /opt/mailman/core/var/data/postfix_lmtp: No such file or directory > Jul 12 13:48:54 ubuntuServer2 postfix/smtpd[19932]: error: open > /opt/mailman/core/var/data/postfix_domains: No such file or directory > Jul 12 13:48:54 ubuntuServer2 postfix/smtpd[19932]: error: open > /opt/mailman/core/var/data/postfix_lmtp: No such file or directory > > > Any thoughts on what the problem is? Have I missed a step? > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

8 years, 3 months

Re: Migrating mailman3 to latest ubuntu lts

by Mark Sapiro

On 12/16/23 10:12 AM, Helio Loureiro wrote: > Hi, > > Well... not that good. Now it is mailman3-web that doesn't work. > > mailman@new-machine ~ (v3.3.9)> source venv/bin/activate.fish > (venv) mailman@new-machine ~ (v3.3.9)> mailman-web > > Type 'mailman-web help <subcommand>' for help on a specific subcommand. > > Available subcommands: > > [django] > check > compilemessages > createcachetable > dbshell > diffsettings > dumpdata > flush > inspectdb > loaddata > makemessages > makemigrations > migrate > optimizemigration > runserver > sendtestemail > shell > showmigrations > sqlflush > sqlmigrate > sqlsequencereset > squashmigrations > startapp > startproject > test > testserver This response indicates that `mailman-web` is not getting settings.py. Have you configured /etc/mailman3/settings.py? See <https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-configu…>. > (venv) mailman@new-machine ~ (v3.3.9)> mailman-web check > System check identified no issues (0 silenced). > (venv) mailman@new-machine ~ (v3.3.9)> mailman-web check migrate You should run `mailman-web migrate` not `mailman-web check migrate` plus others. See <https://docs.mailman3.org/en/latest/install/virtualenv.html#run-database-mi…> et.seq. but first you need the appropriate settings so `mailman-web` returns something like ``` $ mailman-web Type 'mailman-web help <subcommand>' for help on a specific subcommand. Available subcommands: [account] account_unsetmultipleprimaryemails [auth] changepassword createsuperuser [compressor] compress mtime_cache [contenttypes] remove_stale_contenttypes [django] check compilemessages createcachetable dbshell diffsettings dumpdata flush inspectdb loaddata makemessages makemigrations migrate optimizemigration sendtestemail shell showmigrations sqlflush sqlmigrate sqlsequencereset squashmigrations startapp startproject test testserver [django_extensions] admin_generator clean_pyc clear_cache compile_pyc create_command create_jobs create_template_tags delete_squashed_migrations describe_form drop_test_database dumpscript export_emails find_template generate_password generate_secret_key graph_models list_model_info list_signals mail_debug managestate merge_model_instances notes pipchecker print_settings print_user_for_session raise_test_exception reset_db reset_schema runjob runjobs runprofileserver runscript runserver_plus set_default_site set_fake_emails set_fake_passwords shell_plus show_template_tags show_urls sqlcreate sqldiff sqldsn sync_s3 syncdata unreferenced_files update_permissions validate_templates [django_q] qcluster qinfo qmemory qmonitor [haystack] build_solr_schema clear_index haystack_info rebuild_index update_index [hyperkitty] attachments_to_file hyperkitty_import hyperkitty_warm_up_cache mailman_sync update_index_one_list [postorius] mmclient reset_passwords [rest_framework] generateschema [sessions] clearsessions [staticfiles] collectstatic findstatic runserver ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

Re: under which uid should uwsgi/manage.py run?

by Guillermo Hernandez (Oldno7)

On 14/1/22 18:16, Axel Rau wrote: > Hi Guillermo, > > thanks for your reply. > >> Am 14.01.2022 um 12:51 schrieb Guillermo Hernandez (Oldno7) via Mailman-users <mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org>>: >> > . . . >> drwxr-xr-x 21 mailman mailman 1024 Jul 8 2021 lists > How are new lists created by the web frontend with uid www? That's because is not "www" who is doing that work (I suspect). In my apache24 httpd.conf file I have these lines ##### LoadModule wsgi_module "/usr/local/lib/python3.7/site-packages/mod_wsgi/server/mod_wsgi-py37.so" WSGIPythonHome "/usr/local" WSGIDaemonProcess hyperkitty threads=25 python-path=/usr/local/mailman3 user=mailman3 group=mailman WSGIProcessGroup hyperkitty #### In the httpd-vhosts.conf I have all the Alias directives and, related to this, this lines: WSGIScriptAlias /mailman3 /usr/local/mailman3/wsgi.py process-group=hyperkitty WSGIScriptAlias /hyperkitty /usr/local/mailman3/wsgi.py process-group=hyperkitty WSGIScriptAlias /postorius /usr/local/mailman3/wsgi.py process-group=hyperkitty WSGIScriptAlias /archives /usr/local/mailman3/wsgi.py process-group=hyperkitty <Directory "/usr/local/mailman3"> <Files wsgi.py> Require all granted </Files> WSGIProcessGroup hyperkitty </Directory> ##### I believe that you can be suffering of a mixup of configuration files (al least the ownership that has to be mailman). > I like your approach, but must resolve my pgsql cert access issue. > >> I've read your mail about your installation and I did it different. I followed the steps that I detailed in https://forums.freebsd.org/threads/mailman-3.61050/#post-488128 <https://forums.freebsd.org/threads/mailman-3.61050/#post-488128> > I followed the same, but had trouble with the recent cryptography python package. > I’m now at Python3.9 > >> Thus I don't know if it can help, but I know for sure that I don't like that your ../var/etc dir is owned by root. > I have changed that to mailman. > > Axel > --- > PGP-Key: CDE74120 ☀ computing @ chaos claudius > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

3 years, 9 months

Manual setup - permissions

by Tobias Hachmer

Hello, I'm new to mailman3 and started to setup an instance from scratch per hand, but I'm struggeling running the peaces with the correct user/permissions. I can't find anything regarding running this and that with that user in the docs, so I have the following: virtualenv_dir: /opt/venvs/mailman3 Installed packages in venv: - "Django>=1.11" - "django-haystack" - "libsass" - "mailman==3.3.0" - "mailmanclient" - "mailman-hyperkitty==1.1.0" - "postorius==1.3.0" - "hyperkitty==1.3.0" - "whoosh" - "uwsgi" I have installed the core stuff in /opt/mailman3/core, all is owned by user+group "mailman3": root@host:/opt/mailman3# tree . ├── core │ ├── etc │ │ ├── hyperkitty.cfg │ │ ├── mailman.cfg │ │ └── uwsgi.ini │ ├── log │ │ ├── bounce.log │ │ ├── debug.log │ │ ├── mailman.log │ │ ├── plugins.log │ │ └── smtp.log │ └── var │ ├── archives │ │ └── hyperkitty │ │ └── spool │ │ ├── ... │ ├── cache │ ├── data │ │ ├── mailman.db │ │ ├── postfix_domains │ │ ├── postfix_domains.db │ │ ├── postfix_lmtp │ │ └── postfix_lmtp.db │ ├── lists │ │ └── admin.lists.... │ ├── locks │ ├── master.lck │ ├── master.lck|...|...|... │ ├── master.pid │ ├── message" │ │ ├── ... │ ├── queue │ │ ├── archive │ │ ├── bad │ │ ├── bounces │ │ ├── command │ │ ├── digest │ │ ├── in │ │ ├── nntp │ │ ├── out │ │ ├── pipeline │ │ ├── retry │ │ ├── shunt │ │ └── virgin │ └── templates The django project is installed in /opt/mailman3/web, all is owned by user+group "nginx": └── web └── project ├── db │ └── mailmansuite.db ├── emails ├── fulltext_index │ └── _MAIN_0.toc ├── logs │ ├── mailmansuite.log │ ├── uwsgi-error.log │ └── uwsgi.log ├── manage.py ├── __pycache__ │ ├── settings.cpython-35.pyc │ └── urls.cpython-35.pyc ├── run │ └── uwsgi.sock ├── settings.py ├── static ├── urls.py └── wsgi.py The mailman3 core ist running with user+group "mailman3". And the uwsgi service is running as root with drops privileges to user+group "nginx". Now, running the scheduled tasks (which run from user+group "nginx") for django I ran into permission problems, because the nginx user can't access/write to the needed files in /opt/mailman3/core/... If anyone of you is able to read ansible tasks, this is how I set this up via ansible: https://github.com/freifunk-mwu/ansible-ffmwu/blob/mail/roles/service-bundl… I would appreciate any hints how to run the different peaces of mailman3 with the correct user/groups/permissions. Thanks in advance, Tobias

6 years, 1 month

Re: Twitter OAuth2

by Mark Sapiro

On 12/28/22 11:37, Odhiambo Washington wrote: > On Wed, Dec 28, 2022 at 8:23 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 12/27/22 21:46, Odhiambo Washington wrote: >>> On Tue, Dec 27, 2022 at 8:08 PM Mark Sapiro <mark(a)msapiro.net> wrote: >>>> >>>> I see from another post that you've decided against using Twitter, but >>>> to answer the question, Twitter does not require adding anything to >>>> SOCIALACCOUNT_PROVIDERS. >>>> >>> >>> I tried it and ended up with: >>> >>> ERROR 2022-12-28 08:40:18,895 97440 django.request Internal Server Error: >>> /accounts/twitter/login/ >>> Traceback (most recent call last): >> ... >>> allauth.socialaccount.models.SocialApp.DoesNotExist: SocialApp matching >>> query does not exist. >> >> >> Do you have >> >> 'allauth.socialaccount.providers.twitter', >> >> in INSTALLED_APPS? >> > > Here is what I have in settings_local.py: > > 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', > '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', > 'allauth.socialaccount.providers.facebook', > 'allauth.socialaccount.providers.twitter', > #'allauth.socialaccount.providers.stackexchange', > ) Did you add an app at https://site.name/admin/socialaccount/socialapp/ with twitter as a provider? See https://django-allauth.readthedocs.io/en/latest/providers.html#twitter-oaut… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

Re: Confirm on mass subscription

by tlhackque

On 05-Jul-17 22:09, Mark Sapiro wrote: > On 7/5/17 1:48 PM, David Krantz wrote: > > >> Is there a way of requiring all mass subscribed users to confirm their >> email adress? I have an use case where we have a current mail list but >> when moving it to mailman I for different reasons would like to >> confirm all subscribers. Some very shallow testing suggests that if I >> just add them using mass subscribe, they will not have to confirm at >> all. >> >> I have yet to upgrade to 3.1 but I will do so in due time. > > In MM 2.1, you just send the users invitations rather than subscribing > them. In MM3/Postorius, this does not seem to be an option at present. > Actually, 2.1 lets you do it either way. The first radio button on Mass Subscriptions is: "Subscribe these users now or invite them? " MM 2.1 also allows control of whether the new subscribers and/or list owner are notified. And it allows custom text to be added to the invitation/notification (when one is sent). MM3 has none of these controls. Postorious issue #203 and mailman #362 refer to the MM 2.1 regressions. However, I read this somewhat differently: given a list with subscribers (however they were subscribed), it is sometimes useful to be able to ask the members to re-confirm their address/interest. For example, when there's a change of policy (terms of use), or when local opt-in regulations require that that opt-in be reconfirmed periodically. It's handled out-of-band now, but this would seem to be something that Mailman could manage - change users' state to "unconfirmed" and issue the re-invite/re-subscribe notice. But there are some details: re-confirmation probably doesn't want to require moderator re-approval (at least not always). How this interacts with "don't deliver mail from this list" needs definition (probably overrides), but some members (notably moderators/owners/robots) need to be exempt. And like 2.1, the user notification needs to be different to explain that it's a re-confirmation.

8 years, 4 months

Re: mailman3 on new Debian 12 installation, got ssl apache working on all URLs except /mailman3

by Philip Bondi

LE and certbot created those paths for me, somehow. Both on CentOS and Debian. Don't know why. Checked my putty logs. Cannot find the first emergence of strange path. You guys are superheroes. Debian 12: <PRE> pjbondi@shackleton12:~$ sudo -i root@shackleton12:~# cat /etc/os-release PRETTY_NAME="Debian GNU/Linux 12 (bookworm)" NAME="Debian GNU/Linux" VERSION_ID="12" VERSION="12 (bookworm)" VERSION_CODENAME=bookworm ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/" root@shackleton12:~# ls -alF /etc/letsencrypt/live/ total 32 drwx------ 7 root root 4096 Nov 29 07:57 ./ drwxr-xr-x 9 root root 4096 Mar 27 15:02 ../ -rw-r--r-- 1 root root 740 Nov 27 10:27 README drwxr-xr-x 2 root root 4096 Mar 6 09:03 systemdatabase.ca/ drwxr-xr-x 2 root root 4096 Mar 6 09:03 systemdatabase.ca-0001/ drwxr-xr-x 2 root root 4096 Mar 6 09:04 systemdatabase.com/ drwxr-xr-x 2 root root 4096 Mar 6 09:04 systemdatabase.com-0001/ drwxr-xr-x 2 root root 4096 Mar 6 09:04 systemdatabase.homelinux.com/ root@shackleton12:~# </PRE> CentOS 7: <PRE> [1004] $ cat /etc/os-release NAME="CentOS Linux" VERSION="7 (Core)" ID="centos" ID_LIKE="rhel fedora" VERSION_ID="7" PRETTY_NAME="CentOS Linux 7 (Core)" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:centos:centos:7" HOME_URL="https://www.centos.org/" BUG_REPORT_URL="https://bugs.centos.org/" CENTOS_MANTISBT_PROJECT="CentOS-7" CENTOS_MANTISBT_PROJECT_VERSION="7" REDHAT_SUPPORT_PRODUCT="centos" REDHAT_SUPPORT_PRODUCT_VERSION="7" [1005] $ ls -alF /etc/letsencrypt/live/ total 4 drwx------. 7 root root 168 Aug 15 2023 ./ drwxr-xr-x. 9 root root 108 Jan 19 03:22 ../ -rw-r--r--. 1 root root 740 Jul 2 2020 README drwxr-xr-x. 2 root root 93 Jan 19 2023 systemdatabase.ca/ drwxr-xr-x. 2 root root 112 Jan 19 03:22 systemdatabase.ca-0001/ drwxr-xr-x. 2 root root 112 Feb 5 2021 systemdatabase.com/ drwxr-xr-x. 2 root root 112 Jan 19 03:21 systemdatabase.com-0001/ drwxr-xr-x. 2 root root 112 Jan 19 03:20 systemdatabase.homelinux.com/ </PRE> Again. We're almost there with ssl apache configs. - works for LE challenge and Subversion https://systemdatabase.ca/ - 6 paths work for MM3 https://systemdatabase.ca/postorius/, etc - But https://systemdatabase.ca/mailman3 fails

7 months, 2 weeks

Mailman-users search results for query "Postorius"