2.1 New Function .................................................................................................................................................... 2- 1
2.1.1Authentication at TX ................................................................................................................................... 2- 1
2.1.3Authentication at RX................................................................................................................................... 2- 6
2.1.7Setting for communicate SSL.................................................................................................................... 2- 12
2.1.8Initialization of all data and settings.......................................................................................................... 2- 12
2.1.9Backup of Mail Box .................................................................................................................................. 2- 15
3.1.1Overview of the Installation Procedure....................................................................................................... 3- 1
Chapter 4 Maintenance
4.1 Notes when service............................................................................................................................................ 4- 1
4.1.1Points to Note ............................................................................................................................................. 4- 1
4.4 Related Service Mode ..................................................................................................................................... 4- 28
4.4.1Related Service Modes List....................................................................................................................... 4- 28
4.4.2Invalidating the License for Transfer to a Different Device (Level 2)......................................................4- 29
2.1 New Function ..................................................................................................................................................... 2-1
2.1.1 Authentication at TX ................................................................................................................................... 2-1
2.1.3 Authentication at RX................................................................................................................................... 2-6
2.1.5 MAC Address Block Function .................................................................................................................. 2-11
2.1.7 Setting for communicate SSL.................................................................................................................... 2-12
2.1.8 Initialization of all data and settings.......................................................................................................... 2-12
2.1.9 Backup of Mail Box .................................................................................................................................. 2-15
2.1 New Function
Chapter 2
2.1.1 Authentication at TX
When the mail server is set on the internet, you need to prevent from Third Party Mail Relay that the third party uses
the false name. Third Party Mail Relay means that the third party sends large amount of spam mails using the mail
server which other people are operating. If you do not take any measures for this, resources like server and network
lines are exhausted and at the same time, you will get the claim from the user who received the spam mail. As a
measure, the authentication operation when SMTP transmission is prepared.
In case of the inner network (LAN), you can prevent from Third Party Mail Relay by restricting the IP address and
the domain name. In order to send from the outside domain using the mail address or securely use the mail server set
on the internet which the provider prepares, the authentication is indispensable at the transmission. This machine uses
two authentication methods, POP Before SMTP and SMTP AUTH and they enable to send i-FAX and e-mail to
SMTP server which requests the sender's authentication.
POP before SMTP
With this method, before SMTP transmission is performed, the POP server is logged into. SMTP transmission can
only be continued once the POP server has confirmed the IP address of the connected client as authorized within a
specific period of time. After user authentication is carried out at the POP server, the authenticated client IP address
is relayed to the SMTP server, where it is processed. The process requires a certain amount of time. Taking this
processing time into consideration, there is an idle period of 300msec, from POP authentication to the start of SMTP
transmission. If a POP before SMTP transmission is generated during POP reception, POP authentication is made
to wait until the reception is finished and then POP authentication and SMTP transmission are performed. Errors
occurring while the POP server is connected are treated as transmission errors.
0008-4675
With regard to the actual programming, all that is necessary is for System Settings > Network Settings > E-Mail/
I-Fax > Authent./ Encryption > POP Authentication bofore Sending to be set to ON.
Related new user error codes are #810 and #813. For details, refer to Troubleshooting.
SMTP AUTH
In SMTP AUTH, user authentication is performed when the SMTP server is connected, so that mail can only be
received from registered users. This method was standardized in March, 1999, as RFC2554. SMTP AUTH uses
ESMTP protocol, which is an extension of SMTP, and uses the SASL (Simple Authentication and Security Layer)
authentication mechanism, standardized as RFC2222, to authenticate the user by sending the user name and
password information in response to the server challenge data.
<Authentication mechanisms>
The SMTP server can have multiple authentication mechanisms and the most suitable authentication mechanism is
programmed in accordance with the security policy decided by the SMTP server administrator. The client E-Mail
client application selects the authentication algorithm from among the available authentication mechanisms and
performs authentication upon transmission.
This model supports the following five types of authentication mechanism.
2-1
CRAM-MD5
Challenge-Response Authentication Mechanism, computed by using the key-protected MD5 algorithm by HMAC-
MD5 (RFC2104)
NTLM
Windows NT authentication method
User name must be set in the form 'username@NTdomainname'
E.g.:
Windows2000 or earlier: username\\CANON (domain name may be omitted, depending on the environment)
Windows2000: username@canon.co.jp (domain name may be omitted, depending on the environment)
GSSAPI
Authentication system using Kerberos Version 5 (RFC1510)
User name must be set in the form 'username@realmname'.
username@CANON.CO.JP
(In Exchange2000, realm name = domain name)
PLAIN
Assumes that user name and password are sent as plain text (BASE64 encoded) and the communication packet is
encoded. (RFC2595) Allows secure authentication when used in combination with the encoded transmission
described later.
LOGIN
Sends the user name and password as plain text (BASE64 encoded). Actual transaction is the same as with PLAIN.
Similarly, allows secure authentication when used in combination with encoded transmission.
<SMTP AUTH transmission operation>
Even if the unit is programmed for transmission with SMTP AUTH, if the mail server does not support SMTP AUTH
and the encoding system supported by the server does not match that supported by this model, SMTP AUTH
transmission will not be possible. In that case, even if SMTP AUTH is programmed, transmission will be by normal
SMTP and there will be no transmission error generated. If an unauthenticated mail transmission is attempted to a
server that will not allow such transmission, subsequent SMTP protocols will generate an error in the mail server.
Unauthenticated mail can be transmitted to a server that will accept such transmission. These security policies are
determined by the server so, even if SMTP AUTH is not programmed, it is impossible to tell whether transmission
is possible without checking with the customer's server administrator.
<Authentication protocol>
Examples of transmission protocol using SMTP AUTH are given below.
The EHLO response from the client tells whether SMTP AUTH is supported by the server and the authentication
algorithm being used at that time is described. In the event that there are multiple authentication algorithms, multiple
algorithm names are described. The client selects one of the relayed authentication algorithms and then relays it on
to the server. Server challenge data come from the server and coded data made up from the server challenge data,
user name and password are returned in response for authentication. In general, the authentication algorithm to be
Chapter 2
used can be selected on the server side and PLAIN and LOGIN authentication and others which are undesirable from
the perspective of security can be blocked by the server setting. (Security policy is determined by the server.)