4.2

Interactive Processing Mode (SMTP two-way)
4.2.1 Outline of interactive processing mode (SMTP two-way)This processing mode is the processing mode to be used to send a message immediately after amessage for the user system is generated at NACCS Center server. Therefore, this processing
mode provides faster response comparing to e-mail style processing mode (Gateway). Since
NACCS center server sends messages to user systems in real time, it is required that each user
system has to be online all the time, and has to achieve high availability.
In addition, due to the fact that the protocol used when retrieving processing result messages isdifferent, this processing mode is not a processing mode which computers connected to the user
system can use as is, so in order to carry out EDI with the NACCS Center server using the software
package (e-mail style processing mode) installed on computers connected to the user system, it isnecessary that the user system is carefully configured.
The interactive processing mode (SMTP two-way) can be implemented only on environments wherea dedicated SMTP server is installed on the user side and connected with a leased line or opticalbroadband networks.
Figure 4.2.1 shows outline of the interactive processing mode (SMTP two-way) implemented in
NACCS. In addition, for e-mail sending, refer to "4.6.1 e-mail".

1) SMTPSMTP Header

NACCS EDI
Message

NACCS EDI Message(Transmitted one by one)

User's SMTP
server2) SMTPNACCS
SMTP Header

User system

NACCS EDI Message

NACCS's SMTP
Two-Way Server

Core processing

NACCS EDI
Message

NACCS Center server

Figure 4.2.1 Process outline of the interactive processing mode (SMTP two-way)
1) A user creates and sends a NACCS EDI message that contains the necessary data
segments for a transaction from the user’s SMTP server to the NACCS's SMTP Two-Way
Server over SMTP protocol.
2) The message transmitted to the NACCS's SMTP Two-Way Server is transferred to the Core
processing system. The message is processed and a response message is sent to the
NACCS's SMTP Two-Way Server once again. The NACCS's SMTP Two-Way Server sends
the processing result message to the user’s SMTP server. Therefore, the user’s SMTP server
should always be activated.
4-2-1

4.2.2

Interface that users should follow

Users are required to comply with a certain interface in the interactive processing mode. Throughthis interface, a user sends a processing request message originating from the user’s e-mailaddress to the NACCS Center server. And the user must receive all processing result messages (aprocessing result notification message or an output information message) for the request before
sending the next transaction request.
More specifically, the user sends a processing request message with a unique input message ID to
the NACCS Center server. When the user receives all processing result messages corresponded tothe processing request message (processing result notification message or output message) from
NACCS Center server, the user checks that "the input message ID is the same value as specified in
the corresponding request message", and send a subsequent transaction request message.
(Note 1) Value forwarding from a processing request message to its processing result message(background information of the above procedure)
Table 4.2.1 shows patterns of generating processing result messages which are output to the user
system after a processing request message is sent from the user system to NACCS Center server
and is processed at NACCS Center server. In all the patterns, a value specified in Input Message ID
element in a request message is carried over to a processing result notification message or an
output information message.
(See Table 3-5-2 "Correspondence of Input Message ID and Message Tag" for details on Input
Message ID)
Table 4-2-1 Value forwarding from a transaction request message to its processing result message
Processing result message
Pattern

1

2

3

Message Type
Processing
result notification
message
Processing
result notification
messageOccurrence of
Input Message ID
Value Forwarding

[R]

○

[R]

○

OutputInformation
Message[C] or[P], [A][C]: ○[P], [A]: △ (*1)

OutputInformation
Message[R] or [M]○Remarks

Input Information ID in the processing
result notification [R] is verified forcorrespondence check.
*1 Because EXC type output
information message [P] and [A] do not
forward Input Information ID (withexceptions in some kinds of output
information message), Input Information
ID in the Processing Result Notification[R] is verified for correspondence
check.
Because processing result notification
messages are not generated in thequery process, Input Information ID in
the output information message isverified for the correspondence check.

(Note 2) Implication in "3.5.3 Continued processing (Index tag)"
When executing a transaction for continued processing, the user system needs to implement an
extra mechanism for continued processing in addition to the interface in the interactive processing
mode, because in continued processing a value specified in Message Tag in the output information
message sent from the NACCS Center server needs to be carried over to the next transaction
request at the user system without any change.
See "3.5.3 Continued processing (Index Tag)" and Appendix Table 6.8 "Output information code
List: continued processing" for details.

4-2-2

Figure 4.2.2 shows an image of the interface of the Interactive Processing Mode (SMTP two-way).

(1)*

Processing Request Message(* is Input Message ID)

Verified in pattern 1
or 2

Transaction iscompleted
Because one of the messages isalways sent from the center
server in response to the request
message (1), confirm that the
input message ID in one of themessages is identical to the ID
specified in the request.

(1)' Processing Result Notification Message [R]*INQ Typeor(1)' Output Information Message [M] or [R]*Verified inpattern 3
From here, the next request message can be sent

The next request
message can be
sent

(2)

Transaction Request Message ◇(◇ is Input Message ID)

INQ Type(1)' Output Information Message (Screen) [C]Depending on contents of therequest message (1), these typesof message may be generated.
(occasional transmission)*(1)' Output Information Message (Printer) [P], [A] *(1)' Output Information Message (Printer) [P], [A] △INQ Type or EXZ
Type

EXC Type(△ is a space)

Processing result messages
sent in response to a third
party event do not depend on
the interface. (occasionaltransmission)

Output Information Message (Printer) [P], [A]△EXC Type★

(△ is a space)
Send a message in
response to a third
party event

NACCS Center server

User system* Refer to Table 4.2.1 the patterns "pattern 1" through "pattern 3" described in the figure.
* Refer to "3.5 Message Control Items" for information output in Input Message ID.
Figure 4.2.2 Example Usage of the Interface of the Interactive Processing Mode (SMTP Two-Way)

4-2-3

4.2.3

Details of the communications protocol

In the NACCS interactive processing mode (SMTP two-way), TCP/IP on the network andtransport layers and SMTP on the upper layers are used as communications protocols.
(1) SMTP specifications when sending a processing request message on SMTP
(A) Applicable SMTP commands
SMTP commands which can be used when sending a processing request message to the
NACCS Center server in the interactive processing mode (SMTP two-way) are listed in Table
4.2.2.
Table 4.2.2 SMTP Command List (When the Processing Request Message is sent)
Response from NACCS’s
Command
OutlineParameter
SMTP Two-Way Server touser’s SMTP server(Normal response)
HELO
To declare use of theSender host name 250
communications channel (Domain name)and identify the hostMAIL
To start the mailing
FROM: Sender
250
transaction
name
RCPT
To specify the receiver of TO: Receiver user 250
the mailname
DATA
To start sending the mail Message data
354
body
RSET
To stop sending the mail None250
QUIT
To close the connection
None
221

