…321bis-43 ] only. Not for use on Submit port 587. IETF IETF AUTH Authentication RFC4954 SASL mechanism names RFC4954 RFC4954 IETF MUST IETF IETF BURL Remote Content RFC4468 Permitted URL prefixes RFC4468 RFC4468 IETF MUST NOT Submit [ RFC6409 ] only. Not for use with SMTP on port…
…321bis-43 ] only. Not for use on Submit port 587. IETF IETF AUTH Authentication RFC4954 SASL mechanism names RFC4954 RFC4954 IETF MUST IETF IETF BURL Remote Content RFC4468 Permitted URL prefixes RFC4468 RFC4468 IETF MUST NOT Submit [ RFC6409 ] only. Not for use with SMTP on port…
…TP with SMTPUTF8 | [ RFC6531 ] | | UTF8SMTPA | ESMTP with SMTPUTF8 and AUTH | [ RFC4954 ] [ RFC6531 ] | | UTF8SMTPS | ESMTP with SMTPUTF8 and | [ RFC3207 ] [ RFC6531 ] | | | STARTTLS | | | UTF8SMTPSA | ESMTP with SMTPUTF8 and both | [ RFC3207 ] [ RFC4954 ] | | | STARTTLS and AUTH…
…ESMTP with SMTPUTF8 | [RFC6531] | | UTF8SMTPA | ESMTP with SMTPUTF8 and AUTH | [RFC4954] [RFC6531] | | UTF8SMTPS | ESMTP with SMTPUTF8 and | [RFC3207] [RFC6531] | | | STARTTLS | | | UTF8SMTPSA | ESMTP with SMTPUTF8 and both | [RFC3207] [RFC4954] | | | STARTTLS and AUTH | [RFC6531…
…TP with SMTPUTF8 | [ RFC6531 ] | | UTF8SMTPA | ESMTP with SMTPUTF8 and AUTH | [ RFC4954 ] [ RFC6531 ] | | UTF8SMTPS | ESMTP with SMTPUTF8 and | [ RFC3207 ] [ RFC6531 ] | | | STARTTLS | | | UTF8SMTPSA | ESMTP with SMTPUTF8 and both | [ RFC3207 ] [ RFC4954 ] | | | STARTTLS and AUTH…
…ns for MSAs in that document, including the requirement to implement SMTP AUTH [RFC4954] and the requirements of Email Submission Operations [RFC5068], also apply to the submissions port. See Sections 5.5 and 4.2 for additional information on client certificate authentication. Se…
…s for MSAs in that document, including the requirement to implement SMTP AUTH [ RFC4954 ] and the requirements of Email Submission Operations [ RFC5068 ], also apply to the submissions port. See Sections 5.5 and 4.2 for additional information on client certificate authentication.…
…rvice | [RFC5336] | | | Extensions | | | UTF8SMTPA | UTF8SMTP with SMTP AUTH | [RFC4954] [RFC5336] | | UTF8SMTPS | UTF8SMTP with STARTTLS | [RFC3207] [RFC5336] | | UTF8SMTPSA | UTF8SMTP with both | [RFC3207] [RFC4954] | | | STARTTLS and SMTP AUTH | [RFC5336] | +---------------+--…
…vailable. Examples of such mechanisms include SMTP-TLS [ RFC3207 ], SMTP-Auth [ RFC4954 ], OpenPGP RFC4880 ], and S/MIME [ RFC3851 ]. The core of the Internet Mail architecture does not impose any security requirements or functions on the end-to-end or hop-by-hop components. For …
…ce | [ RFC5336 ] | | | Extensions | | | UTF8SMTPA | UTF8SMTP with SMTP AUTH | [ RFC4954 ] [ RFC5336 ] | | UTF8SMTPS | UTF8SMTP with STARTTLS | [ RFC3207 ] [ RFC5336 ] | | UTF8SMTPSA | UTF8SMTP with both | [ RFC3207 ] [ RFC4954 ] | | | STARTTLS and SMTP AUTH | [ RFC5336 ] | +-----…
…es and their MTAs to directly prevent cross-user forgery: based on SMTP AUTH ([ RFC4954 ]), users have to be restricted to using only those email addresses that are actually under their control (see Section 6.1 of [RFC6409] ). Another means to verify the identity of individual us…
…d have been its "initial response" as a response to the empty server challenge. RFC4954 requires the server to accept client responses up to at least 12288 octets of base64-encoded text. The default value is therefore also the minimum value accepted for this parameter. This featu…
…d have been its "initial response" as a response to the empty server challenge. RFC4954 requires the server to accept client responses up to at least 12288 octets of base64-encoded text. The default value is therefore also the minimum value accepted for this parameter. This featu…
…d have been its "initial response" as a response to the empty server challenge. RFC4954 requires the server to accept client responses up to at least 12288 octets of base64-encoded text. The default value is therefore also the minimum value accepted for this parameter. This featu…