Error when adding address to approved/banned senders using an alias domain

[syska]

When adding a approved/banned sender using a alias domain is says:

"The domain xxx.xx is not local" which is not true. Changing it back to normal domain fixes this issue but makes the "alias domain" fearure useless.

I'm pretty sure this is a bug.

[akissa]

Not really, if you add it to the main domain, the aliases will automatically inherit the configuration.

[syska]

Yes, it's inheriting the main config, which is really nice, love that feature.

But it's not working when adding these white/black list rules for domains that inherited there configuration.

[akissa]

Just to be sure. If i have domain d.com which has x.com as an alias. The normal behaviour should be that i add a while/blacklist for d.com the same should apply for x.com.

In your experience is that not happening ?

[syska]

Not sure I want white/black list to be inherited.

I tried adding it like: Going to the frontpage. Clicking a message Add sender to list Which then it take what ever domain in there ( here, it was a "alias domin" ) and then clicking add gave me that error.

Since it's only configuration, like delivery server etc. we use it for.

Since it's really not obviously what domain it's belonging to here and real email addresses can still be different from domain to domain even though it's an alias domain.

Maybe I'm not using it like it's intended :-)

[akissa]

Okay, i now understand the context, i will try and replicate it and see.

[akissa]

This has been fixed in enterprise will backport to community soon.