Outlook 2003 sp3 and Exchange 2003 sp2. I'd like to disable Outlook to send
out read receipt if a message has such option enabled for the emails either
internal or external. I know I can select the option when the message pupup.
But I don't even want to see that. I'd like to set up option to all my
emails, new or old.

Also is there a GPO for such option so I can apply it to all users?

Thanks.

Chris wrote:

> Outlook 2003 sp3 and Exchange 2003 sp2. I'd like to disable Outlook to send
> out read receipt if a message has such option enabled for the emails either
> internal or external. I know I can select the option when the message pupup.
> But I don't even want to see that. I'd like to set up option to all my
> emails, new or old.
>
> Also is there a GPO for such option so I can apply it to all users?
>
> Thanks.

Asking for a read receipt in an e-mail results in adding a header to it.
You need to configure your Exchange server to strip out the header. That
would be a question appropriate for an Exchange newsgroup.

The mail server should be stripping out the header on inbound e-mails coming
from outside the company domain (i.e., for external e-mails coming in). It
should be stripped only for outbound e-mails destined for external
recipients. It should NOT get stripped for e-mails that are delivered
within the Exchange organization as some departments, managers, or company
policies may require their employees to acknowledge read receipts which
means the header must be allowed to request the read receipt in the first
place (like a dept. manager using read receipts to monitor his group are
monitoring their e-mails for critical communications). For e-mails coming
from outside, strip the header. For e-mails going outside, strip the
header. For e-mails routed internally, leave the header.

When read or delivery notifcations are requested by the sender, one of the
following headers are in the received copy of the e-mail:

Read-Receipt-To
Return-Receipt-To (for delivery receipt requests)*
Return-Receipt-Requested

Disposition-Notification-To (for read receipt requests; RFC 3798)*
Generate-Delivery-Report (for delivery receipt requests)

* Used by Microsoft Outlook.

