davige said:
My firm recently moved a client from Exchange 2003 to Google Apps,
thereby using the Google Sync connector for Outlook. Exchange server
is turned off. However, and after doing exhaustive research, have
found that there is a glitch with Outlook, any version as far I know,
that answers Read Receipts even if you have it turned off in Outlook.
Out client does not want this at all, and this was unexpected issue.
Is there a way to block or delete ANY read receipts being answered
from Outlook? Is there a VBS scrript someone has used? It appears to
be a problem with Outlook and Internet web mail providers, but if we
have a way to just block it all, that would be so helpful.
From hunting around the help for Google Apps (something you can do), it
appears a bug in the add-on you installed into Outlook (the Google Apps
Sync Connector). For example, users report about a problem regarding
delegation and how read read reciepts are getting automatically issued
without even having to click the Send button:
http://www.google.com/support/forum/p/Google+Apps/thread?tid=7ed451dcefce0bd2&hl=en
A Google employee claimed that the read receipt behavior is something
configurable within Outlook. Well, you said that you disabled the
tracking function within Outlook. Maybe you have to go into the plug-in
or the GA account to configure behavior.
So you are asking how to undo the code for the plug-in you installed
into Outlook. The obvious choice is not to install the plug-in but that
means foregoing the use of the Google Apps server to do the
Exchange-like functions (i.e., why you left exchange).
Another user claims that Google's Gmail doesn't do read receipts; i.e.,
it is a function of the e-mail client. Since recipients typically have
this tracking disabled (it's done by their e-mail client) usually right
after the first time they are prompted about it, it's a worthless
feature. The article below mentions using web beacons to track e-mail
delivery and opening but most e-mail clients also default to or are
configured to block external content so that doesn't work. MsgTags is
one such service that "borrowed" from the old spammer's trick of using
web beacons but it's easily killed by NOT retrieving that external
content (linked images).
http://www.google.com/support/forum/p/Google+Apps/thread?tid=267618cc593a9ab4&hl=en
In that article is a link to why Gmail doesn't offer read receipt
functionality, which went to:
http://knol.google.com/k/read-receipts-in-gmail#
Yet read receipts are something that the e-mail client can do, too. An
email client can add a header to any outbound e-mail that request a read
receipt. It is not a separate e-mail. When the receipient gets that
e-mail, their client sees the header and will respond or ignore that
request depending on how that e-mail client is configured. So I have to
wonder if you truly do have read receipts disabled in Outlook (both for
sending and when getting a request in a received e-mail).
From
http://www.google.com/apps/intl/en/business/outlook_sync.html, it
certainly appears that you must *pay* for the Premier edition of Google
Apps to get support for the functions afforded by this plug-in, why not
contact Google for the support for which you are paying?
If you don't want to ask Google for help regarding a service with them
for which you are PAYING then go ask over in the Google Apps for Admins
Help Forum. It's a problem with the add-on that you installed (the
Google connector) and the Google Apps Exchange-like mail service.
http://www.google.com/support/forum/p/Google+Apps?hl=en
You could ask in either the Mail Settings or Google Apps Sync for
Outlook forums. I don't use Google Apps (and certainly wouldn't pay for
it and don't even use their free edition). I doubt you'll find a
significant portion of the visitors here use Google Apps and of those to
find an even smaller subsection of those users that use this add-on and
an even tinier subssection of those users that know anything about the
code in the most recent version of this add-on or whatever version you
happen to be using and an even more miniscule subsection of users that
would know the code to undo the bug-like behavior (which is asking one
add-on to undo the behavior of another add-on which may not be possible
since they aren't linked together regarding dependent functions that
would rely on one another).
