1

Topic: iRedMail-0.7.4 has been released.

Dear all,

iRedMail-0.7.4 stable release has been released.

Below's DRAFT plan for iRedMail-0.8, please don't hesitate to let us know your opinions:

  • Drop support for old Linux/BSD releases:

    • Ubuntu 8.04, 9.04, 9.10

    • openSUSE 11.3, 11.4

    • FreeBSD 7.x

  • Arch Linux support. Maybe supported in iRedMail-0.7.5.

  • PostgreSQL support in both iRedMail and iRedAdmin-Pro

  • SpamAssassin: Bayesian spam filtering and self-learning

  • [PROBABLY] OpenBSD support

Major changes since iRedMail-0.7.3:

  • It now works on Ubuntu 11.10, openSUSE-12.1. iRedMail now supports 7 major Linux/BSD distributions, check full list here.

  • Store realtime mailbox quota in separate SQL table to avoid mailbox migration issue. MySQL backend special.

  • Add Policyd-2.0.x (code name "cluebringer") support on Ubuntu 11.10. Important Note: iRedAdmin-Pro doesn't support Policyd-2 yet, customers have to manage Policyd-2 with its built-in webui.

  • Enable two sample dovecot sieve filters in Roundcube webmail: Move spam to Junk, Vacation. Both are disabled by default. With these two samples, end users can easily set vacation message or move spam to Junk folder.

  • SPF verification is now enabled by default.

  • Fixed:

    • Apache daemon user doesn't have permission to read Apache log files in Awstats's cron job.

    • Incorrect per-user realtime mailbox quota if loggin in with shadowAddress. OpenLDAP backend only. Thanks tmihalicek tomislav.mihalicek @gmail>.

    • Incorrect per-user sieve_dir setting in Dovecot. Thanks cetex <oskar@cetex>.

    • Add missing INDEXes for Amavisd database: msgs.mail_id, (msgs.content, msgs.time_num), quarantine.mail_id. Thanks rjnena <rjnena@gmail>, David <dcharbonnier@gmail>.

  • Package update:

    • Roundcube webmail -> 0.7.0.

    • phpMyAdmin -> 3.4.8

    • phpLDAPadmin -> 1.2.2

Addition tutorials you may be interested in:

2

Re: iRedMail-0.7.4 has been released.

Hi!

I would like update my iredmail-0.7.3 ldap system on debian squeeze.
I read this link http://iredmail.org/wiki/index.php?titl … .7.3-0.7.4 and set/edit my config.
Now I must run on it apt-get upgrade/update
or
I run /root/iRedMail-0.7.4/iRedMail.sh
What the next step?

The iRedMail.sh only apply new installation or is it good way the upgrade ?
Thanks

3

Re: iRedMail-0.7.4 has been released.

bunnyi wrote:

I read this link http://iredmail.org/wiki/index.php?titl … .7.3-0.7.4 and set/edit my config.

That's all you need to do to upgrade from 0.7.3 to 0.7.4.

bunnyi wrote:

Now I must run on it apt-get upgrade/update
or
I run /root/iRedMail-0.7.4/iRedMail.sh
What the next step?

The iRedMail.sh only apply new installation or is it good way the upgrade ?
Thanks

iRedMail.sh is used for new fresh installation. Usually, Upgrading iRedMail is just updating config files.

4

Re: iRedMail-0.7.4 has been released.

ZhangHuangbin wrote:

iRedMail.sh is used for new fresh installation. Usually, Upgrading iRedMail is just updating config files.

And if i want to update package like roundcube ? how this is handled ?

thx

5

Re: iRedMail-0.7.4 has been released.

Hi Zhang,

Roundcube 0.7.1 bugfix release has come immediate after stable release 0.7 .
If we install fresh iRedmail 0.7.4,Roundcube 0.7.1 will be installed by default ?

Thanks.

6

Re: iRedMail-0.7.4 has been released.

No. iRedMail-0.7.4 ships 0.7.0. You can upgrade Roundcube to 0.7.1 manually.

