DSE security knowledge hub

Networks & Infrastructure
Knowledge

Page 135 of the DSE Networks & Infrastructure knowledge center, with source-backed guidance and practical next steps.

DSE-authoredOfficial sourcesReviewed guidance
Search the library
Explore this topic

Networks & Infrastructure knowledge center

Guidance for resilient networks, Wi-Fi, firewalls, cabling, power, exposure reduction, and connected-device planning.

Start with the cornerstone guide
DSE post stream

Networks & Infrastructure

1,594 articles
DSE visual briefNetworks & infrastructure

Negotiate requested DSN outcomes and returned content at SMTP time

The RCPT NOTIFY parameter requests DSNs for SUCCESS, FAILURE, or DELAY; NEVER must appear alone and requests no DSN for that recipient. The RCPT ORCPT parameter preserves the original recipient address that corresponds to the actual delivery recipient.

Published Reviewed 3 min readBy DSE Security Editorial Team
Read the guide
DSE visual briefNetworks & infrastructure

Parse enhanced mail status codes into class, subject, and detail

An enhanced mail status code contains three dot-separated fields: delivery class, problem subject, and specific detail. Class 2 means success, class 4 means a persistent transient failure that may succeed later, and class 5 means a permanent failure requiring a change.

Published Reviewed 3 min readBy DSE Security Editorial Team
Read the playbook
DSE visual briefNetworks & infrastructure

Parse multipart boundaries before interpreting nested MIME media types

A multipart body is divided by boundary lines into parts, each containing its own content headers, a blank line, and a body. The multipart Content-Type requires a boundary parameter, and the chosen delimiter must not occur as a delimiter line inside any encapsulated part.

Published Reviewed 3 min readBy DSE Security Editorial Team
Read the briefing
DSE visual briefNetworks & infrastructure

Preserve internationalized addresses in delivery and disposition reports

The UTF-8 address type has native, unitext, and ASCII-safe xtext forms; native UTF-8 cannot be used through a server that lacks SMTPUTF8. A message/global-delivery-status part uses UTF-8 and should preserve non-ASCII recipient addresses in the native UTF-8 address form.

Published Reviewed 3 min readBy DSE Security Editorial Team
Read the checklist
DSE visual briefNetworks & infrastructure

Separate authenticated message submission policy from SMTP relay handling

Port 587 identifies ESMTP message submission, while port 25 may be used only when a site explicitly distinguishes submission agents from transfer agents. A submission agent requires authentication by default unless the session is already independently authenticated or authorized.

Published Reviewed 3 min readBy DSE Security Editorial Team
Read the briefing
DSE visual briefNetworks & infrastructure

Validate Internet message syntax independently of SMTP transport

Internet Message Format defines message content syntax, not the SMTP envelope, transmission method, storage format, or user interface. A message contains a syntactically structured header section followed by an optional body separated by an empty line.

Published Reviewed 3 min readBy DSE Security Editorial Team
Read the explainer