1

Topic: iRedMail-1.0-beta2 has been released.

Dear all,

Second beta release of iRedMail-1.0 has been released, please help test it and report the issues in our support forum. This should be the last beta release and no plan for a RC release.

Note: Please do not deploy beta release on production server, because we do not offer upgrade tutorial for beta release.

Introduce "iRedMail Easy" - the new deployment, upgrade and support platform

iRedMail Easy is the new web-based deployment, (one-click) upgrade and technical support platform introduced few months ago, we release new version frequently (currently one new release per month), with the one-click upgrade support, you can easily keep the iRedMail server up to date without caring about any technical details. It's the recommend way to deploy NEW iRedMail server and get technical support.

For more details, please check our website, the comparison of iRedMail Easy and classic downloadable installer is available too: https://www.iredmail.org/easy.html

If you need to upgrade existing iRedMail server to the iRedMail Easy platform, please check our tutorial: Migrate from iRedMail to iRedMail Easy platform.

Below are changes since iRedMail-1.0-beta2, you can find changes for 1.0-beta1 here.

Removed component
Improvements
  • tools/backup_*.sh: Remove old empty backup directory.

Fixed issues
  • Incorect SSL CA file path on FreeBSD.

  • Improper postrotate command for log files on Linux.

Updated packages
  • iRedAPD -> 3.2

  • netdata -> 1.18.0

----

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

2

Re: iRedMail-1.0-beta2 has been released.

Why does the installer no longer offer MySQL support - only OpenLDAP, MariaDB and PostGresSQL?

3

Re: iRedMail-1.0-beta2 has been released.

Nevermind, brain fart on Maria being a 'replacement'

4 (edited by aluisco 2019-11-18 22:02:12)

Re: iRedMail-1.0-beta2 has been released.

After install on Debian Buster iptables are not working because the file need to copy to correct location, need to fix that, the other problem is this:

root@mx:/home/aluisco# amavisd-new testkeys
TESTING#1 domain.com: dkim._domainkey.domain.com => invalid (public key: OpenSSL error: bad base64 decode)

I read a lot in forum and say problem with openssl library, I replace and reinstall many times, regenerate certificate and put the correct DKIM information on bind but the error is the same again, how I can fix that??

Regards,
Aluisco

5

Re: iRedMail-1.0-beta2 has been released.

aluisco wrote:

After install on Debian Buster iptables are not working because the file need to copy to correct location, need to fix that, the other problem is this:

Which file? Debian 10 uses nftables, not iptables anymore. You can find its config file /etc/nftables.conf.

aluisco wrote:

I replace and reinstall many times, regenerate certificate and put the correct DKIM information on bind but the error is the same again, how I can fix that??

How did you re-generate the dkim key? What's the console output?

6 (edited by aluisco 2019-11-19 11:03:57)

Re: iRedMail-1.0-beta2 has been released.

ZhangHuangbin wrote:
aluisco wrote:

After install on Debian Buster iptables are not working because the file need to copy to correct location, need to fix that, the other problem is this:

Which file? Debian 10 uses nftables, not iptables anymore. You can find its config file /etc/nftables.conf.

aluisco wrote:

I replace and reinstall many times, regenerate certificate and put the correct DKIM information on bind but the error is the same again, how I can fix that??

How did you re-generate the dkim key? What's the console output?

nftables are not working

aluisco wrote:

root@mx:/etc# systemctl status nftables
● nftables.service - nftables
   Loaded: loaded (/lib/systemd/system/nftables.service; enabled; vendor preset: enabled)
   Active: active (exited) since Mon 2019-11-18 21:59:05 CST; 7s ago
     Docs: man:nft(8)
           http://wiki.nftables.org
  Process: 10002 ExecStart=/usr/sbin/nft -f /etc/nftables.conf (code=exited, status=0/SUCCESS)
Main PID: 10002 (code=exited, status=0/SUCCESS)

nov 18 21:59:05 mx systemd[1]: Starting nftables...
nov 18 21:59:05 mx systemd[1]: Started nftables.
root@mx:/etc# iptables -L -n
Chain INPUT (policy ACCEPT)
target     prot opt source               destination         

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination         

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

The output is normal (I replace here the original domain):

aluisco wrote:

root@mx:/etc# amavisd-new genrsa /var/lib/dkim/domain,com.pem 1024
genrsa: Can't create file "/var/lib/dkim/domain.com.pem": File exists
root@mx:/etc# rm /var/lib/dkim/domain.com.pem
root@mx:/etc# amavisd-new genrsa /var/lib/dkim/domain.com.pem 1024
Private RSA key successfully written to file "/var/lib/dkim/domain.com.pem" (1024 bits, PEM format)
root@mx:/etc#

After that I showkeys and replace on bind, restart both services and still the error.

Regards,
Aluisco

7

Re: iRedMail-1.0-beta2 has been released.

aluisco wrote:

nftables are not working

What's the output if you run command below to start nftables manually:

service nftables stop
/usr/sbin/nft -f /etc/nftables.conf
aluisco wrote:

After that I showkeys and replace on bind, restart both services and still the error.

Here's a solution contributed by another user:
https://forum.iredmail.org/post67348.html#p67348

8

Re: iRedMail-1.0-beta2 has been released.

ZhangHuangbin wrote:
aluisco wrote:

nftables are not working

What's the output if you run command below to start nftables manually:

service nftables stop
/usr/sbin/nft -f /etc/nftables.conf
aluisco wrote:

After that I showkeys and replace on bind, restart both services and still the error.

Here's a solution contributed by another user:
https://forum.iredmail.org/post67348.html#p67348

I try to do but there isn't output:

root@mx:/var/log# service nftables stop
root@mx:/var/log# /usr/sbin/nft -f /etc/nftables.conf
root@mx:/var/log# iptables -L -n
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
root@mx:/var/log#

Also I follow the tutorial and reinstall openssl many times, I can't remove because will remove postfix, dovecot, etc. Just can reinstall ...

Regards,
Aluisco

9

Re: iRedMail-1.0-beta2 has been released.

aluisco wrote:

I try to do but there isn't output:

You should run "nft list ruleset" instead of "iptables -L -n".

10

Re: iRedMail-1.0-beta2 has been released.

ZhangHuangbin wrote:
aluisco wrote:

I try to do but there isn't output:

You should run "nft list ruleset" instead of "iptables -L -n".

If you upgrade a server from Debian 9 nftables will not be installed so iRedmail-1.0 must be able to work with both nftables and iptables.

11

Re: iRedMail-1.0-beta2 has been released.

Hello there,

  Without suggesting or committing to some date, is there any updates on the current state of 1.0b2 and some rough estimate on the release of 1.0?
  I am hopeful that it will be available soon as I have a deadline to renew my hosting, which I want to get out of and run my own installation.
  Preferably, an occasional update would be nice just to manage the expectations of the community.

Thanks and good holidays.

12

Re: iRedMail-1.0-beta2 has been released.

iRedMail-1.0 will be released on next monday, Dec 9. smile

13

Re: iRedMail-1.0-beta2 has been released.

ZhangHuangbin wrote:

iRedMail-1.0 will be released on next monday, Dec 9. smile

Good News.

Thanks for the update.