This shows you the differences between two versions of the page.
Next revision | Previous revision Next revision Both sides next revision | ||
dmarc [2020/12/13 17:25] staff created |
dmarc [2020/12/13 17:40] staff |
||
---|---|---|---|
Line 7: | Line 7: | ||
DMARC puts FreeLists in a difficult position: We're essentially required to sign/ | DMARC puts FreeLists in a difficult position: We're essentially required to sign/ | ||
- | ==== Official Remedies ==== | + | ===== Official Remedies |
DMARC itself offers some solutions: | DMARC itself offers some solutions: | ||
Line 15: | Line 15: | ||
Section 3 off their guidance offers the only viable set of options -- we somehow have to replace the From: address with something else -- so that's what we'll discuss next. (Depending on your list's configuration one of " | Section 3 off their guidance offers the only viable set of options -- we somehow have to replace the From: address with something else -- so that's what we'll discuss next. (Depending on your list's configuration one of " | ||
- | === How FreeLists Handles DMARC === | + | ===== How FreeLists Handles DMARC ===== |
First, FreeLists detects domains that publish reject policy DMARC records. If your domain doesn' | First, FreeLists detects domains that publish reject policy DMARC records. If your domain doesn' | ||
Line 23: | Line 23: | ||
If your subscriber' | If your subscriber' | ||
- | '' | + | < |
+ | From: Jane Doe < | ||
+ | </ | ||
We'll replace that with: | We'll replace that with: | ||
- | '' | + | < |
+ | From: "Jane Doe" < | ||
+ | </ | ||
This allows other subscribers on the list to get the best available understanding of who the message came from while complying with DMARC. //The exact format of this header is subject to change as we strive to improve usability.// | This allows other subscribers on the list to get the best available understanding of who the message came from while complying with DMARC. //The exact format of this header is subject to change as we strive to improve usability.// | ||
- | == Improving usability == | + | === Improving usability |
Notice how we form the From: header. To improve usability it's important for your subscribers to put their name (it doesn' | Notice how we form the From: header. To improve usability it's important for your subscribers to put their name (it doesn' | ||
- | == Big domains and DMARC == | + | We do our best to maintain the Reply-to: header. If your list uses the '' |
+ | |||
+ | We add a '' | ||
+ | |||
+ | === Big domains and DMARC === | ||
Unfortunately the Yahoo/ | Unfortunately the Yahoo/ | ||
Line 41: | Line 49: | ||
The following domains don't use DMARC correctly or have incorrect DMARC-like email implementations that force us to employ the DMARC workaround anyway: micron.com, sbcglobal.net, | The following domains don't use DMARC correctly or have incorrect DMARC-like email implementations that force us to employ the DMARC workaround anyway: micron.com, sbcglobal.net, | ||
- | == Implementation notes == | + | === Implementation notes === |
Don't change your '' | Don't change your '' | ||
If the person posting to your list is from a DMARC domain //and isn't a subscriber// | If the person posting to your list is from a DMARC domain //and isn't a subscriber// | ||
- | |||
- | |||