4-2-4

(B)

Command sequence in Transmission of Processing Request Message over SMTP

Figure 4.2.3 shows a sequence of SMTP commands issued during transmission of atransaction request message from a user’s SMTP server to the NACCS’s SMTP Two-Way
Server. In addition, Table 4.2.3 shows description of each command.
Request to open a connection (TCP Port 25)
Normal response (220)

Identify the client host
HELO ZZZZZ.ABC01.NACCS.CUSTOMSNormal response (250)

To start the mailing transaction
MAIL FROM:AAXXXX@ZZZZZ.ABC01.NACCS.CUSTOMSNormal response (250)
To specify the receiver of the mail
RCPT TO:NACCS@SMTP.MAIN.NACCS.CUSTOMSNormal response (250)

User’s SMTP
ServerStart sending the mail body (processing request message)
DATA
Normal response (354)

NACCS’s
SMTP Two-Way
ServerSend line by line (Maximum 1000 byte per line)••• Send line by line
. CRLF
Normal response (250)

To close the connection
QUIT
Normal response (221)

Request to close the connection

NACCS Center
serverUser system

Figure 4.2.3 SMTP Command Sequence on Transmission of a Transaction Request Message(Note) A user of the interactive processing mode (SMTP two-way) needs to issue a QUIT
command after completing transmission of the entire message text when sending
processing request messages. If the user’s SMTP server does not issue a QUIT
command within one hour after the completion of a message transmission, the NACCS’s
SMTP Two-Way server declares a connection timeout and closes the current connection
by force.

4-2-5

Table 4.2.3 SMTP Command List (When the Processing Request Message is sent)
Item
CommandNo.
1
Request to open aconnection

2

HELO Domain name

3

MAIL FROM: Mail address

4

RCPT TO: Mail address

5

DATA

6

Send mail body

Description
User’s SMTP server requests to open a connection toward port
number 25 of NACCS’s SMTP Two-Way Server.
NACCS’s SMTP Two-Way Server sends back the response
code 220 as a normal response.
NACCS center notifies the IP address of NACCS’s SMTP TwoWay Server in advance.
User’s SMTP server specifies domain name of user andexecutes the command. If the server can be used, NACCS’s
SMTP Two-Way Server will open a connection.
NACCS’s SMTP Two-Way Server sends back the response
code 250 as a normal response.
NACCS center notifies user’s domain name in advance.
User’s SMTP server specifies user’s mail address andexecutes the commands.
NACCS’s SMTP Two-Way Server sends back the response
code 250 as a normal response.
NACCS center notifies user’s mail address in advance.
User’s SMTP server specifies NACCS Center server's mailaddress (NACCS@SMTP.PROD.NACCS6) and executes thecommand.
NACCS’s SMTP Two-Way Server sends back the response
code 250 as a normal response.
User’s SMTP server executes starting command to send
processing request message.
NACCS’s SMTP Two-Way Server sends back the response
code 354 as a normal response.
After that, user’s SMTP server can send the message(including communications protocol header).
User’s SMTP server sends processing request message
following NACCS procedure specification. At the end edge of aprocessing request message, only the line with dot (.) can be
sent.
After receiving the end edge, NACCS’s SMTP Two-Way Server
sends back the response code 250 as a normal response.
(Note 1) When sending a processing request message,
because the mapping of the processing result message isneeded, it is necessary to refer to "4.2.2: Interface of theinteractive processing mode that users should follow".
(Note 2) It is necessary to make a line <CRLF> after each
1,000 bytes, but because in NACCS EDI specification, a
new line <CRLF> will be made within 1,000 bytes, it is notnecessary for the user to be aware of it.
(Note 3) In SMTP, because the end edge of a message isrecognized with <CRLF>.<CRLF>, if there is a line in which"." is placed in front in the middle of the message, user’s
SMTP server will add a dummy "." in front. In NACCS’s
SMTP Two-Way Server, the dummy "." will be deleted anddelivered to the Core processing system.

4-2-6

Item
No.
7
RSET

8

QUIT

Command

Description
If user executes this command, it will return to the status after
HELO.
NACCS’s SMTP Two-Way Server sends back the response
code 250 as a normal response.
(Normally, it is not necessary to execute this command).
User’s SMTP server closes the SMTP connection.
NACCS’s SMTP Two-Way Server sends back the response
code 221 as a normal response.

(Note 1) Response code of SMTP
There are optional characters behind 3 digits of each response code, but only refer tothese 3 first digits.
Example: Response of HELO
250 SMTP.PROD.NACCS6
Only refer to the response code and carry out the settlement methods described in the
Table 4.2.4.
* Reason: Because rear characters can be changed depending on Specification changes
in the NACCS center server.
(Note 2) Timeout observation
Observe timeout of SMTP connection so that user’s SMTP server can detect the failure of
NACCS’s SMTP Two-Way Server and network.
In this specification, more than one message can be sent in one connection, and as thetimeout period of SMTP connection cannot be prescribed, the monitoring time must be
decided based on operation methods applied by user.

4-2-7

(C) Settlement in abnormal cases
Settlement methods in case if an error occurs when sending SMTP are described in the Table
4.2.4.

Item
No.
1

Command
Request to
open aconnection

2

HELO

3

MAIL FROM

Table 4.2.4 Settlement methods for sequential errors of SMTP
Estimated errors and settlement methods
NACCS’s SMTP Two-Way Server sends a request to open a connection,
however, the request is not accepted.
Reasons and settlement methods:• The destination IP address is faulty.
→ Determine if it is connected to the IP address of NACCS’s SMTP TwoWay Server which NACCS Center has notified or not.
• The destination port number is faulty.
→ Determine if a request is sent to open a connection to port number 25 ornot.
• The NACCS Center server is under maintenance.
→ Information about maintenance of the NACCS Center server is announced
to the public on NACCS Information, so that should be checked. If the center
is under maintenance, re-send the request to open a connection after the
maintenance work is finished.
• The NACCS Center server or network is damaged.
→ Re-send another request to open a connection after a while. If it is notrecovered for a long time, send an investigation request to the Help desk of
NACCS Center.
The information on damages is also updated on the NACCS Information.
The information on the server's maintenance or damages used for connection
test will not be notified on the NACCS Information, if the server cannot be
connected even in the time when the connection test is done, confirm thesituation with NACCS Center.
Errors in response (except for normal responses (250)) are returned.
Reasons and settlement methods:
1. For syntax error (500)→ Confirm that the character string for sending the HELO command iscorrect.
2. For command sequences error (503).
→ Execute the command with the right sequences described in the Figure
4.2.3.
Timeout due to no response from NACCS’s SMTP Two-Way Server.
Reasons and settlement methods:
As damages may be occurring, cut off the connection for a while and re-send
the request for a connection.
Errors in response (except for normal responses (250)) are returned.
Reasons and settlement methods:
1. For syntax error (500) or parameter error (501) or domain name error (553).
→Confirm that the character string for sending MAIL command is correct.
2. For command sequences error (503).
→ Execute the command with the right sequences described in the Figure
4.2.3.
Timeout due to no response from NACCS’s SMTP Two-Way Server.
Reasons and settlement methods:
As damages may be occurring, cut off the connection for a while and re-send
the request for a connection.

