From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 64009 invoked by alias); 16 Aug 2019 21:02:07 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 64001 invoked by uid 89); 16 Aug 2019 21:02:07 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-6.2 required=5.0 tests=AWL,BAYES_00,GIT_PATCH_2 autolearn=ham version=3.3.1 spammy=authorization, mails, compose, dangerous X-HELO: Ishtar.sc.tlinx.org Received: from ishtar.tlinx.org (HELO Ishtar.sc.tlinx.org) (173.164.175.65) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 16 Aug 2019 21:02:05 +0000 Received: from [192.168.3.12] (Athenae [192.168.3.12]) by Ishtar.sc.tlinx.org (8.14.7/8.14.4/SuSE Linux 0.8) with ESMTP id x7GL21k4069884; Fri, 16 Aug 2019 14:02:04 -0700 Message-ID: <5D5719CA.60108@tlinx.org> Date: Fri, 16 Aug 2019 21:17:00 -0000 From: L A Walsh User-Agent: Thunderbird MIME-Version: 1.0 To: davidmichaelkarr@gmail.com CC: cygwin@cygwin.com Subject: FYI: Google deleting/blocking incoming mails (was Re: More on Win7 update messing up HOME) Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2019-08/txt/msg00236.txt.bz2 On 2019/08/15 19:38, David Karr wrote: > I wish I could get my own messages on this list, so I could add more > information to my first note. > ---- It's a gmail feature! As you have a gmail address, presumably you created it in gmail, which means it should be in your outgoing message folder. If that's the case, then google deletes any incoming email that it thinks is a duplicate of something you sent out (including copies that come back via a list). Of course it isn't an exact duplicate, the headers are different, but they claim only the content counts and that all their users appreciate their deleting of random incoming emails (they are full of excrement, but they believe their IQ is stratospheric, and gives them the right to ignore and set new network standards at will). I had to find a new email provider "real quick" about a year ago, and one of the requirements was that the provider not delete any incoming email from the incoming domain email stream. They claimed they deleted nothing. ... Except...: 1) incoming email that they've seen -- so if someone sends an email to you personally, and 'cc's a list you are on, only one of them will get through. They claim users (they ones that don't know how to filter email) love this simplicity and that they haven't received any complaints. *cough*. 2) if you send email out through gmail, one copy should be in your 'Sent' email, the other one coming back from a list will be deleted. 3) some spam (even if you turn off spam filtering) is classified by them as "dangerous" (either is a virus, or points to a "forbidden" site, or contains "forbidden" links (or text that they might think are links). Those will be blocked without telling you about it. 4) Other random messages that they want to block. I posted a single change description from the linux-kernel change notes to the bug-bash list that described use of a shell feature. For some reason, I never got a copy of the email even though it was wasn't composed on google. It did go to the list and arrived there in ~ 10s as verified by looking in the list archive, but I never received a copy -- abnormal, since I don't compose on google and don't have another copy on google. 5) Email marked as 'google-private or restricted' that won't go into a normal POP or IMAP email box and will only be readable (no copy/past, no forwarding, no print) and can be deleted or replaced in your email box later on, by the email-author. ---- Sometime in October, they are switching to oauth-only authorization, which is only designed to work over HTTP. Other "less secure"[sic] methods will be disabled. I'm not sure, but it seems secure IMAP (and POP) appear to fall into the 'insecure' access methods, though email passed through via 'SENDMAIL' (often/usually unencrypted) won't be affected. So if you have used gmail to collect your email and then download it all to read locally -- it's likely you will want to switch to a different provider. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple