<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Read Receipt as UTC Monrovia/Reykjavik BT please refund our exchange charges? in Email and hosting</title>
    <link>https://business.forums.bt.com/t5/Email-and-hosting/Read-Receipt-as-UTC-Monrovia-Reykjavik-BT-please-refund-our/m-p/80876#M9791</link>
    <description>&lt;P&gt;Hey&amp;nbsp;akristy,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you have set the Office 365 timezone correctly for your mailbox via the &lt;A href="https://outlook.office.com/owa/?path=/options/regional" target="_blank"&gt;Office 365 Timezone Settings page&lt;/A&gt;&amp;nbsp;then you're best contacting Microsoft's Office 365 support directly to let them know that the timestamp is showing incorrect on read receipts.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This shouldn't be an issue however as you can just convert the timezone that appears on the read receipt to figure out the exact date/time read. I don't think this is concrete evidence to bring to court though because the user can simply refuse to accept the read receipt once your email appears in their inbox.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks, Bobby&lt;/P&gt;</description>
    <pubDate>Tue, 04 Sep 2018 12:14:36 GMT</pubDate>
    <dc:creator>Bobby</dc:creator>
    <dc:date>2018-09-04T12:14:36Z</dc:date>
    <item>
      <title>Read Receipt as UTC Monrovia/Reykjavik BT please refund our exchange charges?</title>
      <link>https://business.forums.bt.com/t5/Email-and-hosting/Read-Receipt-as-UTC-Monrovia-Reykjavik-BT-please-refund-our/m-p/71084#M9786</link>
      <description>&lt;P&gt;There’s an ongoing complaint about Office 365’s response to email read receipts and other email tracking.&lt;/P&gt;&lt;P&gt;When an Office 365 user asks for a read receipt, the receipt comes back with a time zone of ‘UTC Monrovia / Reykjavik’ not the readers local time nor the Office 365 users time nor even something like the time zone for the Office 365 servers location.&lt;/P&gt;&lt;P&gt;For example here’s an Office 365 users read receipt from a recipient in Australia:&lt;/P&gt;&lt;PRE&gt;Your message &lt;BR /&gt;To: &lt;BR /&gt;Subject: Test&lt;BR /&gt;Sent: Monday, February 13, 2012 9:08:27 PM (UTC) Monrovia, Reykjavik&lt;BR /&gt;was read on Monday, February 13, 2012 9:07:50 PM (UTC) Monrovia, Reykjavik.&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Both places have the same time zone settings and are top of the time zone list in Windows, which is why it shows up as the default. Reykjavik is a nice place (great soft serve ice-cream) but it’s nowhere near where the sender or recipient are located. Monrovia is the capital of Liberia on the west coast of Africa (not the one in California).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Depending on who you ask, this is either a bug or Office 365 acting ‘as expected’. Naturally Microsoft staff will tell you there’s no problem.&lt;/P&gt;&lt;P&gt;To paying customers it’s a bug and worse, a bug with no fix.&lt;/P&gt;&lt;P&gt;There is false hope given with&amp;nbsp;&lt;A target="_blank" href="http://office-watch.com/?1662"&gt;a time zone change to Outlook Web Apps&lt;/A&gt;&amp;nbsp;but that doesn’t fix the email tracking bug.&lt;/P&gt;&lt;P&gt;The problem is in the design of Exchange Server. Office 365 runs Exchange Server in what Microsoft calls a ‘multi-tenanted’ environment meaning the one server handles email for many separate organizations. This is a change from the way Exchange Server was originally designed and developed for many years; i.e. under the presumption that each server handled a single organization. The consequences of change to multi-tenant use hasn’t been fully handled by Microsoft. It seems Exchange Server relies on the time zone setting of the server with no ability for the organization/tenant to customize that.&lt;/P&gt;&lt;P&gt;Now a single Exchange Server can process messages for different organizations in a range of time zones but Microsoft hasn't added all the necessary features to cope.&amp;nbsp; It's an example of Microsoft curious but long-standing corporate reluctance to deal with time zone related matters.&lt;/P&gt;&lt;P&gt;Since this may be a deep-seated issue in Exchange Server it might not be changed very quickly and even then it will be reluctantly done by Microsoft.&lt;/P&gt;&lt;P&gt;All an Office 365 user can do is&amp;nbsp;&lt;A target="_blank" href="http://mymfe.microsoft.com/Microsoft%20Online%20Services/Feedback.aspx?formID=210"&gt;complain to Microsoft&lt;/A&gt;&amp;nbsp;then wait, hope someone will read the complaints and take action.&lt;/P&gt;</description>
      <pubDate>Mon, 03 Feb 2014 21:13:06 GMT</pubDate>
      <guid>https://business.forums.bt.com/t5/Email-and-hosting/Read-Receipt-as-UTC-Monrovia-Reykjavik-BT-please-refund-our/m-p/71084#M9786</guid>
      <dc:creator>minalo1</dc:creator>
      <dc:date>2014-02-03T21:13:06Z</dc:date>
    </item>
    <item>
      <title>Re: Read Receipt as UTC Monrovia/Reykjavik BT please refund our exchange charges?</title>
      <link>https://business.forums.bt.com/t5/Email-and-hosting/Read-Receipt-as-UTC-Monrovia-Reykjavik-BT-please-refund-our/m-p/71206#M9787</link>
      <description>&lt;P&gt;so you want BT To refund your Exchange cost, because you don't like to convert UTC time???&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I don't actually see a fault..I see a Slight annoyence for you, doesn't bother me, i can't see it bothering that many people, espically seen as Read Recipts are Pointless,&lt;/P&gt;</description>
      <pubDate>Wed, 12 Feb 2014 10:43:01 GMT</pubDate>
      <guid>https://business.forums.bt.com/t5/Email-and-hosting/Read-Receipt-as-UTC-Monrovia-Reykjavik-BT-please-refund-our/m-p/71206#M9787</guid>
      <dc:creator>Plumly</dc:creator>
      <dc:date>2014-02-12T10:43:01Z</dc:date>
    </item>
    <item>
      <title>Re: Read Receipt as UTC Monrovia/Reykjavik BT please refund our exchange charges?</title>
      <link>https://business.forums.bt.com/t5/Email-and-hosting/Read-Receipt-as-UTC-Monrovia-Reykjavik-BT-please-refund-our/m-p/71833#M9788</link>
      <description>&lt;P&gt;I guess if you are not bothered then the rest of the world can sleep safely then, and since you are so obliged to accept faulty software on my behalf!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 15 Mar 2014 23:32:11 GMT</pubDate>
      <guid>https://business.forums.bt.com/t5/Email-and-hosting/Read-Receipt-as-UTC-Monrovia-Reykjavik-BT-please-refund-our/m-p/71833#M9788</guid>
      <dc:creator>minalo1</dc:creator>
      <dc:date>2014-03-15T23:32:11Z</dc:date>
    </item>
    <item>
      <title>Re: Read Receipt as UTC Monrovia/Reykjavik BT please refund our exchange charges?</title>
      <link>https://business.forums.bt.com/t5/Email-and-hosting/Read-Receipt-as-UTC-Monrovia-Reykjavik-BT-please-refund-our/m-p/80873#M9789</link>
      <description>&lt;P&gt;I need the READ RECEIPTS for court as I am building a case to show the person indeed READ my emails and is ignoring me.&amp;nbsp; &amp;nbsp; The timestamp is a SERIOUS ISSUE - how do i fix it?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 04 Sep 2018 00:48:53 GMT</pubDate>
      <guid>https://business.forums.bt.com/t5/Email-and-hosting/Read-Receipt-as-UTC-Monrovia-Reykjavik-BT-please-refund-our/m-p/80873#M9789</guid>
      <dc:creator>akristy</dc:creator>
      <dc:date>2018-09-04T00:48:53Z</dc:date>
    </item>
    <item>
      <title>Re: Read Receipt as UTC Monrovia/Reykjavik BT please refund our exchange charges?</title>
      <link>https://business.forums.bt.com/t5/Email-and-hosting/Read-Receipt-as-UTC-Monrovia-Reykjavik-BT-please-refund-our/m-p/80874#M9790</link>
      <description>&lt;P&gt;IS THERE A FIX YET?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is a serious issue for me, as i am building a court case against someone and trying to prove that they are indeed reading my emails yet ignoring me.&amp;nbsp; &amp;nbsp; The timestamp is a problem and it is seriously poor of Microsoft to release such junk for us to bug fix for them.&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 04 Sep 2018 00:50:55 GMT</pubDate>
      <guid>https://business.forums.bt.com/t5/Email-and-hosting/Read-Receipt-as-UTC-Monrovia-Reykjavik-BT-please-refund-our/m-p/80874#M9790</guid>
      <dc:creator>akristy</dc:creator>
      <dc:date>2018-09-04T00:50:55Z</dc:date>
    </item>
    <item>
      <title>Re: Read Receipt as UTC Monrovia/Reykjavik BT please refund our exchange charges?</title>
      <link>https://business.forums.bt.com/t5/Email-and-hosting/Read-Receipt-as-UTC-Monrovia-Reykjavik-BT-please-refund-our/m-p/80876#M9791</link>
      <description>&lt;P&gt;Hey&amp;nbsp;akristy,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you have set the Office 365 timezone correctly for your mailbox via the &lt;A href="https://outlook.office.com/owa/?path=/options/regional" target="_blank"&gt;Office 365 Timezone Settings page&lt;/A&gt;&amp;nbsp;then you're best contacting Microsoft's Office 365 support directly to let them know that the timestamp is showing incorrect on read receipts.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This shouldn't be an issue however as you can just convert the timezone that appears on the read receipt to figure out the exact date/time read. I don't think this is concrete evidence to bring to court though because the user can simply refuse to accept the read receipt once your email appears in their inbox.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks, Bobby&lt;/P&gt;</description>
      <pubDate>Tue, 04 Sep 2018 12:14:36 GMT</pubDate>
      <guid>https://business.forums.bt.com/t5/Email-and-hosting/Read-Receipt-as-UTC-Monrovia-Reykjavik-BT-please-refund-our/m-p/80876#M9791</guid>
      <dc:creator>Bobby</dc:creator>
      <dc:date>2018-09-04T12:14:36Z</dc:date>
    </item>
  </channel>
</rss>

