public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Nellis, Kenneth" <Kenneth.Nellis@xerox.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: malware
Date: Thu, 09 Jun 2016 15:08:00 -0000	[thread overview]
Message-ID: <0D835E9B9CD07F40A48423F80D3B5A7039D920C3@USA7109MB022.na.xerox.net> (raw)

Dear Cygwin,
A little supposition here, but it appears that the recent posting 
from Viverra Inc. contained a malicious attachment, as detected by 
my company's e-mail malware detection as it intercepted the recent 
digest. I need now to appeal to them to allow me to continue 
receiving e-mail from you. Cygwin has provided me invaluable tools 
to do my software development work, so I hope this matter is 
resolved promptly with my company. Meanwhile I ask that you review 
your spam detection to minimize impact on me and others in my 
situation.
--Ken Nellis

--
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

             reply	other threads:[~2016-06-09 15:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-09 15:08 Nellis, Kenneth [this message]
2016-06-09 15:49 ` malware Marco Atzeri
     [not found]   ` <CAKepmajx8LtDyYun-++CPaSuUMZsEQMKe=P2=JSgZwv36HvmOg@mail.gmail.com>
2016-06-09 15:52     ` malware Jack Adrian Zappa
2016-06-09 16:02       ` malware Marco Atzeri
2016-06-09 16:14         ` malware Corinna Vinschen
2016-06-09 17:19           ` malware Erik Soderquist
2016-06-09 17:49           ` malware David Stacey
2016-06-10  4:18             ` malware Mike Fahlbusch
2016-06-10  1:20           ` malware Andrey Repin

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=0D835E9B9CD07F40A48423F80D3B5A7039D920C3@USA7109MB022.na.xerox.net \
    --to=kenneth.nellis@xerox.com \
    --cc=cygwin@cygwin.com \
    /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).