1

Topic: Possible documentation bugs in iRedAPD

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

According to this page, the configuration is stored in /opt/iredapd/settings.py. However, on my machine it is actually stored in: /opt/iredapd/etc/iredapd.ini

The discrepency may be because I have an old version.

I noticed that for most of the iRedMail software, you were careful to include a header breifly describing the license it is under (as required by the GPL). /opt/iredapd/src/iredapd.py simply has a terse header with the author's name. There is no mention that it may be a part of iRedAdmin-Pro, nor the more restrictive license. Though to be fair, the default copyright license (in the absence of a license grant) is fairly restrictive. In Canada, copies are allowed for things such a personal study (for example).

----

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

2

Re: Possible documentation bugs in iRedAPD

The whole iRedAPD project is licensed under GPL v3 except file libs/daemon.py (src/daemonn.py in old releases) is BSD license. It's mentioned in README.md:
https://bitbucket.org/zhb/iredapd/src/default/README.md