627686 - Thunderbird sends Spam information in email header

Status: RESOLVED INVALID

(MailNews Core :: Networking: SMTP, defect)

Description

[satisfaction]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13
Build Identifier: 

Thunderbird sends the name of my computer in the header as Received: from My Full Name-iMac.local.  How do I stop this major Spam issue.

Reproducible: Always

Steps to Reproduce:
1. send email
2. read header
3.
Actual Results:  
see line Received: from My Full Name-iMac.local

Expected Results:  
do not send this line in the header

Comment 1

[Nikolay Shopik]

Thunderbird doesn't send this information its added by SMTP server.

Comment 2

[Wolfgang Rosenauer [:wolfiR]]

Can we see the full Received header line please?
(Because parts are set by the receiving smtp daemon and others can be client/thunderbird related)

And please note that a email client has to send something for identification.
Thunderbird used the local ip address in the past (see bug 279525).
Sending the hostname is at least the real life practice in common mail useragents.

Comment 3

[satisfaction]

(In reply to comment #1)
> Thunderbird doesn't send this information its added by SMTP server.

Nikolay,  this is not totally correct.  I can send an email using the Netscape email program and this information does not appear.

Comment 4

[satisfaction]

Wolfgang, here is the whole header.  Note the line below Received From:  I have no problem sending the originating IP address.  I just don't want my full name splattered all over the web.

********************************
Received: from Joseph-Sinnigers-iMac.local ([69.141.145.27])
	by omta14.westchester.pa.mail.comcast.net with comcast
	id wfwB1f01d0bhJod3afwBTl; Mon, 17 Jan 2011 15:56:12 +0000
********************************

From - Mon Jan 17 10:56:33 2011
X-Account-Key: account1
X-UIDL: 137980.msScsnQNepeL6evRTk8,RIYx8ZQ=
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
X-Mozilla-Keys:                                                                                 
Return-Path: srs0=dvlvfu=up=bugjammer.com=[e-mail]
Received: from imta29.emeryville.ca.mail.comcast.net (LHLO
 imta29.emeryville.ca.mail.comcast.net) (76.96.27.217) by
 sz0006.wc.mail.comcast.net with LMTP; Mon, 17 Jan 2011 15:56:16 +0000 (UTC)
Received: from bosmailout03.eigbox.net ([66.96.187.3])
	by imta29.emeryville.ca.mail.comcast.net with comcast
	id wfwD1f00k04ps5N0VfwDLW; Mon, 17 Jan 2011 15:56:14 +0000
X-CAA-SPAM: F00000
X-Authority-Analysis: v=1.1 cv=iIhnutgcWA3ueUwADLcq3q7W42mKgfPkmYcsHYM9nW0=
 c=1 sm=1 a=UEGP+kE87Yd094V1csltxA==:17 a=Syi9_DNqAAAA:8
 a=eTWQAWU0iRH4Kk4U5rkA:9 a=f-h7vQzBQoCplWqqMKr7QznActcA:4 a=wPNLvfGTeEIA:10
 a=TdY6AuUNvnBfFxKbS7QA:9 a=nAhH77mXQ-m-MuzyxXYA:7
 a=tclcd6dtLQvEqt9_mmCBkF-xDgkA:4 a=UEGP+kE87Yd094V1csltxA==:117
Received: from bosmailscan08.eigbox.net ([10.20.15.8])
	by bosmailout03.eigbox.net with esmtp (Exim)
	id 1PerRF-0007oZ-7J
	for [e-mail]; Mon, 17 Jan 2011 10:56:13 -0500
Received: from bosimpinc01.eigbox.net ([10.20.13.1])
	by bosmailscan08.eigbox.net with esmtp (Exim)
	id 1PerRE-0006L5-1b
	for [e-mail]; Mon, 17 Jan 2011 10:56:12 -0500
Received: from qmta04.westchester.pa.mail.comcast.net ([76.96.62.40])
	by bosimpinc01.eigbox.net with NO UCE
	id wfwB1f03s0s5p2409fwBq8; Mon, 17 Jan 2011 10:56:11 -0500
X-EN-OrigIP: 76.96.62.40
X-EN-IMPSID: wfwB1f03s0s5p2409fwBq8
Received: from omta14.westchester.pa.mail.comcast.net ([76.96.62.60])
	by qmta04.westchester.pa.mail.comcast.net with comcast
	id wfuh1f00C1HzFnQ54fwCFK; Mon, 17 Jan 2011 15:56:12 +0000
Received: from Joseph-Sinnigers-iMac.local ([69.141.145.27])
	by omta14.westchester.pa.mail.comcast.net with comcast
	id wfwB1f01d0bhJod3afwBTl; Mon, 17 Jan 2011 15:56:12 +0000
Message-ID: <[e-mail]>
Date: Mon, 17 Jan 2011 10:56:10 -0500
From: jos <[e-mail]>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: [e-mail]
Subject: reminder january 22
Content-Type: multipart/alternative;
 boundary="------------050100090906020507070507"






(In reply to comment #2)
> Can we see the full Received header line please?
> (Because parts are set by the receiving smtp daemon and others can be
> client/thunderbird related)
> 
> And please note that a email client has to send something for identification.
> Thunderbird used the local ip address in the past (see bug 279525).
> Sending the hostname is at least the real life practice in common mail
> useragents.

Comment 5

[Wolfgang Rosenauer [:wolfiR]]

Ok, yes. This identifier is sent by Thunderbird as part of the HELO command specified in RFC821.
HELO (EHLO) is supposed to send the hostname of the machine to the receiving SMTP server. This is what Thunderbird does. The fact that it contains your name is Apple's decision though.
I'm not quite sure what to do here. Technically everything is fine but I understand the privacy concerns in your case.
Is it possible to change the hostname easily on MacOS? That would be the easiest thing.

Comment 6

[Nikolay Shopik]

Wolfgang, thanks for clearing this up. I just check on Windows, Linux and Mac OS X machine, this is default behavior for Mac OS X, while Linux and Windows still send ip address in brackets [x.x.x.x] during EHLO

Comment 7

[satisfaction]

Wolfgang, It is almost impossible to change the hostname of the machine.  You have to wipe the disk and start over.  However, I will contact Apple.  Further, I am beginning to wonder if I am perhaps wrong.  I reviewed the headers on several emails.  It seems when the email goes to the receiver in a very simple path, this does not occur.  However, when Comcast sends the email through several relays, the first relay adds this info (hostname of the machine).  I am not completely sure if it is the first  relay or simply one particular relay site.  I will have to contact Comcast about this.  This is the first time that I noticed this effect in all the years of sending email.

Comment 8

[Nikolay Shopik]

I really doubt you need to wipe disk to change your hostname, if you own this computer this is done in 3 clicks. this should help http://osxdaily.com/2007/02/15/changing-your-macs-computer-name/

Comment 9

[Ludovic Hirlimann [:Usul]]

(In reply to comment #7)
> Wolfgang, It is almost impossible to change the hostname of the machine.  You
> have to wipe the disk and start over.  However, I will contact Apple.  

It's doable without whiping the machine out by editing the proper startup script that sets the name of the machine. Can find it right now - but googling the subject should tell you how to.

Comment 10

[satisfaction]

Nikolay, It appears I may have been incorrect in my reply to you.  As seen in my reply to Wolfgang, there appears to be a relation to the sender-receiver path.  So the problem may be, not Thunderbird, but rather Mac or Comcast procedures.  





(In reply to comment #6)
> Wolfgang, thanks for clearing this up. I just check on Windows, Linux and Mac
> OS X machine, this is default behavior for Mac OS X, while Linux and Windows
> still send ip address in brackets [x.x.x.x] during EHLO

Comment 11

[Wolfgang Rosenauer [:wolfiR]]

(In reply to comment #6)
> Wolfgang, thanks for clearing this up. I just check on Windows, Linux and Mac
> OS X machine, this is default behavior for Mac OS X, while Linux and Windows
> still send ip address in brackets [x.x.x.x] during EHLO

Thunderbird tries to get the hostname. If it fails it uses the IP address as above. Usually every platform has support for hostnames but anyway, that's not the issue here.

(In reply to comment #7)
> I am beginning to wonder if I am perhaps wrong.  I reviewed the headers on
> several emails.  It seems when the email goes to the receiver in a very simple
> path, this does not occur.  However, when Comcast sends the email through
> several relays, the first relay adds this info (hostname of the machine).  I am
> not completely sure if it is the first  relay or simply one particular relay
> site.  I will have to contact Comcast about this.  This is the first time that
> I noticed this effect in all the years of sending email.

Technically your client aka Thunderbird sends an
EHLO hostname
to the server. The server decides what to do with that information. Many (all that I know) servers add the information as above to the received header:
Received: from Joseph-Sinnigers-iMac.local ([69.141.145.27])
First is your name as transmitted via the EHLO parameter and the ip address is the one which connected to the server.

Comment 12

[satisfaction]

Nikolay,  I just executed the hostname procedure you suggested with absolutely no problem.  Thank you so very, very much for your guidance.  I will monitor my next few emails to see if the problem is solved and let you know.  This seems so simple.  Again, thank you.  joe




(In reply to comment #8)
> I really doubt you need to wipe disk to change your hostname, if you own this
> computer this is done in 3 clicks. this should help
> http://osxdaily.com/2007/02/15/changing-your-macs-computer-name/