Page MenuHomePhabricator

DomainKeys Identified Mail (DKIM) for (and other projects)
Closed, ResolvedPublic


As a reminder: Echo user (or etc.) in the From: and Reply-To of its email notifications, while the true sender is left to the internals of Received headers.

A user posted headers of a message caught by Yahoo! spam filters which shows they want DKIM headers for the domain in question (unlike SPF which checks, so it should be added for all projects: and to start with, but also the others for future deployments.

Authentication-Results:; domainkeys=neutral (no sig);; dkim=neutral (no sig)

Version: unspecified
Severity: enhancement
See Also:



Event Timeline

bzimport raised the priority of this task from to High.Nov 22 2014, 2:25 AM
bzimport set Reference to bz56413.
bzimport added a subscriber: Unknown Object (MLST).

(In reply to comment #1)

also see:

I received an e-mail that this RT ticket has been closed because this bug report was marked fixed. I think the e-mail was mistaken, though perhaps this issue is now resolved/fixed and the bug report simply needs to be updated? I'm a little confused.

Not fixed. Both (bug 53569) notifications received on a gmail box for show no DKIM info.

Received-SPF: pass ( domain of designates as permitted sender) client-ip=;

spf=pass ( domain of designates as permitted sender);
dmarc=pass (p=NONE dis=NONE)

All Wikimedia outgoing mail should be signed with DKIM now. We have no strict DMARC policy yet and it's unsure whether we'll decide to do so anytime soon, though.