4-2-8

Item
No.
4

Command

Estimated errors and settlement methods

RCPT TO

Errors in response (except for normal responses (250)) are returned.
Reasons and settlement methods:
1. For syntax error (500) or parameter error (501) or domain name error (553).
→ Confirm if the character string of sending RCPT command is right or not.
2. For command sequences error (503).
→ Execute the command with the right sequences described in the Figure
4.2.3.
Timeout due to no response from NACCS’s SMTP Two-Way Server.
Reasons and settlement methods:
As damages may be occurring, cut off the connection for a while and re-send
the request for a connection.

5

DATA

Errors in response (except for normal responses (354)) are returned.
Reasons and settlement methods:
1. For syntax error (500)→ Confirm that character string of sending DATA command is correct.
2. For command sequences error (503).
→ Execute the command with the right sequences described in the Figure
4.2.3.
Timeout due to no response from NACCS’s SMTP Two-Way Server.
Reasons and settlement methods:
As damages may be occurring, cut off the connection for a while and re-send
the request for a connection.

6

Send
processing
requestmessage

7

RSET

Errors occur during communication.
Reasons and settlement methods:
As NACCS’s SMTP Two-Way Server can be damaged, re-send the request
after a short interval. If it is not recovered for a long time, send an investigation
request to the Help desk of NACCS Center.
Errors in response (except for normal responses (250)) are returned.
Reasons and settlement methods:
For syntax error (500)→ Confirm that character string of sending RSET command is correct.
Timeout due to no response from NACCS’s SMTP Two-Way Server.
Reasons and settlement methods:
As damages may be occurring, cut off the connection for a while and re-send
the request for a connection.

8

QUIT

9

OthersErrors in response (except for normal responses (221)) are returned.
Reasons and settlement methods:
For syntax error (500)→ Confirm that the character string of sending QUIT command is correct.
Detect abnormalities during communication.
Reasons and settlement methods:
As damages may be occurring, re-send the request to open a connection.

4-2-9

(2) SMTP specifications when receiving a processing result message on SMTP
(A) Applicable SMTP commands
Table 4.2.5 shows SMTP commands used by the NACCS’s SMTP Two-Way Server andresponses sent by the user’s SMTP server in the interactive processing mode (SMTP two-way).
Table 4-2-5 SMTP Command List (When the Processing Request Message is received)
Command
OutlineParameter
Response from user’s SMTP
server to NACCS’s
SMTP Two-Way Server(Normal response)
HELO
To declare use of theSender host name 250
communications channel (Domain name)and identify the hostMAIL
To start the mailing
FROM: Sender
250
transaction
name
RCPT
To specify the receiver of TO: Receiver user 250
the mailname
DATA
To start sending the mail Message data
354
body
RSET
To stop sending the mail None250
QUIT
To close the connection
None
221

4-2-10(B) SMTP command sequence for receiving a processing result message
Figure 4.2.4 shows a sequence of SMTP commands issued during transmission of a processing
result message from the NACCS’s SMTP Two-Way Server to a user’s SMTP server. Table
4.2.6 shows description of each command.
Request to open a connection (TCP Port 25)
Normal response (220)
Identify the client host
HELO SMTP.MAIN.NACCS.CUSTOMSNormal response (250)
To start the mailing transaction
MAIL FROM:NACCS@SMTP.MAIN.NACCS.CUSTOMSNormal response (250)
Designate the mail receiver
RCPT TO:AAXXXX@ZZZZZ.ABC01.NACCS.CUSTOMSNormal response (250)

SMTP User
パッケージソフト
Server（ゲートウェイ
サーバー）

Start sending the mail body (processing result message)
DATA
Normal response (354)

メールサー
SMTPバー
Two-Way
Center Server

Send line by line (Maximum 1000 byte per line)••• Send line by line
. CRLF
Normal response (250)
To close the connection
QUIT
Normal response (221)

Request to close the connection

NACCS Center
serverUser system

Figure 4.2.4 SMTP Command Sequence on Transmission of a Processing Result Message

When receiving a processing result message, the NACCS’s SMTP Two-Way Server always
issues a QUIT command to close the current connection after completing the transmission of amessage to a user system. Only one message is transmitted during one connection.

4-2-11

Item
No.
1

Table 4.2.6 Description about Command when Receiving SMTP
Command
Description
Request to open aconnection

2

HELO Domain name

3

MAIL FROM: Mail address

4

RCPT TO: Mail address

5

DATA

6

Send processing result
message

7

RSET

8

QUIT

NACCS’s SMTP Two-Way Server sends request to
open a connection toward port number 25 of user’s
SMTP server.
User’s SMTP server sends back the response code
220 as a normal response.
NACCS’s SMTP Two-Way Server specifies domainname as "SMTP.PROD.NACCS6" and executes thecommand. If the server can be used, the user’s SMTP
server will open a connection and send back the
response code 250 as a normal response.
NACCS’s SMTP Two-Way Server specifies center's
mail address (NACCS@SMTP.PROD.NACCS6) and
executes the command.
User’s SMTP server sends back the response code
250 as a normal response.
NACCS’s SMTP Two-Way Server specifies users' mailaddresses and executes their commands.
User’s SMTP server sends back the response code
250 as a normal response.
NACCS’s SMTP Two-Way Server executes a starting
command to send processing result messages.
User’s SMTP server sends back the response code
354 as a normal response.
After that, NACCS’s SMTP Two-Way Server sends themessage (including communications protocol header).
NACCS’s SMTP Two-Way Server sends processing
result messages following NACCS procedure
specification.
After receiving the end edge, User’s SMTP server
sends back the response code 250 as a normal
response.
(Note) In SMTP, as the end edge of a message isrecognized with <CRLF>.<CRLF>, if there is a line with
only ".", NACCS’s SMTP Two-Way Server will add adummy “.” in front of it. In User’s SMTP server, thedummy "." will be deleted and delivered to the Main
processor.
If the NACCS’s SMTP Two-Way Server executes thiscommand, it will return to the status after HELO. User’s
SMTP server sends back the response code 250 as anormal response.
(Normally, it is not necessary to execute this command)
NACCS’s SMTP Two-Way Server closes the SMTP
connection.
User’s SMTP server sends back the response code
221 as a normal response.