7

Re: iRedMail-0.7.4 has been released.

Hi

I've not alreay clear the correct upgrade procedure for adding new feature like policyd2 and something  like that.
Could you please explain me how can be performed ?

thx in advance.

8

Re: iRedMail-0.7.4 has been released.

About upgrading Policyd from 1.8 to 2.x, there's no official upgrade tutorials available, so please just stay on Policyd-1.8. Then push Policyd developers to release upgrade tutorials. http://policyd.sf.net/

9

Re: iRedMail-0.7.4 has been released.

Im doing here a brand new installation, but I got the following error message:

php5-mcrypt is already the newest version.
php5-mcrypt set to manually installed.
php5-mysql is already the newest version.
php5-mysql set to manually installed.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
php5-common : Conflicts: php5-mhash
php5-mhash : Depends: phpapi-20060613+lfs
              Depends: php5-common (= 5.2.6.dfsg.1-1+lenny16) but 5.3.3-7+squeeze8 is to be installed
E: Broken packages
< ERROR > Installation failed, please check the terminal output.

Since I have a newer version of php5-common, what should I do??

10

Re: iRedMail-0.7.4 has been released.

Please use only Debian official apt respositories, and follow iRedMail installation guide STRICTLY.

11

Re: iRedMail-0.7.4 has been released.

my apt/sources.list:

deb http://http.us.debian.org/debian lenny main
deb http://security.debian.org/ lenny/updates main

now the error:
The following packages have unmet dependencies:
amavisd-new : Depends: libcompress-zlib-perl (>= 1.35)
dovecot-imapd : Depends: dovecot-common (= 1:1.0.15-2.3+lenny1) but it is not going to be installed
dovecot-pop3d : Depends: dovecot-common (= 1:1.0.15-2.3+lenny1) but it is not going to be installed
libapache2-mod-wsgi : Depends: python (< 2.6) but 2.6.6-3+squeeze6 is to be installed
mysql-server : Depends: mysql-server-5.1 but it is not going to be installed
php5-common : Conflicts: php5-mhash
php5-imap : Depends: libc-client2007b but it is not going to be installed
             Depends: libkrb53 (>= 1.6.dfsg.2) but it is not going to be installed
             Depends: phpapi-20060613+lfs
             Depends: php5-common (= 5.2.6.dfsg.1-1+lenny16) but 5.3.3-7+squeeze8 is to be installed
php5-ldap : Depends: phpapi-20060613+lfs
             Depends: php5-common (= 5.2.6.dfsg.1-1+lenny16) but 5.3.3-7+squeeze8 is to be installed
php5-mhash : Depends: phpapi-20060613+lfs
              Depends: php5-common (= 5.2.6.dfsg.1-1+lenny16) but 5.3.3-7+squeeze8 is to be installed
python-ldap : Depends: python (< 2.6) but 2.6.6-3+squeeze6 is to be installed
python-mysqldb : Depends: python (< 2.6) but 2.6.6-3+squeeze6 is to be installed
rpm : Depends: librpm4.4 (>= 4.4) but it is not going to be installed
       Depends: librpm4.4 (< 4.5) but it is not going to be installed
E: Broken packages
< ERROR > Installation failed, please check the terminal output.

12

Re: iRedMail-0.7.4 has been released.

iRedMail will add necessary apt repositories on Debian 5, except Debian official repositories.
Please make sure you have below repos in /etc/apt/sources.list:

deb http://http.us.debian.org/debian lenny main contrib non-free
deb http://security.debian.org/ lenny/updates main contrib non-free

iRedMail will add below 2 repos automatically:

# Debian-Volatile. Used for updating ClamAV.
deb http://volatile.debian.org/debian-volatile lenny/volatile main contrib non-free
# Debian-Backports-iRedMail
deb http://backports.debian.org/debian-backports lenny-backports main

Please install iRedMail by following installation guide STRICTLY.

13 (edited by matteo.frakka 2012-04-15 22:35:39)

