4.6Others

4.6.1

e-mail

4.6.1.1

Major check points for e-mail address

Table 4.6.1 shows the major check points for e-mail addresses when the Procedure Specifications
states that "It should be according to the format of the mail address."
Table 4.6.1

Major Check Points for E-Mail Address

Item No.

Check points

1

At Mark "@" is 1 (there should be at mark "@" without fail).

2

Period "." should not be consecutively placed.

3

There should be no Period "." input before and after At Mark "@".

4

Period should not be input in front or at the end.

5Input should be made before and after At Mark "@."

4.6.1.2

e-mail transmission

In NACCS, in some procedures, e-mail will be sent in response to normal termination of those
procedures to the e-mail address input by the user.
Figure 4.6.1 shows an example of e-mail transmission.
In addition, refer to "Appendix Table 6.7 Subjected Procedure List" for subjected procedure whichtransmits e-mails in the process shown in Figure 4.6.1.

Send to each e-mailaddress.
Compressed fileCompressed(ZIP)file (ZIP)e-mail (with PW)(パスワード付)e-mailCompressed file
Compressed(ZIP)file (ZIP)e-mail (with PW)(パスワード付)e-mail

SMTP
Transmitted
message file
PDF file

Transmitted
message file
PDF file

Report Creation Server

E-mail client fordestination user

Control table for e-mail
NACCS Center Server

Figure 4.6.1

Outline of E-Mail Transmission

4-6-1

4.6.1.3

Information transmitted by e-mailTable 4.6.2 shows information transmitted by e-mail.
In addition, for procedure to transmit e-mails, refer to "Appendix Table 6.7 Subjected Procedure
List."
Also, for information transmitted by each e-mail, refer to the "Procedure Specifications" for aprocedure which are specified in "Appendix Table 6.7 Subjected Procedure List" as the procedure
which transmits e-mails.
Table 4.6.2
Item No.

Information name

Information Transmitted by E-Mail

Attribute

Byte

Details of output

1

Destination

sn70 Max 5 destinations(The number of destinations which can be
input is according to the ProcedureSpecifications)
60
Refer to the "Procedure Specifications."

2

Subjectj

3

Mail body

j

300

4

Compressed file name

an

60

5

Compressed password

an

12

6

PDF file namej50

7PDF file--8

Refer to the "Procedure Specifications."
Refer to the "Procedure Specifications."
Refer to the "Procedure Specifications."
Refer to the "Procedure Specifications."
Refer to the "Procedure Specifications."

Transmitted message
an30
Refer to the "Procedure Specifications."
file name9Transmitted message
Refer to the "Procedure Specifications."
file(*1) The compressed password (9 bytes to 12 bytes) is set by respective procedure specifications.
Note that the password assignment rules will be notified separately.

4-6-2

4.6.2

Attachment file

4.6.2.1

Extension

The following shows available extensions.
<Text data>• TEXT Format (extension: txt)
• Microsoft Word Format (should not include execution modules such as macro)(extension: doc, docx)• Microsoft PowerPoint Format (should not include execution modules such as macro)(extension: ppt, pptx)• XML Format (extension: xml)
• HTML Format (extension: htm, html)• Rich Text Format (extension: rtf)
• JustSystem Ichitaro Format (extension: jtd)
<Spreadsheet data>• Microsoft Excel Format (should not include execution modules such as macro)(extension: xls, xlsx)• CSV Format (extension: csv)
<Image data>• JPEG Format (extension: jpeg, jpe, jpg)
• TIFF Format (extension: tif, tiff)• Windows Bitmap Format (extension: bmp)
• GIF Format (extension: gif)
• PDF Format (extension: pdf)
• PNG Format (extension: png)
<Others>• Procedure for Trade Control application form format (extension: jet)

4.6.2.2

File name and format

If at all possible, the name of files to be transmitted should be named so that the receiver cananalogize contents.

4.6.2.2.1 When carrying out MSX or MSY01 procedure
The following shows characters available for file names.
• One-byte alphanumeric characters (capital letter, lowercase letter)• Hyphen• Underscore• Period (only for extension)• Two-byte characters should comply with JIS X 0208:1997. Users can only use JIS Level 1 andLevel 2 Japanese kanji characters.

4.6.2.2.2 When carrying out procedures other than MSX and MSY01
Characters available for file names should be equivalent with the character code system used foroutbound messages (processing request messages). (For more details, refer to "3.6.1.1 Encodedcharacters used in outbound messages (processing request messages)."

4-6-3

4.6.2.3

Character code used for file name

4.6.2.3.1 When carrying out MSX or MSY01 procedure
The following shows character codes available for file names.
(1) When only ASCII is used for file names
Encoding is not necessary.
(2) When Japanese is used for file names
File names should be encoded with BASE64(Old notation：B encode mode). Charactercode used for encoding Japanese file names should be ISO-2022-JP.

4.6.2.3.2 When carrying out procedures other than MSX and MSY01
The following shows character codes available for file names.
(1) When only ASCII is used for file names
Encoding is not necessary.
(2) When Japanese is used for file names
File names should be encoded with BASE64(Old notation：B encode mode). Any of thefollowing character codes should be used for encoding Japanese file names.
• EUC-JP• ISO-2022-JP• Shift_JIS• UTF-8

4.6.2.4

Garbled characters in file nameFor file names of attachment files, due to the fact that a mixture of two-byte and one-bytecharacters is allowed and that undefined areas for two-byte characters use platform-dependent
characters, even within JISX 0208：1997, depending on the user gateway computer models,there is a possibility that garbled characters, etc. may be generated and/or receivers cannot
correctly read the file names of attachment files.

4.6.2.5

File name length

The file name length of an attachment file must be 190 bytes or less. Furthermore, if the file nameof an attachment file sent from the user to NACCS is BASE64 encoded, the NACCS side decodes
the file name in BASE64 and checks to see if it is within 190 bytes. Refer to the "ProcedureSpecifications" because some procedures require a file name length shorter than 190 bytes.

4-6-4