FAQ
Edit report at http://pear.php.net/bugs/bug.php?id=17178&edit=1

ID: 17178
Updated by: daniel.oconnor@gmail.com
Reported By: programmer at protech1inc dot com
Summary: Mail_RFC822::parseAddressList does not accept
RFC-valid group syntax
Status: Open
Type: Bug
Package: Mail
Operating System: Linux
Package Version: 1.2.0
PHP Version: 5.2.6
Roadmap Versions:
New Comment:

Is this a regression from the previous 1.1.14?


Previous Comments:
------------------------------------------------------------------------

[2010-03-01 15:44:29] protechprog

Description:
------------
Empty groups are explicitly allowed by RFC 822 section 6.2.6, but
Mail_RFC822::parseAddressList returns an error.

Test script:
---------------
require "Mail/RFC822.php";
var_dump(Mail_RFC822::parseAddressList("empty-group:;","invalid",false,false));

Expected result:
----------------
array(0) {
}


Actual result:
--------------
object(PEAR_Error)#2 (8) {
["error_message_prefix"]=>
string(0) ""
["mode"]=>
int(1)
["level"]=>
int(1024)
["code"]=>
NULL
["message"]=>
string(12) "Empty group."
["userinfo"]=>
NULL
["backtrace"]=>
array(4) {
[...SNIP...]
}
["callback"]=>
NULL
}

------------------------------------------------------------------------

