Re: [PHP] Help Sending Mail

On Dec 11, 2007 12:20 PM, Richard Lynch <ceo@xxxxxxxxx> wrote:
I dunno if RFC822 specifies which ending but I *do* know that this
breaks the current PEAR mimePart.php code.

RFC 822 has been obsolete since RFC 2822 was introduced in 2001.

We (that is, myself and other members of the IETF) are working on
a new BIS/Draft for a new RFC that will revise (obsolete certain parts
of) 822 and 2822. However, it's already been mentioned that headers
should remain as standardized in 2822 (which I think will most likely
be the case).

--
Daniel P. Brown
[Phone Numbers Go Here!]
[They're Hidden From View!]

If at first you don't succeed, stick to what you know best so that you
can make enough money to pay someone else to do it for you.
.

Relevant Pages

  • Re: Treetop Email Parser
    ... The "obsolete" productions were not obsolete in RFC 822, ... a significant number of clients out there _capable_ of emitting e-mail ...
    (comp.lang.ruby)
  • Re: [PHP] Help Sending Mail
    ... RFC 822 has been obsolete since RFC 2822 was introduced in 2001. ... Just tell GMail to fix their dang code or get the PEAR guys to fix ... A standard nobody follows isn't a standard; ...
    (php.general)
  • Re: mail problem
    ... >I would infer that you should be able to use the ... Note that RFC 822 became obsolete when RFC 2822 was released in April ... The interpretation of quotation marks is an interaction between sendmail ...
    (AIX-L)
  • Re: convert char to codepoint
    ... the FAQ for UTF-8 is obsolete. ... It was replaced by RFC 2279, ... "OBSOLETE, replaced by RFC xxxx" on any RFCs. ...
    (comp.lang.java.programmer)
  • Re: Chris Bliss
    ... For those of you who do not know, the cited document was an RFC (Requests ... detailed protocols which form the backbone of the internet as we know it. ... that RFCs are known to our members, and that they are happy to quote them ...
    (rec.juggling)