curl/tests/data/test902

<testcase>
<info>
<keywords>
SMTP
SMTP HELO
RFC821
</keywords>
</info>

#
# Server-side
<reply>
<servercmd>
REPLY EHLO 500 Command unrecognized
</servercmd>
</reply>

#
# Client-side
<client>
<server>
smtp
</server>
 <name>
RFC821-only SMTP server (EHLO not supported)
 </name>
<stdin>
From: different
To: another

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

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

body
.
</upload>
</verify>
</testcase>
_ Adjusted RFC821 HELO fallback and enabled test804 2010-02-22 21:57:57 +08:00			`<testcase>`
			`<info>`
			`<keywords>`
			`SMTP`
			`SMTP HELO`
			`RFC821`
			`</keywords>`
			`</info>`

			`#`
			`# Server-side`
			`<reply>`
			`<servercmd>`
			`REPLY EHLO 500 Command unrecognized`
			`</servercmd>`
			`</reply>`

			`#`
			`# Client-side`
			`<client>`
			`<server>`
			`smtp`
			`</server>`
			`<name>`
			`RFC821-only SMTP server (EHLO not supported)`
			`</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 23:12:40 +08:00			`From: different`
			`To: another`

			`body`
_ Adjusted RFC821 HELO fallback and enabled test804 2010-02-22 21:57:57 +08:00			`</stdin>`
			`<command>`
ftpserver.pl: Moved specifying the test number from the RCPT address ...to the client address as this frees the RCPT strings to contain just an email address and by passing the test number into curl as the client address remains consistent with POP3 and IMAP tests as they are specified in the URL. 2013-09-29 16:53:49 +08:00			`smtp://%HOSTIP:%SMTPPORT/902 --mail-rcpt 902@example.com --mail-from 902@example.com -T -`
_ Adjusted RFC821 HELO fallback and enabled test804 2010-02-22 21:57:57 +08:00			`</command>`
			`</client>`

			`#`
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<protocol>`
ftpserver.pl: Moved specifying the test number from the RCPT address ...to the client address as this frees the RCPT strings to contain just an email address and by passing the test number into curl as the client address remains consistent with POP3 and IMAP tests as they are specified in the URL. 2013-09-29 16:53:49 +08:00			`EHLO 902`
			`HELO 902`
tests: Fixed smtp mail from addresses 2013-09-19 14:19:25 +08:00			`MAIL FROM:<902@example.com>`
tests: Fixed smtp rcpt to addresses 2013-09-22 22:14:26 +08:00			`RCPT TO:<902@example.com>`
_ Adjusted RFC821 HELO fallback and enabled test804 2010-02-22 21:57:57 +08:00			`DATA`
			`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 23:12:40 +08:00			`From: different`
			`To: another`

			`body`
_ Adjusted RFC821 HELO fallback and enabled test804 2010-02-22 21:57:57 +08:00			`.`
			`</upload>`
			`</verify>`
			`</testcase>`