Faxmaker - updating Office 365 for Receiving
-
@gjacobse said in Faxmaker - updating Office 365 for Receiving:
@scottalanmiller said in Faxmaker - updating Office 365 for Receiving:
@gjacobse said in Faxmaker - updating Office 365 for Receiving:
Client recently updated their ISP and have a new IP address. They are able to SEND faxes, but are having trouble RECEIVING faxes.
Ah, now I understand. The issue is not with faxes at all. This was very bad wording. The issue is that they are not getting email alerts when a fax is received. So the question is about sending email, not about receiving faxes.
The fax is routed to a or the person by email.
They have four fax lines which take the faxes and run it into O365
Right, but the email is the issue, not receiving the fax. The fax is TURNED INTO email, not routed through email. The received product is an email, not a fax. This is critical for troubleshooting.
So the sending and receiving of faxes is working just fine. The issue is that when a fax is turned into an email, the sending of that email fails? This sounds like a pure email problem. Other than the application doing the sending being called GFI-Fax, there doesn't seem to be any faxing actually involved, correct? So, unless, that is incorrect, we should only be talking about email, right?
-
O365 Admin Center Message Trace:
Columns:Date time: From: TO: ~
-
@gjacobse said in Faxmaker - updating Office 365 for Receiving:
O365 Admin Center Message Trace:
Taking the trace back seven days, there is my 'fax' (email) and one other. Different recipient address @faxmaker.com
Both are pending
-
@gjacobse said in Faxmaker - updating Office 365 for Receiving:
O365 Admin Center Message Trace:
Which are the TO and FROM fields, there?
-
@scottalanmiller said in Faxmaker - updating Office 365 for Receiving:
@gjacobse said in Faxmaker - updating Office 365 for Receiving:
O365 Admin Center Message Trace:
Which are the TO and FROM fields, there?
can't seem to make columns:
Date time; From ; To.
-
@gjacobse said in Faxmaker - updating Office 365 for Receiving:
@scottalanmiller said in Faxmaker - updating Office 365 for Receiving:
@gjacobse said in Faxmaker - updating Office 365 for Receiving:
O365 Admin Center Message Trace:
Which are the TO and FROM fields, there?
can't seem to make columns:
Date time; From ; To.
They shoudl not be emailing to outside entities though, right? Faxmaker.com doesn't want to get that email and O365 might not want to relay to NTG. Try sending to internal people.
-
I'll be at work another 5 mins if you want me to send you a fax to test it.
-
@scottalanmiller said in Faxmaker - updating Office 365 for Receiving:
@gjacobse said in Faxmaker - updating Office 365 for Receiving:
@scottalanmiller said in Faxmaker - updating Office 365 for Receiving:
@gjacobse said in Faxmaker - updating Office 365 for Receiving:
O365 Admin Center Message Trace:
Which are the TO and FROM fields, there?
can't seem to make columns:
Date time; From ; To.
They shoudl not be emailing to outside entities though, right? Faxmaker.com doesn't want to get that email and O365 might not want to relay to NTG. Try sending to internal people.
If the Faxmaker device can act like a normal email client, then O365 shouldn't have a problem relaying, because the Faxmaker device will be logging in, not trying to be a spammer.
-
@Dashrender said in Faxmaker - updating Office 365 for Receiving:
I'll be at work another 5 mins if you want me to send you a fax to test it.
Test Fax received. I could see the system answer and receive.
The message is now sitting in Server IIS6.0
inetpub\mailroot\queue -
@Dashrender said in Faxmaker - updating Office 365 for Receiving:
@scottalanmiller said in Faxmaker - updating Office 365 for Receiving:
@gjacobse said in Faxmaker - updating Office 365 for Receiving:
@scottalanmiller said in Faxmaker - updating Office 365 for Receiving:
@gjacobse said in Faxmaker - updating Office 365 for Receiving:
O365 Admin Center Message Trace:
Which are the TO and FROM fields, there?
can't seem to make columns:
Date time; From ; To.
They shoudl not be emailing to outside entities though, right? Faxmaker.com doesn't want to get that email and O365 might not want to relay to NTG. Try sending to internal people.
If the Faxmaker device can act like a normal email client, then O365 shouldn't have a problem relaying, because the Faxmaker device will be logging in, not trying to be a spammer.
It connects via SMTP, so it is always a relay.
-
@gjacobse said in Faxmaker - updating Office 365 for Receiving:
@Dashrender said in Faxmaker - updating Office 365 for Receiving:
I'll be at work another 5 mins if you want me to send you a fax to test it.
Test Fax received. I could see the system answer and receive.
The message is now sitting in Server IIS6.0
inetpub\mailroot\queueI would expect IIS to log something, then.
-
IIS Log file
#Software: Microsoft Internet Information Services 7.5
#Version: 1.0
#Date: 2016-12-13 00:00:42
#Fields: time c-ip cs-method cs-uri-stem sc-status
00:00:42 207.x.x.x - - 0
00:00:42 207.x.x.x EHLO - 0
00:00:42 207.x.x.x - - 0
00:00:42 207.x.x.x MAIL - 0
00:00:42 207.x.x.x - - 0
00:00:42 207.x.x.x RCPT - 0
00:00:42 207.x.x.x - - 0
00:00:42 207.x.x.x BDAT - 0
00:00:47 207.x.x.x - - 0
00:00:47 207.x.x.x RSET - 0
00:00:47 207.x.x.x - - 0
00:00:47 207.x.x.x MAIL - 0
00:00:47 207.x.x.x - - 0
00:00:47 207.x.x.x RCPT - 0
00:00:47 207.x.x.x - - 0
00:00:47 207.x.x.x BDAT - 0
00:00:53 207.x.x.x - - 0
00:00:53 207.x.x.x RSET - 0
00:00:53 207.x.x.x - - 0
00:00:53 207.x.x.x MAIL - 0
00:00:53 207.x.x.x - - 0
00:00:53 207.x.x.x RCPT - 0
00:00:53 207.x.x.x RCPT - 0
00:00:53 207.x.x.x - - 0
00:00:53 207.x.x.x - - 0
00:00:53 207.x.x.x BDAT - 0
00:00:53 67.x.x.x - - 0
00:00:53 67.x.x.x EHLO - 0
00:00:53 67.x.x.x - - 0
00:00:53 67.x.x.x MAIL - 0
00:00:53 67.x.x.x - - 0
00:00:53 67.x.x.x RCPT - 0
00:00:53 67.x.x.x - - 0
00:00:53 67.x.x.x DATA - 0
00:00:53 67.x.x.x - - 0
00:00:55 67.x.x.x - - 0
00:00:55 67.x.x.x QUIT - 0
00:00:55 67.x.x.x - - 0
00:00:55 207.x.x.x - - 0
00:00:55 207.x.x.x QUIT - 0
00:00:55 207.x.x.x - - 0
00:00:56 216.x.x.x EHLO - 250
00:00:56 216.x.x.x MAIL - 250
00:00:56 216.x.x.x RCPT - 250
00:00:56 216.x.x.x RCPT - 250
00:00:56 216.x.x.x BDAT - 250
00:00:56 216.x.x.x QUIT - 240
-
@scottalanmiller said in Faxmaker - updating Office 365 for Receiving:
@Dashrender said in Faxmaker - updating Office 365 for Receiving:
@scottalanmiller said in Faxmaker - updating Office 365 for Receiving:
@gjacobse said in Faxmaker - updating Office 365 for Receiving:
@scottalanmiller said in Faxmaker - updating Office 365 for Receiving:
@gjacobse said in Faxmaker - updating Office 365 for Receiving:
O365 Admin Center Message Trace:
Which are the TO and FROM fields, there?
can't seem to make columns:
Date time; From ; To.
They shoudl not be emailing to outside entities though, right? Faxmaker.com doesn't want to get that email and O365 might not want to relay to NTG. Try sending to internal people.
If the Faxmaker device can act like a normal email client, then O365 shouldn't have a problem relaying, because the Faxmaker device will be logging in, not trying to be a spammer.
It connects via SMTP, so it is always a relay.
OMG stop saying that - yes I know it works like a relay - but it's not relaying to the outside world.. it's relaying to O365 - but I even took that back with my lower post stating that Faxmaker could act like a normal email client, logging into O365 and simply sending an email to someone else.
-
I have to step back from this for other matters...
-
@Dashrender said in Faxmaker - updating Office 365 for Receiving:
OMG stop saying that - yes I know it works like a relay - but it's not relaying to the outside world.. it's relaying to O365 - but I even took that back with my lower post stating that Faxmaker could act like a normal email client, logging into O365 and simply sending an email to someone else.
But I need to keep saying it because it is screwing up your thinking. It IS a relay and it ACTS like a relay. It's relaying email from one MTA through another to a mailbox somewhere with an unknown number of relays behind it. Like the other discussion that we are having... this is a general case that you are trying to make specific. It's not a special case, it works as a relay, because it is a relay.
Relaying to the outside world is actually what it is doing in his example cases.
-
I know that.
-
So - the problem is not the problem but a different problem that is the problem. Facepalm
In talking with the person today, the issue is this:
User Janice creates an email - but is a fax. Generates Email in Outlook and is sent. Office 365 gets it and sees that it is to <number>@faxmaker.com and kicks it out of O365 back to the onsite server FaxMaker where it has access to the modems.
From there, the email is converted to a fax and is sent using one of the four modems attached to the box.
-
Of note - this is totally different then that which was emailed or discussed via phone yesterday with the person.....
-
So why did an IP address change this? Is there a rule in O365 that sent ###@faxmaker.com to a specific IP or Host that wasn't updated?
-
and another question - sooooo... does inbound faxing actually work?
