Re: User management page [was: Changing subscription address]
by Abhilash Raj
> On Mar 20, 2021, at 6:22 AM, Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote:
>
> Core implementation details, so I beinging this here from Mailman
> Users @ mailman3.org.
>
> Abhilash Raj writes:
>
>> I have started working on designing a User management page[2] in
>> Core which should make it easy for superuser to manage several
>> things about a User, including the ones that don’t have an account
>> in Postorius to manage their own.
>
> I don't understand this design with a "page in Core”.
Typo :( Page in Postorius is what I meant to say.
> I was thinking
> about this kind of problem, and tentatively came to the conclusion
> that any reference to something that can be resolved to a User should
> generate a Django account for that User in Postorius or HyperKitty.
Is that necessarily required? Every user in Django has a corresponding
user in Core, but the converse isn’t true and I am not sure if that is even
required.
The purpose of a Django account is to manage my own email
addresses and subscriptions. An admin can manage a Core User that
does or doesn’t have a Django account. The only thing that changes
is what they can do with that user. See below for my thoughts on the
actions an admin would be able to perform.
The high level design of that user management page is that it will provide
a list of Users straight from Core. When you go to an individual User’s
management page,
You will be able to see:
- Does the user have a Django account?
- All Subscriptions for the User
- All addresses of the User
You will be able to perform following actions:
- Add or remove a user’s address
- Verify or un-verify an address
- Set any address as primary for the user
- Update display name of the user
- Update address on any of the subscriptions
If the User has a Django account, you also be able to:
- Manage the User’s password *if* they are using password
for login and not social auth.
- Reset “social login” for the user?
- View some of the RO info about the Django User model, like
last login, superuser status or few other attributes that we feel
is useful for admin in any situation.
What I am on fence about:
- Provide a full blown preferences menu to the admin for that user. This
will also make the UI extremely complex to see and implement.
> Authorization to use that account would still require authentication
> via the usual email verification dance, or some level of admin
> privilege.
>
> The thing is that emails that have not been added to a User are
> unique. They will be the only Address attached to User created to
> manage them until authenticated, and transitively the only address
> attached to an automatically-created Django account (since those are
> 1-1 with core Users if they exist AFAIK).
In Core, when a new address (email1) comes in, a Mailman User(user1)
is created for it.
But, when you have an account in Django with a different email
(email2) and a different Mailman user (user2) and you add a second
email (email1) to your account and are able to prove ownership by
verifying the address, Django will ask Core to add that second address
(email1) to your Mailman user (user2) and absorb “user1”. This
process is already implemented.
However, if two Django accounts are created for “user1” and “user2”
then situation becomes more tricky and currently we don’t have a
way to resolve that short of delete one of the accounts and add the
addresses to other account.
> What's missing here is the ability to merge core Users and their
> corresponding Django accounts. Doing this with nothing more than the
> usual email verification dance is not *obviously* provably secure to
> me, so we need to be careful, but I think it probably will turn out to
> be as secure as you can get. It seems to me that User merging is the
> most pressing problem of this kind. (At least, it affects me on a
> couple of list hosts, as well as on GitHub and GitLab.)
>
>> [2]: https://gitlab.com/mailman/postorius/-/merge_requests/605
>
> I'll take a look tomorrow or early next week.
It is far from actually usable, so you can actually skip it for now ;-) I
can announce it when it is in semi-usable state.
--
thanks,
Abhilash Raj (maxking)
5 years, 7 months
Re: Error -- postorius Un-handled exception
by Stephen J. Turnbull
Mark writes:
> After working my way through your suggestions with no joy I
> discovered to my embarrassment that I hadn't created the
> "mailman-hyperkitty.cfg" file. Once created all was well.
We really should create a "mailman-lint" utility that checks for
things like that.
> This was of course after I had begun the installation process again
> from scratch. My apologies for the waste of bandwidth and your
> time.
It's not a waste. There are reasons for having these random include
files, but they do make configuration more complex, and these stumbles
more likely. I did myself in on the postfix-pgsql patch: not using
postmap, the postfix.cfg doesn't need a postmap_command setting right?
Wrong! "Wasted" my own time there. :-D
Anyway, ask here, somebody probably has done the same before. Maybe
it will come up again and you can go, "when I had that error ...." ;-)
> couple of issues that others might also stumble over:
>
> 1. Installing Xapian needed clang. It didn't like gcc
I'm pretty sure that installing Xapian requires the C++ compiler
(vendor and version) that was used for the packaged library. With the
last year I've definitely compiled a Haystack package for Xapian using
GCC, clang didn't work and neither did my existing GCC nor the most
recent GCC, I had to look up how Ubuntu had compiled it to find the
right version (9.3).
> 3. For the user "mailman" to access the databases I needed to
> change the owner to mailman (even though all privileges has been
> granted) ...
Can confirm. This was NOT necessary in November 2022; it is now.
Probably a PostgreSQL > 13 thing, but since the change is sane and
simple I didn't bother to investigate further.
Steve
2 years, 9 months
Re: Link to account
by Mark Sapiro
On 4/11/23 12:04, Lars Bjørndal wrote:
> Thanks a lot. Maybe I've done a mistake, it doesn.t work.
>
> At the bottom of /etc/mailman3/settings.py I have:
>
> ROOT_URLCONF = 'urls'
>
> `cat /etc/mailman3/urls.py`
>
> [...]
>
> urlpatterns = [
> path(
> '',
> RedirectView.as_view(url=reverse_lazy('list_index'), permanent=True),
> ),
> path('lists/mailman3/', include('postorius.urls')),
> path('lists/archives/', include('hyperkitty.urls')),
> path('lists/', include('django_mailman3.urls')),
> path('lists/accounts/', include('allauth.urls')),
> path('lists/admin/', admin.site.urls),
> ]
>
> In Apache config for the domain, I now have:
>
> <IfModule mod_proxy.c>
> ProxyPreserveHost On
> ProxyPass "lists/mailman3" "http://127.0.0.1:8000/lists/mailman3"
> ProxyPass "lists/archives" "http://127.0.0.1:8000/lists/archives"
> ProxyPass "lists/accounts" "http://127.0.0.1:8000/lists/accounts"
> ProxyPass "lists/admin" "http://127.0.0.1:8000/lists/admin"
> ProxyPass "lists/user-profile" "http://127.0.0.1:8000/lists/user-profile"
> </IfModule>
>
> Restarted mailmanweb, httpd and mailman3.
>
> If I go to list.punktskriftutvalget.no/mailman3/, I get a 404 Not Found response in browser.
>
> So what's wrong, do you think?
You followed
https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…
literally. The literal instructions where to access everything via URLs
like https://mydomain.org/lists/....
If you were to replace `lists` with `mailman3` everywhere in the abpve,
you would then access HyperKitty via a URL like
https://list.punktskriftutvalget.no/mailman3/archives/
and Postorius via
https://list.punktskriftutvalget.no/mailman3/mailman3/
If that's not what you want, it's more complicated and some things might
not be possible. What exactly do you want for access to Postorius,
HyperKitty, user accounts, user profiles and the Django admin UI?
--
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
3 years, 7 months
Re: Installing mailman 3
by Rafael Mora
For testing purpose I turned back to false the DEBUG var and everything
started working fine with HyperKitty
I don't understand... this is the trace when I click Login from Postorius
to HyperKitty
[02/Aug/2017 16:43:42] "GET /postorius/lists/ HTTP/1.1" 200 3645
[02/Aug/2017 16:43:48] "GET /accounts/login/?next=/postorius/lists/
HTTP/1.1" 200 10950
[02/Aug/2017 16:43:49] "GET /static/CACHE/css/hyperkitty.2f591b4e31fe.css
HTTP/1.1" 200 156657
What should I check?
El mié., 2 ago. 2017 a las 10:56, Mark Sapiro (<mark(a)msapiro.net>) escribió:
> On 08/02/2017 07:55 AM, Rafael Mora wrote:
> > HyperKitty is looking for some files in /static/CACHE/... but it doesn't
> > find them:
> >
> > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/b3547a2ab51b.css HTTP/1.1"
> > 404 107
> > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/4c17bb8058aa.css HTTP/1.1"
> > 404 107
> > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/2fa1cba00450.css HTTP/1.1"
> > 404 107
> > [02/Aug/2017 14:53:38] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1"
> 404
> > 105
> > [02/Aug/2017 14:53:39] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1"
> 404
> > 105
> >
> >
> > Should I run any command to activate the CACHE dir?
>
>
> You need to ensure you have a working sass compiler. As I said at
> <
> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…
> >,
> See the third bullet under
> <http://docs.list.org/en/latest/prodsetup.html#dependencies>.
>
> Then you need to run commands like
>
> django-admin collectstatic --clear
> django-admin compress
>
>
> --
> 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
> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
>
--
Atentamente / Best Regards
Ing. Rafael Mora
9 years, 3 months
Re: lmtp runner not starting
by Odhiambo Washington
On Sat, Apr 1, 2023 at 7:55 PM Guillermo Hernandez (Oldno7) via
Mailman-users <mailman-users(a)mailman3.org> wrote:
> This morning I upgraded the mailman3 installation of the less traffic
> server I have: a bunch of lists, with very slow traffic.
>
> (see pip lists at the end)
>
> I sent test mails to a pair of lists, but none were distributed or
> archived. postorius seemed working well. First I thought it was some I
> did wrong in the upgrade procedure, but then I realized the lmtp runner
> was not running.
>
> I followed old messages about similar problem (many of them in this same
> mailman-users list), but I cannot see what is wrong. There is no error
> logged in mailman.log. the mailman.cfg of the lmtp is the default (and
> was working at least a pair of weeks ago)
>
> *-*-*-*-*-*-*-*-* from mailman.cfg
>
> [mta]
> incoming: mailman.mta.postfix.LMTP
> outgoing: mailman.mta.deliver.deliver
> lmtp_host: 127.0.0.1
> lmtp_port: 8024
> smtp_host: localhost
> smtp_port: 25
> configuration: python:mailman.config.postfix
>
> *-*-*-*-*-*-*-*-*
>
> There is no one listening in port 8024. I tried changing the port (to
> 9024), with the same results.
>
> postfix seems working well. I's just there is nothing listening on port
> 8024 because lmtp runner is not running :)
>
> (from maillog):
>
> connect to 127.0.0.1[127.0.0.1]:8024: Connection refused
>
> (another simple test)
>
> root@www:/usr/local/mailman3 # telnet localhost 8024
> Trying 127.0.0.1...
> telnet: connect to address 127.0.0.1: Connection refused
>
> I'm running out of ideas. Any clue to somewhere to dig in?
>
>
> *-*-*-*-*-*-*-*-*-*-* runners started
>
> Apr 01 17:24:40 2023 (4681) out runner started.
> Apr 01 17:24:40 2023 (4680) virgin runner started.
> Apr 01 17:24:41 2023 (4679) command runner started.
> Apr 01 17:24:42 2023 (4688) retry runner started.
> Apr 01 17:24:43 2023 (4686) in runner started.
> Apr 01 17:24:44 2023 (4683) digest runner started.
> Apr 01 17:24:44 2023 (4684) nntp runner started.
> Apr 01 17:24:45 2023 (4682) archive runner started.
> Apr 01 17:24:46 2023 (4685) bounces runner started.
> Apr 01 17:24:47 2023 (4687) task runner started.
> Apr 01 17:24:47 2023 (4687) Task runner evicted 0 expired pendings
> Apr 01 17:24:47 2023 (4687) Task runner deleted 0 orphaned workflows
> Apr 01 17:24:47 2023 (4687) Task runner deleted 0 orphaned requests
> Apr 01 17:24:47 2023 (4687) Task runner deleted 0 orphaned messages
> Apr 01 17:24:47 2023 (4687) Task runner evicted expired cache entries
> Apr 01 17:24:48 2023 (4678) pipeline runner started.
> Apr 01 18:24:48 2023 (4687) Task runner evicted 0 expired pendings
> Apr 01 18:24:48 2023 (4687) Task runner deleted 0 orphaned workflows
> Apr 01 18:24:48 2023 (4687) Task runner deleted 0 orphaned requests
> Apr 01 18:24:48 2023 (4687) Task runner deleted 0 orphaned messages
> Apr 01 18:24:48 2023 (4687) Task runner evicted expired cache entries
>
> *-*-*-*-*-*-*-*-*-* pip lists with versions installed
>
> root@www:/usr/local/mailman3 # pip list | grep mailman
> django-mailman3 1.3.9
> mailman 3.3.8
> mailman-hyperkitty 1.2.1
> mailmanclient 3.3.5
>
> root@www:/usr/local/mailman3 # pip list | grep django
> django-allauth 0.51.0
> django-appconf 1.0.5
> django-compressor 4.0
> django-extensions 3.2.0
> django-gravatar2 1.4.4
> django-haystack 3.2.1
> django-mailman3 1.3.9
> django-picklefield 3.1
> django-q 1.3.9
> djangorestframework 3.13.1
>
> root@www:/usr/local/mailman3 # pip list | grep postorius
> postorius 1.3.8
>
>
Bumping either mailman|lmtp loglevel to DEBUG might help find out.
[logging.lmtp]
level: debug
And I think you can debug everything with (untested):
[logging.here]
level: debug
And restart mailman.
Maybe??
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
3 years, 7 months
Re: Introducing Mailman Web project
by Abhilash Raj
On Mon, Mar 25, 2019, at 5:25 PM, Ralph Seichter wrote:
> * Abhilash Raj:
>
> > For this reason, I decided to combine all the projects together into
> > a Django project which can be easily installed and run:
> >
> > $ pip install mailman-web
> > # Export Settings for commands to just work.
> > $ export DJANGO_SETTINGS=mailman_web.settings
> > $ django-admin migrate
> > $ django-admin runserver
>
> I've tried things a bit differently so I can use the latest version from
> GitLab, and Things Go Boom(TM):
>
> $ python3.7 -m venv venv
> $ . venv/bin/activate
> $ pip install -U pip setuptools
> $ git clone https://gitlab.com/mailman/mailman-web.git
> $ cd mailman-web/
> $ cp docs/mailman-web-example.toml mailman-web.toml
> $ pip install .
> $ DJANGO_SETTINGS_MODULE=mailman_web.settings django-admin migrate
> Traceback (most recent call last):
> [...]
> File
> "/var/lib/nginx/mailman/venv/lib/python3.7/site-packages/postorius/views/user.py", line 34, in <module>
> from postorius.models import List, MailmanUser
> File
> "/var/lib/nginx/mailman/venv/lib/python3.7/site-packages/postorius/models.py", line 223, in <module>
> class EmailTemplate(models.Model):
> File
> "/var/lib/nginx/mailman/venv/lib/python3.7/site-packages/django/db/models/base.py", line 95, in __new__
> "INSTALLED_APPS." % (module, name)
> RuntimeError: Model class postorius.models.EmailTemplate doesn't
> declare an explicit app_label
> and isn't in an application in INSTALLED_APPS.
>
> Did I miss something?
So, that's my fault ;-)
The example configuration is actually not a working example,
but only used for demonstrating how to write a TOML config.
But I see that it actually should be a valid configuration, I'll
open an issue and fix that.
Can you instead remove mailman-web.toml and then
again try:
$ DJANGO_SETTINGS_MODULE=mailman_web.settings django-admin migrate
This should mostly probably work :)
--
thanks,
Abhilash Raj (maxking)
7 years, 7 months
Re: How to subscribe members without sending unsubscribe message
by Stephen J. Turnbull
Flo via Mailman-users writes:
> Thank you. I don't why I don't find these things in Postorius
> easily?
There's a common saying among user interface developers that
"'intuitive' just means 'what you're used to'". It's not a "you"
problem, it's that people have different notions of where such things
"should be found" based on their unique experiences.
In this case, the "mass subscription" tool has controls for all the
things you might care about, including the welcome message. The "mass
removal" tool does not, but once you've used "mass subscription", a
control for the goodbye message is a reasonable expectation. I think
we should add it:
https://gitlab.com/mailman/postorius/-/issues/638
--
GNU Mailman consultant (installation, migration, customization)
Sirius Open Source https://www.siriusopensource.com/
Software systems consulting in Europe, North America, and Japan
1 year, 1 month
Re: Accept these non-members
by Lars Bjørndal
Again, thank you for your reply!
You wrote:
> On 3/6/26 12:52, Lars Bjørndal wrote:
[...]
> > > > I have an announce only Mailman3 list. When I log into the web interface
> > > > as an admin user, and go to the specified list, and choose Settings, I find
> > > > the Message Acceptance tab. There, I find the edit field Accept these
> > > > non-members. But this field is empty, although I know that some people
> > > > have permissions and are able to post to this list. How can I find the
> > > > list of these non-members and add more people or delete someone?
[...]
> > > These are nonmembers whose moderation action is accept or defer. If your
> > > Postorius is >= 1.3.6, and the number of nonmembers is manageable you can
> > > just view the nonmembers list in Postorius and see their moderation action.
[...]
> > > Otherwise a `mailman shell` interaction like
> > > ```
> > > $ mailman shell -l list.example.com
> > > Welcome to the GNU Mailman shell
> > > Use commit() to commit changes.
> > > Use abort() to discard changes since the last commit.
> > > Exit with ctrl+D does an implicit commit() but exit() does not.
> > > The variable 'm' is the list.example.com mailing list
> > > > > > for nm in m.nonmembers.members:
> > > ... if nm.moderation_action in (Action.accept, Action.defer):
> > > ... print(f'{nm} {nm.moderation_action}')
> > > ...
> > > > > >
> > > ```
> > > will print those nonmembers with Action.accept or Action.defer.
All addresses, both addresses that I know has sent messages to the list and others, are marked as MemberRole.nonmember> Action.defer
When I view non-members in postorius, I get some differences:
Some ar marked: Regular List default, and others Regular Default processing.
The list is imported from Mm 2.1 a long time ago. I don't know if that matters.
> > What's the difference between Action.accept and Action.defer?
>
>
> Action.accept accepts the message immediately with no further checks.
> Action.defer passes the membership checks but still goes on to check other
> things like
>
> mis-addressed email commands
> messages with implicit destination
> messages with too many explicit recipients
> messages that are bigger than a specified maximum
> messages with no, or empty, Subject headers
> messages with digest Subject or boilerplate quote
> messages matching a bounce_matching_header line
Hm, this is a mystery to me. Is there othere places I can search for addresses that are aloud to send to the list?
Thanks,
Lars
8 months
[MM3-users]Re: mailman 2 vs. mailman 3: what happened to multipart/digest?
by John Hein
Mark Sapiro wrote at 12:18 -0700 on May 12, 2016:
> On 5/12/16 9:16 AM, deu8yz2mpq(a)snkmail.com wrote:
> > Digest delivery in mailman 2 encapsulated the individual message/rfc822 messages in a multipart/digest container. This allowed email clients to show the messages in the particular digest in a threaded view.
>
>
> This format vs. plain text digests was a user option in Mailman 2.
>
>
> > It seems like the various digest options that I have tried [1] in mailman 3.1.0 (as implemented for the fedora-users mailing list) no longer encapsulate messages in multipart/digest.
>
>
> The core still supports the same plain text and MIME format digests and
> the same individual subscriber and per-list default formats as did
> Mailman 2. The issue is none of these things are exposed in Postorius.
>
> If you subscribe to digests on this list, you will receive the
> 'encapsulated' MIME format because the lists mime_is_default_digest
> setting is True, but currently that has to be set through the
> bin/mailman shell tool.
>
>
> > Is this intentional? Is it a bug - feature that was lost in translation from 2 to 3? Is there a delivery option I'm missing that will turn that back on?
Thanks for the info - and Barry's reply as well. I understand that
MIME digests are supported in Mailman 3 - that's what I'm using (and
thanks, Barry, for the info that Summary Digests is the same right
now). My quibble is that the multipart/digest encapsulation level is
gone.
Barry Warsaw wrote at 15:16 -0400 on May 12, 2016:
> The MIME format of MIME digests should roughly be:
>
> multipart/mixed
> text/plain (the digest heading)
> text/plain (the TOC)
> message/rfc822
> message-1
> message/rfc822
> message-2
> ...
> text/plain (footer)
But mm 2 had:
multipart/mixed
text/plain (the digest heading)
text/plain (the TOC)
multipart/digest <--- this is the part that's gone in mm3
message/rfc822
message-1
message/rfc822
message-2
...
text/plain (footer)
So was that removal intentional, a bug or ??
Maybe you're saying there is definitely an unexposed (in Postorius)
knob for that in mm3.
>
> It is the intent that Postorius will eventually expose all these
> settings. We're not there yet. At present you could possibly do this by
> interacting with mailmanclient, although I'm not certain the settings
> are exposed there. You can do it via bin/mailman shell if you have
> access and know what you're doing (see
> <http://mailman.readthedocs.io/en/release-3.0/src/mailman/runners/docs/diges…>)
>
> If you file an issue at
> <https://gitlab.com/mailman/postorius/issues/new>, it might help
> expedite this.
Okay.
10 years, 6 months
Django Internal Server Error on held_messages
by Hasan Berkay Çağır
Hello,
We've been running a Mailman3 instance with Debian 10's official package:
Mailman Core Version: GNU Mailman 3.2.1 (La Villa Strangiato)
Mailman Core API Version: 3.0
Mailman Core Python Version: 3.7.3 (default, Jan 22 2021, 20:04:44) [GCC 8.3.0]
For some reason, and only on some lists, when we try to see held messages on Postorius, we get an error message "An error occurred while processing your request." and the following error email:
"""
Internal Server Error: /postorius/lists/list.example.com/held_messages
KeyError at /postorius/lists/list.example.com/held_messages
'file'
Request Method: GET
Request URL: https://mailman.example.com/postorius/lists/list.example.com/held_messages
Django Version: 1.11.29
Python Executable: /usr/bin/uwsgi-core
Python Version: 3.7.3
Python Path: ['.', '', '/usr/lib/python37.zip', '/usr/lib/python3.7', '/usr/lib/python3.7/lib-dynload', '/usr/local/lib/python3.7/dist-packages', '/usr/lib/python3/dist-packages']
Server time: Thu, 24 Mar 2022 08:39:10 +0000
Installed Applications:
('hyperkitty',
'postorius',
'django_mailman3',
'django.contrib.admin',
'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')
Installed Middleware:
('django.contrib.sessions.middleware.SessionMiddleware',
'django.middleware.common.CommonMiddleware',
'django.middleware.csrf.CsrfViewMiddleware',
'django.middleware.locale.LocaleMiddleware',
'django.contrib.auth.middleware.AuthenticationMiddleware',
'django.contrib.messages.middleware.MessageMiddleware',
'django.middleware.clickjacking.XFrameOptionsMiddleware',
'django.middleware.security.SecurityMiddleware',
'django_mailman3.middleware.TimezoneMiddleware',
'postorius.middleware.PostoriusMiddleware')
Traceback:
File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner
41. response = get_response(request)
File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response
187. response = self.process_exception_by_middleware(e, request)
File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response
185. response = wrapped_callback(request, *callback_args, **callback_kwargs)
File "/usr/lib/python3/dist-packages/django/contrib/auth/decorators.py" in _wrapped_view
23. return view_func(request, *args, **kwargs)
File "/usr/lib/python3/dist-packages/postorius/auth/decorators.py" in wrapper
58. return fn(*args, **kwargs)
File "/usr/lib/python3/dist-packages/postorius/views/list.py" in list_moderation
520. paginator_class=MailmanPaginator)
File "/usr/lib/python3/dist-packages/django_mailman3/lib/paginator.py" in paginate
72. objects = paginator.page(page_num)
File "/usr/lib/python3/dist-packages/django_mailman3/lib/paginator.py" in page
48. result = self.function(count=self.per_page, page=number)
File "/usr/lib/python3/dist-packages/mailmanclient/restobjects/mailinglist.py" in get_held_page
134. return Page(self._connection, url, HeldMessage, count, page)
File "/usr/lib/python3/dist-packages/mailmanclient/restbase/page.py" in __init__
37. self._create_page()
File "/usr/lib/python3/dist-packages/mailmanclient/restbase/page.py" in _create_page
62. response, content = self._connection.call(self._build_url())
File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py" in call
99. raise HTTPError(url, response.status, content, response, None)
During handling of the above exception (HTTP Error 500: b'A server error occurred. Please contact the administrator.'), another exception occurred:
File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner
41. response = get_response(request)
File "/usr/lib/python3/dist-packages/postorius/middleware.py" in __call__
39. return self.get_response(request)
File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner
43. response = response_for_exception(request, exc)
File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in response_for_exception
93. response = handle_uncaught_exception(request, get_resolver(get_urlconf()), sys.exc_info())
File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in handle_uncaught_exception
135. extra={'status_code': 500, 'request': request},
File "/usr/lib/python3.7/logging/__init__.py" in error
1412. self._log(ERROR, msg, args, **kwargs)
File "/usr/lib/python3.7/logging/__init__.py" in _log
1519. self.handle(record)
File "/usr/lib/python3.7/logging/__init__.py" in handle
1529. self.callHandlers(record)
File "/usr/lib/python3.7/logging/__init__.py" in callHandlers
1591. hdlr.handle(record)
File "/usr/lib/python3.7/logging/__init__.py" in handle
905. self.emit(record)
File "/usr/lib/python3/dist-packages/django/utils/log.py" in emit
118. reporter = ExceptionReporter(request, is_email=True, *exc_info)
File "/usr/lib/python3/dist-packages/django/views/debug.py" in __init__
246. self.template_info = getattr(self.exc_value, 'template_debug', None)
File "/usr/lib/python3.7/tempfile.py" in __getattr__
614. file = self.__dict__['file']
Exception Type: KeyError at /postorius/lists/list.example.com/held_messages
Exception Value: 'file'
Request information:
USER: root
GET: No GET data
POST: No POST data
FILES: No FILES data
COOKIES:
rl_anonymous_id = '*'
rl_user_id = '*'
rl_group_id = '*'
rl_trait = '*'
rl_group_trait = '*'
rl_page_init_referrer = '*'
rl_page_init_referring_domain = '*'
csrftoken = '*'
sessionid = '*'
META:
CONTENT_LENGTH = ''
CONTENT_TYPE = ''
CSRF_COOKIE = '*'
DOCUMENT_ROOT = '/etc/nginx/html'
HTTPS = 'on'
HTTP_ACCEPT = 'text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,*/*;q=0.8'
HTTP_ACCEPT_ENCODING = 'gzip, deflate, br'
HTTP_ACCEPT_LANGUAGE = 'en-US,en;q=0.5'
HTTP_CACHE_CONTROL = 'max-age=0'
HTTP_COOKIE = '*'
HTTP_DNT = '1'
HTTP_HOST = 'mailman.example.com'
HTTP_REFERER = 'https://mailman.example.com/postorius/lists/list.example.com/'
HTTP_SEC_FETCH_DEST = 'document'
HTTP_SEC_FETCH_MODE = 'navigate'
HTTP_SEC_FETCH_SITE = 'same-origin'
HTTP_TE = 'trailers'
HTTP_UPGRADE_INSECURE_REQUESTS = '1'
HTTP_USER_AGENT = 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:98.0) Gecko/20100101 Firefox/98.0'
PATH_INFO = '/postorius/lists/list.example.com/held_messages'
QUERY_STRING = ''
REMOTE_ADDR = '::1'
REMOTE_PORT = '58290'
REQUEST_METHOD = 'GET'
REQUEST_SCHEME = 'https'
REQUEST_URI = '/postorius/lists/list.example.com/held_messages'
SCRIPT_NAME = ''
SERVER_NAME = 'mailman.example.com'
SERVER_PORT = '443'
SERVER_PROTOCOL = 'HTTP/2.0'
uwsgi.core = 0
uwsgi.node = b'example.com'
uwsgi.version = b'2.0.18-debian'
wsgi.errors = <_io.TextIOWrapper name=2 mode='w' encoding='UTF-8'>
wsgi.file_wrapper = ''
wsgi.input = <uwsgi._Input object at 0x7f8f7a6bf870>
wsgi.multiprocess = False
wsgi.multithread = True
wsgi.run_once = False
wsgi.url_scheme = 'https'
wsgi.version = '(1, 0)'
Settings:
Using settings module settings
ABSOLUTE_URL_OVERRIDES = {}
ACCOUNT_AUTHENTICATION_METHOD = 'username_email'
ACCOUNT_DEFAULT_HTTP_PROTOCOL = 'https'
ACCOUNT_EMAIL_REQUIRED = True
ACCOUNT_EMAIL_VERIFICATION = 'mandatory'
ACCOUNT_UNIQUE_EMAIL = True
ADMINS = "(('Mailman Suite Admin', 'admin(a)example.com'),)"
ALLOWED_HOSTS = ['*']
APPEND_SLASH = True
AUTHENTICATION_BACKENDS = "('django.contrib.auth.backends.ModelBackend', 'allauth.account.auth_backends.AuthenticationBackend')"
AUTH_PASSWORD_VALIDATORS = '********************'
AUTH_USER_MODEL = 'auth.User'
BASE_DIR = '/usr/share/mailman3-web'
CACHES = {'default': {'BACKEND': 'django.core.cache.backends.locmem.LocMemCache'}}
CACHE_MIDDLEWARE_ALIAS = 'default'
CACHE_MIDDLEWARE_KEY_PREFIX = '********************'
CACHE_MIDDLEWARE_SECONDS = 600
COMPRESS_CACHEABLE_PRECOMPILERS = '()'
COMPRESS_CACHE_BACKEND = 'default'
COMPRESS_CACHE_KEY_FUNCTION = '********************'
COMPRESS_CLEAN_CSS_ARGUMENTS = ''
COMPRESS_CLEAN_CSS_BINARY = 'cleancss'
COMPRESS_CLOSURE_COMPILER_ARGUMENTS = ''
COMPRESS_CLOSURE_COMPILER_BINARY = 'java -jar compiler.jar'
COMPRESS_CSS_COMPRESSOR = 'compressor.css.CssCompressor'
COMPRESS_CSS_FILTERS = ['compressor.filters.css_default.CssAbsoluteFilter']
COMPRESS_CSS_HASHING_METHOD = 'mtime'
COMPRESS_DATA_URI_MAX_SIZE = 1024
COMPRESS_DEBUG_TOGGLE = None
COMPRESS_ENABLED = True
COMPRESS_JINJA2_GET_ENVIRONMENT = <function CompressorConf.JINJA2_GET_ENVIRONMENT at 0x7f8f7b50d598>
COMPRESS_JS_COMPRESSOR = 'compressor.js.JsCompressor'
COMPRESS_JS_FILTERS = ['compressor.filters.jsmin.JSMinFilter']
COMPRESS_MINT_DELAY = 30
COMPRESS_MTIME_DELAY = 10
COMPRESS_OFFLINE = True
COMPRESS_OFFLINE_CONTEXT = {'STATIC_URL': '/mailman3/static/'}
COMPRESS_OFFLINE_MANIFEST = 'manifest.json'
COMPRESS_OFFLINE_TIMEOUT = 31536000
COMPRESS_OUTPUT_DIR = 'CACHE'
COMPRESS_PARSER = 'compressor.parser.AutoSelectParser'
COMPRESS_PRECOMPILERS = "(('text/less', 'lessc {infile} {outfile}'), ('text/x-scss', 'sassc -t compressed {infile} {outfile}'), ('text/x-sass', 'sassc -t compressed {infile} {outfile}'))"
COMPRESS_REBUILD_TIMEOUT = 2592000
COMPRESS_ROOT = '/var/lib/mailman3/web/static'
COMPRESS_STORAGE = 'compressor.storage.CompressorFileStorage'
COMPRESS_TEMPLATE_FILTER_CONTEXT = {'STATIC_URL': '/mailman3/static/'}
COMPRESS_URL = '/mailman3/static/'
COMPRESS_URL_PLACEHOLDER = '/__compressor_url_placeholder__/'
COMPRESS_VERBOSE = False
COMPRESS_YUGLIFY_BINARY = 'yuglify'
COMPRESS_YUGLIFY_CSS_ARGUMENTS = '--terminal'
COMPRESS_YUGLIFY_JS_ARGUMENTS = '--terminal'
COMPRESS_YUI_BINARY = 'java -jar yuicompressor.jar'
COMPRESS_YUI_CSS_ARGUMENTS = ''
COMPRESS_YUI_JS_ARGUMENTS = ''
CSRF_COOKIE_AGE = 31449600
CSRF_COOKIE_DOMAIN = None
CSRF_COOKIE_HTTPONLY = False
CSRF_COOKIE_NAME = 'csrftoken'
CSRF_COOKIE_PATH = '/'
CSRF_COOKIE_SECURE = False
CSRF_FAILURE_VIEW = 'django.views.csrf.csrf_failure'
CSRF_HEADER_NAME = 'HTTP_X_CSRFTOKEN'
CSRF_TRUSTED_ORIGINS = []
CSRF_USE_SESSIONS = False
DATABASES = {'default': {'ENGINE': 'django.db.backends.mysql', 'NAME': 'mailman3web', 'USER': 'mailman3web', 'PASSWORD': '********************', 'HOST': 'localhost', 'PORT': '', 'OPTIONS': {'init_command': "SET sql_mode='STRICT_TRANS_TABLES'", 'charset': 'utf8mb4'}, 'ATOMIC_REQUESTS': False, 'AUTOCOMMIT': True, 'CONN_MAX_AGE': 0, 'TIME_ZONE': None, 'TEST': {'CHARSET': None, 'COLLATION': None, 'NAME': None, 'MIRROR': None}}}
DATABASE_ROUTERS = []
DATA_UPLOAD_MAX_MEMORY_SIZE = 2621440
DATA_UPLOAD_MAX_NUMBER_FIELDS = 1000
DATETIME_FORMAT = 'N j, Y, P'
DATETIME_INPUT_FORMATS = ['%Y-%m-%d %H:%M:%S', '%Y-%m-%d %H:%M:%S.%f', '%Y-%m-%d %H:%M', '%Y-%m-%d', '%m/%d/%Y %H:%M:%S', '%m/%d/%Y %H:%M:%S.%f', '%m/%d/%Y %H:%M', '%m/%d/%Y', '%m/%d/%y %H:%M:%S', '%m/%d/%y %H:%M:%S.%f', '%m/%d/%y %H:%M', '%m/%d/%y']
DATE_FORMAT = 'N j, Y'
DATE_INPUT_FORMATS = ['%Y-%m-%d', '%m/%d/%Y', '%m/%d/%y', '%b %d %Y', '%b %d, %Y', '%d %b %Y', '%d %b, %Y', '%B %d %Y', '%B %d, %Y', '%d %B %Y', '%d %B, %Y']
DEBUG = False
DEBUG_PROPAGATE_EXCEPTIONS = False
DECIMAL_SEPARATOR = '.'
DEFAULT_CHARSET = 'utf-8'
DEFAULT_CONTENT_TYPE = 'text/html'
DEFAULT_EXCEPTION_REPORTER_FILTER = 'django.views.debug.SafeExceptionReporterFilter'
DEFAULT_FILE_STORAGE = 'django.core.files.storage.FileSystemStorage'
DEFAULT_FROM_EMAIL = 'postorius(a)example.com'
DEFAULT_INDEX_TABLESPACE = ''
DEFAULT_TABLESPACE = ''
DISALLOWED_USER_AGENTS = []
EMAILNAME = 'example.com'
EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend'
EMAIL_HOST = 'localhost'
EMAIL_HOST_PASSWORD = '********************'
EMAIL_HOST_USER = ''
EMAIL_PORT = 25
EMAIL_SSL_CERTFILE = None
EMAIL_SSL_KEYFILE = '********************'
EMAIL_SUBJECT_PREFIX = '[Django] '
EMAIL_TIMEOUT = None
EMAIL_USE_LOCALTIME = False
EMAIL_USE_SSL = False
EMAIL_USE_TLS = False
FILE_CHARSET = 'utf-8'
FILE_UPLOAD_DIRECTORY_PERMISSIONS = None
FILE_UPLOAD_HANDLERS = ['django.core.files.uploadhandler.MemoryFileUploadHandler', 'django.core.files.uploadhandler.TemporaryFileUploadHandler']
FILE_UPLOAD_MAX_MEMORY_SIZE = 2621440
FILE_UPLOAD_PERMISSIONS = None
FILE_UPLOAD_TEMP_DIR = None
FILTER_VHOST = False
FIRST_DAY_OF_WEEK = 0
FIXTURE_DIRS = []
FORCE_SCRIPT_NAME = None
FORMAT_MODULE_PATH = None
FORM_RENDERER = 'django.forms.renderers.DjangoTemplates'
HAYSTACK_CONNECTIONS = {'default': {'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', 'PATH': '/var/lib/mailman3/web/fulltext_index'}}
HOSTNAME = 'localhost.local'
IGNORABLE_404_URLS = []
INSTALLED_APPS = "('hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', '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')"
INTERNAL_IPS = []
LANGUAGES = [('af', 'Afrikaans'), ('ar', 'Arabic'), ('ast', 'Asturian'), ('az', 'Azerbaijani'), ('bg', 'Bulgarian'), ('be', 'Belarusian'), ('bn', 'Bengali'), ('br', 'Breton'), ('bs', 'Bosnian'), ('ca', 'Catalan'), ('cs', 'Czech'), ('cy', 'Welsh'), ('da', 'Danish'), ('de', 'German'), ('dsb', 'Lower Sorbian'), ('el', 'Greek'), ('en', 'English'), ('en-au', 'Australian English'), ('en-gb', 'British English'), ('eo', 'Esperanto'), ('es', 'Spanish'), ('es-ar', 'Argentinian Spanish'), ('es-co', 'Colombian Spanish'), ('es-mx', 'Mexican Spanish'), ('es-ni', 'Nicaraguan Spanish'), ('es-ve', 'Venezuelan Spanish'), ('et', 'Estonian'), ('eu', 'Basque'), ('fa', 'Persian'), ('fi', 'Finnish'), ('fr', 'French'), ('fy', 'Frisian'), ('ga', 'Irish'), ('gd', 'Scottish Gaelic'), ('gl', 'Galician'), ('he', 'Hebrew'), ('hi', 'Hindi'), ('hr', 'Croatian'), ('hsb', 'Upper Sorbian'), ('hu', 'Hungarian'), ('ia', 'Interlingua'), ('id', 'Indonesian'), ('io', 'Ido'), ('is', 'Icelandic'), ('it', 'Italian'), ('ja', 'Japanese'), ('ka', 'Georgian'), ('kk', 'Kazakh'), ('km', 'Khmer'), ('kn', 'Kannada'), ('ko', 'Korean'), ('lb', 'Luxembourgish'), ('lt', 'Lithuanian'), ('lv', 'Latvian'), ('mk', 'Macedonian'), ('ml', 'Malayalam'), ('mn', 'Mongolian'), ('mr', 'Marathi'), ('my', 'Burmese'), ('nb', 'Norwegian Bokmål'), ('ne', 'Nepali'), ('nl', 'Dutch'), ('nn', 'Norwegian Nynorsk'), ('os', 'Ossetic'), ('pa', 'Punjabi'), ('pl', 'Polish'), ('pt', 'Portuguese'), ('pt-br', 'Brazilian Portuguese'), ('ro', 'Romanian'), ('ru', 'Russian'), ('sk', 'Slovak'), ('sl', 'Slovenian'), ('sq', 'Albanian'), ('sr', 'Serbian'), ('sr-latn', 'Serbian Latin'), ('sv', 'Swedish'), ('sw', 'Swahili'), ('ta', 'Tamil'), ('te', 'Telugu'), ('th', 'Thai'), ('tr', 'Turkish'), ('tt', 'Tatar'), ('udm', 'Udmurt'), ('uk', 'Ukrainian'), ('ur', 'Urdu'), ('vi', 'Vietnamese'), ('zh-hans', 'Simplified Chinese'), ('zh-hant', 'Traditional Chinese')]
LANGUAGES_BIDI = ['he', 'ar', 'fa', 'ur']
LANGUAGE_CODE = 'en-us'
LANGUAGE_COOKIE_AGE = None
LANGUAGE_COOKIE_DOMAIN = None
LANGUAGE_COOKIE_NAME = 'django_language'
LANGUAGE_COOKIE_PATH = '/'
LOCALE_PATHS = []
LOGGING = {'version': 1, 'disable_existing_loggers': False, 'filters': {'require_debug_false': {'()': 'django.utils.log.RequireDebugFalse'}}, 'handlers': {'mail_admins': {'level': 'ERROR', 'filters': ['require_debug_false'], 'class': 'django.utils.log.AdminEmailHandler'}, 'file': {'level': 'INFO', 'class': 'logging.handlers.RotatingFileHandler', 'filename': '/var/log/mailman3/web/mailman-web.log', 'formatter': 'verbose'}, 'console': {'class': 'logging.StreamHandler', 'formatter': 'simple'}}, 'loggers': {'django.request': {'handlers': ['mail_admins', 'file'], 'level': 'INFO', 'propagate': True}, 'django': {'handlers': ['file'], 'level': 'INFO', 'propagate': True}, 'hyperkitty': {'handlers': ['file'], 'level': 'INFO', 'propagate': True}, 'postorius': {'handlers': ['file'], 'level': 'INFO', 'propagate': True}}, 'formatters': {'verbose': {'format': '%(levelname)s %(asctime)s %(process)d %(name)s %(message)s'}, 'simple': {'format': '%(levelname)s %(message)s'}}}
LOGGING_CONFIG = 'logging.config.dictConfig'
LOGIN_REDIRECT_URL = 'list_index'
LOGIN_URL = 'account_login'
LOGOUT_REDIRECT_URL = None
LOGOUT_URL = 'account_logout'
MAILMAN_ARCHIVER_FROM = "('127.0.0.1', '::1')"
MAILMAN_ARCHIVER_KEY = '********************'
MAILMAN_REST_API_PASS = '********************'
MAILMAN_REST_API_URL = '********************'
MAILMAN_REST_API_USER = '********************'
MANAGERS = []
MEDIA_ROOT = ''
MEDIA_URL = ''
MESSAGE_STORAGE = 'django.contrib.messages.storage.fallback.FallbackStorage'
MESSAGE_TAGS = {40: 'danger'}
MIDDLEWARE = "('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware')"
MIDDLEWARE_CLASSES = ['django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware']
MIGRATION_MODULES = {}
MONTH_DAY_FORMAT = 'F j'
NUMBER_GROUPING = 0
PASSWORD_HASHERS = '********************'
PASSWORD_RESET_TIMEOUT_DAYS = '********************'
POSTORIUS_TEMPLATE_BASE_URL = 'https://mailman.example.com/'
PREPEND_WWW = False
Q_CLUSTER = {'timeout': 300, 'save_limit': 100, 'orm': 'default', 'poll': 5}
ROOT_URLCONF = 'urls'
SECRET_KEY = '********************'
SECURE_BROWSER_XSS_FILTER = False
SECURE_CONTENT_TYPE_NOSNIFF = False
SECURE_HSTS_INCLUDE_SUBDOMAINS = False
SECURE_HSTS_PRELOAD = False
SECURE_HSTS_SECONDS = 0
SECURE_PROXY_SSL_HEADER = None
SECURE_REDIRECT_EXEMPT = []
SECURE_SSL_HOST = None
SECURE_SSL_REDIRECT = False
SERVER_EMAIL = 'root(a)example.com'
SESSION_CACHE_ALIAS = 'default'
SESSION_COOKIE_AGE = 1209600
SESSION_COOKIE_DOMAIN = None
SESSION_COOKIE_HTTPONLY = True
SESSION_COOKIE_NAME = 'sessionid'
SESSION_COOKIE_PATH = '/'
SESSION_COOKIE_SECURE = False
SESSION_ENGINE = 'django.contrib.sessions.backends.db'
SESSION_EXPIRE_AT_BROWSER_CLOSE = False
SESSION_FILE_PATH = None
SESSION_SAVE_EVERY_REQUEST = False
SESSION_SERIALIZER = 'django.contrib.sessions.serializers.PickleSerializer'
SETTINGS_MODULE = 'settings'
SHORT_DATETIME_FORMAT = 'm/d/Y P'
SHORT_DATE_FORMAT = 'm/d/Y'
SIGNING_BACKEND = 'django.core.signing.TimestampSigner'
SILENCED_SYSTEM_CHECKS = []
SITE_ID = 1
SOCIALACCOUNT_PROVIDERS = {}
STATICFILES_DIRS = '()'
STATICFILES_FINDERS = "('django.contrib.staticfiles.finders.FileSystemFinder', 'django.contrib.staticfiles.finders.AppDirectoriesFinder', 'compressor.finders.CompressorFinder')"
STATICFILES_STORAGE = 'django.contrib.staticfiles.storage.StaticFilesStorage'
STATIC_ROOT = '/var/lib/mailman3/web/static'
STATIC_URL = '/mailman3/static/'
TEMPLATES = [{'BACKEND': 'django.template.backends.django.DjangoTemplates', 'DIRS': [], 'APP_DIRS': True, 'OPTIONS': {'context_processors': ['django.template.context_processors.debug', 'django.template.context_processors.i18n', 'django.template.context_processors.media', 'django.template.context_processors.static', 'django.template.context_processors.tz', 'django.template.context_processors.csrf', 'django.template.context_processors.request', 'django.contrib.auth.context_processors.auth', 'django.contrib.messages.context_processors.messages', 'django_mailman3.context_processors.common', 'hyperkitty.context_processors.common', 'postorius.context_processors.postorius']}}]
TEST_NON_SERIALIZED_APPS = []
TEST_RUNNER = 'django.test.runner.DiscoverRunner'
THOUSAND_SEPARATOR = ','
TIME_FORMAT = 'P'
TIME_INPUT_FORMATS = ['%H:%M:%S', '%H:%M:%S.%f', '%H:%M']
TIME_ZONE = 'UTC'
USE_ETAGS = False
USE_I18N = True
USE_L10N = True
USE_THOUSAND_SEPARATOR = False
USE_TZ = True
USE_X_FORWARDED_HOST = True
USE_X_FORWARDED_PORT = False
WSGI_APPLICATION = 'wsgi.application'
X_FRAME_OPTIONS = 'SAMEORIGIN'
YEAR_MONTH_FORMAT = 'F Y'
"""
I've tried to debug this issue as much as I can but couldn't figure out anything. I wonder if anyone has encountered something like this or might have a clue about what's the problem here?
Thanks in advance,
Berkay
4 years, 7 months