Project

General

Profile

Actions
Copy link

Bug #513

closed

Mailman: DMARC checks are enabled and could fail

Added by Pierre-Louis Bonicoli about 7 years ago. Updated about 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Service :: Mail
Start date:
2017-02-28
Due date:
% Done:

100%

Estimated time:
Patch Available:
Confirmed:
Yes
Branch:
Entity:
DuckCorp
Security:
No
Help Needed:
Yes

Description

DMARC checks are enabled by Mailman.

When a DMARC policy is defined in the sender domain, mails can be rejected:

/var/log/mailman/vette

Feb 28 10:36:38 2017 (7194) DMARC lookup for no-reply@microsoft.com (_dmarc.microsoft.com) found p=reject in _dmarc.microsoft.com. = v=DMARC1; p=reject; pct=100; rua=mailto:d@rua.agari.com; ruf=mailto:d@ruf.agari.com; fo=1
Feb 28 10:36:38 2017 (7194) Message discarded, msgid: <40d1e0c8-6fe4-4fd6-acfc-5e359d1960b2@BN1AFFO11OLC003.protection.gbl>


Received-SPF: None (protection.outlook.com: microsoft.com does not designate
 permitted sender hosts)
Authentication-Results: spf=none (sender IP is )
 smtp.mailfrom=no-reply@microsoft.com;

What puzzles me is what/who added the Received-SPF header in the rejected mail ?

References:
  • https://tools.ietf.org/html/rfc7208#section-9
    The Received-SPF header field is a trace field (see [RFC5322],
   Section 3.6.7) and SHOULD be prepended to the existing header, above
   the Received: field that is generated by the SMTP receiver.
Actions
Copy link

Also available in: Atom PDF