So what happens if - either in Mail or Outlook - you create two separate
email accounts, one for sara@primary.com and the other for sara@new.com?
365 refuses to allow that - as they aliases of the same account, it just says that account already exists.
I accept that you might not want to have mail for the two domains
arriving in separate places, but you could resolve that with a suitable
rule.
Are both your domains hosted with the same hosting service?
Not sure what you mean by a hosting service in this sense. It's all on 365 in the cloud, which we pay shedloads for.
This is driving me potty.
Work has a new, second, trading identity and has registered a new domain. I've
added that domain to 365. 365 reports it as 'healthy'.
I've added an alias to my email account on 365 and it will happily accept and deliver email to me at that address. Lovely.
I've enabled 'send from alias' in mail flow in the Admin centre.
But I still can't *send* from that address without it overwriting the sent from address with the primary domain.
So if primary domain is primary.com and new domain is new.com, I can set Mail (or even Outlook if I have to) to use sara@new.com as a sending address, but when it arrives at the other end it shows as sara@primary.com
I'm not doing well finding a resolution online - all the things I can see I think I've done.
Has anyone here done this successfully?
Sara Merriman wrote:
This is driving me potty.
Work has a new, second, trading identity and has registered a new domain. I've
added that domain to 365. 365 reports it as 'healthy'.
I've added an alias to my email account on 365 and it will happily accept and
deliver email to me at that address. Lovely.
I've enabled 'send from alias' in mail flow in the Admin centre.
But I still can't *send* from that address without it overwriting the sent >> from address with the primary domain.
So if primary domain is primary.com and new domain is new.com, I can set Mail
(or even Outlook if I have to) to use sara@new.com as a sending address, but >> when it arrives at the other end it shows as sara@primary.com
I'm not doing well finding a resolution online - all the things I can see I >> think I've done.
Has anyone here done this successfully?
I've used flavours of Outlook since 2002 - but all on a PC - and have
had no difficulty in creating separate accounts of the form
sara@primary.com and sara@new.com where these are separate mailboxes at
the email hosting service. I have also created Outlook mailboxes of the
form graham@primary.com and sara@primary.com
Note that the mailboxes on the PC within Outlook are not the same as the mailboxes on the hosting service - all that happens is that they
communicate with each other using whatever protocol you specify (POP3,
IMAP, Exchange, etc.) I accept that the behaviour of Outlook on a Mac
might be very different to its behaviour on a PC.
So what happens if - either in Mail or Outlook - you create two separate email accounts, one for sara@primary.com and the other for sara@new.com?
I accept that you might not want to have mail for the two domains
arriving in separate places, but you could resolve that with a suitable
rule.
Are both your domains hosted with the same hosting service?
Sara Merriman wrote:
[snip]
So what happens if - either in Mail or Outlook - you create two separate >>> email accounts, one for sara@primary.com and the other for sara@new.com?
365 refuses to allow that - as they aliases of the same account, it just says
that account already exists.
That may be the root of the problem - you probably should not have
created an alias ..
I accept that you might not want to have mail for the two domains
arriving in separate places, but you could resolve that with a suitable
rule.
Are both your domains hosted with the same hosting service?
Not sure what you mean by a hosting service in this sense. It's all on 365 in
the cloud, which we pay shedloads for.
By hosting service I mean such widely advertised products as GoDaddy or Ionos, which register the domain name and offer web and mail servers.
Does your shedloads cover technical support?
I'm not familiar with using 365. The nearest experience was several
years ago with a Small Business Server which started life as a
stand-alone server, providing file and print sharing for several PCs in
a small business. It also contained a mail server, so emails were
delivered to it by SMTP via its static public IP address.
Later it was modified so all the emails were handled by a MS cloud
server (which might have been called 365) and each PC communicated
directly with the MS mail server. All the user account management was achieved using a management interface on the MS cloud system.
More recently I've heard that such companies now dispense with a local
server completely, and all their documents are held on a MS server in
the cloud. Useful if your users need access from any internet
connection; and awful if the head office internet connection fails -
even for a minute!
Sorry I'm not being much help ...
This is driving me potty.
Work has a new, second, trading identity and has registered a new domain. I've
added that domain to 365. 365 reports it as 'healthy'.
I've added an alias to my email account on 365 and it will happily accept and deliver email to me at that address. Lovely.
I've enabled 'send from alias' in mail flow in the Admin centre.
But I still can't *send* from that address without it overwriting the sent from address with the primary domain.
So if primary domain is primary.com and new domain is new.com, I can set Mail (or even Outlook if I have to) to use sara@new.com as a sending address, but when it arrives at the other end it shows as sara@primary.com
I'm not doing well finding a resolution online - all the things I can see I think I've done.
Has anyone here done this successfully?
365 needed to silently resync inself for several hours apparently. Sending correctly in Mail.app now works. As does office.com. Can't get bloody desktop Outlook to do it yet. But I now have hopes.
On 3 Feb 2023 at 12:06:50 GMT, "Graham J" <nobody@nowhere.co.uk> wrote:
Sara Merriman wrote:
[snip]
365 refuses to allow that - as they aliases of the same account, it just says
So what happens if - either in Mail or Outlook - you create two separate >>>> email accounts, one for sara@primary.com and the other for sara@new.com? >>>
that account already exists.
That may be the root of the problem - you probably should not have
created an alias ..
You have to - it's the only way of registering more than one address per person.
I accept that you might not want to have mail for the two domains
arriving in separate places, but you could resolve that with a suitable >>>> rule.
Are both your domains hosted with the same hosting service?
Not sure what you mean by a hosting service in this sense. It's all on 365 in
the cloud, which we pay shedloads for.
By hosting service I mean such widely advertised products as GoDaddy or
Ionos, which register the domain name and offer web and mail servers.
Oh good lord no - we don't use those.
Does your shedloads cover technical support?
Yes... but have you ever tried making sense of anything MS says when you contact them? I usually find them incomprehensible.
I'm not familiar with using 365. The nearest experience was several
years ago with a Small Business Server which started life as a
stand-alone server, providing file and print sharing for several PCs in
a small business. It also contained a mail server, so emails were
delivered to it by SMTP via its static public IP address.
Later it was modified so all the emails were handled by a MS cloud
server (which might have been called 365) and each PC communicated
directly with the MS mail server. All the user account management was
achieved using a management interface on the MS cloud system.
More recently I've heard that such companies now dispense with a local
server completely, and all their documents are held on a MS server in
the cloud. Useful if your users need access from any internet
connection; and awful if the head office internet connection fails -
even for a minute!
Sorry I'm not being much help ...
Thanks anyway - this is very much a 365 thing, and if it's not something you use or are familiar with, then it's not surprising :)
On 03/02/2023 12:20, Sara Merriman wrote:
On 3 Feb 2023 at 12:06:50 GMT, "Graham J" <nobody@nowhere.co.uk> wrote:
Sara Merriman wrote:
[snip]
365 refuses to allow that - as they aliases of the same account, it just says
So what happens if - either in Mail or Outlook - you create two separate >>>>> email accounts, one for sara@primary.com and the other for sara@new.com? >>>>
that account already exists.
That may be the root of the problem - you probably should not have
created an alias ..
You have to - it's the only way of registering more than one address per
person.
I accept that you might not want to have mail for the two domains
arriving in separate places, but you could resolve that with a suitable >>>>> rule.
Are both your domains hosted with the same hosting service?
Not sure what you mean by a hosting service in this sense. It's all on 365 in
the cloud, which we pay shedloads for.
By hosting service I mean such widely advertised products as GoDaddy or
Ionos, which register the domain name and offer web and mail servers.
Oh good lord no - we don't use those.
Does your shedloads cover technical support?
Yes... but have you ever tried making sense of anything MS says when you
contact them? I usually find them incomprehensible.
I'm not familiar with using 365. The nearest experience was several
years ago with a Small Business Server which started life as a
stand-alone server, providing file and print sharing for several PCs in
a small business. It also contained a mail server, so emails were
delivered to it by SMTP via its static public IP address.
Later it was modified so all the emails were handled by a MS cloud
server (which might have been called 365) and each PC communicated
directly with the MS mail server. All the user account management was
achieved using a management interface on the MS cloud system.
More recently I've heard that such companies now dispense with a local
server completely, and all their documents are held on a MS server in
the cloud. Useful if your users need access from any internet
connection; and awful if the head office internet connection fails -
even for a minute!
Sorry I'm not being much help ...
Thanks anyway - this is very much a 365 thing, and if it's not something you >> use or are familiar with, then it's not surprising :)
We are 365 and have multiple domains. We certainly have groups on
different domains for outgoing mail on a per user basis, but this isn't
quite what you want...
For that my googling seems to suggest that the magic of being able to
pick on the fly is "You need to ensure it's enabled via Set-OrganizationConfig -SendFromAliasEnabled $true"
<https://learn.microsoft.com/en-gb/powershell/module/exchange/set-organizationconfig?view=exchange-ps#-sendfromaliasenabled>
It seems to have been in the works for some time but could be out there now?
<https://www.microsoft.com/en-gb/microsoft-365/roadmap?filters=Outlook&searchterms=64123>
More recently I've heard that such companies now dispense with a local
server completely, and all their documents are held on a MS server in
the cloud. Useful if your users need access from any internet
connection; and awful if the head office internet connection fails -
even for a minute!
A cloud service with a typical slow-speed internet access is really a misconceieved solution.
I think such things were developed from a LAN
environment where full duplex Gigabit or 10 GB was widely available, so
even FTTP at maybe 100 Mbits/sec isn't really enough.
More recently I've heard that such companies now dispense with a local
server completely, and all their documents are held on a MS server in
the cloud. Useful if your users need access from any internet
connection; and awful if the head office internet connection fails -
even for a minute!
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 546 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 166:41:30 |
| Calls: | 10,385 |
| Calls today: | 2 |
| Files: | 14,057 |
| Messages: | 6,416,529 |