Search Discussions

  • Daniel Oconnor at Mar 2, 2010 at 9:23 am
    Edit report at http://pear.php.net/bugs/bug.php?id=17178&edit=1

    ID: 17178
    Updated by: daniel.oconnor@gmail.com
    Reported By: programmer at protech1inc dot com
    Summary: Mail_RFC822::parseAddressList does not accept
    RFC-valid group syntax
    Status: Open
    Type: Bug
    Package: Mail
    Operating System: Linux
    Package Version: 1.2.0
    PHP Version: 5.2.6
    Roadmap Versions:
    New Comment:

    6.2.6. MULTIPLE MAILBOXES

    An individual may have several mailboxes and wish to receive
    mail at whatever mailbox is convenient for the sender to
    access. This standard does not provide a means of specifying
    "any member of" a list of mailboxes.

    A set of individuals may wish to receive mail as a single unit
    (i.e., a distribution list). The <group> construct permits
    specification of such a list. Recipient mailboxes are speci-
    fied within the bracketed part (":" - ";"). A copy of the
    transmitted message is to be sent to each mailbox listed.
    This standard does not permit recursive specification of
    groups within groups.

    While a list must be named, it is not required that the con-
    tents of the list be included. In this case, the <address>
    serves only as an indication of group distribution and would
    appear in the form:

    name:;

    Some mail services may provide a group-list distribution
    facility, accepting a single mailbox reference, expanding it
    to the full distribution list, and relaying the mail to the
    list's members. This standard provides no additional syntax
    for indicating such a service. Using the <group> address
    alternative, while listing one mailbox in it, can mean either
    that the mailbox reference will be expanded to a list or that
    there is a group with one member.



    Read more: http://www.faqs.org/rfcs/rfc822.html#ixzz0h0eWgFvv


    Previous Comments:
    ------------------------------------------------------------------------

    [2010-03-02 05:35:50] doconnor

    Is this a regression from the previous 1.1.14?

    ------------------------------------------------------------------------

    [2010-03-01 15:44:29] protechprog

    Description:
    ------------
    Empty groups are explicitly allowed by RFC 822 section 6.2.6, but
    Mail_RFC822::parseAddressList returns an error.

    Test script:
    ---------------
    require "Mail/RFC822.php";
    var_dump(Mail_RFC822::parseAddressList("empty-group:;","invalid",false,false));

    Expected result:
    ----------------
    array(0) {
    }


    Actual result:
    --------------
    object(PEAR_Error)#2 (8) {
    ["error_message_prefix"]=>
    string(0) ""
    ["mode"]=>
    int(1)
    ["level"]=>
    int(1024)
    ["code"]=>
    NULL
    ["message"]=>
    string(12) "Empty group."
    ["userinfo"]=>
    NULL
    ["backtrace"]=>
    array(4) {
    [...SNIP...]
    }
    ["callback"]=>
    NULL
    }

    ------------------------------------------------------------------------
  • Daniel Oconnor at Mar 2, 2010 at 9:23 am
    Edit report at http://pear.php.net/bugs/bug.php?id=17178&edit=1

    ID: 17178
    Updated by: daniel.oconnor@gmail.com
    Reported By: programmer at protech1inc dot com
    Summary: Mail_RFC822::parseAddressList does not accept
    RFC-valid group syntax
    -Status: Open
    +Status: Feedback
    Type: Bug
    Package: Mail
    Operating System: Linux
    Package Version: 1.2.0
    PHP Version: 5.2.6
    Roadmap Versions:
    New Comment:

    -Status: Open
    +Status: Feedback
    Alright, I'm confused - where's the explicit bit?


    Previous Comments:
    ------------------------------------------------------------------------

    [2010-03-02 10:18:51] doconnor

    6.2.6. MULTIPLE MAILBOXES

    An individual may have several mailboxes and wish to receive
    mail at whatever mailbox is convenient for the sender to
    access. This standard does not provide a means of specifying
    "any member of" a list of mailboxes.

    A set of individuals may wish to receive mail as a single unit
    (i.e., a distribution list). The <group> construct permits
    specification of such a list. Recipient mailboxes are speci-
    fied within the bracketed part (":" - ";"). A copy of the
    transmitted message is to be sent to each mailbox listed.
    This standard does not permit recursive specification of
    groups within groups.

    While a list must be named, it is not required that the con-
    tents of the list be included. In this case, the <address>
    serves only as an indication of group distribution and would
    appear in the form:

    name:;

    Some mail services may provide a group-list distribution
    facility, accepting a single mailbox reference, expanding it
    to the full distribution list, and relaying the mail to the
    list's members. This standard provides no additional syntax
    for indicating such a service. Using the <group> address
    alternative, while listing one mailbox in it, can mean either
    that the mailbox reference will be expanded to a list or that
    there is a group with one member.



    Read more: http://www.faqs.org/rfcs/rfc822.html#ixzz0h0eWgFvv

    ------------------------------------------------------------------------

    [2010-03-02 05:35:50] doconnor

    Is this a regression from the previous 1.1.14?

    ------------------------------------------------------------------------

    [2010-03-01 15:44:29] protechprog

    Description:
    ------------
    Empty groups are explicitly allowed by RFC 822 section 6.2.6, but
    Mail_RFC822::parseAddressList returns an error.

    Test script:
    ---------------
    require "Mail/RFC822.php";
    var_dump(Mail_RFC822::parseAddressList("empty-group:;","invalid",false,false));

    Expected result:
    ----------------
    array(0) {
    }


    Actual result:
    --------------
    object(PEAR_Error)#2 (8) {
    ["error_message_prefix"]=>
    string(0) ""
    ["mode"]=>
    int(1)
    ["level"]=>
    int(1024)
    ["code"]=>
    NULL
    ["message"]=>
    string(12) "Empty group."
    ["userinfo"]=>
    NULL
    ["backtrace"]=>
    array(4) {
    [...SNIP...]
    }
    ["callback"]=>
    NULL
    }

    ------------------------------------------------------------------------
  • Daniel Oconnor at Mar 2, 2010 at 9:25 am
    Edit report at http://pear.php.net/bugs/bug.php?id=17178&edit=1

    ID: 17178
    Updated by: daniel.oconnor@gmail.com
    Reported By: programmer at protech1inc dot com
    Summary: Mail_RFC822::parseAddressList does not accept
    RFC-valid group syntax
    -Status: Feedback
    +Status: Open
    Type: Bug
    Package: Mail
    Operating System: Linux
    Package Version: 1.2.0
    PHP Version: 5.2.6
    Roadmap Versions:
    New Comment:

    -Status: Feedback
    +Status: Open
    Oops, I should read that much more carefully.


    Previous Comments:
    ------------------------------------------------------------------------

    [2010-03-02 10:19:33] doconnor

    -Status: Open
    +Status: Feedback
    Alright, I'm confused - where's the explicit bit?

    ------------------------------------------------------------------------

    [2010-03-02 10:18:51] doconnor

    6.2.6. MULTIPLE MAILBOXES

    An individual may have several mailboxes and wish to receive
    mail at whatever mailbox is convenient for the sender to
    access. This standard does not provide a means of specifying
    "any member of" a list of mailboxes.

    A set of individuals may wish to receive mail as a single unit
    (i.e., a distribution list). The <group> construct permits
    specification of such a list. Recipient mailboxes are speci-
    fied within the bracketed part (":" - ";"). A copy of the
    transmitted message is to be sent to each mailbox listed.
    This standard does not permit recursive specification of
    groups within groups.

    While a list must be named, it is not required that the con-
    tents of the list be included. In this case, the <address>
    serves only as an indication of group distribution and would
    appear in the form:

    name:;

    Some mail services may provide a group-list distribution
    facility, accepting a single mailbox reference, expanding it
    to the full distribution list, and relaying the mail to the
    list's members. This standard provides no additional syntax
    for indicating such a service. Using the <group> address
    alternative, while listing one mailbox in it, can mean either
    that the mailbox reference will be expanded to a list or that
    there is a group with one member.



    Read more: http://www.faqs.org/rfcs/rfc822.html#ixzz0h0eWgFvv

    ------------------------------------------------------------------------

    [2010-03-02 05:35:50] doconnor

    Is this a regression from the previous 1.1.14?

    ------------------------------------------------------------------------

    [2010-03-01 15:44:29] protechprog

    Description:
    ------------
    Empty groups are explicitly allowed by RFC 822 section 6.2.6, but
    Mail_RFC822::parseAddressList returns an error.

    Test script:
    ---------------
    require "Mail/RFC822.php";
    var_dump(Mail_RFC822::parseAddressList("empty-group:;","invalid",false,false));

    Expected result:
    ----------------
    array(0) {
    }


    Actual result:
    --------------
    object(PEAR_Error)#2 (8) {
    ["error_message_prefix"]=>
    string(0) ""
    ["mode"]=>
    int(1)
    ["level"]=>
    int(1024)
    ["code"]=>
    NULL
    ["message"]=>
    string(12) "Empty group."
    ["userinfo"]=>
    NULL
    ["backtrace"]=>
    array(4) {
    [...SNIP...]
    }
    ["callback"]=>
    NULL
    }

    ------------------------------------------------------------------------
  • Daniel Oconnor at Mar 2, 2010 at 9:31 am
    Edit report at http://pear.php.net/bugs/bug.php?id=17178&edit=1

    ID: 17178
    Updated by: daniel.oconnor@gmail.com
    Reported By: programmer at protech1inc dot com
    Summary: Mail_RFC822::parseAddressList does not accept
    RFC-valid group syntax
    Status: Open
    Type: Bug
    Package: Mail
    Operating System: Linux
    Package Version: 1.2.0
    PHP Version: 5.2.6
    Roadmap Versions:
    New Comment:

    http://svn.php.net/viewvc/pear/packages/Mail/trunk/Mail/RFC822.php?view=markup#l489


    Previous Comments:
    ------------------------------------------------------------------------

    [2010-03-02 10:21:41] doconnor

    -Status: Feedback
    +Status: Open
    Oops, I should read that much more carefully.

    ------------------------------------------------------------------------

    [2010-03-02 10:19:33] doconnor

    -Status: Open
    +Status: Feedback
    Alright, I'm confused - where's the explicit bit?

    ------------------------------------------------------------------------

    [2010-03-02 10:18:51] doconnor

    6.2.6. MULTIPLE MAILBOXES

    An individual may have several mailboxes and wish to receive
    mail at whatever mailbox is convenient for the sender to
    access. This standard does not provide a means of specifying
    "any member of" a list of mailboxes.

    A set of individuals may wish to receive mail as a single unit
    (i.e., a distribution list). The <group> construct permits
    specification of such a list. Recipient mailboxes are speci-
    fied within the bracketed part (":" - ";"). A copy of the
    transmitted message is to be sent to each mailbox listed.
    This standard does not permit recursive specification of
    groups within groups.

    While a list must be named, it is not required that the con-
    tents of the list be included. In this case, the <address>
    serves only as an indication of group distribution and would
    appear in the form:

    name:;

    Some mail services may provide a group-list distribution
    facility, accepting a single mailbox reference, expanding it
    to the full distribution list, and relaying the mail to the
    list's members. This standard provides no additional syntax
    for indicating such a service. Using the <group> address
    alternative, while listing one mailbox in it, can mean either
    that the mailbox reference will be expanded to a list or that
    there is a group with one member.



    Read more: http://www.faqs.org/rfcs/rfc822.html#ixzz0h0eWgFvv

    ------------------------------------------------------------------------

    [2010-03-02 05:35:50] doconnor

    Is this a regression from the previous 1.1.14?

    ------------------------------------------------------------------------

    [2010-03-01 15:44:29] protechprog

    Description:
    ------------
    Empty groups are explicitly allowed by RFC 822 section 6.2.6, but
    Mail_RFC822::parseAddressList returns an error.

    Test script:
    ---------------
    require "Mail/RFC822.php";
    var_dump(Mail_RFC822::parseAddressList("empty-group:;","invalid",false,false));

    Expected result:
    ----------------
    array(0) {
    }


    Actual result:
    --------------
    object(PEAR_Error)#2 (8) {
    ["error_message_prefix"]=>
    string(0) ""
    ["mode"]=>
    int(1)
    ["level"]=>
    int(1024)
    ["code"]=>
    NULL
    ["message"]=>
    string(12) "Empty group."
    ["userinfo"]=>
    NULL
    ["backtrace"]=>
    array(4) {
    [...SNIP...]
    }
    ["callback"]=>
    NULL
    }

    ------------------------------------------------------------------------

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouppear-bugs @
categoriesphp
postedMar 2, '10 at 4:40a
activeMar 2, '10 at 9:31a
posts5
users1
websitepear.php.net

1 user in discussion

Daniel Oconnor: 5 posts

People

Translate

site design / logo © 2022 Grokbase