Custom Form Send Permissions

[Boyd]

I've created a custom Outlook form that is published to the
Organizational Forms Library. The process for which this form is used
is as follows:
1) From within Access, I have code that opens an instance of the
Outlook form, populates fields based on data in my database, and sends
the Outlook form to a recipient.
2) The recipient receives the Outlook form, populates a few text boxes,
then clicks a Submit button. The vbScript behind this button changes
the "To" field to my email address, then sends and closes the form.
3) When I receive the completed Outlook form in my inbox, I import the
form data into my Access database thru code.

For this process to work successfully, I need to add each recipient as
a Delegate to my inbox. Otherwise, the Outlook form is bounced back to
them when they click Submit, with the following message: "You do not
have permission to send to this recipient."

What am I missing here? There has to be a way of sending Outlook
forms, and having them returned, without delegating access to my inbox.

Any help/direction is greatly appreciated.
Thanks,
Boyd

 

[Sue Mosher [MVP-Outlook]]

The problem is that you're trying to resend a message that already has a From address of your own account. Two possible solutions:

1) Set the value of Item.SendOnBehalfOfName to the current user.

2) Forward the item instead of resending.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Boyd]

Thanks Sue, I appreciate the prompt reply.
With "Item.SendOnBehalfOfName" behind my submit button, I receive the
following error: "Object doesn't support this property or method".
Any ideas??

Boyd

 

[Dmitry Streblechenko]

It is SentOnBehalfOfName

Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

 

[Sue Mosher [MVP-Outlook]]

Thanks! (The object browser is your friend, Boyd.)

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers


It is SentOnBehalfOfName

Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

 

[Boyd]

Thanks Sue and Dmitry!
Using "SentOnBehalfOfName" seems to work perfectly.

Boyd

 

[Boyd]

I'm running into another snag when using "SentOnBehalfOfName". My
custom form isn't responding to it consistently. My command button
has the following code within the Click event:
Set objPage = Item.GetInspector.ModifiedFormPages("Message")
Item.SentOnBehalfOfName = Item.UserProperties("To")
Item.To = "(e-mail address removed)"
Item.Send

I had a user who received an "undeliverable" message when clicking the
button, then tried clicking again, and the form sent without a
problem.
Is it possible that the value in the "To" field (which has resolved to
the users account name, not the email address) isn't being recognized
by the Exchange server? Is it better practice to use the actual
address, instead of the resolved name?

Any help is appreciated.
Thanks, Boyd

 

[Dmitry Streblechenko]

If you are using a name, you indeed can get error, even if the name come
from GAL due to ambiguity: e.g. if you specify "admin" and you have users
named "admin" and "administrator", you will get an ambiguous error.
Addresses are definitely better.

Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

 

[Boyd]

Thanks Dmitry. I changed the "SentOnBehalfOfName" to the user's email
address, instead of the outlook account name, but the user is still
receiving the returned "undeliverable" message.

Does anyone have an example using "SentOnBehalfOfName" that works for
them? I really want to avoid adding every possible user as a delegate
to my Inbox.

Thanks,
Boyd

If you are using a name, you indeed can get error, even if the name come
from GAL due to ambiguity: e.g. if you specify "admin" and you have users
named "admin" and "administrator", you will get an ambiguous error.
Addresses are definitely better.

Dmitry Streblechenko (MVP)http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

I'm running into another snag when using "SentOnBehalfOfName". My
custom form isn't responding to it consistently. My command button
has the following code within the Click event:
Set objPage = Item.GetInspector.ModifiedFormPages("Message")
Item.SentOnBehalfOfName = Item.UserProperties("To")
Item.To = "(e-mail address removed)"
Item.Send

I had a user who received an "undeliverable" message when clicking the
button, then tried clicking again, and the form sent without a
problem.
Is it possible that the value in the "To" field (which has resolved to
the users account name, not the email address) isn't being recognized
by the Exchange server? Is it better practice to use the actual
address, instead of the resolved name?

Any help is appreciated.
Thanks, Boyd

Thanks Sue and Dmitry!
Using "SentOnBehalfOfName" seems to work perfectly.
Boyd
Sue Mosher [MVP-Outlook] wrote:
Thanks! (The object browser is your friend,Boyd.)
--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

messageIt isSentOnBehalfOfName
Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool
messageThanks Sue, I appreciate the prompt reply.
With "Item.SendOnBehalfOfName" behind my submit button, I receive the
following error: "Object doesn't support this property or method".
Any ideas??
Boyd- Hide quoted text -- Show quoted text -- Hide quoted text -- Show quoted text -

 

