curl/tests/data/test919

<testcase>
<info>
<keywords>
SMTP
SASL
SASL AUTH PLAIN
SASL-IR
RFC4616
RFC4954
</keywords>
</info>

#
# Server-side
<reply>
<servercmd>
AUTH PLAIN
REPLY AUTH 235 Authenticated
</servercmd>
</reply>

#
# Client-side
<client>
<server>
smtp
</server>
 <name>
SMTP plain authentication with initial response
 </name>
<stdin>
mail body
</stdin>
 <command>
smtp://%HOSTIP:%SMTPPORT/%TESTNUMBER --mail-rcpt recipient@example.com --mail-from sender@example.com -u user:secret --sasl-ir -T -
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
<protocol>
EHLO %TESTNUMBER
AUTH PLAIN AHVzZXIAc2VjcmV0
MAIL FROM:<sender@example.com>
RCPT TO:<recipient@example.com>
DATA
QUIT
</protocol>
<upload>
mail body
.
</upload>
</verify>
</testcase>
tests: Added SMTP AUTH with initial response tests 2013-04-27 08:04:02 -04:00			`<testcase>`
			`<info>`
			`<keywords>`
			`SMTP`
tests: Added "SASL" authentication keyword 2014-03-30 06:20:19 -04:00			`SASL`
tests: Replaced email authentication keywords with SASL based keywords As the email protocols implement SASL authentication rather than IMAP, POP3 and SMTP specific authentication, updated the authentication keywords to reflect this. 2014-03-30 07:01:15 -04:00			`SASL AUTH PLAIN`
tests: made the SASL modes separate keywords 2014-03-15 06:13:13 -04:00			`SASL-IR`
tests: Added SMTP AUTH with initial response tests 2013-04-27 08:04:02 -04:00			`RFC4616`
			`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 PLAIN`
tests: Added SMTP AUTH with initial response tests 2013-04-27 08:04:02 -04:00			`REPLY AUTH 235 Authenticated`
			`</servercmd>`
			`</reply>`

			`#`
			`# Client-side`
			`<client>`
			`<server>`
			`smtp`
			`</server>`
			`<name>`
			`SMTP plain authentication with initial response`
			`</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`
tests: Added SMTP AUTH with initial response tests 2013-04-27 08:04:02 -04: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 -u user:secret --sasl-ir -T -`
tests: Added SMTP AUTH with initial response tests 2013-04-27 08:04:02 -04: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`
sasl: Don't send authcid as authzid for the PLAIN mechanism as per RFC 4616 RFC 4616 specifies the authzid is optional in the client authentication message and that the server will derive the authorisation identity (authzid) from the authentication identity (authcid) when not specified by the client. 2019-04-18 16:54:35 -04:00			`AUTH PLAIN AHVzZXIAc2VjcmV0`
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>`
tests: Added SMTP AUTH with initial response tests 2013-04-27 08:04:02 -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`
tests: Added SMTP AUTH with initial response tests 2013-04-27 08:04:02 -04:00			`.`
			`</upload>`
			`</verify>`
			`</testcase>`