| [ Index ] |
PHP Cross Reference of Unnamed Project |
[Source view] [Print] [Project Stats]
Copyright 2012-2014 Horde LLC (http://www.horde.org/) See the enclosed file COPYING for license information (BSD). If you did not receive this file, see http://www.horde.org/licenses/bsd.
| Copyright: | 2012-2014 Horde LLC |
| License: | http://www.horde.org/licenses/bsd New BSD License |
| File Size: | 118 lines (3 kb) |
| Included or required: | 0 times |
| Referenced: | 0 times |
| Includes or requires: | 0 files |
Horde_Mail_Rfc822_Identification:: (3 methods):
__construct()
parse()
_parseMessageId()
Class: Horde_Mail_Rfc822_Identification - X-Ref
Class to parse identification headers (RFC 5322 [3.6.4]): Message-ID,| __construct($value = null) X-Ref |
| Constructor. param: string $value Identification field value to parse. |
| parse($value) X-Ref |
| Parse an identification header. param: string $value Identification field value to parse. |
| _parseMessageId() X-Ref |
| Message IDs are defined in RFC 5322 [3.6.4]. In short, they can only contain one '@' character. However, Outlook can produce invalid Message-IDs containing multiple '@' characters, which will fail the strict RFC checks. Since we don't care about the structure/details of the Message-ID, just do a basic parse that considers all characters inside of angled brackets to be valid. return: string A full Message-ID (enclosed in angled brackets). |
| Generated: Thu Aug 11 10:00:09 2016 | Cross-referenced by PHPXref 0.7.1 |