Search results for "sapiro" - lists.mailman3.org

[MM3-users] Re: Solved Re: after last upgrade I've got a CSRF failed verification

by Guillermo Hernandez (Oldno7)

El 27/10/22 a las 21:39, Mark Sapiro escribió: > On 10/27/22 03:04, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> >> Since I made all the mailman3 enviroment wide server open (not using >> venv) I already executed the migration doing a >> >> su -m mailman3 -c "python3 manage.py collectstatic" >> su -m mailman3 -c "python3 manage.py migrate" >> >> Being mailman3 the user who runs all of mailman3 related stuff >> >> I had problems doing the migrate part, showing an error of lacking >> perms. I solved it running the migration under root (I know it could >> be trouble after, but...) > > It would be much better to identify the problem files/directories and > adjust their ownership. It is possible that running stuff as root in > the past left things owned by root causing the issue. The problem was in the intent of execute one of the migrate parts and showed about python files. I'm pretty sure that I've been very carefull not running things as root before as I know it can mess all up. But this time it was an dead end and I needed to go through. In a few days I will upgrade another server. I will document the error if I find it again. > >> >> After that the compress part showed errors... but the postorius web >> maintenance was working well except for the CSRF error verification. >> I will trace the compress errors and will try to find the problem later. > > > Do you have `COMPRESS_ENABLED = True` in your settings? If that's not > the issue, it may be in the settings for COMPRESS_PRECOMPILERS > I will try to trace it and comment what I find. Thaks a lot for your support. -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

3 years, 5 months

[MM3-users] Re: upgrading in FreeBSD 13.1-p7: problem with aiosmtpd and lmtp runner

by Guillermo Hernandez (Oldno7)

El 4/4/23 a las 3:31, Mark Sapiro escribió: > Guillermo Hernandez (Oldno7) wrote: > >> I thought I said it: I reboot this server everyday at 06:40 CEST time. >> That's why I'm sure it's not an undetected problem for weeks. The lists >> in this last upgraded server are with daily traffic. I'm suscribed to all. > > I've looked at this a bit further. Prior to Mailman core 3.3.4 we required aiosmtpd>=1.1. In 3.3.4 we required aiosmtpd>=1.4.1 and now we require aiosmtpd>=1.4.3. The code in aiosmtpd that triggers the issue in the socket module was added in aiosmtpd==1.3.1. So it is likely that your prior Mailman core version was <3.3.4 and your aiosmtpd dependency was <1.3.1, so the Mailman upgrade would also have upgraded aiosmtpd to a version which triggered the socket issue. I think tou are completely right about the aiosmtpd changes. But I had mailman 3.3.5 installed since end of september of '21, mailman 3.3.6 since end of october '22, and mailman 3.3.7 since the beginning of december of last year. You can search the list and find my messages about that upgrades and problems I had with them. Just to make it clear: It happened upgrading from 3.3.7 to 3.3.8 The upgrade procedure I did all the times is pip install --upgrade django-mailman3 mailman mailman-hyperkitty mailmanclient postorius django hyperkitty uwsgi mod-wsgi and if I see some trouble I did it with a --force-reinstall parameter (not that I remember it happened last times that I upgraded) (and then the collectstatic, etc.) If I missed something, I don't know. > _______________________________________________ > Mailman-users mailing list --mailman-users(a)mailman3.org > To unsubscribe send an email tomailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > Archived at:https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/mess… > > This message sent toguillermo(a)querysoft.es > -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

2 years, 11 months

[MM3-users] Re: Archive search failing on one list

by Mark

