ietf-822
[Top] [All Lists]

Re: OPES and Email

2005-07-07 14:01:05

On Thu, Jul 07, 2005 at 02:58:31PM -0400, Tony Hansen wrote:
Heads up, email experts!

I don't know if you saw the recent I-D documents that came out, entitled
OPES SMTP Use Cases (draft-ietf-opes-smtp-use-cases-02.txt).
...
I'm co-chair of the OPES group, and am aware of its potential
ramifications to the email world. So, I'd appreciate it if you could
review the use-cases document. Discussion about the document is
occurring on the ietf-openproxy(_at_)imc(_dot_)org mailing list. (If you'd 
rather
not join that list, I can channel your comments.)

Hello Tony,

In my first quick scan (oh my.. 13 000 plus IDs in IETF archive!
mere 1932 IDs after cleaning all expired/completed/etc...)
I spotted example SMTP session that violates a bunch of protocol
syntax details - and we have just had a discussion about the myriad
ways that people violate them..


  S: 220 mail.example.com Sample ESMTP MAIL Service, Version: 1.2 ready at Thu, 
20 Jan 2005 11:24:40+0100
  C: HELO ThatsMe

corrected:  HELO thatsme.example.org

  S: 250 mail.example.com Hello [192.168.0.138]
  C: MAIL FROM: steve(_at_)example(_dot_)org

corrected:  MAIL FROM:<steve(_at_)example(_dot_)org>

  S: 250 2.1.0 steve(_at_)example(_dot_)org(_dot_)(_dot_)(_dot_)(_dot_)Sender OK
  C: RCPT TO: paul(_at_)example(_dot_)com

corrected:  RCPT TO:<paul(_at_)example(_dot_)com>

  S: 250 2.1.5 paul(_at_)example(_dot_)com

e.g. must have angle-brackets, must not have spaces in places
where they are not specified as allowed per RFC 2821 strict syntax.



About the idea of "put attachments in web-server" -- one thing
that I hate profoundly is MS Exchange's habit of converting
incoming TEXT/PLAIN email into TEXT/HTML in some obscure situations.
Sender didn't  send HTML, and recipient (= me) doesn't want HTML.
Why that beast must do such stupidity ? 

This idea of converting message so that the attachment can be
downloaded from elsewere (other than over IMAP) sounds like
its writers are thinking that everybody will move to webmail
and HTML.

All in all, as a user I am very much opposed to ideas where my
emails encounter any other conversions, than those of transfer
encoding.


Thanks!

      Tony Hansen
      tony(_at_)att(_dot_)com
-- 
/Matti Aarnio   <mea(_at_)nic(_dot_)funet(_dot_)fi>


<Prev in Thread] Current Thread [Next in Thread>