public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: cyg Simple <cygsimple@gmail.com>
To: cygwin@cygwin.com
Cc: overseers@sourceware.org
Subject: Re: cygwin Digest 27 Mar 2018 08:53:38 -0000 Issue 10744
Date: Fri, 20 Apr 2018 15:01:00 -0000	[thread overview]
Message-ID: <6727d6e6-3010-bbf1-daf0-90a991e45a7b@gmail.com> (raw)
In-Reply-To: <634051d4-2aca-e925-c6b3-2f65140406ca@gmail.com>

On 4/18/2018 2:45 AM, Marco Atzeri wrote:
> On 4/18/2018 3:15 AM, Stephen Lyons wrote:
>> On 27/03/2018 09:53, cygwin-digest-help@cygwin.com wrote:
> 
>>
>> For unusual reasons I was looking at my EMail on a Windows PC and it's
>> Anti-Virus (AVG Free) detected a Win32:Malware-gen infection in the file
>> Inquiry.exe inside Inquiry.gz inside the third message of this digest
>> (Issue: 10744) - given that that was a spam message anyhow, is such
>> *malicious* junk common in this mailing list?  Is it was just that I
>> happened to be using a vulnerable platform (i.e. Windows) whereas I
>> normally lurk from a *nix one that means I'm encountering something that
>> Windows/Cygwin users see frequently here?
>>
>> Stephen
>>
> 
> We have noted an increase of SPAM and some are passing through the
> filters of the mailing list.
> 
> It is usually not common but in my experience gmail is rejecting
> 5-10 mail per year from the mailing list due to dangerous attachment.
> 

Yes and then the bounced mail causes the sourceware.org mail system to
send a probe mail to see if my mail account is still active.  Which is
annoying.

I've CC overseers to see if we can come with a solution to this issue.

-- 
cyg Simple

           reply	other threads:[~2018-04-20 15:01 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <634051d4-2aca-e925-c6b3-2f65140406ca@gmail.com>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6727d6e6-3010-bbf1-daf0-90a991e45a7b@gmail.com \
    --to=cygsimple@gmail.com \
    --cc=cygwin@cygwin.com \
    --cc=overseers@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).