X-Recipient: archive-cygwin@delorie.com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=TkkfE0rWxSSLF7tEb4/4Q/+f/wHBg0R1vD5WbYjcesbtiLr5tiVrN
	blFm2PkJOC10DSX3HmGeyYW21c5ItL6fldpBusq8wzvV2Tna/XLnWyhAm2ZqIuRl
	neo65ha2hFroKD9qwc4UBYhNvDOuC9nm8WNaz5zTeMNUM4C06c6U58=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	 bh=+YifXAojqmddndmRHnEHL9z4ly0=; b=GotYIzXFwEauKYRigpei5eMo3HwI
	3fwW67etuAh3RRDvWF4Z9qtyH/DMybFmC4cGiTB3Woh7ToDMnIpMNmhuNKDTSkjE
	iGN1s4ryCwiBLTYB3ZIttJYVnzljM2yLdec3rnb5x0iRZ/3MZULzv+0ADTKInc/z
	W9e7FRutMinfGG8=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO: mho-02-ewr.mailhop.org
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX1/uNbwZuNE5EzwGuXdW1wnO
Date: Thu, 20 Feb 2014 10:36:45 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: $PATH contains dot but unclear where it comes from
Message-ID: <20140220153645.GB7958@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <5304E874.20906@cygwin.com> <CAM9pMnOfTto2QodJeWiEGdLCEPOKHd=_83GFvUzim6d=Rt0V2w@mail.gmail.com> <5304FB23.3000005@cygwin.com> <1369691347.20140219231051@yandex.ru> <530506C9.6040408@cygwin.com> <53050C58.6000008@hones.org.uk> <87ob22n902.fsf@Rainer.invalid> <53051EE4.20803@cygwin.com> <937868018.20140220022304@yandex.ru> <CAM9pMnO0ZvjBt_hVK_d=4igUu9nzG=HN=6ZK0tF86SvYEjRpiA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAM9pMnO0ZvjBt_hVK_d=4igUu9nzG=HN=6ZK0tF86SvYEjRpiA@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)

On Thu, Feb 20, 2014 at 03:12:47PM +0100, Robert Klemme wrote:
>Thanks to all who helped so far!
>
>On Wed, Feb 19, 2014 at 11:23 PM, Andrey Repin <anrdaemon@yandex.ru> wrote:
>
>> So far, I'm not convinced that issue is Cygwin-specific. The fact that it
>> doesn't manifest in Windows is actually because of it's (windows) native
>> ignorance for this matter.
>
>I sent a lengthy email with all the detailed shell outputs earlier but
>it was blocked by spam filter. :-(

i.e.,
DONT_USE_RAW_EMAIL_IN_BODY
UNWANTED_LANGUAGE_BODY
ZIP_ATTACHED

The "ZIP_ATTACHED" was enough to cause it to be interpreted as spam but
the "raw email" block made it even more blockable.

But, of course, the cygwin mailing list is not the place to complain
about being blocked.

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

