Exhange Server 2016

[Jarsky]

I linked above an article on enabling protocol logs and setting location

[Bruno_A]

On 12/26/2019 at 1:04 PM, Jarsky said:

I linked above an article on enabling protocol logs and setting location

Thanks a lot, I hadn't noticed it. I'll have a look at that. I think, however, it might be best to find a smart host solution.

[leadeater]

On 12/25/2019 at 9:18 AM, wkdpaul said:

You'll need to create an MX record on your public DNS. Never checked if you could use O365 to point to your on-premise Exchange server. It's probably doable, but again, you need public DNS records.

Hybrid Exchange setup is supported in both configurations of O365 being the public transport server or your On-Prem Exchange server. Once the mail hits either one of those it just looks at the transport rules for the destination mailbox and sends it on to where it need to go within your Exchange setup, so no matter where it comes in by it'll get to where it needs to go (unless you monkey with the transport and send connectors and break it but we're free to break anything right ).

 

So it's actually not a bad option to purchase an O365 subscription that supports custom domains as a single user license for home labs and then point your MX records for your own domain to Exchange Online so it can do all the spam filtering and route mail to your lab Exchange Server and your lab Exchange Server can send mail back through to Exchange Online then out to the public internet. Gets past all the typical residential mail server blocking etc and protects you as well.

[Bruno_A]

5 hours ago, leadeater said:

Hybrid Exchange setup is supported in both configurations of O365 being the public transport server or your On-Prem Exchange server. Once the mail hits either one of those it just looks at the transport rules for the destination mailbox and sends it on to where it need to go within your Exchange setup, so no matter where it comes in by it'll get to where it needs to go (unless you monkey with the transport and send connectors and break it but we're free to break anything right ).

 

So it's actually not a bad option to purchase an O365 subscription that supports custom domains as a single user license for home labs and then point your MX records for your own domain to Exchange Online so it can do all the spam filtering and route mail to your lab Exchange Server and your lab Exchange Server can send mail back through to Exchange Online then out to the public internet. Gets past all the typical residential mail server blocking etc and protects you as well.

I was actually able to get my Server working as intended. I've got ports 80, 443 and 25 forwarded to the Exchange server in my router, so, I can access the OWA and receive emails, and used Amazon SES as a Smart Host to relay my outgoing emails. I am able to send emails to the internet, as long as the email is a verified email in the SES console. This is a limitation for new accounnts, I believe, that I already requested to lift.

 

Regarding the Office 365, that is an interesting setup. I do have an email domain in Office 365 For Business that I use for my emails and One Drive. How would that work? Would the Office 365 work as an SMTP relay that receives outgoing emails from my Exchange Server and send them to the destination, and the other way around? Receives from the sender and sends to my Exchange server?

[leadeater]

10 hours ago, Bruno_A said:

Would the Office 365 work as an SMTP relay that receives outgoing emails from my Exchange Server and send them to the destination, and the other way around? Receives from the sender and sends to my Exchange server?

All of the above, you can configure it to send and receive however you wish of any combination. Office 365/Exchange Online works more like an actual Exchange server in your Exchange Server environment  or it's more than just a SMTP relay but that is the big thing most people need. It's better to relay inbound and outbound email through Office 365 as it gets spam filtered and all the important reverse lookups and DNS security IDs are done for you so you are way less likely to get blacklisted. I think you're getting all that now with Amazon SES anyway though.

[Bruno_A]

16 hours ago, leadeater said:

All of the above, you can configure it to send and receive however you wish of any combination. Office 365/Exchange Online works more like an actual Exchange server in your Exchange Server environment  or it's more than just a SMTP relay but that is the big thing most people need. It's better to relay inbound and outbound email through Office 365 as it gets spam filtered and all the important reverse lookups and DNS security IDs are done for you so you are way less likely to get blacklisted. I think you're getting all that now with Amazon SES anyway though.

As it turns out, while Amazon SES delivers my emails, some email services will send it to Junk, such as Outlook and Office 365 emails. I need to find something better. I either find some information on how to improve my chances of not going to Junk, or I'll have a look at how I could use Office 365 For Business as a Relay.