Virtualmin not adding domains to virtual alias table

I lost hours to this issue today, again. See my ticket at https://www.virtualmin.com/node/14135#comment-61810 - not receiving external mail.

So my host did this, manually: I added bizwaste.com to the virtual_alias_domains line in /etc/postfix/main.cf and restarted postfix. After doing that, mail is being delivered from an external location.

Is there any intelligible reason that Virtualmin shouldn't be doing this as part of provisioning a domain? Rimuhosting and I are agreed that : "I don't understand why it's not managing that."

I believe that this domain was provisioned from WHMCS, as that's how I set up most of my domains.

I don't believe that this issue shows up in the Validation report, either.

Status: 
Closed (fixed)

Comments

So was this domain ever able to accept email? I'd be interested to know if bizwaste.com was in the file initially and then got removed, or if it never appears in the first place ..

It would take mail from me, via Outlook, and my nextwavetech.us account, which is on the same server, but not from Yahoo. So it was an internal/external thing.

I would need to do a little experiment here. I am going to add mmmmmm.com via WHMCS, then add nnnnnn.com via Virtualmin, then check the main.cf for these domains.

OK, after executing those domain creations, and seeing them in Virtualmin, I searched my main.cf for mmmmmm and nnnnnn, and found neither. I would have expected to have found both.

If you need me to test anything else, please let me know. I really want resolution on this, because it is embarrassing me in front of my clients, and has cost me a lot of hours.

Best, K

I don't think that anyone would have removed a working domain from the main.cf, but it's possible. This is one file that it might be worth "auditing" somehow, it seems.

Either this is something unique to my OS, or my particular install, or some permissions on my server, or else hundreds of VPS owners are manually editing their Postfix configurations every time they create a domain.

It seems more likely that it's on the end of "unique" because, otherwise, I think you would have heard a lot more about it.

Those domains won't appear in main.cf though - they should instead appear in the /etc/postfix/virtual file, with lines like :

mmmmmm.com mmmmmm.com

OK, both of those domains are in the virtual file.

If what you say is true, or relevant, how come adding the domains to main.cf solved my issue of bizwaste not receiving external mail, and are you just talking around the issue?

Shouldn't Virtualmin be adding those domains to the main.cf file, so that I don't have to do it manually?

Anyway, can you make it so that when I create a new domain, it just works as expected, like, for example, that it can receive email from addresses outside of the server on which it lives?

This issue is currently more than nullifying the productivity gains I get from being able to update scripts through the Script Installer.

Thanks, K

So it shouldn't actually be necessary to add a domain to the main.cf file - assuming you are adding it to the mydestination line. The domain being in the virtual file should do the same thing.

If you like, I could login to your system and see what is going wrong here, as it clearly isn't behaving like other virtualmin installs..

Well, I don't currently add anything manually to anywhere, including mydestination- I really don't know and don't care to know what that is, I hope that Virtualmin takes care of it. I just push the buttons and fill out the forms. I've never once gotten notice that I had a manual step to perform, which I would have expected, if I had a manual step to perform.

Please do login and see at nextwavetech.us:10000. Let me know if you need me to do anything else.

Best, Ken

Ok, I see the issue - in your /etc/postfix/main.cf file, you had the virtual_alias_domains option set, which overrides the list of virtual domains from the /etc/postfix/virtual file! I disabled that virtual_alias_domains , and verified that the virtual file contains all the same domains..

So you shouldn't see this issue anymore.

Wow! Awesome! This issue has been a scourge. Thanks!

Glad we finally got it worked out .... I've never really looked at that particular Postfix directive before.

Automatically closed -- issue fixed for 2 weeks with no activity.