Hi,

the mail server was setup from the beginning with iredmail. There was no migration at any point.
The results of the command:
MariaDB [vmail]> SELECT address,forwarding FROM forwardings WHERE address='panagiotis@iccs.gr';
+-----------------------------+-----------------------------+
| address                     | forwarding                  |
+-----------------------------+-----------------------------+
| panagiotis@iccs.gr | panagiotis@iccs.gr |
+-----------------------------+-----------------------------+
1 row in set (0.00 sec)

Was there supposed to be more?

Bug confirmed.

I cannot reproduce this one.

I do see a similar problem when I try to save a forwarding or an alias - it says record saved but the field is empty. When I have a look in the database, I see that an entry in the forwarding table is made but with address and forwarding being the same instead of having the forwarding email address in the forwarding field.
Is this related to the bug you already found and when will be the release date for the update that fixes this behavior?

All the best

Mike

Hello Zhang,
also pls double check what happens with forwardings that have destination domain similar to domain in iredmail database. Deleting that domain leads to deleting all forwardings where is that domain present. (not creating new topic, sry)

For some reasons I had one domain temporarily hosted in iredmail, which was disabled in iredmail sometime later (and forwarded to real mailserver). (old.com)
We had also another domain (new.com), but lot of users and aliases there had forwardings in database to mailserver old.com, batch created by manual SQL insertion like

'insert into forwardings(address, forwarding, domain, dest_domain, is_list, active) values ('targetuser@new.com', 'targetuser@old.com', 'new.com', 'old.com', 1, 1);'

Thing is - when I removed the old.com domain in iredadmin, all these forwardings (where old.com was present as dest_domain) were deleted. I think Iredadmin should not delete forwardings belonging under another domain(new.com) which destination domain is same as domain being currently deleted(old.com).
I've checked the code of Iredadmin, and here you have the problematic part:
/iredadmin/libs/sqllib/domain.py - line 626

       for tbl in ['forwardings', 'moderators']:
            conn.delete(tbl,
                        vars=sql_vars,
                        where='dest_domain IN $domains')

... for table forwardings adding sthg like

where='dest_domain IN $domains AND domain IN $domains'

should work probably fine

Sorry Zhang but I have to strongly disagree here - there's no logic about deleting forwardings belonging under different domain than I am deleting. That those mails will be bounced (if the domain/mailbox/whatever isn't created elsewhere) is the correct solution (so the administrator will get a hint about forgotten forwarding in different domain that is not working).

I found this out after few days when these forwardings weren't working without any notification from Iredmail or anything, because it just silently stopped forwarding.  Situations when this can happen are a bunch, for example mailserver migration, DNS switching..

Just imagine you have one Iredmail with two domains and you are moving one of those domains to another Iredmail server(both domains are variously forwarding emails between each other - pretty usual situation)..
Et cetera et cetera..

Regards,
Martin Rott

EDIT: to the primary question in this thread, I see there almost similar pattern in user SQL library - the SQL queries are totally unaware of the mail domain under which the user belongs, couldn't be this the root cause? Also - this leads to situation when different domain admin deletes database records belonging under another domain. Again, this can lead to consequences that are far more lethal than keeping some address in db which gets bounced if domain doesn't exist anymore. 

I absolutely love Iredmail, we bought Iredadmin-Pro and are looking forward for buying support just to keep at least some funding for this excellent opensource project, just trying to convince you that this is potentially really dangerous.

The logic is slightly different than removing a domain, you just remove one user, but the domain is still hosted on your server. So we should remove this user from forwarding destination. isn't it?

Thank you very much.

I have installed the latest update, but I still have problems with domain aliases, sometimes I can enter one, but not two sometimes ist doesn't save any at all.
Should this have been fixed or do we need to wait for another update?