(Note 1) Timeout observation
Observe timeout from sending request to open a connection until QUIT command is finishedso that NACCS’s SMTP Two-Way Server can detect the failures of user’s SMTP server andnetwork. If the QUIT command is not finished in 3 minutes after request to open aconnection has been sent, NACCS’s SMTP Two-Way Server will recognize it as a timeout.

4-2-12

(C) Settlement in abnormal cases
If NACCS’s SMTP Two-Way Server recognizes interferences such as unavailability of request
to open a connection, errors of SMTP sequence or timeout, messages except for transaction
output for printer will not be guaranteed.
If a transaction output for the printer cannot be sent normally, NACCS’s SMTP Two-Way Server
will store that transaction output in the Error message queue of the output message cache in
the Center. The messages stored in the Error message queue can be retrieved if the user
carries out the Error message retrieving procedure (SYG).
(Note) The Error message retrieving procedure (SYG), and guaranteed message type, etc. ismentioned in "3.7 Output message cache and retrieving procedure".

4-2-13

4.2.4

Message format

In the interactive processing mode (SMTP two-way), a communications protocol header and a
trailer are added to a NACCS EDI message, an attachment file transmission message or a XML
format message.
The message formats are outlined as follows:(1) NACCS EDI message
Figure 4.2.5 shows outline of NACCS EDI message format (interactive processing mode
(SMTP two-way)).

NACCS EDI message
Communications
Protocol Header(SMTP Header)

Input (Output)
Common Field

Procedure-By-Procedure
Field

Communications
Protocol Trailer(SMTP Trailer)

Max. 700,000 bytes (Note)(Refer to "3 Message structure and format")・ ・ ・ ・ ・ ・ ・Subject(Refer to "4.2.4 (4) Contents of the SMTP header (A) NACCS EDI message")(Refer to "4.2.4(5) Contents of Subject field of the SMTP header")Figure 4.2.5 Outline of NACCS EDI Message Format (Interactive Processing Mode (SMTP Two-Way))(Note) Refer to "3.1.2 NACCS EDI message format Table 3.1.1" for the maximum allowable
message size transmitted among relevant ministers’ system.

Figure 4.2.6 shows a layout of a NACCS EDI message sent to the NACCS center server
from a user in the interactive processing mode (SMTP two-way).
(1) A NACCS EDI message body comes after the "<CRLF>" code placed after the SMTP
header.
(2) "." (Period) and "<CRLF>" are placed after the NACCS EDI message body, as
communications protocol trailer.

4-2-14

Procedure-By-Procedure Field

LF

LF

.

CR

LF

…

CR

LF

…

CR

…

LF

CR

LF

…

CR

LF

CR

CR

Communications
Protocol Trailer(SMTP)NACCS EDI message
Input common
fieldContentTransferEncoding:
8bit

LF

ContentType:Text/plain;charset="EUC-JP"

CR

LF

CR

MimeVersion:1.0

LF

CR

To:
……

LF

From:
……

CR

Communications Protocol Header(SMTP)

Figure 4.2.6 Message Layout
Note: The following figure shows segments of a message displayed on text editor tools, etc.
From:XXXXXXXX...XXX<CRLF>
To:XXXXXXXX...XXX<CRLF>
Mime-Version:1.0<CRLF>

Communications protocol header(SMTP header)Content-Type:Text/plain;charset="EUC-JP"<CRLF>
Content-Transfer-Encoding:8bit<CRLF><CRLF>XXXXXXXXXXX.....XXX<CRLF>
XXXX...XXX<CRLF>
XXXX...XXX<CRLF>
XXXX...XXX<CRLF>.<CRLF>

Input common field
Procedure-by-procedure field

NACCS EDI
messageCommunications protocol trailer(SMTP trailer)(Note) Appearance of <CRLF> may be different depending on text editors, etc.

! Communications protocol trailer
In SMTP, a line containing ". <CRLF>" (a period line) is added to the end of the massage.
Termination of the message is recognized by the sequence of "<CRLF>. <CRLF>", whichis the combination of "<CRLF>", placed at the last message body and this additional
period line.
! How to distinguish between communications protocol trailer and "." (dot)"." is communications protocol trailer which describes the end edge of the response. In
SMTP, the end edge of a message is recognized with <CRLF>.<CRLF>. If there is amessage in which "." is placed in front of the line, in order to distinguish with thecommunications protocol trailer, the Center will add "." (Byte stuff) in front of the line andsend it back to user. In case if the arrival response message has a "." in front of the line
and the next character string is not <CRLF>, user will delete "." (Byte stuffing) in front of
the line. Failure to delete byte stuff causes errors such as messages containing an
additional unwanted "." (dot) and messages with an extra byte at the user’s system.

4-2-15

(2) Attachment file transmission message
Figure 4.2.7 shows outline of attachment file transmission message (interactive processing
mode (SMTP two-way)).
Refer to "4.6.2 Attachment file" for attachment files available for NACCS.

Attachment file transmission message
Communications
Protocol Header(SMTP Header)

NACCS EDI message(attached file registration
procedure, etc.)

Attachmentdata 1・・・

Attachmentdata nCommunications
Protocol Trailer(SMTP Trailer)

Max. 10,000,000 bytes (Note)(Refer to "3 Message structure and format")(Refer to "4.2.4 (4) Content of the SMTP header (B) attachment file transmission message")

Figure 4.2.7 Outline of Attachment File Transmission Message Format (Interactive Processing Mode
(SMTP Two-Way))(Note)

Refer to "3.1.2 NACCS EDI message format Table 3.1.1" for maximum allowableattachment data size transmitted among relevant ministers’ system.

Figure 4.2.8 shows a layout of an attachment file transmission message sent to NACCS center
server from a user in the interactive processing mode (SMTP two-way).
(1) Filing method
In NACCS, BASE64 of MIME (Multipurpose Internet Mail Extensions) is used when sending
and receiving the message. Attachment file transmission message is stored in the attachedfile format.
Details of regulations when sending and receiving the attachment file transmission message
is as follows.
• MIME version is 1.0.
• The Content-type of the SMTP header is Multipart/mixed, the Content-type of the
NACCS message is Text/plain, the Content-type of the attached file is specified
according to each attached file.
• The Content-Transfer-Encoding of the attached file is appointed as BASE64.
• NACCS EDI message can't be abbreviated. In addition, the attached file needs to beplaced behind the NACCS EDI message.
• In Content-Disposition, specify the "attachment" and specify the file's name in"filename".
(2) Image of message• The attachment file transmission message is structured with a communications protocolheader, and a message and communications protocol trailer.
• NACCS EDI message, attached file's body encoded with BASE64 comes after the<CRLF> code placed after SMTP header.
• <CRLF>, "."(period), and <CRLF> are placed after the attachment file transmission
message as the communications protocol trailer.
4-2-16

