Thanks for the answer, but in my case this did not work.

the timezone in hyperkitty still wrong.

Thanks for the answer, but the users timezones in "Profiles" and "Timezone" in config of Django Mailman 3(Django admin screen) already have the time zone that I want and the timezone in hyperkitty still wrong.

Or is it somewhere else that set the user's timezone?

thanks for listening.

On 6/29/20 12:18 PM, Marco Marinello wrote:

I'm expirencing the same behaviour in Postorius. Is it possible to set a default timezone for new users? Already set it in settings_local.py but not having any effect, still seeing "Africa/Abidajin" in new users.

Do you mean the users time zone as displayed in the user's profile? This is a Django setting and the default should come from the TIME_ZONE setting in settings_local.py, at least if USE_TZ is set True

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

I've had to find and fix this on an installation today ..

If, like mine, all your users will be OK defaulting to one timezone, you can change the default in the database model. I think that, ideally, the application would pick something sensible at account creation time instead .. but this is good enough for me today..

Find the models.py file in django3-mailman

eg, if you installed in a venv, it might be somewhere like /opt/mailman/venv/lib/python3.7/site-packages/django_mailman3/models.py

Find this line:

timezone = models.CharField(max_length=100, choices=TIMEZONES, default="")

and change the default to be what you want, eg:

timezone = models.CharField(max_length=100, choices=TIMEZONES, default="Europe/London")

Now the model needs to be updated, and the software restarted:

$ mailman-web makemigrations Migrations for 'django_mailman3': venv/lib/python3.7/site-packages/django_mailman3/migrations/0003_auto_20210521_1212.py - Alter field timezone on profile

$ mailman-web migrate Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: Applying django_mailman3.0003_auto_20210521_1212... OK

# systemctl restart mailman-web

Test by creating a new account and viewing the profile.