Faxmaker - updating Office 365 for Receiving
-
There is no inbound email functionality when dealing with a fax, right? So what role should Office 365 be playing when we are talking about receiving a fax?
-
As best as I can see from the log files, Faxes are being received, but they are not being getting into the mail system via the gateway.
IIS is not currently running, and when it is, it pulls all sorts of junk which gets ported the
inetpub/mailroot/badmailfolder. -
Open a command prompt and try to telnet to the SMTP address on O365, see if that's working.
-
One thing in reading: http://www.gfi.com/support/products/Using-GFI-FaxMaker-with-Office-365
RECEIVING
Login to the Office 365 Portal (http://portal.microsoftonline.com/)
Under the Management section, navigate to 'Domains'
Select the radio button next to your mail domain, then select 'Manage DNS'
Copy the 'Points to address' value which aligns to the Type MX row
In the GFI FaxMaker Configuration, select 'Email2FAXGateway', Properties
Under the 'SMTP connector' tab, in the Mail server name field, place the value from Step 4 above. Port field can be configured with a value of 25
If desired, you may configure your Email2FAXGateway settings to Use SSL
Select to 'Send test email' to an email address of a user configured in the 'Licensed users' node of the GFI FaxMaker Configuration and ensure success in receipt
So now, the MX record is show in the Mail Server Name/Ip and Port.
Sending still works, I just have no way to test receiving.
-
@gjacobse said in Faxmaker - updating Office 365 for Receiving:
As best as I can see from the log files, Faxes are being received, but they are not being getting into the mail system via the gateway.
Thats outbound, then, not inbound. I thought that we determined that outbound was working.
-
@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.
-
@gjacobse said in Faxmaker - updating Office 365 for Receiving:
Sending still works, I just have no way to test receiving.
Sending EMAIL still works? You are leaving out the biggest details.
-
@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
-
@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
