Outlook Banter

Outlook Banter (http://www.outlookbanter.com/)
-   Outlook and VBA (http://www.outlookbanter.com/outlook-vba/)
-   -   recipient email address is invalid, but resolved property is true (http://www.outlookbanter.com/outlook-vba/90941-recipient-email-address-invalid-but.html)

Mark VII May 28th 09 08:36 PM

recipient email address is invalid, but resolved property is true
 
Greetings --

I'm working on some email automation via VBA. (For a variety of reasons, I
can't use the system address book, and keep the email addresses in an Access
table. Long story.) I want to be able to protect against a fat-fingered
address in the table.

What I have so far creates the MailItem, adds a recipient, then uses the
Resolve method to make sure the email address exists in our system. (We have
Exchange servers.)

What is happening is the resolved property is returning True, even if the
address is invalid.

Here's a code extract:

Dim appOutlook As Outlook.Application
Dim nsNameSpace As Outlook.Namespace
Dim miMailItem As Outlook.MailItem
Dim rcpRecipient As Outlook.Recipient

Set appOutlook = CreateObject("Outlook.application")
Set nsNameSpace = appOutlook.GetNamespace("MAPI")
Set miMailItem = appOutlook.CreateItem(olMailItem)
miMailItem.Subject = "some text"
Set rcpRecipient = miMailItem.Recipients.Add("invalid.email@ourcompan y.com")
If rcpRecipient.Resolved = True Then
'* OK, continue
Else
'* issue error message and abort
End If

The Resolved property always returns True, I can't trap for an invalid email
address. Should I be doing something differently to detect an invalid
address?

Thanks,
Mark

Ken Slovak - [MVP - Outlook] May 28th 09 09:44 PM

recipient email address is invalid, but resolved property is true
 
How could Outlook possibly know if that was an invalid address?

If the format of the email address is correct it will resolve. That doesn't
mean that it's an actual email address that you can send to.

I can resolve but that doesn't mean that address actually
exists anywhere.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Professional Programming Outlook 2007.
Reminder Manager, Extended Reminders, Attachment Options.
http://www.slovaktech.com/products.htm


"Mark VII" wrote in message
...
Greetings --

I'm working on some email automation via VBA. (For a variety of reasons,
I
can't use the system address book, and keep the email addresses in an
Access
table. Long story.) I want to be able to protect against a fat-fingered
address in the table.

What I have so far creates the MailItem, adds a recipient, then uses the
Resolve method to make sure the email address exists in our system. (We
have
Exchange servers.)

What is happening is the resolved property is returning True, even if the
address is invalid.

Here's a code extract:

Dim appOutlook As Outlook.Application
Dim nsNameSpace As Outlook.Namespace
Dim miMailItem As Outlook.MailItem
Dim rcpRecipient As Outlook.Recipient

Set appOutlook = CreateObject("Outlook.application")
Set nsNameSpace = appOutlook.GetNamespace("MAPI")
Set miMailItem = appOutlook.CreateItem(olMailItem)
miMailItem.Subject = "some text"
Set rcpRecipient =
miMailItem.Recipients.Add("invalid.email@ourcompan y.com")
If rcpRecipient.Resolved = True Then
'* OK, continue
Else
'* issue error message and abort
End If

The Resolved property always returns True, I can't trap for an invalid
email
address. Should I be doing something differently to detect an invalid
address?

Thanks,
Mark



Sue Mosher [MVP][_3_] May 28th 09 10:05 PM

recipient email address is invalid, but resolved property is true
 
An SMTP address in the format is always a valid email
address to Outlook and will always resolve regardless of whether it exists
in any of the user's address lists.

--
Sue Mosher, Outlook MVP
Author of Microsoft Outlook 2007 Programming:
Jumpstart for Power Users and Administrators
http://www.outlookcode.com/article.aspx?id=54


"Mark VII" wrote in message
...
Greetings --

I'm working on some email automation via VBA. (For a variety of reasons,
I
can't use the system address book, and keep the email addresses in an
Access
table. Long story.) I want to be able to protect against a fat-fingered
address in the table.

What I have so far creates the MailItem, adds a recipient, then uses the
Resolve method to make sure the email address exists in our system. (We
have
Exchange servers.)

What is happening is the resolved property is returning True, even if the
address is invalid.

Here's a code extract:

Dim appOutlook As Outlook.Application
Dim nsNameSpace As Outlook.Namespace
Dim miMailItem As Outlook.MailItem
Dim rcpRecipient As Outlook.Recipient

Set appOutlook = CreateObject("Outlook.application")
Set nsNameSpace = appOutlook.GetNamespace("MAPI")
Set miMailItem = appOutlook.CreateItem(olMailItem)
miMailItem.Subject = "some text"
Set rcpRecipient =
miMailItem.Recipients.Add("invalid.email@ourcompan y.com")
If rcpRecipient.Resolved = True Then
'* OK, continue
Else
'* issue error message and abort
End If

The Resolved property always returns True, I can't trap for an invalid
email
address. Should I be doing something differently to detect an invalid
address?

Thanks,
Mark




Mark VII May 29th 09 06:24 PM

recipient email address is invalid, but resolved property is t
 
Sue and Ken --

Thanks for clarifying. I wasn't sure if an email address in internet format
was actually validated or not.

Mark


All times are GMT +1. The time now is 02:43 PM.

Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 2.4.0
Copyright ©2004-2006 OutlookBanter.com