1

Topic: Upgrade overwrites default_settings parameters

==== Required information ====
- iRedMail version:
- Store mail accounts in which backend (LDAP/MySQL/PGSQL):
- Web server (Apache or Nginx):
- Linux/BSD distribution name and version:
- Related log if you're reporting an issue:
====
Hello,
Maybe I set it wrong somehow but I have set in /var/www/iredadmin/libs/default_settings.py

# It's RECOMMEND for better performance. Samples:
#   - hashed: domain.ltd/u/s/e/username-2009.09.04.12.05.33/
#   - non-hashed: domain.ltd/username-2009.09.04.12.05.33/
MAILDIR_HASHED = False

# Prepend domain name in path. Samples:
#   - with domain name: domain.ltd/username/
#   - without: username/
MAILDIR_PREPEND_DOMAIN = True

# Append timestamp in path. Samples:
#   - with timestamp: domain.ltd/username-2010.12.20.13.13.33/
#   - without timestamp: domain.ltd/username/
MAILDIR_APPEND_TIMESTAMP = False

Each upgrade overwrites Hashed maildires and append timestamps.
Shoul I set it somwhere else? or it's a bug in a scritpt

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: Upgrade overwrites default_settings parameters

It's mentioned in file 'libs/default_settings.py':

# --------------------------------------
# WARNING
# --------------------------------------
# Please place all your custom settings in settings.py to override settings
# listed in this file, so that you can simply copy settings.py while upgrading
# iRedAdmin.
# --------------------------------------

File libs/default_settings.py is used to store default settings, if you want to custom these settings, please set the same parameter name with proper value in iRedAdmin-Pro main config file 'settings.py' (/var/www/iredadmin/settings.py in your case). This way, you will always keep custom settings after upgrading iRedAdmin-Pro by copying 'settings.py' to new version.