ATM_ID: BDFA4452-1D40-11E8-AD7B-EAEDC098612E

MFF:

PLANNEDTIMESTAFF:

ID: DPQA_Regression_SCANNING/Testcases/FS_46.045_Internet_Fax/108148

TESTCASE_HEADLINE: Validating that the receiver will not send email message in response to a received MDN

GROUP:

FEATURE:

SUB_FEATURE:

INPUT: <p></p>
<ol><li value="1">Make sure that SMTP and POP3 is configured with valid Server details in device.<br />
</li><li value="2">Make sure that the Internet Fax Service is enabled in Properties- Apps - Display.<br />
</li><li value="3">Make sure that the Sender Email client (outlook) is kept opened. (i.e.. The outlook configured using Internet Fax From Address).</li></ol>

PROCEDURE: <p></p>
<ol><li value="1">From device LUI - Touch Internet Fax App.<br />
</li><li value="2">Add Recipient either Manually or through Address Book.<br />
</li><li value="3">Place multipage document in DADH and submit the job.<br />
</li><li value="4">Open outlook and check that the mail "Delivered: Scanned from a Xerox Multifunction Printer" mail has been received to the sender email address.<br />
</li><li value="5">Check that the "Read: Your message was processed successfully. (MDN)" is received and verify no other email message (non-MDN response) was issued by receiver (to avoid mail loops).<br />
</li><li value="6">Also check that the received MDN response has human-readable text which has the confirmation/what error condition is. </li></ol>

OUTPUT: <p>To avoid mail loops a receiver should not issue an e-mail message (i.e. non-MDN response) in response to a received MDN request or in response to a processing failure. The receiver should generate MDN in human-readable text which has confirmation or what error condition is.</p>

PROCESS:

PRIORITY:

TEST_TYPE:

LOE:

RESOURCE_HW:

RESOURCE_CONSUMEABLES:

RESOURCE_MEDIA:

SKILL_SET:

TEST_CASE_TYPE:

TESTCASE_SOURCE:

SPEC: FS 46.045 Internet Fax

SPEC_VERSION: 1.0058

SPEC_TAG: [46.045.054.7]
[46.045.054.8]
[46.045.054.8.1]
[46.045.054]
[46.045.054.1]

ATM_OWNER:

APPROVE_QE:

APPROVED_QE:

APPROVE_SE:

APPROVED_SE:

APPROVE_SPAR:

APPROVED_SPAR:

ASSOCIATED_TESTCASES:

TRAINING:

TESTCASE_VERSION:

TESTCASE_STATE:

TESTCASE_PLATFORM:

TESTCASE_PRODUCT:

TESTCASE_APPROVALS:

CDATE: 1519902453

MDATE: 1519902453

MUSER: USWU60000

AUTHOR: USWU60000

ATM_MCOMMENTS: Imported from spreadsheet

HISTORY:

ATM_LOCKED:

ATM_REQLINK: 83F9BB5A-8841-1014-92B9-D35A1C95E13A, 83FC696C-8841-1014-BC05-94576C811C31, 83FF09A8-8841-1014-AEB8-EFA58A602DBF, 83E4FC65-8841-1014-9D68-901C5E5FA516, 83E27A27-8841-1014-9E4D-916E696F8B9B

ATM_REQCOUNT: 5

QA_TEAM:

TC_WEIGHTAGE:

FILENAME:

FILEDESC: <p>[46.045.054.7] (FT-14212) CCSFEAT4567.7 To avoid mail loops a receiver shall not issue an e-mail message (i.e. non-MDN response) in response to a received MDN request or in response to a processing failure. <br />
[46.045.054.8] (FT-14212) CCSFEAT4567.8 The receiver shall generate the MDN as a multi-part/report with two components:  <br />
&nbsp;[46.045.054.8.1] (FT-14212) CCSFEAT4567.8.1 Human-readable text that says what the error condition or confirmation is. <br />
[46.045.054] (FT-14212) CCSFEAT4567 MDN capabilities supported by the Receiver    <br />
&nbsp;[46.045.054.1] (FT-14212) CCSFEAT4567.1 The receiving device shall implement MDN capability in accordance with RFC2298 (specifies a multi-part/report with a human-readable part and a machine-readable part). </p>

FILES: