Re: SPF is harmful. Adopt it.
Jonathan de Boyne Pollard <[email protected]>
| Newsgroups | gmane.mail.im2000 |
|---|---|
| Organization | Wack's Wicks Works |
| Message-ID | <[email protected]> |
JCB> (An exception: senders need not serve up message content in JCB> SMTP-land; they *must* do so in IM2000-land. I'm nervous JCB> about requiring more widespread server deployment -- given JCB> how poor server deployment already is for SMTP, DNS, HTTP, JCB> and the like -- just to *send* messages. Seems like it JCB> introduces another major "point of failure", in that, with JCB> IM2000, both the sender *and* the recipient of an email JCB> must have working message-exchange servers.) This is worrying about nothing. One already has such concerns with SMTP-based Internet mail. The recipient's mailhost must have a working SMTP Relay server. If call-back sender verification is in use, so too must the sender's mailhost. JCB> And note that this scenario, designed to favor IM2000, JCB> assumes that readers of email will be willing and/or able to JCB> take some extra steps when it comes to reading email, such as JCB> clicking an "obtain just the headers" button, waiting for JCB> remote retrieval, reading what comes back, then clicking JCB> "obtain the whole message" button, waiting for remote JCB> retrieval, reading what comes back, then clicking "this is JCB> spam, I really didn't want to see it". You aren't thinking like an MUA writer. MUAs don't necessarily have explicit buttons for every single operation in the IMAP. They just display a user interface and execute the appropriate sets of protocol transactions behind the scenes. Why do you think that they must have explicit buttons for every single MSRAP transaction? JCB> So I'd be interested in seeing any discussion of how IM2000 JCB> rollout would play, given *today's* user base, which should JCB> be presumed to behave almost exactly as users have long JCB> behaved: scroll down the one-line notices of incoming email, JCB> look at each email's content as it comes up (which they're JCB> used to it doing, *fast*), then either skipping each email, JCB> clicking on "delete", or clicking on "save to some folder". Read the case studies.