LF
LF

LF

LF

LF

CR

CR
CR

ContentDisposition:
attachment;
filename="file name"

CR

LF

LF

Refer to
NACCS
EDI
message

CR

CR

CR

Content-Type:multipart/mixed;boundary="YYYYYY"

LF

LF

MimeVersion:1.0

CR

LF

CR

To:
XXXX

LF

From:
XXXXX

CR

Communications Protocol Header(SMTP header)

Body

LF

ContentTransferEncoding:
8bit (Note)

CR

LF

ContentType:Text/plain;charset="EUC-JP"

Text

CR

LF

YYY
YYY

CR

- (hyphen)- (hyphen)

Text

Body

Body

LF

．

CR

LF

- (hyphen)- (hyphen)- (hyphen)- (hyphen)

LF

CR

YYY
YYY

CR

Communications
protocol trailer (SMTP)

Attachment file

Attachment file
Body

CR

ContentTransferEncoding:
BASE64LF

Content-Type: "Basing on
attached file";
name="file name"

CR

LF

YYY
YYY

CR

- (hyphen)- (hyphen)

Attachment file

(Note) Setting point of this item is based on email software. "8 bit" is just an example.

Figure 4.2.8 Example of Attachment File Transmission Message Structure

4-2-17

Note:
Text presentation of the above contents on text editor tools, etc. is described as follow.
From:XXXXX…XXX<CRLF>
To:XXXXX…XXX<CRLF>
Mime-Version:1.0<CRLF>
Content-Type:multipart/mixed; boundary="YYYYYY"<CRLF><CRLF>--YYYYYY<CRLF>
Content-Type:Text/plain; charset="EUC-JP"<CRLF>
Content-Transfer-Encoding:8bit<CRLF><CRLF>XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX…XXX

Communications protocolheader(SMTP header)<CRLF> NACCS EDI message<CRLF>--YYYYYY<CRLF>
Content-Type: "Basing on attached file"; name="file name"<CRLF>
Content-Transfer-Encoding:BASE64<CRLF>
Content-Disposition: attachment; filename="file name"<CRLF><CRLF>ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ…ZZ<CRLF>--YYYYYY-<CRLF>.<CRLF>

Repeatable

Attached file's bodyCommunications protocol
trailer(SMTP trailer)

4-2-18(3)XML format message

Figure 4.2.9 shows outline of XML format message format (interactive processing mode (SMTP
two-way)).

XML format message
Communications
Protocol Header

XML message(SMTP Header)Communications
Protocol Trailer(SMTP Trailer)

Max. 700,000 bytes(Refer to "3 Message structure and format")(Refer to "4.2.4 (4) Contents of the SMTP header (C) XML format")

Figure 4.2.9 XML Format Message (Interactive Processing Mode (SMTP Two-Way))Lay out of an XML format message sent to NACCS Center server from a user in the interactive
processing mode is described as follow.
(1) An XML format message body comes after the "<CRLF>" code placed after the SMTP
header.
(2) <CRLF>, "." (period) and <CRLF> are placed after the XML format message ascommunications protocol trailer.
(3) Make a new line after each 1,000 bytes. If not, an error will occur.
(4) <CRLF> exists in each line of XML message.
(5) Character code of XML message is EUC-JP, EUC-JP must be recorded in encoding field of
XML header.
For details of XML format message structure which user sends to NACCS center sever ininteractive processing mode (SMTP two-way), refer to Appendix 15 and ProcedureSpecifications.

4-2-19

Note:
Text presentation of the above contents on text editor tools, etc. is described as follow.
From:XXXXX…XXX<CRLF>
To:XXXXX…XXX<CRLF>
Mime-Version:1.0<CRLF>
Content-Type:Text/xml; charset="EUC-JP"<CRLF>
Content-Transfer-Encoding:8bit<CRLF><CRLF>

Communications protocolheader(SMTP header)<?xml version="1.0" encoding="EUC-JP" standalone="no" ?>• <RootElement>• <Header>• <DocumentType><DocumentTypeCode>XXX</DocumentTypeCode><DocumentTypeDescription>XX…XXX</DocumentTypeDescription></DocumentType>• <DocumentIdentification><MessageFunction> XX…XXX </MessageFunction><MessageTransferSequenceNo>XX</MessageTransferSequenceNo></DocumentIdentification><SenderID> XX…XXX </SenderID></Header>- <Body>•* XML message•
Refer to Appendix 15 and Procedure•Specifications for more details.
•• <AdditionalInformation><InformationType> XX…XXX </InformationType></AdditionalInformation></Body></RootElement><CRLF>.<CRLF>

Communications protocol
trailer(SMTP trailer)

4-2-20(4) Contents of the SMTP header(A) NACCS EDI message
Contents of the SMTP header included in processing requests or processing result messages
are as follows.
(1) Processing request message
Table 4.2.7 shows the contents of the SMTP header in a processing request message sentfrom a user.
Table 4.2.7 SMTP header (processing request message)
Item
No.

Item