Re: iRedMail-0.7.4 has been released.

Hi!
I've just installed iRedMail 0.74 LDAP version on Debian squeeze (64bit) and I want to notice you something that may be wrong: I've found two file "aliases" on my system: /etc/alises and /etc/postfix/aliases. These files are very similar but your /etc/postfix/aliases has duplicated entry for "root":

/etc/postfix/aliases wrote:

# /etc/aliases
mailer-daemon: postmaster
postmaster: root
nobody: root
hostmaster: root
usenet: root
news: root
webmaster: root
www: root
ftp: root
abuse: root
noc: root
security: root
root: test
clamav: root
root: www@testdomain.lan
policyd: www@testdomain.lan
amavis: root

Secondly, system services that use smtp to send warning (like mdadm) still use mail aliases from previous /etc/aliases:

/etc/aliases wrote:

# /etc/aliases
mailer-daemon: postmaster
postmaster: root
nobody: root
hostmaster: root
usenet: root
news: root
webmaster: root
www: root
ftp: root
abuse: root
noc: root
security: root
root: test
clamav: root

I've removed existent /etc/aliases and I've replaced it with a symlink to /etc/postfix/aliases. After that, I've used the command "newalias" to update /etc/postfix/aliases.db and now anything seems to work fine.

14

Re: iRedMail-0.7.4 has been released.

matteo.frakka wrote:

root: test

iRedMail doesn't create this alias, it was copied from /etc/aliases (see comment below).

But i did a quick fix for this: comment out all aliases for root, then add 'root: www@xxx'.
Commit log:
https://bitbucket.org/zhb/iredmail/chan … 5cfb412870

matteo.frakka wrote:

Secondly, system services that use smtp to send warning (like mdadm) still use mail aliases from previous /etc/aliases:

If /etc/postfix/aliases doesn't exist, iRedMail will copy /etc/aliases to /etc/postfix/aliases.
if /etc/aliases doesn't exist, iRedMail will create an empty /etc/postfix/aliases first, then add others (root, amavis, policyd, etc).

15

Re: iRedMail-0.7.4 has been released.

ZhangHuangbin wrote:
matteo.frakka wrote:

root: test

iRedMail doesn't create this alias, it was copied from /etc/aliases (see comment below).

Yes, "test" is the "first user" that I've created at the end of the debian setup, following the installer instructions. So I suppose that iRedMail installation fail to replace this line alias with "root: www@xxx" during setup process when coping the content of /etc/aliases to /etc/postfix/aliases.

ZhangHuangbin wrote:

But i did a quick fix for this: comment out all aliases for root, then add 'root: www@xxx'.

Yes, done. But I need also to run again the command "newalias" to update /etc/postfix/aliases.db
Could an outdated /etc/postfix/aliases.db cause the problem of sending mails to incorrect aliases that I reported earlier?

ZhangHuangbin wrote:

If /etc/postfix/aliases doesn't exist, iRedMail will copy /etc/aliases to /etc/postfix/aliases.
if /etc/aliases doesn't exist, iRedMail will create an empty /etc/postfix/aliases first, then add others (root, amavis, policyd, etc).

Right.
But why you haven't choose to replace the old /etc/aliases (now outdated) with a symlink to the new (updated) file placed in /etc/postfix? Is a wrong procedure? I ask you just for curiosity...

16

Re: iRedMail-0.7.4 has been released.

matteo.frakka wrote:

Could an outdated /etc/postfix/aliases.db cause the problem of sending mails to incorrect aliases that I reported earlier?

Yes. You have to execute 'newaliases' after modified /etc/postfix/aliases.

matteo.frakka wrote:

But why you haven't choose to replace the old /etc/aliases (now outdated) with a symlink to the new (updated) file placed in /etc/postfix? Is a wrong procedure? I ask you just for curiosity...

/etc/aliases is usually used by Sendmail, not Postfix. I don't think it's not a good idea to use the same config file in two MTAs.