Search the Archives

RFC 2821: [expanded: one more]... doesn't cover mail-mail attachments...

Reader comments:

Comment by Mr. Raymond Kenneth Petry
Submitted on 10/26/2004
Related RFC: RFC 2821
Rating: Not yet rated	Rate this comment:
[expanded: one more]... doesn't cover mail-mail attachments (I want to attach another message to an e-mail: especially in reporting 'spam'; not merely manual-copy header and body)... doesn't cover intrinsic security-- doesn't report-back to ISP of offending connections: especially service-attacks... doesn't cover security thresholding (IP's can be fake, but ISP not readily: also IP's can be mobile, but not ISP's)... doesn't cover hostname encryption (I want my e-mail-servers to re-key my hostname 3-monthly, keeping my username and domain as these identify my e-mail, and informing correspondents to resend)... doesn't cover server-server-secure (where's APOP-- it was supposed to keep my message transmissions First Class!?)... doesn't specify logical connections of messages and attachments (my PIM can file attachments but not message-alone: but my e-mail is used for updates, too)... doesn't support e-mail-to-auto-ftp (I want to e-mail my ftp -or- I want a separate ftp-upload-password so others can send to my ftp but not read-delete; Likewise, coming vid-link is multimode: web, and, voice-e-mail, to be blended)/rkp

FAQS.ORG makes no guarantees as to the accuracy of the posts. Each post is the personal opinion of the poster. These posts are not intended to substitute for medical, tax, legal, investment, accounting, or other professional advice. FAQS.ORG does not endorse any opinion or any product or service mentioned mentioned in these posts.

<< Back to: RFC 2821