Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Fri, 5 Mar 2004 10:11:20 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Email Mangling Message-ID: <20040305151120.GC4036@redhat.com> Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i Reply-To: cygwin AT cygwin DOT com Note-from-DJ: This may be spam 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 AT cygwin DOT 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/