Ricoh MP C2004/C2504 Service Manual Part 37

Table of contents:
< Previous page: Part 36 | You are viewing page: Part 37 | Next page: Part 38 >

005

SDK-5

*CTL


006

SDK-6

*CTL

007

SDK-7

*CTL

[0 to 99999999 / 0 / 1/step]

008

SDK-8

*CTL

009

SDK-9

*CTL

010

SDK-10

*CTL

011

SDK-11

*CTL

012

SDK-12

*CTL



8621

Func Use Counter

001

Function-001

*CTL

[0 to 99999999 / 0 / 1/step]

002

Function-002

*CTL

003

Function-003

*CTL

004

Function-004

*CTL

005

Function-005

*CTL

006

Function-006

*CTL

[0 to 99999999 / 0 / 1/step]

007

Function-007

*CTL

008

Function-008

*CTL

009

Function-009

*CTL

010

Function-010

*CTL

011

Function-011

*CTL

[0 to 99999999 / 0 / 1/step]

012

Function-012

*CTL

013

Function-013

*CTL

014

Function-014

*CTL

015

Function-015

*CTL

016

Function-016

*CTL

[0 to 99999999 / 0 / 1/step]

017

Function-017

*CTL


018

Function-018

*CTL

019

Function-019

*CTL

020

Function-020

*CTL

021

Function-021

*CTL

[0 to 99999999 / 0 / 1/step]

022

Function-022

*CTL

023

Function-023

*CTL

024

Function-024

*CTL

025

Function-025

*CTL

026

Function-026

*CTL

[0 to 99999999 / 0 / 1/step]

027

Function-027

*CTL

028

Function-028

*CTL

029

Function-029

*CTL

030

Function-030

*CTL

031

Function-031

*CTL

[0 to 99999999 / 0 / 1/step]

032

Function-032

*CTL

033

Function-033

*CTL

034

Function-034

*CTL

035

Function-035

*CTL

036

Function-036

*CTL

037

Function-037

*CTL

038

Function-038

*CTL

039

Function-039

*CTL

040

Function-040

*CTL

041

Function-041

*CTL

[0 to 99999999 / 0 / 1/step]

042

Function-042

*CTL

Controller SP Mode Tables

043

Function-043

*CTL


044

Function-044

*CTL

045

Function-045

*CTL

046

Function-046

*CTL

047

Function-047

*CTL

048

Function-048

*CTL

049

Function-049

*CTL

050

Function-050

*CTL

051

Function-051

*CTL

[0 to 99999999 / 0 / 1/step]

052

Function-052

*CTL

053

Function-053

*CTL

054

Function-054

*CTL

055

Function-055

*CTL

056

Function-056

*CTL

057

Function-057

*CTL

058

Function-058

*CTL

059

Function-059

*CTL

060

Function-060

*CTL

061

Function-061

*CTL

[0 to 99999999 / 0 / 1/step]

062

Function-062

*CTL

063

Function-063

*CTL

064

Function-064

*CTL



8631

[T:FAX TX PGS]

These SPs count by color mode the number of pages sent by fax to a telephone number.


Controller SP Mode Tables

001

B/W

*CTL

[0 to 99999999 / 0 / 1/step]

002

Color

*CTL

[0 to 99999999 / 0 / 1/step]

8633

[F:FAX TX PGS]

These SPs count by color mode the number of pages sent by fax to a telephone number.

001

B/W

*CTL

[0 to 99999999 / 0 / 1/step]

002

Color

*CTL

[0 to 99999999 / 0 / 1/step]

Even if SP 1-012-001 = 0 the most recently used scan destination can still be cleared by the Scanner Auto Reset timer. If the Scanner Auto Reset timer is shorter than the System Auto Reset timer, then the most recently used scan destination will be cleared when the Scanner Auto Reset timer elapses.

      1. THE SETTING OF SMTP AUTHENTICATION IN SCAN TO

        EMAIL

        Scan to Email fails with the error message "Transmission has failed ". The SMTP username and password are correct. How can I make Scan to Email pass ?

        Change SP 5-860-022 "SMTP Auth. From Field Replacement" to On. By doing this, Scan to Email will pass the SMTP authentication.

        • Using this option to solve the above problem, the device email address will appear in the email's "From" field. The email address of the user who sent the email will appear in the "Reply-to" field.

          Explanation

          This is an SMTP authentication issue that aborts transmission of an already started Scan to Email. Currently this has only been reproduced using MS-Exchange server.

          MS-Exchange requires that all of the following match:

          1. The sender's address in the "MAIL FROM" field. This is also known as the "envelope sender" or "MIME sender". It is an SMTP command sent at the beginning of the email transmission process.

          2. The sender's address in the mail header "From:" field. This appears as "From" in email clients. It is a part of the email itself.

          3. The email address corresponding to the SMTP username used to login into the SMTP server. When the MFP logins into the SMTP server, the email address of the username 3) will be compared to 1) and 2). If these comparisons fail, authentication will also fail. Exchange server will stop the transmission procedure, and the "Transmission has failed" message will be returned to the sender.


          Typical Example

          NG case:

          SP5-860-022 is Off:

          1. The "MAIL FROM" field = device (Fig.1 )

          2. The mail header "From:" field = user (Fig.2 )

          3. The SMTP username = device (Fig.1 )

          When the SMTP server compares 2) and 3) the Exchange Server will stop the transmission procedure.

          OK case:

          SP5-860 can be used to make the values in the above example, match.

          In this example, if SP5-860-022 is On, the user's email address in the mail header '2)' will be replaced by the Administrator's email address. (see Fig.3 )

          To solve the problem, the Administrator's address must be the same as the device's address. If this is done:

          1. The "Mail From: field = device (Fig.1 )

            Software Configuration

          2. The mail header "From:" field = administrator (Fig.3 )

          3. The SMTP username = device (Fig.1 )

            1,2 and 3 must match and the authentication should be successful.


            • The user's email address will still be inserted into the reply-to field.

          Fig.1 Default device SMTP username, password and email address


          image

          Fig.2 A user's email address in the Address Book

          image

          Fig.3 Administrator's email address


          image


      2. THE QUALIFICATION SWITCHING OF SCAN TO FOLDER

Determining which account Scan to Folder uses to access a scan destination and the effects of System SP 5-846-021.

This method depends on how the destination is accessed, whether authentication is being used, and SP 5-846-021.

Cases:

< Previous page: Part 36 | You are viewing page: Part 37 | Next page: Part 38 >