On 2023-10-11 04:38, Mark Sapiro wrote: > > Steve has addressed your issues with multiple Django admin commands, > some of which apparently don't reference the correct settings. > >> The format of my final line is different to yours ... > It is not a clue as to the problem. The format of that > `representation` changed in HyperKitty 1.3.5. What is your version? > HyperKitty version 1.3.4 > What happens if you do, with the appropriate Django admin and list > name, > ``` > python3 manage.py update_index_one_list thepost(a)example.com > ``` > Thank you Mark and Steve, That worked a treat! python3 manage.py update_index_one_list thepost(a)example.com Running that command returned the message "Indexing 12 emails", then returned to the shell prompt when done. It successfully indexed the messages in the archive, and I could then do a search on the existing messages. On 2023-10-11 00:54, Stephen J. Turnbull wrote: > The process of search index construction is both CPU and wall-clock > time intensive. For this reason, the cron jobs that do regular > index updating (I think once an hour?) are separate from the utility > that constructs the index in the first place when you have existing > archives (either migrated from another MLM such as Mailman 2, or if > you're upgrading to better archive software). The messages in the archive came directly from the list (ie. they weren't imported). It looks as though running that command flushed out a cobweb, as the hourly indexing is now happening. Some time after I had run that indexing command, a new message was posted to the list, and appeared in the archive. I searched (a)immediately, (b) 15 mins after, and (c)an hour and a bit after. As Steve said, the newer messages are automatically indexed hourly. So it wasn't until after that hourly index that the search terms in the newer messages were showing up in the search results. I can't say I understand the inner workings of the process yet, but we have a working archive search and I'm very happy about that. Thank you again, Mark

2 years, 5 months

[MM3-users] Re: update problems in virtualenv

by Christian H. Kuhn

Hi Mark, thank you for your answer. I did both updates, and haven't seen the warning since. KR QNo Am 05.11.2025 um 01:40 schrieb Mark Sapiro: > On 11/4/25 11:47, Christian H. Kuhn via Mailman-users wrote: >> Hi all, >> >> i followed https://docs.mailman3.org/en/latest/install/virtualenv.html >> and ran in different problems. Here's the first. >> >> All mailman-web runjobs report: >> >> System check identified some issues: >> >> WARNINGS: >> ?: settings.ACCOUNT_AUTHENTICATION_METHOD is deprecated, use: >> settings.ACCOUNT_LOGIN_METHODS = {'username', 'email'} >> ?: settings.ACCOUNT_EMAIL_REQUIRED is deprecated, use: >> settings.ACCOUNT_SIGNUP_FIELDS = ['email*', 'username*', 'password1*', >> 'password2*'] > > > This is https://gitlab.com/mailman/mailman-web/-/issues/37 fixed for the > next release. There are two ways to fix this. You can upgrade mailman- > web in your venv by activating the venv and doing > > pip install --upgrade git+https://gitlab.com/mailman/mailman-web > > Or you can add the following to your settings.py after the imports from > mailman_web.settings.base and mailman_web.settings.mailman > ``` > del ACCOUNT_EMAIL_REQUIRED > del ACCOUNT_AUTHENTICATION_METHOD > ACCOUNT_SIGNUP_FIELDS = ['username*', 'email*', 'password1*', 'password2*'] > ACCOUNT_LOGIN_METHODS = {'email', 'username'} > ``` > >> (venv) mailman@bywater:~/mm/var/data$ pip install --upgrade >> mailman==3.3.10 >> Collecting mailman==3.3.10 > ... >> INFO: pip is looking at multiple versions of mailman to determine >> which version is compatible with other requirements. This could take a >> while. >> ERROR: Could not find a version that satisfies the requirement >> nntplib; python_version >= "3.13" (from mailman) (from versions: none) >> ERROR: No matching distribution found for nntplib; python_version >= >> "3.13" >> >> standard-nntplib 3.13.0 is installed. > > This is an issue with Mailman 3.3.10 and Python >= 3.13 fixed by > https://gitlab.com/mailman/mailman/-/merge_requests/1348 > > Here again if you want to upgrade Mailman core you can do > > pip install --upgrade git+https://gitlab.com/mailman/mailman > > to get the latest from gitlab. >

4 months, 4 weeks

[MM3-users] Re: Apple Mail encoding again

by Stephen J. Turnbull

Mark Sapiro writes: > On 4/14/22 08:21, Stephen J. Turnbull wrote: > Yes. The C-T-E on all the multipart parts was quoted-printable, not > allowed under RFC 2045. That's what I expected (we're talking about Apple Mail), but thanks for confirming. > The Python email library says the message is defective. Mailman's lmtp > runner in turn rejects the defective message with a 501 status > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/runners/lmtp.p… > > It could accept a defective message or one with specific defects, but > this is problematic for further processing. For example, at least one > MUA, Thunderbird, renders such a message with an empty body. Sure, but that's not our problem. I mean, I have my MUA set to ignore HTML so I get empty bodies all the time! :-) We are perfectly within our rights to just let the Apple Mail and Thunderbird users fight about it. :-) If it causes problems for *our* processing, that's another matter. I don't see why it would, though. Whether we *want* to do that depends on how much trouble that causes for our main constituency (list and site admins), and whether we can provide discoverable documentation of the problem. My take is that this seems to be an extremely rare problem, and at least some MUAs are able to read the message, so we should let it through. If we wanted to be really obnoxious, we could add a header to the message This message does not conform to mail standards. Some clients may omit some or all of the content. Or we could make passing it an option, perhaps as a pseudo-content type in "Pass these content types" or as a separate option. I feel strongly enough that Postel implies "let it through" that I'll write up a PR shortly (a few days). Sleep on it, we bring in Abhilash and I guess Barry?, and if you all still don't like it, veto it -- my time is no big deal, it'll only be an hour to put it together I think. Steve

