Schlagwort-Archive: Exchange

Duplicate items in „sent“ for shared mailboxes

Now test these two things. When you are sending email as some non-problematic shared mailbox. Do you see an email in the Sent Item of the shared mailbox as well as in your Personal-Sent Items as well. What do you see if you send email from a problematic shared mailbox, do you still see the user(actual sender) copy. Run the Get-MailboxSentItemsConfiguration against the working shared mailboxes and let me know if the settings are same. Check if your Outlook is configured to be running in Cached Mode. If yes try switching to Online and see if still the issue re-occurs. Is DelegateSentItemsStyle registry key present or set with a value.Key: HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\PreferencesName: DelegateSentItemsStyleAlso on the problematic shared mailbox, change the settings as below and let me know the results.

Set-MailboxSentItemsConfiguration "Customer Support Feedback" -SendAsItemsCopiedTo Sender

Quelle: Duplicate items in „sent“ for shared mailboxes

Used maildomain list

Report for all uses mail domains in Exchange mailbox address list with accepted domains and an example. Also helpful to find wrong entries 🙂

$acceptedDomains = $(Get-AcceptedDomain).DomainName
$aDomains = [String]::Join(„,@“,$acceptedDomains).Split(„,“)
$aDomains[0] = „@$($aDomains[0])“
$domains=@()
$domains.Clear()
$a = New-Object -TypeName psobject
$a | Add-Member Noteproperty Name „@myinternaldomain.local“
$a | Add-Member Noteproperty Count 0
$a | Add-Member Noteproperty Primary 0
$a | Add-Member Noteproperty Firstentry „“
$a | Add-Member Noteproperty FirstPrimary „“
$a | Add-Member Noteproperty AcceptedDomain „1“
$domains += $a
$x = Get-Mailbox -ResultSize Unlimited$y = $x.EmailAddresses | ?{$_ -like „*@*“}
foreach($z in $y){
$i = $z.IndexOf(„@“)
$d = $z.Substring($i).ToLower()
$isPrimary = $z.StartsWith(„SMTP:“)
if($domains.Name.Contains($d)){
$domains[$domains.Name.Indexof($d)].Count ++
}else{
$a = New-Object -TypeName psobject
$a | Add-Member Noteproperty Name $d
$a | Add-Member Noteproperty Count 1
$a | Add-Member Noteproperty Primary 0
$a | Add-Member Noteproperty Firstentry $z
$a | Add-Member Noteproperty FirstPrimary „“
if($aDomains.Contains($d)){
$a | Add-Member Noteproperty AcceptedDomain „1“
}else{
$a | Add-Member Noteproperty AcceptedDomain „0“
}
$domains += $a
}
if($isPrimary){
$domain = $domains[$domains.Name.Indexof($d)]
$domain.Primary ++
if($domain.FirstPrimary.Length -eq 0){$domain.FirstPrimary = $z}
}
}
$domains | Out-GridView

Connecting to Office 365/Exchange

…..a script with a set of functions to allow me connect to each individual Office 365 service or Exchange Online: Connect-AzureActiveDirectory: Connects to Azure Active Directory Connect-AzureRMS: Connects to Azure Rights Management Connect-ExchangeOnline: Connects to Exchange Online Connect-SkypeOnline: Connects to Skype for Business Online Connect-EOP: Connects to Exchange Online Protection Connect-ComplianceCenter: Connects to Compliance Center Connect-SharePointOnline: Connects to SharePoint Online Connect-MSTeams: Connects to Microsoft Teams Get-Office365Credentials: Gets Office 365 credentials Connect-ExchangeOnPremises: Connects to Exchange On-Premises Get-OnPremisesCredentials: Gets On-Premises credentials Get-ExchangeOnPremisesFQDN: Gets FQDN for Exchange On-Premises Get-Office365Tenant: Gets Office 365 tenant name (SharePoint) Set-Office365Environment: Configures Uri’s and region to use…..

Quelle: Connecting to Office 365/Exchange | EighTwOne (821)

Mailflow issue from Exchange On-Prem to Office 365 – Lalit Bisht Blogs

You are on Exchange Hybrid environment and sending emails to Office 365 via specific SendConnector which has TlsCertificateName attribute configured and EOP is doing certificate validation for Inbound SMTP connections.

You might see any of the following errors in the queue/Protocol Logs.
–> 454 4.7.5 The certificate specified in TlsCertificateName of the SendConnector could not be found.
–> TLS negotiation failed with error NoCredentials.
–> „421 4.4.1 Connection timed out.“ Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts

It may be because of the following issues:
–> You changed the third party SMTP certificate but didn’t update the TlsCertificateName attribute on the send connector.
–> Third party certificate is not assigned to the SMTP services.
–> Status of that third party certificate shows „INVALID“ or „RevocationCheckFailure“.

Please perform the following to resolve the issue.
–> Update the TLSCertificateName attribute on the Office 365 SendConnector.

$cert = Get-ExchangeCertificate -Thumbprint
$TLSCert = (‘<I>’+$cert.issuer+'<S>’+$cert.subject)
Set-SendConnector -Identity -TLSCertificateName $TLSCert
–>Make sure required certificate is assigned to the SMTP service and certificate Status shows VALID.

Quelle: Mailflow issue from Exchange On-Prem to Office 365 – Lalit Bisht Blogs

Use shared mailbox mobile and other clients

Eine „shared mailbox“ aus Exchange 20XX bzw. Office365 kann nicht einfach auf mobilen Geräten (und anderen, die keinen eigenen Outlook Client installiert haben) genutzt werden. Dazu gibt es aber Lösungen

  1. IMAP-Konfig:
    E-Mail: xy@mydomain.com
    User: firstname.lastname@mydomain.com/xy
    PW: MyPassword
  2. Konto aktivieren
    Im Active Directory das Konto der „Shared Mailbox“ aktivieren und ein Kennwort festlegen. Dann kann das Postfach wie jedes andere am Client hinzugefügt werden.