Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Fri, 5 Mar 2004 12:18:29 -0600 From: Gregory Borota Reply-To: cygwin@cygwin.com To: cygwin@cygwin.com Subject: Re: Email Mangling In-Reply-To: <20040305151120.GC4036@redhat.com> Message-ID: References: <20040305151120.GC4036@redhat.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Note-from-DJ: This may be spam http://cygwin.com/ml/cygwin/2004-03/msg00245.html http://cygwin.com/cgi-bin/get-raw-msg?listname=cygwin&date=2004-03&msgid=Pine.CYG.4.58.0403041424140.812%40lap On Fri, 5 Mar 2004, Christopher Faylor wrote: > On Fri, Mar 05, 2004 at 08:12:29AM -0500, Igor Pechtchanski wrote: > >On Fri, 5 Mar 2004, Gregory Borota wrote: > >>Looking at the headers for a message I sent recently (id 89248) I see > >>that my email address was not mutilated in the Received: field. If one > >>uses SBC Yahoo's smtp server he has his email address as username. > >> > >>If this is a very isolated incident then maybe nobody should bother. > >>If not maybe it should. I personally no longer care, I changed the > >>smtp server, just wanted to point this out (don't know if this subject > >>already discussed, too many hits for sbc yahoo if googling the > >>archive). > > > >Since the raw text is generated by a CGI script, steps could be taken > >to block spam harvesters from even seeing it... OTOH, it might be > >easier to just run the substitution on the Received: header... > > Since 89248 is not a URL, I am not sure what we're talking about here. > I looked at a couple of messages and don't see anything other than > cygwin@cygwin.com in the received lines, which sort of makes sense. > > cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/