On Tue, Apr 14, 2026 at 11:39 AM Markus Grandpré < markus.grandpre@uni-konstanz.de> wrote:
Dear list members
A user of our Mailman system reports having trouble logging in to access a mailing list archive. In the error messages that the Mailman system sends via email, we find:
... Internal Server Error: /mailman3/accounts/login/
ZoneInfoNotFoundError at /accounts/login/ 'No time zone found with key US/Eastern'
Request Method: POST Request URL: https://mailman.uni-konstanz.de/mailman3/accounts/login/ Django Version: 4.2.28 Python Executable: /usr/bin/uwsgi-core Python Version: 3.13.5 ... Exception Type: ZoneInfoNotFoundError at /accounts/login/ Exception Value: 'No time zone found with key US/Eastern' Raised during: allauth.account.views.LoginView Request information: USER: ****
GET: No GET data
POST: csrfmiddlewaretoken = 'E6IT1iObdZYMyGKUgAHSxJ6LCzSZPDOKZmgVCaN9Kaae3s5gJy75Dwh8ptWjzcdI' login = '****' password = '****' next = '/mailman3/hyperkitty/list/basex-talk@mailman.uni-konstanz.de/'
FILES: No FILES data
COOKIES: csrftoken = '********************' ...
(full error stack is attached to this email)
Is there a server-side solution available for our GNU Mailman system 3.3.10 (Tom Sawyer), which runs on Debian GNU/Linux 13 (trixie)?
Out of curiosity, is that time zone setting inside your config files? And what does the logs say if you check them? Again, seeing as you are using Python 3.13 and this - 'Python Executable: /usr/bin/uwsgi-core' (because I do not expect to see /usr/bin in $PATH when using the virtualenv install) - are you running in a virtualenv? Check your MM3 logs for a clue.
Others will have a way to nail the culprit.
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]