Funny, I just realized for the first time that RFC 2368, the RFC approved just before the one containing the List-Unsubscribe header, was the spec for the mailto: URL format.
« Case study - Lyris ListManager | Main | Will Using the List-Unsubscribe Header Harm My Deliverability? »
TrackBack
TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00d83420aa6d53ef00d835687f8469e2
Listed below are links to weblogs that reference Interesting juxtaposition - RFC 2368 (mailto):
Verify your Comment
Previewing your Comment
This is only a preview. Your comment has not yet been posted.
Your comment could not be posted. Error type:
Your comment has been saved. Comments are moderated and will not appear until approved by the author. Post another comment
As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.
Having trouble reading this image? View an alternate.
Recent Posts
- Communicator Corp now supports list-unsubscribe
- List-Unsubscribe with Domain Keys
- MailUp adds support for List-Unsubscribe
- AOL Unsubscribe button coming soon?
- Google Gmail recommends List-Unsubscribe
- ReturnPath info on List-Unsubscribe
- Learn more about Unsubscribe at Lashback
- Case study - StrongMail Systems
- Will Using the List-Unsubscribe Header Harm My Deliverability?
- Interesting juxtaposition - RFC 2368 (mailto)
Comments