Overview
Inbound faxes as well as fax transmission reports may sometimes fail to be delivered to the intended users due to external factors on the customer environments such as the presence of local and/or perimeter firewalls, spam filtering tools, SMTP relaying restrictions by the receiving Email servers, or settings on the end-users' mail clients preventing delivery of Emails from non-whitelisted senders.
This article provides information on how to mitigate the above scenarios to ensure successful delivery of all inbound faxes and fax transmission notification Emails that may be getting blocked.
Information
Local firewall settings may prevent email relay requests from GFI FaxMaker Online thereby preventing users from receiving faxes through email or receiving fax transmission notifications when they send faxes.
In some instances depending on the email server configuration, inbound faxes and FaxMaker Online notification emails may be delivered to the users' mailboxes but in the Spam/Junk folder. In this scenario inform users to check their Spam/Junk folder for missing faxes or notifications.
To ensure that all FaxMaker Online emails (faxes and notifications) are delivered to the intended users' Inbox, confirm that your local firewall settings do not block SMTP relay attempts from the GFI FaxMaker Online SMTP server.
Additionally, (if applicable) verify that the firewall or spam filter is not blocking emails from notify@gfifax.com
by adding the sender to your Whitelist and if possible the entire gfifax.com
domain should be whitelisted.
To ensure that users receive faxes and fax notifications without impediment, the following IP addresses which are used to transmit FaxMaker Online emails should be Whitelisted by your mail host/spam filtering tool:
216.187.65.178 |
If a spam filtering tool reports that any of the above IPs has been blacklisted by a third-party DNSBL (DNS Blocklist), your mail server may block inbound Emails from FaxMaker Online which will affect the delivery of inbound faxes and fax transmission notification reports.
When this happens, open a support ticket for the server team to validate the blacklisting and put in a request to the DNSBL vendor to whitelist the mail server IP in question. DNSBLs are however controlled by 3rd parties and the response time varies for different vendors. A faster option as you wait for the IP to be removed from the DNSBL would be to whitelist the IPs with your mail host/spam filtering tool as described above.