Skip to main content
Kofax

SMTP Automatic reply

Summary

3579

Description

Setting up a SMTP auto reply service for TC/LINK-SM in 7 Steps:

  1. Configure Null-TUM Channel:

    This is done by starting the WCONFIG program with commandline option '–a'
    e.g.: "C:\MT\78601\WCONFIG.EXE c:\mt\myinst –a" (do not copy-paste this command, type it!)

    Within the HW/SW assignment you have to select: NU NULL channel
    (1 channel > T for TCTI instead of using any LAN Link)

  2. Change following configlines within the NULL TUM channel:

Configline 2:     R                         a new, unused channelgroup
Configline 6:  Autoreply channel Email comment within the line statistics
Configline 24:    2                        Automatic distribution for sending copies
Configline 41:    30330                Default termination for sendorders created
Configline 42: noreply:                 Default originator for sendorders created

  1. Create a Mask +MAIL5V/A+3
    Remove any leading ---A4--- lines within the mask and select “No Cover” within the send options. It is important, that the line “Originator: $O1070$;”, which is used for creating the reply send order, is listed within the first 15 lines of the mask document. Optionally the mask can contain the mask variable $B$, it is filled with the username specified within brackets (see step 6.) SMLinkDomain should be replaced by the Mail domain as it handled by TC/LINK-SM (configured within the registry value 'TCLSM\SMLinkDomain')

Example:
Important information:
Originator:
$O1070$;
Receiver: $B$@SMLinkDomain
The email was successfully delivered to $B$@SMLinkDomain Please wait for our response and do not reply to this email.
This email was automatically generated!

Save this file in the TCfW System folder with the file name "A+3" in the Folder '+MAIL5V'.

  1. Create a distribution Directory +MAIL5V/AVV99

    The important entry within the AVV99 file is the 2nd line. If there already is an existing '+MAIL5V/AVV99', simply add the 2nd line to the existing AVV99. The first line of the AVV99 file, which defines the default recipient if no match is found, should contain only a single comma.

    Originator: \;,\

    If there is no AVV99 file, please remove any leading ---A4--- lines from the new message, choose “No Cover” within the send options and save the file in the TCfW System Folder with the file name "AVV99" in the Folder '+MAIL5V'.

  2. Create a service using the 'A+3' Mask
    The prefix of the service should go to the channel group of the NULL TUM channel configured in step 1. Additionally the mask +3 (created in step 3.) should be used in combination with send switch 'B', which advices the NULL TUM channel to create sending copy files:

Service Name: SMTPNOTI
Service Type: Free format
Description: Autoreply for EMAIL messages
Abilities: Image, Text, restricted
Text Prefix: R:+3B

  1. Create an in-event for the recipient:
    The event can be auto terminating or not, depending on requirements of the customer. Enter a blank number followed by the Username, enclosed in brackets.

Service: SMTPNOTI
Number: (username)

Set the Archive entry to 'Always'

ATTENTION: It is important to use a blank before starting with a bracket "(", the part between brackets should contain the users SMTPIN address and is taken out by the $B$ parameter within the +3 Mask.

  1. Create the originator of the “Noreply” message

Create a new KCS TCOSS user with userID = "noreply" (which we have defined in the config line 42 of the NULL TUM channel). This user should have an INACTIVE TOPCALL address = "NOREPLY" and an ACTIVE SMTP address = "NOREPLY". (the NOREPLY address will be the answering address from the Mailsystem to the end customer.)

1) Address with Service           "SMTP"    (active):       noreply@SMLinkDomain
2) Address with Service           "TOPCALL" (inactive):     noreply

How does it work?

If an incoming SMTP Email message is received, the message is distributed to the user and the event sendorder to service SMTPNOTI (NULLTUM channel) is triggered. This channel generates a new sending copy file ATUxxxx file, which is sent back to the original originator of the inbound e-mail.

The originator of this inbound send order is also service SMTP, for example:

Originator of EMAIL Inbound send order: SMTP,a.a@domain.com

Then the normal SMTP Email inbound routing is done and the message is distributed to a user (based on the entered email address).

When the email reaches the inbox of the user (let’s assume inbox of user AB), the configured IN EVENT using service SMTPNOTI becomes active, which is defined in our case with: Service=SMTPNOTI, Number= (AB)

The originator of this event sendorder is the user for whom the event was defined (user AB:), appending the original originator (email address of original sender). The service prefix for the original originator SMTP is replaced by the queue defined for this Service SMTP (TCLSMQI:a.a@domain.com) so for the example above we get following Originator:

Originator of the Event send order: AB :TCLSMQI:a.a@domain.com

The recipient of this event send order is built according to the definition within the event, so when resolving the service prefix for the service SMTPNOTI, the recipient of the event sendorder will be:

Recipient of the Event send order: R :+3B (AB)

The channel group R is polled by the NULL TUM channel.

This send order uses mask +3, where the mask variable is included:

$O1070$ will remove the AB : part from the originator (see above)

$B$ will extract that part of the number which is specified with brackets (AB):

So the message as it is received on the NULL TUM channel looks like:

Important information:
Originator:
TCLSMQI:a.a@domain.com ;
Receiver: AB@SMLinkDomain
The email was successfully delivered to AB@SMLinkDomain! Please wait for our response and do not reply to this email.
This email was automatically generated!

Because of using the NULL TUM send switch B, the NULL TUM channel will create a sending copy document, which looks exactly the same as the message shown above (the sending copy is an exact copy of the message as it is received on the NULL TUM channel). The file name of this sending copy document is '+MAIL5V/ATUxxxx'.

Because of configuring config line 24 of the NULL TUM channel to value 2, there will be automatic distribution of this generated sending copy document, that means TCOSS will search the VV99 table for matching entries and will generate a sendorder, if it finds a matching entry:

In our case, TCOSS will find a match on the 2nd line of the VV99 table.

This 2nd line of the VV99 table uses a search string with variables, which is marked within the VV99 entry with a backslash character: 

Originator: \;,\

So TCOSS searches through the content of the sending copy document, if it finds a string, which starts with Originator: (do not forget the blank after Originator: ) and ends with a semicolon character.

The string parts placed in-between these “begin-” and “endmarks” is represented by the backslash character:

Originator: \;

Originator: TCLSMQI:a.a@domain.com ;

Similar as in the rr99, the backslash character can be used on the right side of the VV99 entry, where the sendorder for this match is defined. The comma after the semicolon character is the separator between search string and send order definition, so in our case the TCOSS will create a send order for the sending copy document going to:

TCLSMQI:a.a@domain.com

which is in fact the originator of the original email inbound send order. The originator for this sending copy send order is taken from configline 42 of the NULL TUM channel, the termination of this sending copy send order is taken from configline 41 of the NULL TUM channel.

So the originator of this event send order is 'noreply:'. As this noreply: user has defined only one active SMTP address, this SMTP address (noreply@SMLinkdomain) will show up as originator of the reply email message.

Recipient of sending copy sendorder: a.a@domain.com

Applies to

  • Microsoft Windows (32bit and 64bit).
  • TC/SP, TC/LP, TC/CP – all supported versions.

Keywords: SMTPAutoreply, auto, reply, automaticNoreply

  • Was this article helpful?