Skip to main content
Kofax

International Fax (advanced) addressing via SMTP message

Summary

This "Fast Publish" solution is based on one case only and most likely doesn't cover all possible solution scenarios or error descriptions. This solution is provided as-is and may contain limited technical imperfections and consequently may be revised at any time. If you have the same or similar error situation and the provided solution doesn't help in resolving your issue, or if you have further questions or possible additions, please contact your next level of support. 3634

Description

Every fax message that needs to be sent out to an international destination needs to have a [+] as prefix.

To accomplish this we have three different possibilities for addressing to such number:

  1. Using the General Syntax for addressing.
  2. Using the Advanced Syntax for addressing.
  3. Modification of the SMTP Map file.

Using the General Syntax for addressing

When sending out fax messages using the the SMTP Service it is not a problem if we use the general syntax for addressing:

[fullname#][service#]number[#answerback]@mail-domain

Example for general syntax addressing:
    FAX#+4312345@yourcompany.com

When addressing by using the general syntax form, we can simply use the [+] as the international prefix and address the message to the desired destination.

Using the Advanced Syntax for addressing

If on the customer side the "advanced" addressing of fax messages via the SMTP Service is activated (using the Arr99) it isn't possible to set the [+] as prefix because it is interpreted as a Mask in TCfW.

"Advanced" addressing syntax for Fax messages sent via the SMTP Service:

number@[service].mail-domain

Example for "Advanced" addressing syntax:
    +4312345@fax.yourcompany.com

In this case the part [+4] is treated as a Mask in TCfW and therefor it will be cut of, so TCfW will address (in this case) to the number: "312345".

Solution for Advanced Syntax addressing

The easiest way how we can manipulate the [+] and to prevent it from be treated as a mask is by making a small change in the MAP file and a input into the Arr99. It is necessary to insert these lines as the FIRST Entry into the "TO_TC_RECP" section of the SMTP.MAP file.

Your SMLinkDomain must be the same as your [mail-domain].

  1. Open SMTP Map file (Default: C:\TCOSS\TCLP\SMTP.MAP)
  2.  Scroll to the "TO_TC_RECP" Section
  3. Insert as FIRST Entry these lines below: (without TO_TC_RECP-------------------------------------)

TO_TC_RECP -------------------------------------------
ENTRY -------- SMTP REM TestEntry
* SET_FREE_ADDRESS * SET_FREE_ADDRESS
REPLACE SRC.TS_FREE_ADDR "+"
"*"
ISOLATE_LOCALPART SRC.TS_FREE_ADDR VAR.1
VAR.2
COPYFMT VAR.2 ".!?" VAR.3 VAR.4
file:///C:/Kapow_temp/CRMKB/snapshots/3634/index.html 2/4
7/11/2018
COMPARESTRING
IEQU REG.TCLSM\SMLinkDomain VAR.4
COPYFMT
VAR.1
"#?!" DST.TS_FULLNAME VAR.6
COPYAPPEND DST.TS_RECP_ID VAR.6
SEARCH_ADDRTYPE VAR.3
VAR.6
SEP=.
REM End TestEntry

  1. Save MAP File.
  2. Restart TC/Link-SM.
  3. Open the Arr99 file.
  4. Add these lines into the "**ROUTE" section. (Without the **ROUTE):

**ROUTE
TCLSMQI:*~@[mail-domain],F:00~,SMTP to FAX
TCLSMQI:~@[mail-domain],F:~,SMTP to FAX

  1. Save the Arr99 file.

Explanation.

The change of the [+] into a [*] is done directly by the service. In the second step the Arr99 is waiting for a [*] in the Route section. As soon as a [*] is detected it replaces it with [00] which is an alternative to the [+]. If there is no [*] then the resulting number doesn't contain any [00], like it is supposed to. On this way we prevent that the [+] is interpreted as a mask.

Possible disadvantage for using this solution.

As the SMTP Service provides binary capabilities, which means that no document conversion will be done which can result in loss of data, since maybe some critical attachments aren't converted.

Modification of the SMTP Map File.

In this kind of solution the disadvantage which exists in the Advanced Syntax addressing is eliminated. As this solution requires some specific code manipulation of the SMTP Map file, it must be forwarded to the Professional Services which results in additional costs for the customer. If the customer wants to have it done this way, please contact your next level of support for further steps.

Applies to

  • Microsoft Windows Server 2003
  • Microsoft Windows Server 2008
  • TC/LP – All supported – (article based on 2.34.00)

Keywords: SMTP.MAPMAP FileError 605