Contents specified by the user
The sender of the mail.
In NACCS a source (user) e-mail address assigned by NACCS Center is
specified.
If no address is specified, an error occurs.
(See "4.2.4 (6) E-mail address used in the interactive processing mode
(SMTP two-way)")
The receiver of the mail.
In NACCS the NACCS Center server's e-mail address allocated for theinteractive processing mode (SMTP two-way) is specified.
(See "4.2.4 (6) E-mail address used in the interactive processing mode
(SMTP two-way)")
In NACCS 1.0 is specified.
Text/plain;charset="EUC-JP" is specified.
In NACCS characters are treated as EUC characters.
8bit is specified.

1

From

2

To

3
4

MIME-version
Content-Type
Content-TransferEncoding

5(2) Processing result message
Table 4.2.8 shows contents of the SMTP header in a processing result message (processing
result notification message and output information message) sent from NACCS to a user.
Table 4-2-8 SMTP header (processing result message)
Item
No.

Item

Contents specified by the SMTP two-way NACCS center server
The sender of the mail.
In NACCS, the NACCS Center server's e-mail address allocated for theinteractive processing mode (SMTP two-way) is specified.
(See "4.2.4 (6) E-mail address used in the interactive processing mode
(SMTP two-way)")
The receiver of the mail.
In NACCS user’s e-mail address used to store processing result
messages is specified.
(See "4.2.4 (6) E-mail address used in the interactive processing mode
(SMTP two-way)")
The date the message is sent to the receiver is specified.
(See "4.2.4 (5) Contents of Subject field of the SMTP header")In NACCS 1.0 is specified.
Text/plain;charset="EUC-JP" is specified.
In NACCS characters are treated as EUC characters.
8bit is specified.

1

From

2

To

3
4
5
6

Date
Subject
MIME-version
Content-Type
Content-TransferEncoding

7

4-2-21

(B) Attachment file transmission message
Contents of the SMTP header included in processing request message and processing result
message are as follows.
(1) Processing request message
Table 4.2.9 shows contents of the SMTP header in a processing request message sent from auser.
Table 4.2.9 SMTP Header (Processing Request Message)
Item
No.

Item

1

From

2

To

3
4
5

6

MIME-version
Content-Type
ContentTransferEncoding
ContentDisposition

Contents specified by the user
The sender of the mail.
In NACCS, a source (user) e-mail address assigned by NACCS center is
specified. If no address is specified, error will occur.
(See "4.2.4 (6) E-mail address used in the interactive processing mode
(SMTP two-way)")
The receiver of the mail.
In NACCS, the NACCS Center server's e-mail address allocated for theinteractive processing mode (SMTP two-way) is specified.
(See "4.2.4 (6) E-mail address used in the interactive processing mode
(SMTP two-way)")
In NACCS 1.0 is specified.
If it is not specified, that e-mail will be omitted.
multipart/mixed; boundary="optional value" is specified as multipart type.
If it is not specified, that e-mail will be omitted.
It is not specified in SMTP header.
8bit is specified in NACCS message and BASE64 is specified in attachedfile.
It is not specified in SMTP header and NACCS message.
Attachment is specified in attached file and "file name" in filename.

(2) Processing result message
For details about contents of the SMTP header in a processing result message sent from
NACCS to a user, refer to "4.2.4 (4) Content of the SMTP header (A) NACCS EDI message –Table 4.2.7" above.

4-2-22

(C) XML format message
Contents of the SMTP header included in processing request message and processing result
message are as follows.
(1) Processing request message
Table 4.2.10 shows contents of the SMTP header in a processing request message sent froma user.

Item

Table 4-2-10 SMTP Header (Processing Request Message)
Contents specified by the user

Item
No.
1

From

2

To

3

MIME-version

4

Content-Type

5

ContentTransferEncoding

The sender of the mail.
In NACCS, a source (user) e-mail address assigned by NACCS center is
specified. If no address is specified, error will occur.
(See "4.2.4 (6) E-mail address used in the interactive processing mode
(SMTP two-way)")
The receiver of the mail.
In NACCS, the NACCS center server's e-mail address allocated for theinteractive processing mode (SMTP two-way) is specified.
(See "4.2.4 (6) E-mail address used in the interactive processing mode
(SMTP two-way)")
In NACCS 1.0 is specified.
If it is not specified, that e-mail will be omitted.
In NACCS, due to using message in EUC, Text/xml; charset="EUC-JP" isspecified.
In NACCS characters are treated as EUC characters.
8bit is specified.

(2) Processing result message
For details about contents of the SMTP header in a processing result message sent from
NACCS to a user, refer to "4.2.4 (4) Content of the SMTP header (A) NACCS EDI message– Table 4.2.7" above.

4-2-23

(5) Contents of the Subject field of the SMTP header
The contents of the Subject field of the SMTP header included in a processing result message
sent from the NACCS center server to a user are as follows.
(1) Contents of Subject field
A common format is used for both processing result notification messages and output
information messages.
Table 4.2.11 shows contents of Subject field.
Table 4.2.11 Contents of Subject Field
Field namelengthProcedureBy-Procedure
Field
Data

64

OutlineFor example, procedure code, processing result code,
declaration number, AWB number are specified.
A one-byte space is used as a data separator.

(2) Remark
Since contents of Subject field are included in a NACCS EDI message body, Subject field is
not specifically useful for users who do not need to handle its contents.
(Subject field can be omitted)

4-2-24

(6) E-mail address used in the interactive processing mode (SMTP two-way)(A) Outline of e-mail address and address allocation guideline
Figure 4.2.10 shows an example e-mail addresses specified in the SMTP headers enclosed inprocessing request and processing result messages. User’s e-mail address is specified in From
field of "1) processing request message" and To field of "2) processing result message".
NACCS Center server's e-mail address is specified in the To field of "1) processing request
message" and the From field of "2) processing result message."

From field of the SMTP header isverified

1) From: AXXXX@ZZZZZ.ABC01.NACCS.CUSTOMS
To: NACCS@SMTP.MAIN.NACCS.CUSTOMSSMTP Header

User's SMTP
ServerSMTP Header

NACCS EDI
Message

NACCS EDI Message

NACCS EDI Message

NACCS’s
SMTP Two-Way
Server

NACCS EDI
MessageCore
Processing
system2) From: NACCS@SMTP.MAIN.NACCS.CUSTOMS
To: AXXXX@ZZZZZ.ABC01.NACCS.CUSTOMS
Date: ・・・・・・・・
Subject: ・・・・・・・・

User system

NACCS Center server

Figure 4.2.10 Usage of E-Mail Addresses in the SMTP Header(B) User e-mail address format
Figure 4.2.11 shows the format of user e-mail addresses used in the interactive processing
mode (SMTP two-way).

AAXXXX@ ZZZZZ.ABC01.NACCS6
E-mail account(Unique 6 digits notoverlapping)

Domain name(See Figure 4.2.14)

Figure 4.2.11 User E-mail Address Format in the Interactive Processing Mode (SMTP Two-Way) (inSingle-Byte Capital Letters)

Since NACCS Center allocates an e-mail address to each user for the interactive processing
mode (SMTP two-way), users are not allowed to choose their own e-mail address.
4-2-25

(C) NACCS Center server e-mail address format
Figure 4.2.12 shows the format of the NACCS center server e-mail address used in theinteractive processing mode (SMTP two-way).

NACCS @ SMTP.PROD.NACCS6

E-mail account(Fixed)(See Figure 4.2.15)

Figure 4.2.12 NACCS Center Server E-Mail Address Format in the Interactive Processing Mode (SMTP
Two-Way) (in Single-Byte Capital Letters)Moreover, the main center and the backup center can be switched by changing the DNS serverdata in NACCS Center. As a result, the user does not need to recognize the NACCS server's
mail address when the backup center is operated.
In addition, Figure 4.2.13 shows examples of NACCS Center server mail addresses when there
is a switch over to the backup center when a disaster, etc. occurs at the main center.

NACCS @ SMTP.PROD.NACCS6

E-mail account(Fixed)Figure 4.2.13 Backup NACCS Center Server E-Mail Address Format in the Interactive Processing Mode
(SMTP Two-Way) (in Single-Byte Capital Letters)(D) User domain name format
The format of user domain names used in the interactive processing mode (SMTP two-way) is
described in Figure 4.2.14.

ZZZZZ.ABC01.NACCS6

User side
SMTP server
Host name(Fixed)User domain name(= "Abbreviated company name (3 letters)" + 2 chrs)

Figure 4.2.14 User Domain Name Format in the Interactive Processing Mode (SMTP Two-Way) (inSingle-Byte Capital Letters)
4-2-26

(E) NACCS Center server domain name
The format of the NACCS Center server domain name used in the interactive processing mode
(SMTP two-way) is described in Figure 4.2.15.

SMTP.PROD.NACCS6

Server name(="SMTP")(Fixed)Figure 4.2.15 NACCS Center Server Domain Name Format in the Interactive Processing Mode (SMTP
Two-Way) (in Single-Byte Capital Letters)(F) E-mail address used in a message sent from a user
E-mail addresses in the From and To fields of the SMTP header in a processing request
message sent from a user to the NACCS’s SMTP Two-Way Server are specified as follows.
From: user e-mail address (e.g.: AAXXXX@ZZZZZ.ABC01.NACCS6)To:
NACCS center server e-mail address(e.g.: NACCS@SMTP.PROD.NACCS6)
Entry of an e-mail address in From and To fields is mandatory because the e-mail address in
the From field is used to authenticate the user at the NACCS’s SMTP Two-Way Server and thee-mail address in the To field is used to specify the user’s SMTP Server as the message
destination.
If the NACCS’s SMTP Two-Way Server cannot authenticate the e-mail address specified in the
From field, the message is discarded.

(G) E-mail address used in a message sent to a user
E-mail addresses in From and To fields of the SMTP header in a processing result message
sent from the NACCS’s SMTP Two-Way Server to a user are specified as follows.
From: NACCS center server e-mail address(e.g.: NACCS@SMTP.PROD.NACCS6)
To:
user e-mail address (e.g.: AAXXXX@ZZZZZ.ABC01.NACCS6)
These addresses are specified at the NACCS’s SMTP Two-Way Server.

(H) Notification of E-mail address
The e-mail address used in a message sent to / from a user is provided and announced by
NACCS Center. Users must use these addresses.

4-2-27

4.2.5

Procedure sequential processing

Figure 4.2.16 shows procedure sequential processing in interactive processing mode (SMTP twoway). For message classifications, refer to "Chapter 3 Message structure and format".

NACCS’s SMTP Two-Way
ServerUser‘s SMTP server

Core processing
system1) Processing Request Message2) Processing Request Message4) Processing result message (for screen)
Message Type R

6) Processing result message (for screen)
Message Type R

3) Procedure
processing5) Processing result message (for screen)
Message Type C

