In addition to commit fe260b75 fixed the same issue for RFC-821 based
SMTP servers and allow the credientials to be given to curl even though
they are not used with the server.

Reported-by: Melissa

Added SMTP (RFC-821 only) based test case as a reference for the fix
provided by commit fe260b75.

Follow up to 9317eced makes test 1056 work again.

This limitation was removed in commit 0bc4938e

Remove a superfluous "negotiated http2" info line

We're progressing throught drafts so there's no point in having a fixed
one in a symbol that'll survive.

This makes it possible to fetch from an IPv6 literal without specifying
the -g option.  Globbing remains available elsehwere in the URL.

For example:
  curl http://[::1]/file[1-3].txt



This creates no ambiguity, because there is no overlap between the
syntax of valid globs and valid IPv6 literals.  Globs contain hyphens
and at most 1 colon, while IPv6 literals have no hyphens, and at least 2
colons.

The peek_ipv6() parser simply whitelists a set of characters and counts
colons, because the real validation happens later on.  The character set
includes A-Z, in case someone decides to implement support for scopes
like [fe80::1%25eth0] in the future.

Signed-off-by: Paul Marks <pmarks@google.com>

As the second URL won't be passed input from stdin.

When the protocol part fails, the data usually does too but the protocol
part is often more fundamental and often provide the clues you need to
fix the test case.

Extended the regex to include other valid characters such as those used
in the reply text of Test 836.

As the email protocols implement SASL authentication rather than IMAP,
POP3 and SMTP specific authentication, updated the authentication
keywords to reflect this.

In the initializer for len, there is no prototype for "strlen".
In this statement, there is no prototype for "memcpy".

Added support for falling back to <data> when <data1>, <data2>, etc...
don't exist in the <reply> section of a unit test.

Specifying user credentials when the SMTP server doesn't support
authentication would cause curl to display "No known authentication
mechanisms supported!" and return CURLE_LOGIN_DENIED.

Reported-by: Tom Sparrow
Bug: http://curl.haxx.se/mail/lib-2014-03/0173.html

The test is only valid when one of four SSL backends is in use,
and must otherwise return success.

The improved connection reuse logic would otherwise create a new
connection for each one, which isn't supported by the test
server, nor expected by the test.