Hello Jack,

> The latest messages from MAU and Paul F. Siebern regarding TB! not being able 
> to
> access Gmail after March 31st reminded me that I too had received a message 
> from
> Google regarding March 31st. Only my message was to inform me of the 
> following:
> This is a reminder that on April 2, 2019 we’re shutting down consumer Google+
> and will begin deleting content from consumer Google+ accounts. Photos and
> videos from Google+ in your Album Archive and your Google+ pages will also be
> deleted.

I  also received that one, but it is different. It pertains to Google+
which,  as  you  quote,  will  be shutting down. The "March 31st" date
mentioned  in this message, is when they suggest you start downloading
your content, if you don't want to loose it.

> However, I had to manually search through several different TRASH folders to
> find the message. This is because when I tried to use TB!'s search function to
> find messages which had the string "google" in it, it always returned many 
> hits,
> most of which, if not all, did not contain that string. I used the criteria 
> "ANY
> PART" or "TEXT" or "SENDER" assuming that that's where that string would be.

I'd  bet  they *did* contain the string, most probably in the headers.
Most  of  which are not shown/displayed unless you select View/RFC-822
headers. This is so because "ANY PART" means exactly that, any part of
the  message (the whole message) even if some part(s) are not normally

> Although my message from Google did not mention TB!'s permission to fetch mail
> from Google, The March 31st deadline was contained in the message.

As  I said above, they suggest you start saving/downloading G+ content
*before* March 31st.

> That aside, does anyone know why the search function would return so many
> invalid hits? Was I doing it incorrectly?

Explained above. Most probably they were not invalid hits. 

Best regards,

Miguel A. Urech (Els Poblets (Alicante) - Spain)
Using The Bat! v8.8.2.3 (BETA)

Current version is 8.0.18 | 'Using TBUDL' information:

Reply via email to