curl/tests/data/test905

<testcase>
<info>
<keywords>
SMTP
SMTP AUTH CRAM-MD5
RFC2195
RFC4954
</keywords>
</info>

#
# Server-side
<reply>
<servercmd>
AUTH CRAM-MD5
REPLY AUTH 334 PDE4OTYuNjk3MTcwOTUyQHBvc3RvZmZpY2UucmVzdG9uLm1jaS5uZXQ+
REPLY dGltIGI5MTNhNjAyYzdlZGE3YTQ5NWI0ZTZlNzMzNGQzODkw 235 Authenticated
</servercmd>
</reply>

#
# Client-side
<client>
<server>
smtp
</server>
<features>
crypto
</features>
 <name>
SMTP CRAM-MD5 authentication
 </name>
<stdin>
mail body
</stdin>
 <command>
smtp://%HOSTIP:%SMTPPORT/905 --mail-rcpt recipient@example.com --mail-from sender@example.com -u tim:tanstaaftanstaaf -T -
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
<protocol>
EHLO 905
AUTH CRAM-MD5
dGltIGI5MTNhNjAyYzdlZGE3YTQ5NWI0ZTZlNzMzNGQzODkw
MAIL FROM:<sender@example.com>
RCPT TO:<recipient@example.com>
DATA
QUIT
</protocol>
<upload>
mail body
.
</upload>
</verify>
</testcase>
Implement SMTP authentication 2010-04-19 05:16:30 -04:00			`<testcase>`
			`<info>`
			`<keywords>`
			`SMTP`
			`SMTP AUTH CRAM-MD5`
			`RFC2195`
			`RFC4954`
			`</keywords>`
			`</info>`

			`#`
			`# Server-side`
			`<reply>`
			`<servercmd>`
tests: Updated SMTP AUTH tests to use the new AUTH directive ...rather than specify a customised EHLO response. 2013-09-19 15:29:24 -04:00			`AUTH CRAM-MD5`
Implement SMTP authentication 2010-04-19 05:16:30 -04:00			`REPLY AUTH 334 PDE4OTYuNjk3MTcwOTUyQHBvc3RvZmZpY2UucmVzdG9uLm1jaS5uZXQ+`
			`REPLY dGltIGI5MTNhNjAyYzdlZGE3YTQ5NWI0ZTZlNzMzNGQzODkw 235 Authenticated`
			`</servercmd>`
			`</reply>`

			`#`
			`# Client-side`
			`<client>`
			`<server>`
			`smtp`
			`</server>`
			`<features>`
			`crypto`
			`</features>`
			`<name>`
			`SMTP CRAM-MD5 authentication`
			`</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			`mail body`
Implement SMTP authentication 2010-04-19 05:16:30 -04:00			`</stdin>`
			`<command>`
tests: Updated email addresses in SMTP tests following recent changes 2013-09-29 11:48:02 -04:00			`smtp://%HOSTIP:%SMTPPORT/905 --mail-rcpt recipient@example.com --mail-from sender@example.com -u tim:tanstaaftanstaaf -T -`
Implement SMTP authentication 2010-04-19 05:16:30 -04: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 04:53:49 -04:00			`EHLO 905`
Implement SMTP authentication 2010-04-19 05:16:30 -04:00			`AUTH CRAM-MD5`
			`dGltIGI5MTNhNjAyYzdlZGE3YTQ5NWI0ZTZlNzMzNGQzODkw`
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>`
Implement SMTP authentication 2010-04-19 05:16:30 -04: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 11:12:40 -04:00			`mail body`
Implement SMTP authentication 2010-04-19 05:16:30 -04:00			`.`
			`</upload>`
			`</verify>`
			`</testcase>`