From: Pete Zaitcev <zaitcev@redhat.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Project Hail List <hail-devel@vger.kernel.org>
Subject: Re: [Patch 2/3] chcli cleanup: gcc warning
Date: Tue, 2 Mar 2010 19:41:50 -0700 [thread overview]
Message-ID: <20100302194150.30eddb80@redhat.com> (raw)
In-Reply-To: <4B8DC6F0.7080703@garzik.org>
On Tue, 02 Mar 2010 21:18:24 -0500
Jeff Garzik <jeff@garzik.org> wrote:
> Note that your mailer is mangling patches via "quoted-printable":
No, it does not. Look at this:
[zaitcev@lembas ~]$ grep fstat Mail/inbox/*
Mail/inbox/10891:# diffstat add_function.patch hub_revision_ACPI_modes.patch
Mail/inbox/15830:- rc =3D fstat(fd, &stat);
Mail/inbox/15830:+ rc =3D fstat(fd, &st);
Mail/inbox/15833:- rc = fstat(fd, &stat);
Mail/inbox/15833:+ rc = fstat(fd, &statb);
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: quoted-printable
> [...]
> =20
> - rc =3D fstat(fd, &stat);
> + rc =3D fstat(fd, &st);
> if (rc) {
Clearly, its your own message you are complaining about, not mine,
because my patch changed the variable to 'statb' (and it's not
corrupt, see above grep), while your patch changed to it to 'st'.
"My mailer" did not even touch it. Heck, I did not even see that
message (although I did a git pull to see if the "note" you promised
was attached to the changelog).
> > Received-SPF: fail (google.com: domain of zaitcev@redhat.com does not designate 207.234.209.181 as permitted sender) client-ip=207.234.209.181;
> > Authentication-Results: mx.google.com; spf=hardfail (google.com: domain of zaitcev@redhat.com does not designate 207.234.209.181 as permitted sender) smtp.mail=zaitcev@redhat.com
>
> If I had to guess, I would say you are sending redhat.com mail from a
> non-redhat-spf-authenticating box. Being a Red Hatter myself, I have no
> clue how to fix this, and would just ignore it ;-)
LOL.
1. http://david.woodhou.se/why-not-spf.html
2. No, I do not send work mail through direct SMTP connections.
What you see is exactly why SPF is harmful shit:
step 1: I send mail to list
step 2: vget forwards it to your MX:
[zaitcev@lembas ~]$ host -t mx garzik.org
garzik.org mail is handled by 10 mx1.dvmed.net.
[zaitcev@lembas ~]$ host mx1.dvmed.net.
mx1.dvmed.net has address 207.234.209.181
step 3: your redirector at srv1.dvmed.net forwards it to Google
step 4: Google Mail is run by morons who implement SPF checking
Cheers,
-- Pete
next prev parent reply other threads:[~2010-03-03 2:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 2:08 [Patch 2/3] chcli cleanup: gcc warning Pete Zaitcev
2010-03-03 2:18 ` Jeff Garzik
2010-03-03 2:41 ` Pete Zaitcev [this message]
2010-03-03 11:45 ` Jeff Garzik
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=20100302194150.30eddb80@redhat.com \
--to=zaitcev@redhat.com \
--cc=hail-devel@vger.kernel.org \
--cc=jeff@garzik.org \
/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