7) Processing result message (for screen)
Message Type C

File exchange block8) Processing Result Message (Printer)
Message Type P
10) Processing Result Message (Printer)
Message Type P

9) Processing Result Message (Printer)
Message Type P

11) Processing Result Message (Printer)
Message Type P

Figure 4.2.16 Example of Processing in Interactive Processing Mode (SMTP Two-Way)
1) User’s SMTP server sends processing request message in SMTP to NACCS’s SMTP Two-Way
Server.
• For SMTP sending sequence, refer to "4.2.3 Details of communications protocol".
• As processing request message format is different for each procedure, refer to procedure
specifications.
• Processing request message formats are represented by NACCS EDI format, MIME format andXML format.
2) NACCS’s SMTP Two-Way Server checks the message and sends the processing request message
to the core processing system.
3) The core processing system checks the message and executes the procedure.
4) and 5) The core processing system sends processing result message (for screen) to NACCS’s SMTP
Two-Way Server.
(According to the procedure specifications, there are cases in which more than one processing
result message (for screen) will occur. Figure 4.2.16 shows the case in which processing result
messages (for screen) of Message Type R and C are sent).
6) and 7) NACCS’s SMTP Two-Way Server sends the processing result message (for screen) in SMTP
to user’s SMTP server.
• For the SMTP receiving sequence, refer to "4.2.3 Details of communications protocol".
• Because the processing result message (for screen) formats are different for each procedure, referto the procedure specifications.
4-2-28

• Processing result message formats (for screen) are NACCS EDI format and XML format.
• 1 mail address of user can only send the next message after the processing result messages (forscreen) (message type is either R or C) described in 6) and 7) return to processing request
messages described in 1). Therefore, in the user’s SMTP server, confirmation must be carried out
to check if the processing result messages (for screen) (message type is R or C) described in 6)
and 7) has returned to processing request messages described in 1). In addition, because 1 mailaddress cannot send more than one message at the same time, more than one message can only
be sent if there is more than one mail address for the user.
* According to the procedure specifications, there are cases in which it is not Message Type [R] or[C] but Message Type[M] will return. In these cases, it is necessary to carry out the confirmation
procedure to check if Message Type [M] has returned or not.
8) and 9) The core processing system sends the processing result message (for printer) to the NACCS’s
SMTP Two-Way Server.
(No processing result message (for printer) may be generated or multiple processing result
messages (for printer) may be generated depending on the procedure. Figure 4.2.16 shows a casein which 2 transaction output messages are sent).
10) and 11)The NACCS’s SMTP Two-Way Server sends the processing result message (for printer) touser’s SMTP server.
• For the SMTP receiving sequence, refer to "4.2.3 Details of communications protocol".
• Because processing result message (for printer) formats are different according to each procedure
specification, refer to procedure specification.
• Processing result message (for printer) formats are NACCS EDI format and XML format.

(Note 1) Processing result messages (for printer) have the same patterns as described in "Figure 4.2.7
Image of the interface of the interactive processing mode (SMTP two-way)". It is only
necessary to check up with the processing response message if the message type is [R] or [M](Note 2) Arrival order toward user’s SMTP server of 6), 7),10),and 11) is not guaranteed.
(Note 3) EXC message, EXZ message makes the opportunities for the third party to carry out theprocedure, but just the sequence of 8),10) or 9),11) in Figure 4.2.16.

4-2-29

4.2.6