[Dmitry Streblechenko]

What exactly dod you mean by "undeliverable"? What is thee exact error
message?

Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

Thanks Dmitry. I changed the "SentOnBehalfOfName" to the user's email
address, instead of the outlook account name, but the user is still
receiving the returned "undeliverable" message.

Does anyone have an example using "SentOnBehalfOfName" that works for
them? I really want to avoid adding every possible user as a delegate
to my Inbox.

Thanks,
Boyd

If you are using a name, you indeed can get error, even if the name come
from GAL due to ambiguity: e.g. if you specify "admin" and you have users
named "admin" and "administrator", you will get an ambiguous error.
Addresses are definitely better.

Dmitry Streblechenko (MVP)http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

message

I'm running into another snag when using "SentOnBehalfOfName". My
custom form isn't responding to it consistently. My command button
has the following code within the Click event:
Set objPage = Item.GetInspector.ModifiedFormPages("Message")
Item.SentOnBehalfOfName = Item.UserProperties("To")
Item.To = "(e-mail address removed)"
Item.Send

I had a user who received an "undeliverable" message when clicking the
button, then tried clicking again, and the form sent without a
problem.
Is it possible that the value in the "To" field (which has resolved to
the users account name, not the email address) isn't being recognized
by the Exchange server? Is it better practice to use the actual
address, instead of the resolved name?

Any help is appreciated.
Thanks, Boyd

Thanks Sue and Dmitry!
Using "SentOnBehalfOfName" seems to work perfectly.

Boyd

Sue Mosher [MVP-Outlook] wrote:
Thanks! (The object browser is your friend,Boyd.)

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

messageIt isSentOnBehalfOfName

Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

messageThanks Sue, I appreciate the prompt reply.
With "Item.SendOnBehalfOfName" behind my submit button, I receive
the
following error: "Object doesn't support this property or method".
Any ideas??

Boyd- Hide quoted text -- Show quoted text -- Hide quoted text --
Show quoted text -

 

[Boyd]

What exactly dod you mean by "undeliverable"? What is thee exact error
message?

Dmitry Streblechenko (MVP)http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

Thanks Dmitry. I changed the "SentOnBehalfOfName" to the user's email
address, instead of the outlook account name, but the user is still
receiving the returned "undeliverable" message.

Does anyone have an example using "SentOnBehalfOfName" that works for
them? I really want to avoid adding every possible user as a delegate
to my Inbox.

Thanks,
Boyd

If you are using a name, you indeed can get error, even if the name come
from GAL due to ambiguity: e.g. if you specify "admin" and you have users
named "admin" and "administrator", you will get an ambiguous error.
Addresses are definitely better.
Dmitry Streblechenko (MVP)http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool
message
I'm running into another snag when using "SentOnBehalfOfName". My
custom form isn't responding to it consistently. My command button
has the following code within the Click event:
Set objPage = Item.GetInspector.ModifiedFormPages("Message")
Item.SentOnBehalfOfName = Item.UserProperties("To")
Item.To = "(e-mail address removed)"
Item.Send
I had a user who received an "undeliverable" message when clicking the
button, then tried clicking again, and the form sent without a
problem.
Is it possible that the value in the "To" field (which has resolved to
the users account name, not the email address) isn't being recognized
by the Exchange server? Is it better practice to use the actual
address, instead of the resolved name?
Any help is appreciated.
Thanks, Boyd
Thanks Sue and Dmitry!
Using "SentOnBehalfOfName" seems to work perfectly.
Boyd
Sue Mosher [MVP-Outlook] wrote:
Thanks! (The object browser is your friend,Boyd.)
--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

messageIt isSentOnBehalfOfName
Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool
messageThanks Sue, I appreciate the prompt reply.
With "Item.SendOnBehalfOfName" behind my submit button, I receive
the
following error: "Object doesn't support this property or method".
Any ideas??
Boyd- Hide quoted text -- Show quoted text -- Hide quoted text --
Show quoted text -- Hide quoted text -

- Show quoted text -

The email bounces back to the sender with the following message: "You
do not have permission to send to this recipient. For assistance,
contact your system administrator." The only way I currently can get
the email to go thru is by adding the sender as a delegate to my
Inbox.

Thanks,
Boyd

 

[Sue Mosher [MVP-Outlook]]

That's to be expected unless the sender has Send on Behalf or Send As permission over the person whose name you're trying to use for the From. Adding a person as a delegate grants Send on Behalf permission. Send As permission can be granted only by an administrator.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers