26

Re: iRedMail-1.0 has been released.

Has the issue "connect to 127.0.0.1:7777: Connection refused" been fixed in the release (or another since 0.97)? This happens when the policy service is down for unknown reasons.

I've been bugged by it for almost a year, and I have had to check my server for it everyday due to its randomness nature. Would have peace of mind if so!

Congrats on this great milestone!

27

Re: iRedMail-1.0 has been released.

Hi Zhang, just installed iRedMail-1.0 and login to iredadmin is ok but after i installed phpldapadmin and accessed to server_ip/phpldapadmin/ "404 not found"

I used ubuntu 18

command to install phppdaladmin

apt-get install phpldapadmin

sudo ln -s / usr/share/phpldapadmin /var/www/html

https://yourdomain/phpldapadmin

the result is 404 not found

Any advice?

Thanks

28

Re: iRedMail-1.0 has been released.

After upgrading to 1.0, following the upgrading docs and enabling mailbox quota checks, Dovecot fails to do auth lookups and logs the following error:

> Dec 18 11:55:36 mail iredapd [87.234.62.36] RCPT, bob@example.org -> alice@example.com, DUNNO [sasl_username=, sender=bob@example.org, client_name=mail.example.org, reverse_client_name=mail.example.org, helo=mail.example.org, encryption_protocol=TLSv1, encryption_cipher=ECDHE-RSA-AES256-SHA, server_port=25, process_time=0.0095s]
> Dec 18 11:55:36 mail dovecot: auth-worker(30339): Warning: sqlpool(mysql): Query failed, retrying: Unknown column 'mailbox.enablequota' in 'where clause'
> Dec 18 11:55:36 mail dovecot: auth-worker(30339): Error: sql(alice@example.com): User query failed: Unknown column 'mailbox.enablequota' in 'where clause'
> Dec 18 11:55:36 mail dovecot: quota-status(alice@example.com)<30451><>: Error: user alice@example.com: Auth USER lookup failed
> Dec 18 11:55:36 mail dovecot: quota-status: Error: Failed to lookup user alice@example.com: Internal error occurred. Refer to server log for more information.

I bet it's due to the MySQL `user_query` in `/etc/dovecot/dovecot-sql.conf` that contains `AND mailbox.enable%Ls%Lc=1`.

Looking at the `vmail` table it seems like most features have a corresponding `enable_<feature>` column. Maybe you missed to create that one for `enable_quota`?

29

Re: iRedMail-1.0 has been released.

mejo wrote:

> Dec 18 11:55:36 mail dovecot: auth-worker(30339): Error: sql(alice@example.com): User query failed: Unknown column 'mailbox.enablequota' in 'where clause'

I bet it's due to the MySQL `user_query` in `/etc/dovecot/dovecot-sql.conf` that contains `AND mailbox.enable%Ls%Lc=1`.

Looking at the `vmail` table it seems like most features have a corresponding `enable_<feature>` column. Maybe you missed to create that one for `enable_quota`?

After a second look, my assumption is that the feature is named ambiguously. It's supposed to be named `quota-status` (and the corresponding table field exists if you follow the upgrade instructions), but dovecot for some reason thinks it's named `quota`, therefore searching for table name `enable_quota`, not for `enable_quota-status`.

30

Re: iRedMail-1.0 has been released.

I am on iRedMail-0.9.9 with iRedAPD-3.1. Can I upgrade to iRedMail-1.0 without first upgrading iRedAPD to 3.2?

31

Re: iRedMail-1.0 has been released.

You can upgrade iRedAPD from 3.1 to the latest 3.3 directly.

----

Buy me a cup of coffee ($5) to support iRedMail:

buy me a cup of coffee

32

Re: iRedMail-1.0 has been released.

mejo wrote:

After upgrading to 1.0, following the upgrading docs and enabling mailbox quota checks, Dovecot fails to do auth lookups and logs the following error:

@ZhangHuangbin: did you have a look at this issue yet?

33

Re: iRedMail-1.0 has been released.

mejo wrote:

@ZhangHuangbin: did you have a look at this issue yet?

Please just follow our upgrade tutorial strictly. The column name is "enablequota-status" as mentioned in upgrade tutorial. The format of column name is "enable<feature>", not "enable_<feature>".

----

Buy me a cup of coffee ($5) to support iRedMail:

buy me a cup of coffee

34

Re: iRedMail-1.0 has been released.

Hello,

As has occured with SO many releases in the past (0.9.4, 0.9.8, and 0.9.8) there is once again a bug on FreeBSD 12 w/ ZFS jails in which the script runs, MariaDB is installed, but the tables are not configured.

Also, php-fpm is running on LOCAL_ADDRESS:999 instead of a unix socket (which is broken for security reasons on jails - 12.X has made changes to sysvipc within jails. I don't have the link but I can find it)

What did I do?

I downloaded 0.9.9 and disabled the block for the upgrade check. Then I simply use portmaster to keep everything up to date. Been running that way for years, since I am a fairly knowledgeable sysadmin, but I simply lack the scripting skills to fix this myself.

Please investigate. I'll pull the logs tomorrow.

Cheers,
-D

35

Re: iRedMail-1.0 has been released.

Dear @luckied,

Could you create a new forum topic and share the detailed error message(s)? i will try to reproduce the issue (without ZFS) and hopefully fix them all.

----

Buy me a cup of coffee ($5) to support iRedMail:

buy me a cup of coffee

36

Re: iRedMail-1.0 has been released.

Have the issues with Gmail marking mail sent from an iRedMail system as spam been resolved in this release?

37 (edited by awol123 2020-01-14 02:18:44)

Re: iRedMail-1.0 has been released.

Upgrading from 0.9.9 to 1.0.0, Debain 9.11 (stretch)

All mandatory parts done other than roundcube - latest version is now 1.4.2, is this ok to use? Instructions refer to 1.4.1.

I didn't realise this had not been installed with dpkg, for manual installation on an iRedMail server, do I use the 'Dependant' or 'Complete' package?

Tried the dependant one and get the error:

root@x:~/roundcubemail-1.4.2/bin# ./installto.sh /opt/www/roundcubemail
PHP Fatal error:  Uncaught Error: Class 'PEAR' not found in /root/roundcubemail-1.4.2/program/lib/Roundcube/bootstrap.php:103
Stack trace:
#0 /root/roundcubemail-1.4.2/program/include/iniset.php(62): require_once()
#1 /root/roundcubemail-1.4.2/program/include/clisetup.php(25): require_once('/root/roundcube...')
#2 /root/roundcubemail-1.4.2/bin/installto.sh(23): require_once('/root/roundcube...')
#3 {main}
  thrown in /root/roundcubemail-1.4.2/program/lib/Roundcube/bootstrap.php on line 103

-------
UPDATE: It's the complete package that is required, all working fine with 1.4.2.

unzipped to /root
/root/roundcubemail-1.4.2/bin/installto.sh /opt/www/roudcubemail

Doesn't change the folder name post upgrade, symlink still points to /opt/www/roundcubemail-1.3.8.

File permissions and ownership has changed:

BEFORE
root@x:/opt/www/roundcubemail-1.3.8-backup# ls -l
total 272
drwxr-xr-x  2 root     root       4096 Mar 23  2019 bin
----------  1 root     root     155016 Oct 23  2018 CHANGELOG
-rw-r--r--  1 root     root       1046 Oct 23  2018 composer.json-dist
drwxr-xr-x  2 root     root       4096 Mar 23  2019 config
-rw-r--r--  1 root     root      12726 Oct 23  2018 index.php
----------  1 root     root      10901 Oct 23  2018 INSTALL
d---------  3 root     root       4096 Mar 23  2019 installer
----------  1 root     root      35147 Oct 23  2018 LICENSE
drwxr-xr-x  2 www-data www-data   4096 Mar 23  2019 logs
drwxr-xr-x 35 root     root       4096 Mar 23  2019 plugins
drwxr-xr-x  8 root     root       4096 Mar 23  2019 program
drwxr-xr-x  3 root     root       4096 Mar 23  2019 public_html
----------  1 root     root       3876 Oct 23  2018 README.md
drwxr-xr-x  4 root     root       4096 Mar 23  2019 skins
d---------  7 root     root       4096 Oct 23  2018 SQL
drwxr-xr-x  2 www-data www-data   4096 Jan 13 02:02 temp
----------  1 root     root       3579 Oct 23  2018 UPGRADING
drwxr-xr-x  8 root     root       4096 Mar 23  2019 vendor

AFTER:
root@x:/opt/www/roundcubemail# ls -l
total 304
drwxr-xr-x  2      501       80   4096 Jan 13 18:04 bin
-rw-r--r--  1      501       80 177290 Jan  1 20:00 CHANGELOG
-rw-r--r--  1      501       80    940 Jan  1 20:00 composer.json-dist
drwxr-xr-x  2 root     root       4096 Jan 13 18:05 config
-rw-r--r--  1      501       80  12731 Jan  1 20:00 index.php
-rw-r--r--  1      501       80  12529 Jan  1 20:00 INSTALL
drwxr-xr-x  3      501       80   4096 Jan 13 18:04 installer
-rw-r--r--  1      501       80  35147 Jan  1 20:00 LICENSE
drwxr-xr-x  2 www-data www-data   4096 Mar 23  2019 logs
drwxr-xr-x 35      501       80   4096 Jan 13 18:04 plugins
drwxr-xr-x  8      501       80   4096 Jan 13 18:04 program
drwxr-xr-x  3 root     root       4096 Mar 23  2019 public_html
-rw-r--r--  1      501       80   3810 Jan  1 20:00 README.md
drwxr-xr-x  5      501       80   4096 Jan 13 18:04 skins
drwxr-xr-x  7      501       80   4096 Jan  1 20:00 SQL
drwxr-xr-x  2 www-data www-data   4096 Jan 13 02:02 temp
-rw-r--r--  1      501       80   4148 Jan  1 20:00 UPGRADING
drwxr-xr-x  9      501       80   4096 Jan 13 18:04 vendor

38 (edited by Neutro 2020-02-03 03:00:11)

Re: iRedMail-1.0 has been released.

Hey Zhang,

Thank you for iredmail 1.0! smile

I've just tried to install it on Debian 10 but after i added the firewall rules using the installer script the firewall service for debian was not working anymore.

So i did another install and at the firewall rules step this is the question asked:

< Question > Would you like to use firewall rules provided by iRedMail?
< Question > File: /etc/default/iptables, with SSHD ports: 22. [Y|n]

If i searched correctly the file iptables is not used anymore on Debian 10, it's nftables.

Might that be a small problem in the firewall script that doesn't detect Debian 10 firewall file properly?

In the meantime i skipped the firewall rules, will add them manually later from the example config files.

#edit: even when manually installing nftables before launching iredmail installer the install script still thinks iptables is the file. Answering no then manually copying the nftables.conf provided in the sample firewall folder and restarting nftables works great!

Thanks smile

#edit: also discovered that after a fresh install i have the same bug that the one you reported here:

https://sogo.nu/bugs/view.php?id=4684

[Warning] Aborted connection 34 to db: 'sogo' user: 'sogo' host: 'localhost' (Got an error reading communication packets)

I've tried reinstalling from scratch with only sogo and iredadmin and this problem happens right after the post-install reboot.

This problem also translates to mariadb service not beeing able to be terminated on server regular reboot / shutdown: "A stop job is running for Mariadb database service" is displayed and freezes the server indefinitively until manual power off.

Disabling the 2 sogo crob job stop the errors as previously reported in the forum.

I created an account and sent a message on the sogo bug report topic.

But i'm surprised to get this error on a fresh debian 10 install with mariadb. Am i the only one?

#PS: also noticed that when i click on "logout" on iredadmin pannel i get a "internal server error" message. It doesn't block anything but i thought i'd just mention it also here wink