참고 자료 · 34

이메일 발신자 신뢰도 및 전달률 향상

발신자 ID, 메시지 클래스, 수신 거부 동작 및 거부 원인 확인

업데이트됨 · 16 min

빈 장비실의 통신 랙과 네트워크 배선 AI로 생성한 편집용 일러스트

이 가이드가 달성하는 목표

  • 흐름 매핑
  • 도메인 인증
  • 수신 거부 활성화
  • 거부 진단

빠른 확인

  • 어떤 시스템이 해당 도메인으로 이메일을 전송하나요?
  • 실제 메시지가 예상되는 SPF, DKIM 및 DMARC 검사를 통과합니까?
  • 각 메시지는 홍보성 메시지입니까, 아니면 거래 메시지입니까?
  • 수신 거부 기능이 제대로 작동합니까?
  • 거부 사유별로 메시지 그룹화되어 있습니까?

단계별 방법

  1. 1

    메시지 전송 현황 파악

    뉴스레터, 자동화, 수신 확인 및 알림을 구분합니다. 각 흐름에 대해 도메인, 공급자, 전송량, 목적 및 수신자를 기록합니다.

    결과물: 흐름 및 도메인 맵

  2. 2

    인증을 확인합니다.

    전송된 샘플에서 SPF, DKIM, DMARC 및 발신 도메인 정렬을 테스트합니다. 예상되는 DNS 구성이 모든 전송 경로가 작동함을 보장하는 것은 아닙니다.

    결과물: 검사된 헤더 및 인증 결과

  3. 3

    수신자의 기대에 부합합니까?

    가입, 전송 빈도, 약속된 콘텐츠 및 홍보성 트래픽과 거래성 트래픽의 분리를 확인합니다. 서비스 메시지에서 예기치 않은 홍보를 방지합니다.

    결과물: 메시지 클래스별 규칙

  4. 4

    구독 취소 테스트

    해당 프로모션 메일에 대해, 제공업체 요구 사항 및 RFC 8058에 부합하는 링크 표시 및 원클릭 동작을 확인합니다. 실제로 구독 취소가 처리되는지 테스트합니다.

    결과물: 전체 구독 취소 증거

  5. 5

    평판 모니터링

    영구 및 일시적 거부, 불만 사항, 수신자-제공업체 간 신호를 추적합니다. 전체 평균 대신 흐름 및 제공업체별로 분석합니다.

    결과물: 배달 실패 원인 분석

  6. 6

    수정 및 재테스트.

    주소 인증, 부적격 목록, 기술적 오류 및 구독 취소 오류부터 우선적으로 확인합니다. 상황에 따라 점진적으로 분석량을 늘립니다.

    결과물: 수정 계획 및 관찰 결과

관리 지표

지표측정 대상첫 번째 조치
인증SPF/DKIM/DMARC 결과가 예상되는 실제 메시지전송 경로 수정
거부흐름별 비율 및 원인목록 정리 또는 수정
출금적용된 프로모션 요청헤더 및 처리 수정
불만 접수캠페인별 추적 보고서타겟팅 및 빈도 수정

일반적인 실수

  • 게시된 DNS가 모든 흐름을 증명한다고 가정
  • 거래 메일과 프로모션 메일 혼합
  • 열람 여부와 받은 편지함 배치를 혼동하는 문제
  • 수신자를 실제로 삭제하지 않는 수신 거부 링크를 표시하는 문제

자주 묻는 질문

SPF만으로 충분한가요?

아닙니다. 수신자 요구 사항은 발송량과 상황에 따라 다르므로 DKIM, DMARC 및 해당 정렬도 확인해야 합니다.

모든 메시지에 원클릭이 필요한가요?

공급자 규칙은 프로모션 메시지와 거래 메시지를 구분하므로 각 흐름을 먼저 분류해야 합니다.

열람 여부가 전달을 증명하나요?

아닙니다. 열람 지표에는 한계가 있으며 전달 결과를 대체할 수 없습니다.

이메일 보안: 신원, 정렬 및 전송

이 언어판의 상세 참고 설명은 영어로 제공됩니다.

Domain authentication, transport confidentiality and inbox placement are different questions. SPF, DKIM and DMARC inform domain identity; MTA-STS and DANE concern server-to-server connections; reports help observe failures. None of these signals proves a message is benign.

References and status checked on .

Which mechanism answers which question?

Which mechanism answers which question?
Mechanism and sourceWhat is checkedWhere to find evidenceLimit to retain
SPF

SPF · RFC 7208

Authorisation of the sending IP for the SMTP envelope domain; DMARC uses MAIL FROM.The evaluated domain’s TXT record and receiver result. Evaluation allows 10 DNS-querying terms, rather than simply 10 network requests.Forwarding may change the observed IP. Selecting multiple SPF records produces permerror; an SPF pass does not prove alignment with From.
DKIM

DKIM · RFC 6376

DKIM cryptography · RFC 8301

Cryptographic verification of signed message parts for the signature’s d= domain.DKIM-Signature, selector s=, domain d= and key under selector._domainkey. RFC 8301 requires RSA ≥ 1,024 bits, recommends ≥ 2,048 bits and excludes rsa-sha1.A valid signature from another domain may not satisfy DMARC. Changes to signed parts can break verification; DKIM does not encrypt the message.
DMARC

DMARC · RFC 9989

Links the visible From domain to at least one SPF- or DKIM-authenticated, aligned identifier.The TXT policy discovered through _dmarc and trustworthy results produced at reception. Record alignment mode and the domain actually evaluated.A pass neither guarantees delivery nor endorses content. Receivers retain local policy; DNS errors and non-conforming messages require separate handling.
DMARC aggregate / failure reports

