[ntsysadmin] Linux Mail Servers Not Talking To Microsoft Outlook
Fraser Coast Digital Solutions
Hi All I’m Have Problems with Webhosted Provider’s Linux Mail Servers Not Sending and Receiving Email on Outlook IOS App And Desktop Outlook Client For Two Separate Clients Of Mine
Client 1 Has problems On Outlook IOS with Her New Email Account Not Sending Email Yes Try Email Settings Multiple Times and Talking to Webhosting Provider’s IT support With No Luck but Its Works on Gmail App for IOS For Sending Email and Receiving email.
Client 2 Has Problems with Not Sending and Receiving Email on Outlook 2019 Desktop Client on cPanel Mail Server I’m Waiting On email settings From Client
These Ave Australia Webhosted Provider’s Linux Mail Servers
Thank You
Tim Mayfield
IT Support Technician - Photographer
Fraser Coast Digital Solutions
Mobile: 0477106489
Email: T...@frasercoastdigitalsolutions.com.au
Michael B. Smith
What errors do you get?
Thanks.
Regards,
Michael B. Smith
Managing Consultant
Smith Consulting, LLC
--
You received this message because you are subscribed to the Google Groups "ntsysadmin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
ntsysadmin+...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ntsysadmin/SY4PR01MB5772CACA90ED1101A14FEF55946F9%40SY4PR01MB5772.ausprd01.prod.outlook.com.
Fraser Coast Digital Solutions
Thank You
Tim Mayfield
IT Support Technician - Photographer
Fraser Coast Digital Solutions
Mobile: 0477106489
Sent: Monday, August 22, 2022 10:18 pm
To: ntsys...@googlegroups.com <ntsys...@googlegroups.com>
Subject: RE: [ntsysadmin] Linux Mail Servers Not Talking To Microsoft Outlook
Shawn K. Hall
lookup failed twice. I suspect your name servers are either having
problems or are too aggressively filtering requests.
-S
> -----Original Message-----
> From: ntsys...@googlegroups.com
> [mailto:ntsys...@googlegroups.com] On Behalf Of Fraser
> Coast Digital Solutions
> Sent: Monday, August 22, 2022 08:06
> To: ntsys...@googlegroups.com
> Subject: Re: [ntsysadmin] Linux Mail Servers Not Talking To
> Microsoft Outlook
>
> please see attached she try to send a test email to me but no
> luck this email account is IMAP
>
>
> Thank You
>
> Tim Mayfield
>
> IT Support Technician - Photographer
>
> Fraser Coast Digital Solutions
>
> Mobile: 0477106489
>
> Email: T...@frasercoastdigitalsolutions.com.au
>
>
> Email: T...@frasercoastdigitalsolutions.com.au
> <mailto:T...@frasercoastdigitalsolutions.com.au>
>
>
> --
> You received this message because you are subscribed to the
> Google Groups "ntsysadmin" group.
> To unsubscribe from this group and stop receiving emails from
> it, send an email to ntsysadmin+...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ntsysadmin/SY4PR01MB5772CACA
> 90ED1101A14FEF55946F9%40SY4PR01MB5772.ausprd01.prod.outlook.co
> m
> A90ED1101A14FEF55946F9%40SY4PR01MB5772.ausprd01.prod.outlook.c
> om?utm_medium=email&utm_source=footer> .
> --
> You received this message because you are subscribed to the
> Google Groups "ntsysadmin" group.
> To unsubscribe from this group and stop receiving emails from
> it, send an email to ntsysadmin+...@googlegroups.com.
> To view this discussion on the web visit
> e89d0ab1ce80d70%40smithcons.com
> <https://groups.google.com/d/msgid/ntsysadmin/801a7dcadeb64c4d
> ae89d0ab1ce80d70%40smithcons.com?utm_medium=email&utm_source=footer> .
>
> --
> You received this message because you are subscribed to the
> Google Groups "ntsysadmin" group.
> To unsubscribe from this group and stop receiving emails from
> it, send an email to ntsysadmin+...@googlegroups.com.
> To view this discussion on the web visit
> C25F9AD5E33240DF94719%40SY4PR01MB5772.ausprd01.prod.outlook.co
> m
> <https://groups.google.com/d/msgid/ntsysadmin/SY4PR01MB57724B0
> DC25F9AD5E33240DF94719%40SY4PR01MB5772.ausprd01.prod.outlook.c
> om?utm_medium=email&utm_source=footer> .
>
>
Michael B. Smith
Email is never sent via IMAP. It is an email retrieval protocol.
You didn’t answer my question: what error(s) did you get?
To view this discussion on the web visit https://groups.google.com/d/msgid/ntsysadmin/SY4PR01MB57724B0DC25F9AD5E33240DF94719%40SY4PR01MB5772.ausprd01.prod.outlook.com.
Fraser Coast Digital Solutions
Thank You
Tim Mayfield
IT Support Technician - Photographer
Fraser Coast Digital Solutions
Mobile: 0477106489
Chad Johnson
Hi Michael this only error I get can't be saved to draft when my client is sending to any email address
Thank You
Tim Mayfield
IT Support Technician - Photographer
Fraser Coast Digital Solutions
Mobile: 0477106489
Sent From Outlook On IPhone
Fraser Coast Digital Solutions
Thank You
Tim Mayfield
IT Support Technician - Photographer
Fraser Coast Digital Solutions
Mobile: 0477106489
Sent: Tuesday, August 23, 2022 10:46 pm
To: ntsysadmin <ntsys...@googlegroups.com>
James Iversen
I look to you all for guidance and advice regarding an issue which has plagued our audit logging...
On all my DC's I get a "Login Failed (NTLM - Unknown Username) for user 'User...@Big.Corp.prv' from ISEPSN on DC1 at 'date\time'.
These occur whenever anyone attempts to access the Interwebz.
Our flesh and blood users have had their UPN suffix changed from @Big.Corp.prv to @Corp.com to allow for provisioning in AzureAD.
The @Big.Corp.prv suffix still exists, however is not the primary UPN suffix on their AD User Object.
Microsoft in their infinite wisdom has chosen to require a ".com" login for O365 and AzureAD
We have been using O365 for a long time, however AzureAD Sync was never previously enabled.
Now, we are testing the AzureAD Sync with a few users in a selected OU. I suppose changing the users who are not :synched" back to @Big.Corp.prv, but this does not solve for the larger issue...
Since this change, the logs have exploded with Unknown Username Error Code: 0xc0000064. Even for those who are being synched.
Does anyone know if there is a provision for making the authentication process from an ISE device less noisy?
Is there a configuration which can be modified to allow for
Authentication still succeeds, however is seems sloppy to me having all these failures in our logs...
Thoughts?
| James
Iversen Network Systems Analyst IT Infrastructure 1899 Central Plaza East Edmeston, NY 13335 | |
nycm.com | |
Join us on Facebook at www.facebook.com/NYCMInsurance.
***CONFIDENTIALITY NOTICE***
This email and any attachments to it are confidential and intended solely for the individual or entity to whom it is addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you have received this email in error, please contact the sender by reply email and destroy all copies of the original message.
Michael B. Smith
>> Microsoft in their infinite wisdom has chosen to require a ".com" login for O365 and AzureAD
This isn’t accurate.
I don’t know Cisco ISE, but in general, you should sync only validated domains in Azure/O365 and that is the normal configuration of Azure AD Connect.
Thanks.
Regards,
Michael B. Smith
Managing Consultant
Smith Consulting, LLC
--
You received this message because you are subscribed to the Google Groups "ntsysadmin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
ntsysadmin+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ntsysadmin/OFDCC10847.5565D2EB-ON852588A7.00464E8B-852588A7.004E15E9%40nycm.com.
Kurt Buff
To view this discussion on the web visit https://groups.google.com/d/msgid/ntsysadmin/68df5d9a134e499aafc823c03dca2842%40smithcons.com.
David Svirskis
This is covered well here - Prepare a non-routable domain for directory synchronization - Microsoft 365 Enterprise | Microsoft Docs
Microsoft verifies your control of a domain through public DNS. Any publicly routable domain should work (it doesn’t have to be a .com) but it *must* be publicly routable.
Microsoft cannot verify your exclusive control of a non-routable domain - you and dozens of unrelated organisations might be using the exact same internal domain name. Accordingly they will not allow validation of such domains within your Azure/Office 365 tenancy, and correspondingly non-routable domains *cannot* be used as a basis for account synchronisation.
Cheers,
David
From: ntsys...@googlegroups.com <ntsys...@googlegroups.com> On Behalf Of Kurt Buff
Sent: Thursday, 25 August 2022 11:53 AM
To: ntsys...@googlegroups.com
Join us on Facebook at
***CONFIDENTIALITY NOTICE***
This email and any attachments to it are confidential and intended solely for the individual or entity to whom it is addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you have received this email in error, please contact the sender by reply email and destroy all copies of the original message.
--
You received this message because you are subscribed to the Google Groups "ntsysadmin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ntsysadmin+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ntsysadmin/OFDCC10847.5565D2EB-ON852588A7.00464E8B-852588A7.004E15E9%40nycm.com.
--
You received this message because you are subscribed to the Google Groups "ntsysadmin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ntsysadmin+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ntsysadmin/68df5d9a134e499aafc823c03dca2842%40smithcons.com.
--
You received this message because you are subscribed to the Google Groups "ntsysadmin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
ntsysadmin+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ntsysadmin/CADy1Ce6K5xVtL4OLCR%3Dy7maTcGgze%2BS6cRcsYZZaJq67gXLkuQ%40mail.gmail.com.
Melvin Backus
We do a similar setup. The secondary UPN only exists for users who are in the sync group and are therefore licensed and synced for M365.
--
There are 10 kinds of people in the world...
those who understand binary and those who don't.
¯\_(ツ)_/¯
Join us on Facebook at
***CONFIDENTIALITY NOTICE***
This email and any attachments to it are confidential and intended solely for the individual or entity to whom it is addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you have received this email in error, please contact the sender by reply email and destroy all copies of the original message.
--
You received this message because you are subscribed to the Google Groups "ntsysadmin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ntsysadmin+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ntsysadmin/OFDCC10847.5565D2EB-ON852588A7.00464E8B-852588A7.004E15E9%40nycm.com.
--
You received this message because you are subscribed to the Google Groups "ntsysadmin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ntsysadmin+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ntsysadmin/68df5d9a134e499aafc823c03dca2842%40smithcons.com.
--
You received this message because you are subscribed to the Google Groups "ntsysadmin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
ntsysadmin+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ntsysadmin/CADy1Ce6K5xVtL4OLCR%3Dy7maTcGgze%2BS6cRcsYZZaJq67gXLkuQ%40mail.gmail.com.
James Iversen
Yes, that is the procedure which was followed to prepare our users in the non-routable domain Big.Corp.prv to Corp.com for directory synchronization using AzureAD Connect.
The issue is with an ISE PSN interpreting the existing on-prem users authenticating using the Corp.com suffix. The non-routable .prv domain is still a valid secondary UPN.
Upon new user creation, the non-routable domain .prv is applied and must be modified to .com for provisioning by synch in AzureAD.
The .com is valid and we are the verified holder of the managed domain.
| James
Iversen Network Systems Analyst IT Infrastructure 1899 Central Plaza East Edmeston, NY 13335 |
| Phone: | (607) 965-2706 |
nycm.com | |
From: "'David Svirskis' via ntsysadmin" <ntsys...@googlegroups.com>
To: "ntsys...@googlegroups.com" <ntsys...@googlegroups.com>
Date: 08/24/2022 10:27 PM
Subject: RE: [ntsysadmin] Authentication issue with On-Prem AD and Cisco ISE after Suffix change
ATTENTION: This email was sent from someone outside of NYCM.
To view this discussion on the web visit https://groups.google.com/d/msgid/ntsysadmin/e5fe9f7ef8e746c1a8f6704caabd2fba%40ausmarinetech.com.au.
Join us on Facebook at www.facebook.com/NYCMInsurance.
***CONFIDENTIALITY NOTICE***
This email and any attachments to it are confidential and intended solely for the individual or entity to whom it is addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you have received this email in error, please contact the sender by reply email and destroy all copies of the original message.
James Iversen
My ignorance is showing ;-)
I agree a .com, .biz, .net, .org, etc... should be required with a public cloud service.
From: "Michael B. Smith" <mic...@smithcons.com>
To: "ntsys...@googlegroups.com" <ntsys...@googlegroups.com>
Date: 08/24/2022 06:29 PM
Subject: RE: [ntsysadmin] Authentication issue with On-Prem AD and Cisco ISE after Suffix change
Sent by: ntsys...@googlegroups.com
ATTENTION: This email was sent from someone outside of NYCM.
>> Microsoft in their infinite wisdom has chosen to require a ".com" login for O365 and AzureAD
Join us on Facebook at
www.facebook.com/NYCMInsurance.
***CONFIDENTIALITY NOTICE***
This email and any attachments to it are confidential and intended solely
for the individual or entity to whom it is addressed. Any unauthorized
review, use, disclosure or distribution is prohibited. If you have received
this email in error, please contact the sender by reply email and destroy
all copies of the original message.
--
You received this message because you are subscribed to the Google Groups
"ntsysadmin" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to ntsysadmin+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ntsysadmin/OFDCC10847.5565D2EB-ON852588A7.00464E8B-852588A7.004E15E9%40nycm.com.
--
You received this message because you are subscribed to the Google Groups "ntsysadmin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ntsysadmin+...@googlegroups.com
To view this discussion on the web visit https://groups.google.com/d/msgid/ntsysadmin/68df5d9a134e499aafc823c03dca2842%40smithcons.com.
Michael B. Smith
The dripping? 😊
My test tenant (blogging) domain is “essential.exchange”. Azure understands all the TLDs, to the best of my knowledge.
What it _syncs_ is up to you (the admin).
To view this discussion on the web visit https://groups.google.com/d/msgid/ntsysadmin/OFDCD1D4EF.8A78CB14-ON852588A9.0045A5D2-852588A9.0045C016%40nycm.com.