It is really more an alias than a redirect/forwarder (speaking in domain terms). This command creates an entry in the qmail/users/assign file directing all transactions for the new, alias domain name, to the current, real domain. This eliminates needing symlinks, and other harddrive intensive operations. (Explanation stolen from here )
I was able to send/reply as info@original_domain.url as well as info@alias_domain.url and both would show up at the recipient with the correct sender address. And both accounts receive everything the same, as they “share” the inbox (it is really the inbox of the original_domain). So it is ideal e.g. for the RFC mail accounts. When we addd domains as server alias, we had no way of adding the mailaccounts postmaster@, hostmaster@, webmaster@ and abuse@ but those are required according to RFC and not having those could potentially get you into trouble.
I will now always use vaddaliasdomain when creating server aliases, even if our customers don’t want email accounts for the pointer domains.
I would even go as far as saying this could be a great feature in Sitworx, when adding a pointer domain as server alias (Checkbox “Also add this domain as E-Mail-Alias Domain”)
Yeah, that sounds similar to what I’ve done with Exchange servers in the past. You make one default domain, but you can have the server accept email on other domains as well.
Glad you got it all squared away. This is definitely going to come in handy for other InterWorx users in the future that run into this!
I hope you don’t mind, no guarantees it will be added but Nathan replied as below
I think this thread is a little special and may bypass the normal channels for feature requests, so please everyone，do not expect this every time to happen, but kudos to you guys and IW. You all rock
Many thanks
John
That was a great discussion! I’m going to submit a feature request regarding the alias discussion.
Thanks,
-Nathan
Hi i just wanted to add my 2 pence on this.
I came here looking for a solution to use multiple domains in a Wordpress Multisite setup on interworx. But i could not just use the pointers as i wanted to use email and SSL with the added domains.
To get around this i just setup my main wordpress in the primary domain for the account. i then just created secondary domains which had all the email and SSL functionality I needed.
i then enabled the shell user for the primary account and then i just created a soft symlink of the primary html folder in the base folder of the secondary domain folders (renaming/deleting the original secondary domain html folder).
Now multisite works with email and SSL with no problems at all
(looking at all the complex solutions above to get email working let alone SSL)
excellent! Looking up my own post about WP multisite I saw your comment and tried it. It works perfectly, thanks for sharing this solution.
I think it doesn’t say so in anywhere in this thread, but IW came through (as so often) and have indeed implemented the mail alias functionality in Siteworx shortly after our discussion here in 2016.
So now we have two ways, both quite convenient: [LIST=1]
If you only need "shared" mail accounts across several multisite domains, you simply set them up as ServerAlias domains and tick the mail alias box.
If you need fully independent mail accounts for each domain, you set them up as secondary domains and symlink the document root to the parent domain (i.e. first child of the multisite installation).
[/LIST]
Cheers,
Michael