DMARC aggregate reports · RFC 9990

DMARC failure reports · RFC 9991

Observation of streams using the domain: aggregate statistics and, separately, details about failing messages.rua / ruf destinations, covered period and received reports. Their formats are now specified in separate RFCs published in May 2026.Missing reports do not prove no mail was sent. Detailed reports may expose message data; define suitable access, minimisation and retention.
MTA-STS

MTA-STS · RFC 8461

Recipient-domain policy for SMTP TLS transport and expected MX hosts._mta-sts TXT, HTTPS policy at /.well-known/mta-sts.txt and certificate. Three modes: testing, enforce and none.Applies to supporting servers and transport, without end-to-end encryption. Initial discovery and caching have their own limits.
TLS-RPT

SMTP TLS Reporting · RFC 8460

Reporting of successful and failed TLS negotiation or validation between servers._smtp._tls TXT, reporting destinations and received JSON data, correlated with transport logs.Observation does not enforce encryption. TLS reports and DMARC domain-identity reports describe different events.
DANE for SMTP

DANE for SMTP · RFC 7672

TLS transport authentication using DNSSEC-protected TLSA records.Validated DNSSEC chain, SMTP service TLSA record and a match with the presented certificate or key.DNSSEC validation is required on this path. DANE does not validate From or replace SPF, DKIM and DMARC.
ARC

ARC · RFC 8617

Carries authentication assessments along paths involving intermediaries.ARC header sets, chain validation and a trust decision about intermediaries.RFC 8617 is Experimental. ARC is not a trust framework and does not automatically make a message safe or deliverable.

DMARC in 2026: documentation changes

Reference
RFC 9989, published in May 2026, replaces RFC 7489 and RFC 9091. Aggregate and failure reporting are separated into RFC 9990 and RFC 9991.
Discovery and alignment
The specification defines DNS Tree Walk discovery. Do not infer organisational domains by naively retaining the final two labels.
Testing a deployment
pct is removed; the new t=y requests handling one level below the published failure policy: reject becomes quarantine, and quarantine becomes none. t=n is the default.
Interoperability
The standard advises against p=reject for general-purpose email domains. Inventory forwarding and mailing lists and check actual implementations before changing policy.

Publication of an RFC does not show that every provider already implements that version. Check documentation, observed results and exceptions in your own streams. These examples are educational and provide no ready-to-deploy DNS record. RFC 9989 →

Understand DMARC logic with a scenario

Simplified model: a conforming From message, an already discovered DMARC policy, one SPF MAIL FROM result and one examined DKIM signature. You supply alignment based on the evaluated domains and mode. The tool performs no DNS resolution or signature verification and predicts no delivery.

(SPF pass AND aligned) OR (DKIM pass AND aligned)

With multiple DKIM signatures, check each result / d= pair: one valid, aligned signature can suffice. Never combine one signature’s pass with an aligned domain from another failing signature. DNS discovery errors, absent policy and invalid From fields are outside this model. All choices stay in your browser.

Six educational cases, readable without JavaScript

Six educational cases, readable without JavaScript
ScenarioSPF: result / alignmentDKIM: result / alignmentExpected interpretation
Aligned SPF is sufficientpass — authenticated
Yes
fail — observed failure
No
pass — at least one authenticated and aligned path

The SPF path meets both conditions.

Aligned DKIM is sufficientfail — observed failure
No
pass — authenticated
Yes
pass — at least one authenticated and aligned path

The DKIM path meets both conditions independently of the other path in this model.

Two passes without alignmentpass — authenticated
No
pass — authenticated
No
fail — no authenticated and aligned path in this scenario

Two third-party domains passing technically does not validate From.

Aligned domains, no authenticationfail — observed failure
Yes
fail — observed failure
Yes
fail — no authenticated and aligned path in this scenario

A matching domain does not replace successful authentication.

Incomplete evidenceResult not supplied
Alignment not supplied
fail — observed failure
No
Undetermined — complete the observations

Missing evidence on one path cannot be invented.

Proven DKIM, unknown SPFResult not supplied
Alignment not supplied
pass — authenticated
Yes
pass — at least one authenticated and aligned path

One complete positive result suffices even when the other path is unknown.

Prepare an actionable email review

Prepare an actionable email review
StreamEvidence to correlateUseful decision
Alerts, receipts and resetsProvider and From domain, envelope and DKIM identities, tracking ID, SMTP response and available delivery event.Separate transport failure, authentication error and absence of reading. Define an alternative for a critical service.
Campaigns and newslettersDomains and subdomains, alignment results, representative samples from every platform, withdrawal mechanism and stream-specific errors.Repair the affected sending path before changing a global policy; do not equate authentication with recipient expectations.
Forwarding and mailing listsPath before and after the intermediary, message changes, SPF/DKIM outcomes and ARC information when present.Explain the observed break and local policy; do not assume a valid ARC chain compels acceptance.
Transport to MX hostsRelevant MTA-STS policy or TLSA, certificates, DNSSEC validation for DANE, TLS reports and timestamped logs.Associate failures with the relevant host and period. Test changes within authorised scope and retain rollback.

Continue with domain and DNS governance →

Primary sources and publication dates

Dates below identify RFC publication months, separately from the consultation date. Descriptions and cases are editorial summaries rather than complete normative extracts.

공식 참조

참조는 방법을 뒷받침합니다. 상황에 맞게 검사를 조정하십시오. 이는 인증이 아닙니다. 원본 참조 제목 및 소스 문서는 다른 언어로 작성되었을 수 있습니다.