public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: green@namesys.com, linux-kernel@vger.kernel.org, flx@thebsh.namesys.com
Subject: Re: [BK] PATCH ReiserFS 1 of 3 RESEND
Date: Mon, 09 Sep 2002 19:52:26 +0400	[thread overview]
Message-ID: <3D7CC3BA.2040201@namesys.com> (raw)
In-Reply-To: Pine.LNX.4.44.0209090831240.1641-100000@home.transmeta.com

Thanks for your suggestion, we will act on it and do so.

Hans

Linus Torvalds wrote:

>Hans,
> one of the reasons for problems with your patches is that your emails 
>seem to sometimes be labeled as spam.
>
>And one of the major reasons for that is apparently simply that your 
>"From:" address is not a good one:
>
>	From: reiser@reload.namesys.com (Hans Reiser)
>
>where "reload.namesys.com" is not in the MX domain:
>
>	dig -t MX reload.namesys.com
>
>gives no answer. As a result, spam detectors look at the From: line and 
>consider you an extremely suspect person, likely to be up to no good.
>
>I would suggest you fix your mailer to have a valid MX-record return 
>address, ie <reiser@namesys.com> instead of <reiser@reload.namesys.com>.
>
>(Yes, I realize that both addresses likely work perfectly fine, and that
>"reload"  is the machine you actually use for sending the email, but
>still.. I bet I'm not the only one who uses spam filtering software that
>cares about issues like this.)
>
>[ Cc to linux-kernel left intact not to publicly castigate Hans, but 
>  because I know this is true for some other people too. ]
>
>			Linus
>
>
>
>  
>


  parent reply	other threads:[~2002-09-09 15:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-09 11:31 [BK] PATCH ReiserFS 1 of 3 RESEND Hans Reiser
2002-09-09 15:40 ` Linus Torvalds
2002-09-09 15:48   ` Tomas Szepe
2002-09-10 10:41     ` Helge Hafting
2002-09-09 15:52   ` Hans Reiser [this message]
2002-09-10  6:59   ` Kai Henningsen
2002-09-10  9:07     ` Matti Aarnio

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=3D7CC3BA.2040201@namesys.com \
    --to=reiser@namesys.com \
    --cc=flx@thebsh.namesys.com \
    --cc=green@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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