- When clicking send in Microsoft Outlook, you receive an NDR email notification or email with an error text, either from Microsoft Exchange server or from the GFI FaxMaker machine.
- No error is shown in the GFI FaxMaker Monitor.
- The fax recipient did not receive the fax page(s).
- You encounter an NDR email notification from Microsoft Exchange server with a message similar to the following:
The message has been queued on server 'srvr.domain.local' since 11/16/2011 5:41:04 PM (UTC+02:00). The last attempt to send the message was at 11/16/2011 5:37:21 PM (UTC+02:00) and generated the error '444 4.4.4 NONSMTPGW.UnauthorizedAccess The access requested is not permitted by the OS for the specified path.'.
- Microsoft Exchange 2010
- All supported environments
This problem is caused by a routing issue. For example, if the GFI FaxMaker SMTP connector does not have the correct address space configured, Microsoft Exchange server will not know where to route emails (email fax requests) addressed to that are sent to firstname.lastname@example.org or [FAX: number].
This is also the case if the IIS SMTP server does not have the GFI FaxMaker domains configured as aliases.
- Stop the GFI FaxMaker FaxServer and the GFI FaxMaker Message Transfer Agent (MTA) services.
- Send an email fax request from Microsoft Outlook.
- Check if the email arrives in the ..\FaxMaker\sinkdrop directory. The files in this directory will be in .eml format. If no email is found in this directory, then the problem is with how the faxes are routed to GFI FaxMaker server.
- If the email arrives in this directory, start the GFI FaxMaker Message Transfer Agent service. This will cause the MTA to process the outbound email fax request from the ..\FaxMaker\sinkdrop directory. The SFM, BDY and other attachments of this email are stored in the ..\FaxMaker\out directory by the MTA.
- Check the content of the ..\FaxMaker\out directory.
- Expand Administrative Group > Routing Groups > First Routing Group > Connectors
- Here you should find the GFI FaxMaker SMTP Connector. If you do not find the connector, you will need to create it.
- Open the Properties for this connector and ensure that you have entered the IP address of the GFI FaxMaker server in the Forward all mail through this connector to the following smart host under the General tab.
- Once this is done, click the Address Space tab and ensure that you have the following address spaces:
Once you have confirmed that your GFI FaxMaker SMTP connector is set up correctly, you should ensure that your IIS Settings are set up correctly when GFI FaxMaker is installed on a separate machine to the Microsoft Exchange server.
- Browse to IIS Manager.
- Ensure that the faxmaker.com, smsmaker.com, FAX and SMS domains are present as aliases.
- Ensure that you have added your email domain.
- On the Microsoft Exchange server, open command prompt and
telnetport 25 of the GFI FaxMaker machine:
C:\Documents and Settings\Administrator> telnet %faxmakerip% 25
- If the SMTP Service is running, then you will receive an answer similar to this one:
220 ISA.xyz.gfi Microsoft ESMTP MAIL Service, Version: 6.0.3790.1830 ready at Wed, 26 Mar 2008 08:34:56 +0000
- Type "
250 ISA.test.gfi Hello [192.168.1.1]
- Try to access the virtual SMTP Server with the following SMTP
mail from: email@example.com
250 2.1.0 firstname.lastname@example.org....Sender OK
- If you receive an error message at this point, then we know that an object from the Faxmaker.com domain is not allowed to access the virtual SMTP Server.
- Next, enter a fax number and send it to the faxmaker.com domain. For testing purposes, this does not need to be a real fax number.
rcpt to: email@example.com
250 2.1.5 firstname.lastname@example.org
- If you receive an error at this point, it will most likely be a relay problem. In that case, you must permit the machine that you are using for this test to relay.
- Try to complete the test.
354 Start mail input; end with <CRLF>.<CRLF>
hello, this is a test
250 2.6.0 <ISAbpH71yEXUIEA000000a5@SvenISA.xyz.gfi> Queued mail for delivery
If you receive a message ID, then the test was successful.