1

Topic: How to upgrade iredadmin pro 1.3.1 to new version

Dear Admin,

How to use iredadmin pro 1.3.1 for iredmail 0.8.5 ?

If I use, message error,

[Fri Sep 20 17:20:30 2013] [error] [client 114.31.241.250] mod_wsgi (pid=26025): Target WSGI script '/var/www/iredadmin/iredadmin.py' cannot be loaded as Python module.
[Fri Sep 20 17:20:30 2013] [error] [client 114.31.241.250] mod_wsgi (pid=26025): Exception occurred processing WSGI script '/var/www/iredadmin/iredadmin.py'.
[Fri Sep 20 17:20:30 2013] [error] [client 114.31.241.250] Traceback (most recent call last):
[Fri Sep 20 17:20:30 2013] [error] [client 114.31.241.250]   File "/var/www/iredadmin/iredadmin.py", line 8, in <module>
[Fri Sep 20 17:20:30 2013] [error] [client 114.31.241.250]     from libs import iredbase
[Fri Sep 20 17:20:30 2013] [error] [client 114.31.241.250]   File "/var/www/iredadmin/libs/iredbase.py", line 34, in <module>
[Fri Sep 20 17:20:30 2013] [error] [client 114.31.241.250]     webmaster = cfg.general.get('webmaster', 'root')
[Fri Sep 20 17:20:30 2013] [error] [client 114.31.241.250]   File "/usr/lib/python2.6/site-packages/web/utils.py", line 76, in __getattr__
[Fri Sep 20 17:20:30 2013] [error] [client 114.31.241.250]     raise AttributeError, k
[Fri Sep 20 17:20:30 2013] [error] [client 114.31.241.250] AttributeError: 'general'

Thanks

Regard,

Tony

==== Required information ====
- iRedMail version:
- Store mail accounts in which backend (LDAP/MySQL/PGSQL):
- Linux/BSD distribution name and version:
- Related log if you're reporting an issue:
====

----

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

2

Re: How to upgrade iredadmin pro 1.3.1 to new version

Please set correct file permission for file /var/www/iredadmin/settings.ini, it must be owned by user/group: vmail:vmail, permission 0400.

3

Re: How to upgrade iredadmin pro 1.3.1 to new version

I have set owned by vmail:vmail, result same error. then i changed to iredadmin:iredadmin, succeeded.
Problem is I can't login admin with postmaster user after I change to iRedAdmin-Pro.
If I replace iredadmin link to iRedadmin-0.2.2, I can login to admin.

message error login only :
223.255.225.78 - - [25/Sep/2013:23:40:10 +0700] "GET /iredadmin/login?msg=INVALID_CREDENTIALS HTTP/1.1" 200 4551

4

Re: How to upgrade iredadmin pro 1.3.1 to new version

pathic wrote:

I have set owned by vmail:vmail, result same error. then i changed to iredadmin:iredadmin, succeeded.

Sorry about my mistake, it's iredadmin:iredadmin, not "vmail:vmail".

pathic wrote:

Problem is I can't login admin with postmaster user after I change to iRedAdmin-Pro.
If I replace iredadmin link to iRedadmin-0.2.2, I can login to admin.

Do you have correct settings in iRedAdmin-Pro config file (settings.ini)? You can simply copy config file from iRedAdmin-0.2.2. For example:

# cd /var/www/
# cp -p iRedAdmin-0.2.2/settings.ini iRedAdmin-Pro-xxx-xxx/

Be careful, config file 'settings.ini' must be owned by 'iredadmin:iredadmin', permission 0400.

5

Re: How to upgrade iredadmin pro 1.3.1 to new version

-r-------- 1 iredadmin iredadmin 3793 Sep 25 23:39 iRedAdmin-Pro-MySQL-1.3.1/settings.ini

here setting ini,

[general]
# Site webmaster's mail address.
webmaster = xxx

# Debug mode: True, False.
# Warning: Do *NOT* enable debug in product server.
debug = False

# Mail detail message of '500 internal server error' to webmaster: True, False.
# If set to True, iredadmin will mail detail error to webmaster when
# it catches 'internal server error' via LOCAL mail server to aid
# in debugging production servers.
mail_error_to_webmaster = False

# Default language.
lang = en_US

# Database backend: mysql.
backend = mysql

# Base directory used to store all mail data.
# iRedMail uses '/var/vmail/vmail1' as default storage directory.
# Tip: You can set a per-domain storage directory in domain profile page.
storage_base_directory = /var/vmail/vmail1

