DKIM sign outgoing mail
Bug #387327 reported by
Craig
This bug report is a duplicate of:
Bug #387321: mail from launchpad can be spoofed by spammers.
Edit
Remove
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
[LEGACY] Canonical WebOps | ||
Bug Description
The launchpad.net domain does not have DKIM records, which means that other mail systems can masquerade as launchpad.net very easily and send spam as if they were the real launchpad.net mail servers.
http://
DKIM is easy to configure with most MTAs, and the security improvement and spam reduction is well worth the small amount of time spent during configuration.
Revision history for this message
| Craig (candrews-integralblue) wrote | #1 |
| affects: | launchpad → launchpad-foundations |
| tags: | added: email |
| Changed in launchpad-foundations: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| tags: | added: features |
| summary: |
- Add DKIM/DomainKeys to Launchpad.net + DKIM sign outgoing mail |
Revision history for this message
| Gary Poster (gary) wrote | #2 |
| Changed in launchpad-foundations: | |
| assignee: | nobody → Canonical LOSAs (canonical-losas) |
| tags: | added: dkim |
Revision history for this message
| Martin Pool (mbp) wrote | #3 |
To post a comment you must log in.
I don't think is a duplicate of 316272. This bug is requesting the launchpad.net domain verifies DKIM when sending and receiving mail. 316272 is asking for DKIM data to be used in establishing user identity when receiving email, which IMHO, is an entirely different subject, and one that I think is harder to implement.