![]() |
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Search this Thread | Display Modes |
#1
|
|||
|
|||
![]()
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 |
Ads |
#2
|
|||
|
|||
![]()
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 address. Should I be doing something differently to detect an invalid address? Thanks, Mark |
#3
|
|||
|
|||
![]()
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 address. Should I be doing something differently to detect an invalid address? Thanks, Mark |
#4
|
|||
|
|||
![]()
Sue and Ken --
Thanks for clarifying. I wasn't sure if an email address in internet format was actually validated or not. Mark |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
getting email address of To property in Outlook Inbox and From property in Outlook Outbox | Omatase | Outlook - General Queries | 1 | July 19th 07 01:04 PM |
Why does the Address property of the Recipient object in the Outlook object model look funny? | Omatase | Outlook - General Queries | 2 | July 13th 07 09:09 PM |
Invalid recipient?!? | TR Young | Outlook - General Queries | 5 | December 1st 06 06:03 PM |
Setting Restrict for NoAging property, resolved | Greg J | Outlook and VBA | 1 | October 24th 06 05:54 AM |
SafeItem.TO property is empty when the recipient is in address | Martin | Outlook and VBA | 0 | January 25th 06 11:13 AM |