Office 365/Connector
-
@dbeato said in Office 365/Connector:
@Jimmy9008 said in Office 365/Connector:
Hi folks,
Been struggling with this for a while now (1 day or so) and cannot seem to get this working. I have contacted Office 365 support, but no help yet. (This stopped working on Sunday). Would be great to have some ideas on what to check...
I have a local exchange server. This has a send connector to office 365 for two domains abc.co.uk, and abc.com. This routes emails to our Office 365 smart host address.
Within Office 365 I have a connector for accepting email from our IP and have those two domains entered as accepted domains.
When sending emails to the local exchange, all emails arrive successfully to my @abc.com inbox. When I try to send to an external email account, say, gmail, nothing comes through...
Any ideas?
Best,
JimRun the Hybrid Deployment Wizard again and then you should be able to send again. I have needed to do this multiple times for my Hybrid customers when it stops after a reboot or so it decides.
Just running this again now...
-
@dafyre said in Office 365/Connector:
Any chance your IP changed?
Nope. I just checked to be sure, but were static anyway.
-
Client Access Server is out of date. Running some updates to then retry the Deployment Wizard.
-
Figured out what is going on here.
Our developers recently built an API to our site. Somewhere in China is using the API to create a 7 days trial a few times a second.
The trial form uses SMTP to get our Exchange server to email them an activation link. Exchange routes the mail through Office 365, which has blocked the address as spam/attack. So, that is why no emails to other domains (legit customers).
So we're using Exchange 2013, does anybody know a way to drop/block any traffic our from the Exchange server to domain qq.com? All other traffic can flow fine, I just want to drop that traffic from our Exchange out.
Will add a rule to Office 365 too.
Best,
Jim -
@Jimmy9008 said in Office 365/Connector:
Figured out what is going on here.
Our developers recently built an API to our site. Somewhere in China is using the API to create a 7 days trial a few times a second.
The trial form uses SMTP to get our Exchange server to email them an activation link. Exchange routes the mail through Office 365, which has blocked the address as spam/attack. So, that is why no emails to other domains (legit customers).
So we're using Exchange 2013, does anybody know a way to drop/block any traffic our from the Exchange server to domain qq.com? All other traffic can flow fine, I just want to drop that traffic from our Exchange out.
Will add a rule to Office 365 too.
Best,
JimThat is backwards. Disable the API. Fire the developers. Add security to the API and then reenable it.
To actually answer your question, you can block any host in the Exchange ECP.
-
@JaredBusch said in Office 365/Connector:
@Jimmy9008 said in Office 365/Connector:
Figured out what is going on here.
Our developers recently built an API to our site. Somewhere in China is using the API to create a 7 days trial a few times a second.
The trial form uses SMTP to get our Exchange server to email them an activation link. Exchange routes the mail through Office 365, which has blocked the address as spam/attack. So, that is why no emails to other domains (legit customers).
So we're using Exchange 2013, does anybody know a way to drop/block any traffic our from the Exchange server to domain qq.com? All other traffic can flow fine, I just want to drop that traffic from our Exchange out.
Will add a rule to Office 365 too.
Best,
JimThat is backwards. Disable the API. Fire the developers. Add security to the API and then reenable it.
To actually answer your question, you can block any host in the Exchange ECP.
Thanks Jared, found it once home last night and the rules are in place
just didnt have time to update on here.
Yeah, I'd love to do that but the dev team are my boss so thats not happening (sadly)Thanks folks!
-
This kind of problem goes to show that devs do need to understand at least some IT aspects and the implications their software has.
-
Its disappointing. We could see these emails coming for a while yet the team above me ignored them. After over 16k emails, we were blocked, which then gives me a headache to sort it out.
So disappointing.
-
@Dashrender said in Office 365/Connector:
This kind of problem goes to show that devs do need to understand at least some IT aspects and the implications their software has.
That IT needs to be part of software projects.
The developers don't have to know.
Yes, it can be one and the same person with the role. But It is different roles that need filled.
-
Added tags.