Some are obsolete or non-standard (but may be de facto standards); however,
Microsoft has used them at some time. Only the last 2 are standardized by
RFC. These headers have as their value the e-mail address to which the
acknowledgement message (i.e., the notification or receipt) gets sent.
Because the Disposition-Notification-To header is defined by RFC 3798
(http://www.rfc-editor.org/rfc/rfc3798.txt), so also is its MDN (Message
Disposition Notification) format, the content of the acknowledgement,
defined by that RFC. Although widely used, Return-Receipt-To is not an RFC
standard header (see http://www.rfc-editor.org/rfc/rfc2076.txt) but instead
a de facto standard so it may not be recognized by all e-mail clients (for
those that support read receipt handling). Also, its acknowledgement
message (i.e., receipt) is not defined by RFC so there is no standardized
format for a delivery reciept.

very helpful. Actually I think I didn't make my question clear. We are
implementing a new email retention policy. One thing it will do is to delete
emails older than 1 year in the Deleted items folder. The problem is that
many users who deletes emails without read it and many of these emails are
with read receipt enabled. We tried the new policy on one mailbox. Once it
ran through mailbox management it generates lots of read receipts to either
external or internal users.

I think one way to avoid such mess is to scan each messages in the Deleted
items folder. If it's unread with read receipt header then remove the
header. Then run the retention policy. Will it work? Is it possible to
scan the messages and remove the header?

Thanks.

"VanguardLH" wrote:

> Chris wrote:
>
> > Outlook 2003 sp3 and Exchange 2003 sp2. I'd like to disable Outlook to send
> > out read receipt if a message has such option enabled for the emails either
> > internal or external. I know I can select the option when the message pupup.
> > But I don't even want to see that. I'd like to set up option to all my
> > emails, new or old.
> >
> > Also is there a GPO for such option so I can apply it to all users?
> >
> > Thanks.
>
> Asking for a read receipt in an e-mail results in adding a header to it.
> You need to configure your Exchange server to strip out the header. That
> would be a question appropriate for an Exchange newsgroup.
>
> The mail server should be stripping out the header on inbound e-mails coming
> from outside the company domain (i.e., for external e-mails coming in). It
> should be stripped only for outbound e-mails destined for external
> recipients. It should NOT get stripped for e-mails that are delivered
> within the Exchange organization as some departments, managers, or company
> policies may require their employees to acknowledge read receipts which
> means the header must be allowed to request the read receipt in the first
> place (like a dept. manager using read receipts to monitor his group are
> monitoring their e-mails for critical communications). For e-mails coming
> from outside, strip the header. For e-mails going outside, strip the
> header. For e-mails routed internally, leave the header.
>
> When read or delivery notifcations are requested by the sender, one of the
> following headers are in the received copy of the e-mail:
>
> Read-Receipt-To
> Return-Receipt-To (for delivery receipt requests)*
> Return-Receipt-Requested
>
> Disposition-Notification-To (for read receipt requests; RFC 3798)*
> Generate-Delivery-Report (for delivery receipt requests)
>
> * Used by Microsoft Outlook.
>
> Some are obsolete or non-standard (but may be de facto standards); however,
> Microsoft has used them at some time. Only the last 2 are standardized by
> RFC. These headers have as their value the e-mail address to which the
> acknowledgement message (i.e., the notification or receipt) gets sent.
> Because the Disposition-Notification-To header is defined by RFC 3798
> (http://www.rfc-editor.org/rfc/rfc3798.txt), so also is its MDN (Message
> Disposition Notification) format, the content of the acknowledgement,
> defined by that RFC. Although widely used, Return-Receipt-To is not an RFC
> standard header (see http://www.rfc-editor.org/rfc/rfc2076.txt) but instead
> a de facto standard so it may not be recognized by all e-mail clients (for
> those that support read receipt handling). Also, its acknowledgement
> message (i.e., receipt) is not defined by RFC so there is no standardized
> format for a delivery reciept.
> .
>

Chris wrote:

> "VanguardLH" wrote:
>
>> Chris wrote:
>>
>>> Outlook 2003 sp3 and Exchange 2003 sp2. I'd like to disable Outlook to send
>>> out read receipt if a message has such option enabled for the emails either
>>> internal or external. I know I can select the option when the message pupup.
>>> But I don't even want to see that. I'd like to set up option to all my
>>> emails, new or old.
>>>
>>> Also is there a GPO for such option so I can apply it to all users?
>>
>> Asking for a read receipt in an e-mail results in adding a header to it.
>> You need to configure your Exchange server to strip out the header. That
>> would be a question appropriate for an Exchange newsgroup.
>>
>> The mail server should be stripping out the header on inbound e-mails coming
>> from outside the company domain (i.e., for external e-mails coming in). It
>> should be stripped only for outbound e-mails destined for external
>> recipients. It should NOT get stripped for e-mails that are delivered
>> within the Exchange organization as some departments, managers, or company
>> policies may require their employees to acknowledge read receipts which
>> means the header must be allowed to request the read receipt in the first
>> place (like a dept. manager using read receipts to monitor his group are
>> monitoring their e-mails for critical communications). For e-mails coming
>> from outside, strip the header. For e-mails going outside, strip the
>> header. For e-mails routed internally, leave the header.
>>
>> When read or delivery notifcations are requested by the sender, one of the
>> following headers are in the received copy of the e-mail:
>>
>> Read-Receipt-To
>> Return-Receipt-To (for delivery receipt requests)*
>> Return-Receipt-Requested
>>
>> Disposition-Notification-To (for read receipt requests; RFC 3798)*
>> Generate-Delivery-Report (for delivery receipt requests)
>>
>> * Used by Microsoft Outlook.
>>
>> Some are obsolete or non-standard (but may be de facto standards); however,
>> Microsoft has used them at some time. Only the last 2 are standardized by
>> RFC. These headers have as their value the e-mail address to which the
>> acknowledgement message (i.e., the notification or receipt) gets sent.
>> Because the Disposition-Notification-To header is defined by RFC 3798
>> (http://www.rfc-editor.org/rfc/rfc3798.txt), so also is its MDN (Message
>> Disposition Notification) format, the content of the acknowledgement,
>> defined by that RFC. Although widely used, Return-Receipt-To is not an RFC
>> standard header (see http://www.rfc-editor.org/rfc/rfc2076.txt) but instead
>> a de facto standard so it may not be recognized by all e-mail clients (for
>> those that support read receipt handling). Also, its acknowledgement
>> message (i.e., receipt) is not defined by RFC so there is no standardized
>> format for a delivery reciept.
>
> very helpful. Actually I think I didn't make my question clear. We are
> implementing a new email retention policy. One thing it will do is to delete
> emails older than 1 year in the Deleted items folder. The problem is that
> many users who deletes emails without read it and many of these emails are
> with read receipt enabled. We tried the new policy on one mailbox. Once it
> ran through mailbox management it generates lots of read receipts to either
> external or internal users.
>
> I think one way to avoid such mess is to scan each messages in the Deleted
> items folder. If it's unread with read receipt header then remove the
> header. Then run the retention policy. Will it work? Is it possible to
> scan the messages and remove the header?

Don't know what is your non-disclosed method of deleting old items. The
e-mail client will issue the read receipt (if the option is enabled and set
to Automatic) when you open the e-mail with the read-receipt header. It is
a function of the e-mail client. Auto-archive does not open items to move
them out of the current message store into a .pst archive file. So don't
open the items to delete them. Or configure the client to ignore read
receipt requests.

Looks like your "implementation" up on the mail server (or whatever is "it")
needs work. It should not open the e-mails. It should not behave like an
e-mail client that is configured to acknowledge and send the receipt
e-mails.

What we have set is just a mailbox policy run by Exchange mailbox manager. I
spoke with MS support. They told me that it has built process to check read
recepient header before deleting. No way to disable it. Lots of people have
asked such function. Now, I'm thinking to make a script which will crawl all
mailboxes on a server to check in specified folders for any unread emails
older than xxx days with read recepient header. If so delete the header.
Then run mailbox policy. This way it shouldn't generate any read recepient
to the senders anymore. The problem is I'm having difficult to write the
script. Any suggestions for a good source for Exchange scripting?

Thanks.

"VanguardLH" wrote:

> Chris wrote:
>
> > "VanguardLH" wrote:
> >
> >> Chris wrote:
> >>
> >>> Outlook 2003 sp3 and Exchange 2003 sp2. I'd like to disable Outlook to send
> >>> out read receipt if a message has such option enabled for the emails either
> >>> internal or external. I know I can select the option when the message pupup.
> >>> But I don't even want to see that. I'd like to set up option to all my
> >>> emails, new or old.
> >>>
> >>> Also is there a GPO for such option so I can apply it to all users?
> >>
> >> Asking for a read receipt in an e-mail results in adding a header to it.
> >> You need to configure your Exchange server to strip out the header. That
> >> would be a question appropriate for an Exchange newsgroup.
> >>
> >> The mail server should be stripping out the header on inbound e-mails coming
> >> from outside the company domain (i.e., for external e-mails coming in). It
> >> should be stripped only for outbound e-mails destined for external
> >> recipients. It should NOT get stripped for e-mails that are delivered
> >> within the Exchange organization as some departments, managers, or company
> >> policies may require their employees to acknowledge read receipts which
> >> means the header must be allowed to request the read receipt in the first
> >> place (like a dept. manager using read receipts to monitor his group are
> >> monitoring their e-mails for critical communications). For e-mails coming
> >> from outside, strip the header. For e-mails going outside, strip the
> >> header. For e-mails routed internally, leave the header.
> >>
> >> When read or delivery notifcations are requested by the sender, one of the
> >> following headers are in the received copy of the e-mail:
> >>
> >> Read-Receipt-To
> >> Return-Receipt-To (for delivery receipt requests)*
> >> Return-Receipt-Requested
> >>
> >> Disposition-Notification-To (for read receipt requests; RFC 3798)*
> >> Generate-Delivery-Report (for delivery receipt requests)
> >>
> >> * Used by Microsoft Outlook.
> >>
> >> Some are obsolete or non-standard (but may be de facto standards); however,
> >> Microsoft has used them at some time. Only the last 2 are standardized by
> >> RFC. These headers have as their value the e-mail address to which the
> >> acknowledgement message (i.e., the notification or receipt) gets sent.
> >> Because the Disposition-Notification-To header is defined by RFC 3798
> >> (http://www.rfc-editor.org/rfc/rfc3798.txt), so also is its MDN (Message
> >> Disposition Notification) format, the content of the acknowledgement,
> >> defined by that RFC. Although widely used, Return-Receipt-To is not an RFC
> >> standard header (see http://www.rfc-editor.org/rfc/rfc2076.txt) but instead
> >> a de facto standard so it may not be recognized by all e-mail clients (for
> >> those that support read receipt handling). Also, its acknowledgement
> >> message (i.e., receipt) is not defined by RFC so there is no standardized
> >> format for a delivery reciept.
> >
> > very helpful. Actually I think I didn't make my question clear. We are
> > implementing a new email retention policy. One thing it will do is to delete
> > emails older than 1 year in the Deleted items folder. The problem is that
> > many users who deletes emails without read it and many of these emails are
> > with read receipt enabled. We tried the new policy on one mailbox. Once it
> > ran through mailbox management it generates lots of read receipts to either
> > external or internal users.
> >
> > I think one way to avoid such mess is to scan each messages in the Deleted
> > items folder. If it's unread with read receipt header then remove the
> > header. Then run the retention policy. Will it work? Is it possible to
> > scan the messages and remove the header?
>
> Don't know what is your non-disclosed method of deleting old items. The
> e-mail client will issue the read receipt (if the option is enabled and set
> to Automatic) when you open the e-mail with the read-receipt header. It is
> a function of the e-mail client. Auto-archive does not open items to move
> them out of the current message store into a .pst archive file. So don't
> open the items to delete them. Or configure the client to ignore read
> receipt requests.
>
> Looks like your "implementation" up on the mail server (or whatever is "it")
> needs work. It should not open the e-mails. It should not behave like an
> e-mail client that is configured to acknowledge and send the receipt
> e-mails.
> .
>

Chris wrote:

> What we have set is just a mailbox policy run by Exchange mailbox manager. I
> spoke with MS support. They told me that it has built process to check read
> recepient header before deleting. No way to disable it. Lots of people have
> asked such function. Now, I'm thinking to make a script which will crawl all
> mailboxes on a server to check in specified folders for any unread emails
> older than xxx days with read recepient header. If so delete the header.
> Then run mailbox policy. This way it shouldn't generate any read recepient
> to the senders anymore. The problem is I'm having difficult to write the
> script. Any suggestions for a good source for Exchange scripting?

I never had to admin an Exchange server. There are Exchange newsgroups
for asking on how to use it, configure it, and add scripts to it.

microsoft.public.exchange.*