3 years, 11 months

[MM3-users] Re: HyperKitty/Mailman3 issues

by Florian Schulze

On 22 Nov 2018, at 19:53, Mark Sapiro wrote: > On 11/22/18 2:58 AM, Florian Schulze wrote: >> Hi! >> >> I tried setting up Scheduled Tasks as described in >> <http://docs.mailman3.org/en/latest/config-web.html#scheduled-tasks-required> >> >> but the "runjobs" command can't be found. I see the hyperkitty and >> mailman commands when using "help". > > > Does "help" show a list under [django_extensions] including runjob and > runjobs? > > Is 'django-extensions' in the list of INSTALLED_APPS in your Django > settings? That was the issue. Thanks! >> The "qcluster" service is working. >> >> Using Django 2.1.1 and HyperKitty 1.2.1. >> >> Maybe related to that, I have two issues with archives. >> >> 1. Changing the archiving setting in the Web-UI to something else >> than >> public seems to have no effect. The already archived messages are >> still >> accessible in public. > > > This is related. It is one of the "daily" jobs that updates this. Note > that changing to "private" will require login after the "daily" jobs > run, but changing to "do not archive" will leave the existing archive > accessible. After manually running the daily job, the archive is now private. >> 2. Related to 1., how can I remove a list archive without affecting >> other lists? > > > There's no easy way. For the "prototype" archiver, the archives for a > list are in var/archives/prototype/listname(a)example.com/ and that > directory can be removed, but that doesn't affect HyperKitty. > HyperKitty's archives are in the Mailman database and multiple tables > are involved. > > One could try just removing the row for the list from the > hyperkitty_mailinglist table. That may render the list's archive > inaccessible via the web UI, but I have no idea what would be broken > by > doing this. I hope this will be added at some point. For now I have the archive set to private. Thanks again for the pointers! Regards, Florian Schulze

7 years, 3 months

[MM3-users] Re: Solved Re: after last upgrade I've got a CSRF failed verification

by Guillermo Hernandez (Oldno7)

El 27/10/22 a las 21:39, Mark Sapiro escribió: >> After that the compress part showed errors... but the postorius web >> maintenance was working well except for the CSRF error verification. >> I will trace the compress errors and will try to find the problem later. > > > Do you have `COMPRESS_ENABLED = True` in your settings? If that's not > the issue, it may be in the settings for COMPRESS_PRECOMPILERS While I'm tracing the problem out, this is the configuration I had working and the error it shows after upgrade: <------- snip of settings.py> # COMPRESS_PRECOMPILERS = ( ('text/less', 'lessc {infile} {outfile}'), ('text/x-scss', 'sassc -t compressed {infile} {outfile}'), ('text/x-sass', 'sassc -t compressed {infile} {outfile}'), ) # On a production setup, setting COMPRESS_OFFLINE to True will bring a # significant performance improvement, as CSS files will not need to be # recompiled on each requests. It means running an additional "compress" # management command after each code upgrade. # http://django-compressor.readthedocs.io/en/latest/usage/#offline-compression #### activo compresion 18/12/20 COMPRESS_OFFLINE = True ###COMPRESS_OFFLINE = False <---------- end snip> And below is the error it shows: /usr/local/mailman3 # su -m mailman3 -c "python3 manage.py compress" Traceback (most recent call last): File "/usr/local/mailman3/manage.py", line 10, in <module> execute_from_command_line(sys.argv) File "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line utility.execute() File "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", line 440, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", line 279, in fetch_command klass = load_command_class(app_name, subcommand) File "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", line 49, in load_command_class return module.Command() File "/usr/local/lib/python3.9/site-packages/django/core/management/base.py", line 274, in __init__ raise TypeError("requires_system_checks must be a list or tuple.") TypeError: requires_system_checks must be a list or tuple. -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

3 years, 5 months

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Eggert Ehmke

I have a file /opt/mailman/.bashrc file with this line: source /opt/mailman/venv/bin/activate works quite well with systemd. My service file looks like this: [Unit] Description=GNU Mailing List Manager After=syslog.target network.target mysqld.service [Service] Type=forking PIDFile=/opt/mailman/mm/var/master.pid Environment="MAILMAN_CONFIG_FILE=/etc/mailman3/mailman.cfg" User=mailman Group=mailman ExecStart=/opt/mailman/venv/bin/mailman start ExecReload=/opt/mailman/venv/bin/mailman restart ExecStop=/opt/mailman/venv/bin/mailman stop [Install] WantedBy=multi-user.target Eggert Am Donnerstag, 20. Oktober 2022, 08:38:05 CEST schrieb Mark Sapiro: > On 10/19/22 21:23, Stephen J. Turnbull wrote: > > Onyeibo Oku writes: > > > Mailman starts well from virtual environment though, ... but systemd > > > doesn't replicate that success. > > > > systemd doesn't know anything about venv. If it's possible to source > > (not call as a command!) the venv bin/activate script via systemd, > > that should fix it. If not, we'll have to figure out what it is that > > the venv provides that the current systemd config does not. I would > > guess that after sourcing the venv's bin/activate > > Our suggested systemd script at > https://docs.mailman3.org/en/latest/install/virtualenv.html#starting-mailman > -automatically has > > ExecStart=/opt/mailman/venv/bin/mailman start > ExecReload=/opt/mailman/venv/bin/mailman restart > ExecStop=/opt/mailman/venv/bin/mailman stop > > /opt/mailman/venv/bin/mailman should work whether or not a venv is active. > > Judging from the traceback, Onyeibo Oku's /opt/mailman/venv/bin/mailman > is quite different from mine which is just > ``` > #!/opt/mailman/venv/bin/python3 > # EASY-INSTALL-ENTRY-SCRIPT: 'mailman==3.3.5','console_scripts','mailman' > __requires__ = 'mailman==3.3.5' > import re > import sys > from pkg_resources import load_entry_point > > if __name__ == '__main__': > sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0]) > sys.exit( > load_entry_point('mailman==3.3.5', 'console_scripts', 'mailman')() > ) > ``` > What is yours? and can you start mailman as the mailman user with > ``` > /opt/mailman/venv/bin/mailman start > ``` > without activating the venv?

3 years, 5 months

[MM3-users] Re: Help with fresh debian install

by Mark Dadgar

Thanks for the al the help - much appreciated! Mailman3 is a HUGE step up from 2.1.x. Running the commands as the correct user solved my issues. Specially, I ran the import21 command as the “list” user (created by the debian/ubuntu package) and the hyperkitty import command as the “www-data” user. I had to add login shells to the passwd entries for those users to make it happen as they get installed with nologin. I imported a 24G archive inbox and something went wrong along the way - the archives for many months consist of just a single identical thread. Re-running the import results in the following in just a few seconds: www-data@mail:/tmp$ python /usr/share/mailman3-web/manage.py hyperkitty_import -l trackjunkies(a)pdc-racing.net /backups/trackjunkies.mbox Importing from mbox file /backups/trackjunkies.mbox to trackjunkies(a)pdc-racing.net Computing thread structure Synchronizing properties with Mailman Warming up cache The full-text search index will be updated every minute. Run the 'manage.py runjob update_index' command to update it now. Any thoughts on how I can re-run the full import to make sure that all the archives are present? Thanks! - Mark ----- mark(a)pdc-racing.net | 408-348-2878 > On Oct 3, 2019, at 9:25 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 10/3/19 5:17 PM, Mark Dadgar wrote: >> >> I brought up a fresh install of Mailman3 via the current Debian package alongside my current 2.1 setup (installed and updated from source since 2002) on Ubuntu 18.04 LTS. >> >> Importing lists from 2.1 has been a real problem. >> >> I am trying to import a list with no archives to keep it simple while I prove out the process. If I run the mailman import21 comment as my user, I get the following errors: >> >> — >> mark@mail:/tmp$ mailman import21 announce(a)pdc-racing.net ./announce-config.pck >> Traceback (most recent call last): >> File "/usr/bin/mailman", line 11, in <module> >> load_entry_point('mailman==3.1.1', 'console_scripts', 'mailman')() >> File "/usr/lib/python3/dist-packages/mailman/bin/mailman.py", line 94, in main >> initialize(config_path) >> File "/usr/lib/python3/dist-packages/mailman/core/initialize.py", line 189, in initialize >> initialize_2(propagate_logs=propagate_logs) >> File "/usr/lib/python3/dist-packages/mailman/core/initialize.py", line 152, in initialize_2 >> mailman.core.logging.initialize(propagate_logs) >> File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 157, in initialize >> _init_logger(propagate, sub_name, log, logger_config) >> File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 110, in _init_logger >> handler = ReopenableFileHandler(sub_name, path_abs) >> File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 50, in __init__ >> self._stream = self._open() >> File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 53, in _open >> return codecs.open(self.filename, 'a', 'utf-8') >> File "/usr/lib/python3.6/codecs.py", line 897, in open >> file = builtins.open(filename, mode, buffering) >> PermissionError: [Errno 13] Permission denied: '/var/log/mailman3/mailman.log' > > > This is the issue. I don't know how the Debian packages do this, but I > recommend having a 'mailman' user that owns everything and running > commands as that user. > > >> Error in atexit._run_exitfuncs: >> Traceback (most recent call last): >> File "/usr/lib/python3.6/logging/__init__.py", line 1945, in shutdown >> h.flush() >> File "/usr/lib/python3/dist-packages/mailman/core/logging.py", line 56, in flush >> if self._stream: >> AttributeError: 'ReopenableFileHandler' object has no attribute '_stream' > > > This is due to the prior permissions error. > >> If I run it as root, it runs for a long time but spews a HUGE stream of these errors to /var/log/mailman3/mailman.log: > > > If there are a lot of members to add, that can take a long time. The > current version of import21 has a progress thermometer for this. > >> — >> Oct 03 17:08:48 2019 (19118) Skipping and preserving unparseable message: 1570147727.3029191+80f1cc4d18f54868ad6162e8e41e52567185e983 >> Oct 03 17:08:49 2019 (19118) Uncaught runner exception: [Errno 13] Permission denied: '/var/lib/mailman3/queue/virgin/1570147728.618866+174175d39c301feab4ebb2aac0a51226334fa54c.pck' >> Oct 03 17:08:49 2019 (19118) Traceback (most recent call last): >> File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 156, in _one_iteration >> msg, msgdata = self.switchboard.dequeue(filebase) >> File "/usr/lib/python3/dist-packages/mailman/core/switchboard.py", line 150, in dequeue >> with open(filename, 'rb') as fp: >> PermissionError: [Errno 13] Permission denied: '/var/lib/mailman3/queue/virgin/1570147728.618866+174175d39c301feab4ebb2aac0a51226334fa54c.pck' > > First, I don't know what these messages are. Normally import21 doesn't > send any mail. I'm guessing it's trying to send 'you are subscribed' > notices to the users, but it shouldn't be doing this. > > All these files should wind up in Mailman's var/queue/bad/ directory > with a .psv extension. You should be able to examine them with the > 'mailman qfile' command. > > Whatever they are, the error comes from virgin runner so import21 should > have actually succeeded. Did it import the list? > > >> It also dumps some mail footer templates into the template directory that are owned by root, which seems … incorrect? > > > It makes a weak effort at converting the list's msg_footer and > digest_footer into MM 3 templates in > templates/list/<list-id>/<list-lang>/. These are owned by root in your > case because you ran import21 as root. > > >> Any thoughts on what’s going wrong here? > > > It looks like this may be an issue with the Debian package, at least the > sending of messages part. > > As for the rest, the Debian package should install stuff as a Mailman > user, perhaps 'mailman' or 'list', and you should be running all > commands as that user. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > 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/

