mirror/curl
2
0
Fork 0
mirror of https://github.com/curl/curl.git synced 2024-12-15 06:40:09 +08:00
Code Issues Packages Projects Releases Wiki Activity
63c53ea627
curl/tests/data/test905

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

60 lines
895 B
Plaintext
Raw Normal View History

Implement SMTP authentication
2010-04-19 17:16:30 +08:00
<testcase>
<info>
<keywords>
SMTP
tests: Added "SASL" authentication keyword
2014-03-30 18:20:19 +08: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 19:01:15 +08:00
SASL AUTH CRAM-MD5
Implement SMTP authentication
2010-04-19 17:16:30 +08:00
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-20 03:29:24 +08:00
AUTH CRAM-MD5
tests: Updated CRAM-MD5 tests to use test user details
2013-11-12 17:42:59 +08:00
REPLY AUTH 334 PDE5NzIuOTg3NjU0MzIxQGN1cmw+
REPLY dXNlciA3MDMxNzI1NTk5ZmRiYjVkNDEyNjg5YWEzMjNlM2UwYg== 235 Authenticated
Implement SMTP authentication
2010-04-19 17:16:30 +08:00
</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 23:12:40 +08:00
mail body
Implement SMTP authentication
2010-04-19 17:16:30 +08: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-13 00:38:26 +08:00
smtp://%HOSTIP:%SMTPPORT/%TESTNUMBER --mail-rcpt recipient@example.com --mail-from sender@example.com -u user:secret -T -
Implement SMTP authentication
2010-04-19 17:16:30 +08: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-13 00:38:26 +08:00
EHLO %TESTNUMBER
Implement SMTP authentication
2010-04-19 17:16:30 +08:00
AUTH CRAM-MD5
tests: Updated CRAM-MD5 tests to use test user details
2013-11-12 17:42:59 +08:00
dXNlciA3MDMxNzI1NTk5ZmRiYjVkNDEyNjg5YWEzMjNlM2UwYg==
tests: Updated email addresses in SMTP tests following recent changes
2013-09-29 23:48:02 +08:00
MAIL FROM:<sender@example.com>
RCPT TO:<recipient@example.com>
Implement SMTP authentication
2010-04-19 17:16:30 +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
mail body
Implement SMTP authentication
2010-04-19 17:16:30 +08:00
.
</upload>
</verify>
</testcase>
Reference in New Issue Copy Permalink