Mail "access denied" error after update to 1.7

If I don’t intend to support receiving email at the burnsville.local domain, should I just remove it from the Mail settings? I suppose I’ll need to ensure that Addusers is enabled? Do I even need the burnsville.local domain in the Domains and users settings?

Yes you can delete that mail domain. Mail domains are typically registered in the public DNS to work properly. A private .local has little sense.

You may want to enable the “Add users” flag if you want user names as valid email addresses – Mail — NS8 documentation

The user domain instead is an LDAP db. Don’t remove it unless you want to loose users groups and passwords!

2 Likes

I haven’t deleted the .local domain from Mail settings yet because I am fearful of breaking things. I did do the following:

I enabled Add user addresses in the .com domain (both .local and .com are enabled)

  • Email from external is NOT delivered and is NOT returned due to access denied

I then disabled Add user addresses in the .local domain (only .com is enabled)

  • Email from external IS returned due to access denied

This makes be wary of deleting the .local domain in Mail. Any suggestions?

Charlie

1 Like

Usually deleting a mail domain shouldn’t be an issue, it just can be recreated, no data is lost.
Do you use virtualization? You could create a snapshot and revert if something goes wrong.

That’s bad, I didn’t test 2 ADs and 2 mail domains with same names yet.

I do use virtualization and did create a snapshot even before trying the steps above :wink:

To be clear, I have two Domains defined, both connected to the same AD (named .local and .com)

So my configuration is only 1 AD, but two mail domains.

It is entirely possible that I don’t have Domains and Mail Domains configured “properly”, although things are working, so I’m hesitant to make changes that I don’t fully understand. FYI - this NS8 server is a migration from an NS7 server, so some of the configuration settings were carried over.

1 Like

Mail version 1.7.2-dev.1 is available for testing. You can upgrade to the testing version from the Software Center page.

We tested your setup in lab and we are confident the warning message does not apply to your environment :slight_smile:

For any issue you can revert the update with the commands above

Thank you in advance for your help!

2 Likes

@davidep, I’ll be in the office tomorrow morning to give it a try and report back my findings.

2 Likes

Sorry, we found another bug regarding alias addresses, a fix will be provided soon.

1 Like

OK, I’ll wait.

2 Likes

Mail version 1.7.2-dev.2 is available for testing. Fixes the access of user/group addresses in combination with a mail domain named after the LDAP user domain.

2 Likes

I updated to 1.7.2-dev.2 and it appears to be working.

2 Likes

Should I revert and wait for the formal release?

No, I think you can keep it.
If there are other issues, just revert to the latest stable.

1 Like

Version 1.7.2-dev.3 is available for testing. It reduces the number of LDAP queries during Postfix address expansion. I’m already running it on my production server.

It can be installed from Software Center, with the Update to testing version action.

2 Likes