6 years, 5 months

[MM3-users] Re: Auth question

by David Krantz

On Fri, Mar 31, 2017 at 12:01 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > This is <https://gitlab.com/mailman/hyperkitty/issues/106>. > > I'm not sure what you mean by drop and recreate the databases. You > should just drop the `social_auth*` tables, or if there's nothing in the > database you want, just starting with an empty database should work. Very good! Thank you very much, I got a bit further. The database contained a couple of test lists that I can recreate, so nothing of value. The strange thing was that drop database followed by create database did not yield an empty database in Postgres. I probably forgot a commit somewhere. I got a bit further. The problem with not being an expert on Django is that the configuration of all web frameworks is that is a bit involved. I have no experience of Django outside of this and I just want to get it running in this case. Now I get the following errors in the mailman_web-log, somehow complaining on the url mapping. ERROR 2017-03-31 00:51:31,558 exception 2456 140113416898304 Internal Server Error: /mailman3/lists/ Traceback (most recent call last): [...] File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/template/defaulttags.py", line 458, in render url = reverse(view_name, args=args, kwargs=kwargs, current_app=current_app) File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/urls/base.py", line 91, in reverse return force_text(iri_to_uri(resolver._reverse_with_prefix(view, prefix, *args, **kwargs))) File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/urls/resolvers.py", line 497, in _reverse_with_prefix raise NoReverseMatch(msg) NoReverseMatch: Reverse for 'hk_user_login' not found. 'hk_user_login' is not a valid view function or pattern name. The Django 1.18 points to a Django 1.11rc1, should probably be mentioned. My urls.py (a copy from the docs, I think) from django.conf.urls import include, url from django.core.urlresolvers import reverse_lazy from django.views.generic import RedirectView from django.contrib import admin # Comment the next two lines to disable the admin: #admin.autodiscover() urlpatterns = [ url(r'^$', RedirectView.as_view(url=reverse_lazy('hyperkitty.views.index.index'))), url(r'^mailman3/', include('postorius.urls')), url(r'^archives/', include('hyperkitty.urls')), url(r'', include('django_mailman3.urls')), url(r'^accounts/', include('allauth.urls')), # Django admin url(r'^admin/', include(admin.site.urls)), ] cheers // David

9 years

Search results for query "sapiro"