My org is set up in a cross-forest Exchange environment. Domain A is Exchange 2010 and Domain B Exchange 2013. We haven't migrated mailboxes yet and for our executive admins that manage execs in both orgs have two mailboxes, one in each domain. The scenario here is one exec admin has mailbox in Domain A forward all mail to her mailbox in Domain B. When she sends meeting invites out to a mailbox in Domain A she gets the reply in her Domain A mailbox that then forwards to her Domain B mailbox. If she sends an invite to a mailbox in Domain B, only her Domain B mailbox gets the reply. Why is the reply not going to her Domain A mailbox and then forwarding to the Domain B mailbox?
I solved my own problem. The Domain B mailbox had the Primary SMTP address of the Domain A mailbox instead of a corresponding mail contact in Domain B for Domain A. I removed the SMTP address and created a contact in Domain B to point to Domain A and now all traffic goes to that mailbox and then forwards to the mailbox in Domain B.
Related
Suppose that an organization uses an Microsoft Exchange server for emails. How to dump all the emails between the organization to email addresses in another organization for a given period (say all the emails sent and received in the last year)? Is there an easy way to do it in the backend of the Microsoft Exchange server?
I got a shared mailbox in O365 made of my old emailaccount. All the messages that are sent to it need to be forwarded to my new mailadress and everyone who mails to my old mailaddress needs to get an Out of Office notice saying the I am not working at the office anymore and thanking everyone for the cooperation.
I have an Out of Office configured in O365 admin panel, both for internal and external senders AND I also got the forwarding there configured and activated.
However, when people send to my old account, I get it in my new mailbox BUT the person then does NOT get the Out of Office. Mind you, it's not an ordinary user account but a Shared Mailbox. What did I do wrong?
For our domain(mydomain.com) , we have an Office 365 account that takes care of emails and the website is hosted with a hosting company on a shared server. From my shared server Laravel App I was sending emails using the office 365 SMTP server. The hosting company now blocks this connection to office 365 SMTP server:
"Please note that your account is hosted on a shared server where outgoing SMTP connections are restricted. This is to protect the reputation of the server IP address and prevent potential spamming.
You canconsider upgrading to a cloud server plan"
I do not wish to upgrade to a cloud server plan, are there any other options for an SMTP server ? , that my Laravel app could use ? I have a reseller account with many cpanel accounts on the shared server. So i could use another one of my domains smtp server but I need the emails sent out to be from an office 365 email address. So contact#mydomain.com. Possible solutions ?
If you are sending emails, its actually not recommended to use the SMTP server used by your normal email provider (e.g. Office 365, GMail).
Instead you should use a transactional email service, which is designed for sending a large number of emails programically.
See:
Sendgrid
Amazon SES
If you are unable to send emails using a particular port (which seems to be your issue), feel free to send emails user their respective API's:
Sendgird:
https://sendgrid.com/docs/for-developers/sending-email/api-getting-started/
and https://sendgrid.com/docs/api-reference/
Amazon SES: https://docs.aws.amazon.com/ses/latest/DeveloperGuide/send-email-api.html
This will still use the usual HTTP ports, and use different ip's, therefore bypass any port & ip restrictions when sending emails.
When a case is created, and emails are sent to the client, the mail syncs correctly between exchange/outlook, and CRM. However when a reply comes back from the client to the service representative, the mails are not automatically tracked as part of the original case that was set even though CRM reference details are present in the email subject line. The track number is correctly injected into the subject of the email and is still present when the client responds.
Our setup is as follow:
CRM : CRM 2016 on dedicated server (all roles)
Exchange : Exchange 2016 on dedicated server (all roles)
SQL : SQL Server 2014 ENT. With DB failover on dedicated server (all roles)
Exchange is configured as Internal Relay, and has outlook anywhere and active sync configured and externally facing. (no other protocols)
CRM mail is configured with Email Profile Authentication using an impersonation account to access and communicate with exchange.
Email accounts are processed using server side synchronisation. And users are using CRM for outlook.
Emails automatically appear in CRM, and can be tracked and set regarding. Appointments and tasks also sync as expected.
The following screen grabs summaries the settings
There are a couple of things that needs to be done here:
Under your Settings > Email, please make sure you add a bit more of digits to the incremental message counter, perhaps to 7.
Tick the box that says "Track emails sent between Dynamics 365 users"
NOTE
For the Emails to create activities in CRM there are a couple of things you need to make sure happens:
- The Customer should reply to a CRM Active Queue
AND
- The tracking subject "CRM:000001" needs to match
I'm having an issue, I have an On-Premise CRM Dynamics environment with Server Side synchronization, the sync works fine.
When creating appointments the System Users receive a meeting invite, but this is not sent to contacts in the system (even though some of them are emails from the same AD).
Is there an error log I can check, or some extra configuration needed in exchange server for it to work?
P.S. I'm attaching the current configuration.
When using server side synchronization, the account used as part of the authentication setup must have elevated permissions to send email on behalf of others or you need to modify the user's settings to allow others to send emails on their behalf, this could be what is causing the issue, also could you open up the emails that were not sent, they should also have an error message describing why the sending the email failed.