Others(1) Retention period of messages stored in the output message cache
Users must promptly retrieve the processing result messages in the output message cache. After
that, the messages in the output message cache will be deleted.
However, the processing result messages which are not retrieved by users will be retained in the
output message cache for 7 days since the registration day (including Saturday, Sunday andNational holiday). Message deletion will be carried out at a specified time during the night.
In "Golden Week" (holiday week from the end of April to early May) or New year's holiday, NACCS
Center will change the setting for a special retention period.
(Reference) An Example of Deleting the Processing Result Messages Stored in the output
message cache(In case if the definite time is temporarily set at 0:30)
August 1 (Fri.) 12:30
August 8 (Fri.) 0:30|
August 2 (Sat.) 0:30|↓↓
August 3
August 4 August 5 August 6 August 7↓――――――――|――――|――――|――――|――――|――――|―――――――|||←―――――――――Message's retention period―――――――-→|||
Registration
Deletion(2) Retention period for attachment files stored in attachment file storage table
For retention period for attachment files for each procedure, refer to Procedure Specifications.
(3) Restrictions
Interactive processing mode (SMTP two-way) users have to obey the following restrictions.
(1) Interactive processing mode (SMTP two-way) installs user’s SMTP sever in User system, andcan only use if the access line is leased connection or broadband optical connection.
(2) In principle, user’s SMTP server must be activated and be in a condition where messages
can be received at all times.
(3) If hardware failure occur in NACCS center server and no response returns, users have to
wait at least 5 minutes and try to connect with NACCS’s SMTP Two-Way Server again, later.
(4) If errors occur in NACCS center server and a processing result notification message returns
notifying "Center busy," users have to wait at least 3 minutes and try to connect with
NACCS’s SMTP Two-Way Server again, later.
(5) Users have to carry out stored message retrieving procedure (REQ), error message
retrieving procedure (SYG) periodically (some times a day, if that does not cause thedifficulties to the procedures), and to retrieve the messages stored in the output message
cache in the NACCS center server. However, carrying out these procedures frequently may
overload the NACCS center sever, so it is safer to take an interval of about 30 minutes before
executing the next procedure.
(6) If the processing result messages for processing request messages sent by users are not
returned in 2 minutes, it is considered that the process has timed out and users must send
these messages again.

4-2-30(4) Other notices
Interactive processing mode (SMTP two-way) users have to pay attention to the notices below.
(1) Messages via the File exchange block in NACCS center server may return to users 2 times
due to the timing of damages occur. Because input information is set in the Input Message ID
without any changes, it is possible that the second message can be ignored by configuring
the user system. (except for EXC messages).
(2) If more than one processing result message occurs in 1 transaction, the arrival order of thesemessages cannot be guaranteed in User system (Refer to Figure 4.2.17). Therefore, the user
system should not be built by assuming that the processing result notification message are
executed first.
(3) If NACCS’s SMTP Two-Way Server can not complete the connection with user’s SMTP
server in 3 minutes, NACCS’s SMTP Two-Way Server seem to be timeout, the connection
will be cut compulsively and the messages will be omitted. However, if these messages aretransaction outputs, they will be stored in the Error message queue of the output message
cache in the Center. The messages stored in Error message queue can be retrieved if users
carry out Error message retrieving procedure (SYG).
(4) When sending the processing request messages, the messages in which the user’s mailaddress in "From" line of SMTP header is not completely consistent will be omitted in
NACCS’s SMTP Two-Way Server. User system must specify the right mail address and send
the messages again.
(5) Because the NACCS’s SMTP Two-Way Server sends the receiving completion notificationback to the core processing system, users should not send it.
(6) In case of an overload in the system, operation limit such as halts of receiving transaction
request messages from all users may be used. In this case, NACCS Center will contact users
by telephone, fax, or NACCS notice board, etc.
(7) [Deleted](8) If NACCS is operated in the back up center due to a large-scale failure or a large-scaledisaster, connect to SMTP two-way server of the back up center.
(9) An environment to test the connection is built partly in the back up center. Therefore, if themain center is affected by a large-scale failure or a large-scale disaster, the system will
operate in the back up center, and the connection test may be unavailable.

4-2-31

If multiple processing result messages occur during 1 transaction, thearrival order between the processing result notification messages andoutput information messages (for printer) cannot be guaranteed in theUser system.

Send processing request
message

SMTP User Server

Processing result
notification message

SMTP TwoWay Center
ServerCore
processing
systemOutput information
message (for printer)

User system

NACCS Center server

Figure 4.2.17 Arrival Order of More than One Processing Result Messages (Example)

Figure 4.2.18 [Deleted]

4-2-32(5)Value of each timer classification

Table 4.2.12 shows value of each timer prescribed in interactive processing mode (SMTP two-way).
Besides, specified place for each timer is described from Figure 4.2.19 to Figure 4.2.22.

ID
T01

T02
T03
T04

T05

T06
T07

T08

Table 4.2.12 Timer's Value List
Observation content
Observation time for the SMTP connection between user ‘s
SMTP server and NACCS’s SMTP Two-Way Server whenuser sends the message
Time without communication after NACCS’s SMTP TwoWay Server opens a connection with user’s SMTP server
Time without communication after user’s SMTP server
opens a connection with NACCS’s SMTP Two-Way Server
Observation time for the SMTP connection between
NACCS’s SMTP Two-Way Server and user’s SMTP serverwhen the Center sends the message
Time from when the user’s SMTP server finishes sending
the processing result message until the correspondence
processing response message is sent backTime to re-send in case if NACCS center server or network
gets error and no response returns.
Time to re-send in case if errors occur in NACCS center
server and the processing result notification message
returns notifying "Center busy"
Interval to carry out stored message retrieving procedure(REQ) and error message retrieving procedure (SYG)
periodicallyTimer's value
Specified by user

Specified by user
1 hour3 minutes

2 minutes

5 minutes
At least 3 minutes

It is recommended totake about 30 minuteinterval before
executing the next
procedure.

(Note) Value of timer is the specified value in the present system.
(Note) T01 through T08 described in ID column of Table 4.2.12 are the IDs of each timer describedfrom Figure 4.2.19 to Figure 4.2.22.

4-2-33

User’s SMTP
server

NACCS’s SMTP
Two-Way Server
Request to open a connection
HELO
MAIL
RCPT

T01

T03
DATA
Send the message<CRLF>.<CRLF>
QUITRequest to open a connection
HELO
MAIL
RCPT
T02

T04
DATA
Send the message<CRLF>.<CRLF>
QUIT

Figure 4.2.19 Setting Timer in Normal Communication

4-2-34

User s SMTP
server

NACCS s SMTP
Two-Way Server

Send processing request message
Error

T05
No
response

Time out detection

Processing result message(for screen)

Observe only message
type R or M

T06

Send processing request message
Processing result message (for screen)

Figure 4.2.20 Observation Timer for Processing Result Message

User’s SMTP
server

NACCS’s SMTP
Two-Way Server

Send processing request message
Processing result message (Center busy)
T07
Send processing request message
Processing result message (normal)

Figure 4.2.21 Setting Timer in Case Center is Busy

4-2-35

User’s SMTP
server

NACCS’s SMTP
Two-Way Server

Processing request message (SYG or REQ)
Processing Result Message
T08
Processing request message (SYG or REQ)
Processing Result Message

Figure 4.2.22 Setting Timer for SYG Procedure, REQ procedure

4-2-36