curl/tests/data/test900

<testcase>
<info>
<keywords>
SMTP
</keywords>
</info>

#
# Server-side
<reply>
</reply>

#
# Client-side
<client>
<server>
smtp
</server>
 <name>
SMTP
 </name>
<stdin>
From: different
To: another

body
</stdin>
 <command>
smtp://%HOSTIP:%SMTPPORT/%TESTNUMBER --mail-rcpt recipient@example.com --mail-from sender@example.com -T -
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
<protocol>
EHLO %TESTNUMBER
MAIL FROM:<sender@example.com>
RCPT TO:<recipient@example.com>
DATA
QUIT
</protocol>
<upload>
From: different
To: another

body
.
</upload>
</verify>
</testcase>
test 802 is the first SMTP test, although not strictly SMTP yet... 2009-12-29 16:28:53 -05:00			`<testcase>`
			`<info>`
			`<keywords>`
			`SMTP`
			`</keywords>`
			`</info>`

			`#`
			`# Server-side`
			`<reply>`
			`</reply>`

			`#`
			`# Client-side`
			`<client>`
			`<server>`
			`smtp`
			`</server>`
			`<name>`
			`SMTP`
			`</name>`
			`<stdin>`
tests: Corrected the SMTP tests to be RFC2821 compliant The emails that are sent to the server during these tests were incorrectly formatted as they contained one or more LF terminated lines rather than being CRLF terminated as per Section 2.3.7 of RFC-2821. This wasn't a problem for the test suite as the <stdin> data matched the <upload> data but anyone using these tests as reference would be sending incorrect data to a server. 2013-04-28 11:12:40 -04:00			`From: different`
			`To: another`

			`body`
test 802 is the first SMTP test, although not strictly SMTP yet... 2009-12-29 16:28:53 -05:00			`</stdin>`
			`<command>`
tests: use %TESTNUMBER instead of fixed number This makes the tests easier to copy and relocate to other test numbers without having to update content. Closes #6738 2021-03-12 11:38:26 -05:00			`smtp://%HOSTIP:%SMTPPORT/%TESTNUMBER --mail-rcpt recipient@example.com --mail-from sender@example.com -T -`
test 802 is the first SMTP test, although not strictly SMTP yet... 2009-12-29 16:28:53 -05:00			`</command>`
			`</client>`

			`#`
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<protocol>`
tests: use %TESTNUMBER instead of fixed number This makes the tests easier to copy and relocate to other test numbers without having to update content. Closes #6738 2021-03-12 11:38:26 -05:00			`EHLO %TESTNUMBER`
tests: Updated email addresses in SMTP tests following recent changes 2013-09-29 11:48:02 -04:00			`MAIL FROM:<sender@example.com>`
			`RCPT TO:<recipient@example.com>`
test 802 is the first SMTP test, although not strictly SMTP yet... 2009-12-29 16:28:53 -05:00			`DATA`
(SMTP) support DATA better in the server and make sure to "escape" CRLF.CRLF sequences in uploaded data. The test server doesn't "decode" escaped dot-lines but instead test cases must be written to take them into account. Added test case 803 to verify dot-escaping. 2009-12-30 16:52:27 -05:00			`QUIT`
			`</protocol>`
			`<upload>`
tests: Corrected the SMTP tests to be RFC2821 compliant The emails that are sent to the server during these tests were incorrectly formatted as they contained one or more LF terminated lines rather than being CRLF terminated as per Section 2.3.7 of RFC-2821. This wasn't a problem for the test suite as the <stdin> data matched the <upload> data but anyone using these tests as reference would be sending incorrect data to a server. 2013-04-28 11:12:40 -04:00			`From: different`
			`To: another`

			`body`
(SMTP) support DATA better in the server and make sure to "escape" CRLF.CRLF sequences in uploaded data. The test server doesn't "decode" escaped dot-lines but instead test cases must be written to take them into account. Added test case 803 to verify dot-escaping. 2009-12-30 16:52:27 -05:00			`.`
			`</upload>`
test 802 is the first SMTP test, although not strictly SMTP yet... 2009-12-29 16:28:53 -05:00			`</verify>`
			`</testcase>`