"Send on Behalf" with a personalized email alias via GoDaddy custom Domain

%3CLINGO-SUB%20id%3D%22lingo-sub-2455619%22%20slang%3D%22en-US%22%3E%22Send%20on%20Behalf%22%20with%20a%20personalized%20email%20alias%20via%20GoDaddy%20custom%20Domain%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2455619%22%20slang%3D%22en-US%22%3EIntroduction%3A%3CBR%20%2F%3E%3CBR%20%2F%3EI%20have%20MS365%20Personal%20Subscription%20and%20want%20to%20upgrade%20to%20MS365%20Family%20Subscription%2C%20to%20then%20setup%20my%20family.%20I%20thought%20I'd%20invest%20in%20doing%20so%20and%20make%20use%20of%20a%20new%20GoDaddy%20custom%20domain%20and%20then%20connecting%20and%20adding%20the%20personalized%20alias.%20However%2C%20before%20I%20upgrade%20the%20subscription%2C%20I%20wanted%20to%20test%20functionality%20making%20sure%20all%20works%20as%20expected%2C%20however%20I'm%20experiencing%20this%20showstopper%20situation%20and%20if%20it%20can't%20be%20%22fixed%22%2C%20then%20I'm%20not%20going%20with%20Family%20Subscription%20and%20also%20not%20repeat%20this%20exercise%20for%20other%20families%20unfortunately.%3CBR%20%2F%3E%3CBR%20%2F%3EIssue%3A%3CBR%20%2F%3E%3CBR%20%2F%3EWhen%20sending%20an%20email%20to%20external%20parties%2C%20using%20the%20new%20alias%20from%20address%2C%3CBR%20%2F%3E%3CBR%20%2F%3E(which%20didn't%20need%20to%20manually%20type%2C%20but%20just%20select%3A%20%22someone%40customdomain%22)%2C%3CBR%20%2F%3E%3CBR%20%2F%3Ethe%20emails%20are%20delivered%20but%20with%20the%20unfortunate%20%22send%20on%20behalf%22%20tag%20which%20is%20then%20also%20identified%20as%20suspicious%20because%20the%20sender%20is%20different%20from%20the%20from%20address.%3CBR%20%2F%3E%3CBR%20%2F%3EResult%3A%3CBR%20%2F%3E%3CBR%20%2F%3EAm%20I%20missing%20something%3F%20Should%20I%20make%20my%20new%20custom%20alias%20the%20primary%20address%3F%20I%20can't%20use%20this%20whole%20premium%20solution%20to%20send%20such%20tagged%20emails%20if%20this%20is%20going%20to%20be%20the%20case%2C%20who%20would%20want%20to%20%3F%20Manual%20client-side%20whitelisting%20isn't%20worth%20the%20effort.%3CBR%20%2F%3E%3CBR%20%2F%3ESupplemental%3A%3CBR%20%2F%3E%3CBR%20%2F%3E-%20Using%20a%20standard%20alias%20with%20a%20Microsoft%20Domain%20does%20not%20tag%20it%2C%20it%20works%20as%20expected.%3CBR%20%2F%3E%3CBR%20%2F%3E-%20Email%20header%20results%20from%20the%20custom%20domain%20alias%3A%20SPF%3Dpass%2C%20DKIM%3Dpass%2C%20CompAuth%3Dfailed%2C%20DMARC%3Dnot%20configured%20even%20with%20Microsoft%20Domains%20such%20as%20%40live%2C%20%40hotmail%2C%20%40outlook.%20(Would've%20wanted%20to%20add%20the%20DNS%20record%20for%20DMARC%20to%20reject%20as%20a%20next%20step).%3CBR%20%2F%3E%3CBR%20%2F%3EHere%20are%20a%20couple%20of%20screenshots%20from%20Outlook%20clients%20on%20pc%20%26amp%3B%20mobile%2C%20and%20even%20GMail%20on%20web%20is%20complaining%3A%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2455619%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOutlook%20for%20Android%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOutlook%20for%20Windows%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOutlook%20on%20the%20web%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Occasional Contributor
Introduction:

I have MS365 Personal Subscription and want to upgrade to MS365 Family Subscription, to then setup my family. I thought I'd invest in doing so and make use of a new GoDaddy custom domain and then connecting and adding the personalized alias. However, before I upgrade the subscription, I wanted to test functionality making sure all works as expected, however I'm experiencing this showstopper situation and if it can't be "fixed", then I'm not going with Family Subscription and also not repeat this exercise for other families unfortunately.

Issue:

When sending an email to external parties, using the new alias from address,

(which didn't need to manually type, but just select: "someone@customdomain"),

the emails are delivered but with the unfortunate "send on behalf" tag which is then also identified as suspicious because the sender is different from the from address.

Result:

Am I missing something? Should I make my new custom alias the primary address? I can't use this whole premium solution to send such tagged emails if this is going to be the case, who would want to ? Manual client-side whitelisting isn't worth the effort.

Supplemental:

- Using a standard alias with a Microsoft Domain does not tag it, it works as expected.

- Email header results from the custom domain alias: SPF=pass, DKIM=pass, CompAuth=failed, DMARC=not configured even with Microsoft Domains such as @live, @hotmail, @outlook. (Would've wanted to add the DNS record for DMARC to reject as a next step).

Here are a couple of screenshots from Outlook clients on pc & mobile, and even GMail on web is complaining:

0 Replies