# Default mta transport.
# iRedMail uses 'dovecot' as defualt transport.
# Tip: You can set a per-domain or per-user transport in domain or user
#      profile page.
mtaTransport = dovecot

# Show user login date instead of created date: True, False.
# Please refer to iRedAdmin FAQ if you don't know how to track user last
# login data: http://www.iredmail.org/admin_faq.html
show_login_date = True

# Min/Max admin password length.
#   - min_passwd_length: 0 means unlimited, but at least 1 character
#                        is required.
#   - max_passwd_length: 0 means unlimited.
# User password length is controlled in domain profile.
min_passwd_length = 0
max_passwd_length = 0

[iredadmin]
# Database used to store iRedAdmin data. e.g. sessions, log.
host =  127.0.0.1
port =  3306
db = iredadmin
user = iredadmin
passwd =  07SsdoAx9E9G2fUKgBvlxxxxxxxxxx

############################################
# Database used to store mail accounts.
#
[vmaildb]
host =  127.0.0.1
port =  3306
db = vmail
user = vmailadmin
passwd =  FcbWMtsaClvOslcK26sExxxxxxxxxx

#################################################################
# Settings used for Policyd (1.8.x) integration. Provides global
# white-/blacklist, sender/recipient throttling, etc.
#
[policyd]

# Enable policyd integration: True, False.
enabled = True

# SQL Database used to store policyd data, eg. whitelist, blacklist.
# You can find related information in policyd config files:
#   - On RHEL/CentOS:   /etc/policyd.conf
#   - On Debian/Ubuntu: /etc/postfix-policyd.conf
#   - On FreeBSD:       /usr/local/etc/policyd.conf
# Related parameters:
#   host    -> MYSQLHOST
#   port    -> 3306 (Default)
#   db      -> MYSQLDBASE
#   user    -> MYSQLUSER
#   passwd  -> MYSQLPASS
host =  127.0.0.1
port =  3306
db = policyd
user = policyd
passwd =  z3swrlbnJFQwQEJznnqfxxxxxxxxxx

##############################################################################
# Settings used for Amavisd-new integration. Provides spam/virus quaranting,
# releasing, etc.
#
[amavisd]

########### Logging into SQL (@storage_sql_dsn) ##########
# Logging into SQL: True, False.
# Log info of incoming/outgoing emails into SQL.
# It's @storage_sql_dsn setting in amavisd. You can find this setting
# in amavisd-new config files:
#   - On RHEL/CentOS:   /etc/amavisd.conf
#   - On Debian/Ubuntu: /etc/amavis/conf.d/50-user.conf
#   - On FreeBSD:       /usr/local/etc/amavisd.conf
# Reference:
# http://www.iredmail.org/wiki/index.php?title=IRedMail/FAQ/Integrate.MySQL.in.Amavisd
logging_into_sql = True

host =  127.0.0.1
port =  3306
db = amavisd
user = amavisd
passwd =  ScOH0Ni3vYd7Eiqh7DbZxxxxxxxxxx

# #### Quarantining ####
# Release quarantined SPAM/Virus mails: True, False.
# iRedAdmin-Pro will connect to @quarantine_server to release quarantined mails.
# How to enable quarantining in Amavisd-new:
# http://www.iredmail.org/wiki/index.php?title=IRedMail/FAQ/Quarantining.SPAM
quarantine = True

# Port of Amavisd protocol 'AM.PDP-INET'. Default is 9998.
quarantine_port = 9998

6

Re: How to upgrade iredadmin pro 1.3.1 to new version

Does it work after you copy iRedAdmin-0.2.2/settings.ini to iRedAdmin-Pro?

7

Re: How to upgrade iredadmin pro 1.3.1 to new version

ZhangHuangbin wrote:

Does it work after you copy iRedAdmin-0.2.2/settings.ini to iRedAdmin-Pro?

Not work, everytime login message always wrong username and password. if I rollback to iRedAdmin-0.2.2, no problem (work fine)

8

Re: How to upgrade iredadmin pro 1.3.1 to new version

Did you upgrade iRedMail to 0.8.5 first?

9

Re: How to upgrade iredadmin pro 1.3.1 to new version

ZhangHuangbin wrote:

Did you upgrade iRedMail to 0.8.5 first?

yes, iRedMail current version is 0.8.5 and my iRedAdmin Pro 1.3.1