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 }

Is this a regression from the previous 1.1.14?

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

Alright, I'm confused - where's the explicit bit?

Oops, I should read that much more carefully.

Added patch potentialfix.

This bug has been fixed in SVN. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.