Sender ID: Difference between revisions
No edit summary |
|||
| Line 30: | Line 30: | ||
the same as SPF, ''mfrom'' stands for MAIL FROM, the checked | the same as SPF, ''mfrom'' stands for MAIL FROM, the checked | ||
identity in SPF. Because SPF is more widely deployed than the later | identity in SPF. Because SPF is more widely deployed than the later | ||
proposed <tt>spf2.0/mfrom</tt> publishers of sender policies | proposed <tt>spf2.0/mfrom</tt>, publishers of sender policies | ||
wishing to protect their address in MAIL FROM Return-Paths | wishing to protect their address in MAIL FROM Return-Paths | ||
generally prefer the classic <tt>v=spf1</tt> format. | generally prefer the classic <tt>v=spf1</tt> format. | ||
| Line 52: | Line 52: | ||
...finally resulting either in one address, the ''pra'', or | ...finally resulting either in one address, the ''pra'', or | ||
an error for illegal combinations as explained in RFC 2822. | an error for illegal combinations as explained in RFC 2822. | ||
Simplified the rules are <tt>Sender</tt> beats <tt>From</tt> | Simplified, the rules are: <tt>Sender</tt> beats <tt>From</tt> | ||
and <tt>Resent-</tt>* beats <tt>Sender</tt>. Note that it's | and <tt>Resent-</tt>* beats <tt>Sender</tt>. Note that it's | ||
illegal to have more than one <tt>From</tt>-address without a | illegal to have more than one <tt>From</tt>-address without a | ||