|
|
Posted by "Richard Lynch" on 10/01/01 11:31
On Thu, November 3, 2005 8:16 am, Richard Heyes wrote:
> Marcus Bointon wrote:
>> The PEAR rfc822 class is pretty good, but it should be noted it's
>> designed for parsing entire to, cc, bcc fields which may contain
>> multiple addresses, and it's not quite as simple as asking it 'is
>> this
>> address ok'.
>
> News to me...
>
> if (!PEAR::isError(Mail_RFC822::parseAddressList('joe@example.com')))
> {
> // Valid...
> }
This one would accept:
'joe@example.com,jill@example.com'
right?
> It even has a method specifically for "normal" email addresses of the
> form user@domain.com...
>
> if (Mail_RFC822::isValidInetAddress('joe@example.com')) {
> // Valid...
> }
But this one, for real, for sure, tells me that the single email
address is precisly in compliance with RFC822?
Jeez, now all I gotta do is figure out how the heck to get this function.
Hopefully without being forced to swallow all of PEAR in one gulp,
which was my last experience trying to use a PEAR class...
--
Like Music?
http://l-i-e.com/artists.htm
Navigation:
[Reply to this message]
|