From: mark gross <mgross@linux.intel.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH v2 0/2] v2: more sampling fun 0
Date: Tue, 25 Feb 2020 13:51:30 -0800 [thread overview]
Message-ID: <20200225215130.GA111853@mtg-dev.jf.intel.com> (raw)
In-Reply-To: <87zhd6iecx.fsf@nanos.tec.linutronix.de>
On Tue, Feb 25, 2020 at 09:47:10PM +0100, speck for Thomas Gleixner wrote:
> speck for mark gross <speck@linutronix.de> writes:
>
> > On Tue, Feb 25, 2020 at 10:55:30AM -0600, speck for Josh Poimboeuf wrote:
> >> On Mon, Feb 24, 2020 at 01:45:10PM -0800, speck for mark gross wrote:
> >> > From: mark gross <mgross@linux.intel.com>
> >> > Subject: [PATCH v2 0/2] more sampling fun
> >>
> >> It looks like the actual patches didn't come through?
> >
> > Heavy sigh....
> >
> > I have nothing but badd luck with this. I updated my .gitconfig on the new
> > workstation to use mgross@linux.intel.com and I git commit --ammend ed the
> > commit I thought was blocked because it had an author of mark.gross@intel.com
> > instead of the other one.
>
> I put an alias in, so both addresses work on the list.
>
> > I assume they are getting held up by something on the list server end but, I
> > have no idea what I'm doing to piss it off. :(
> >
> > If anyone could help clue me in I'll try to correct whatever I'm doing wrong.
> > The other two patches where sent using the same process:
> >
> > * git format-patch -o mail -n --to speck@linutronix.de --thread --cover-letter v5.6-rc3
> > * speckify-gitmail -s "more sampling fun" mail/ spec/
> > * for b in `ls`; do sendmail -t -i -f smtp.intel.com <$b; done
>
> Which looks about correct, but then the receiving end says:
>
> 2020-02-24 22:57:31 1j6LjH-00076x-B2 <= smtp.intel.com@mtg-dev.jf.intel.com H=mga11.intel.com [192.55.52.93] P=esmtps X=TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256 S=3729 id=cover.1582580710.git.mgross@linux.intel.com
> 2020-02-24 22:57:32 1j6LjH-00076x-B2 => crypto-ml <speck@linutronix.de> R=local_user T=mail_spool
> 2020-02-24 22:57:32 1j6LjH-00076x-B2 Completed
>
> That's the cover letter. And then the other two seem to be broken:
>
> 2020-02-24 22:57:32 H=mga07.intel.com [134.134.136.100] sender verify fail for <smtp.intel.com@mtg-dev.jf.intel.com>: Unrouteable address
> 2020-02-24 22:57:32 H=mga07.intel.com [134.134.136.100] F=<smtp.intel.com@mtg-dev.jf.intel.com> rejected RCPT <speck@linutronix.de>: Sender verify failed
>
> 2020-02-24 22:57:32 H=mga06.intel.com [134.134.136.31] sender verify fail for <smtp.intel.com@mtg-dev.jf.intel.com>: Unrouteable address
> 2020-02-24 22:57:32 H=mga06.intel.com [134.134.136.31] F=<smtp.intel.com@mtg-dev.jf.intel.com> rejected RCPT <speck@linutronix.de>: Sender verify failed
>
> Now, looking at your sendmail command line:
>
> -t -i -f smtp.intel.com
>
> -f is the envelope sender address. smtp.intel.com is definitely not a
> valid envelope-from address, it's a hostname and it looks like sendmail
> magically makes that into:
doh, thats likely my problem! I changed it to mgross@linux.intel.com and am
retrying.
>
> envelope-from <smtp.intel.com@mtg-dev.jf.intel.com>
>
> and that mtg-dev.jf.intel.com is probably your host name:
>
> mtg-dev . Jones Farm . intel.com
All true.
>
> which is bonkers to begin with because I'm pretty sure that nothing can
> send mail to that address.
>
> Now in the cover letter the From: field is correct:
>
> From: mark gross <mgross@linux.intel.com>
>
> but I'm pretty sure, that your other two mails are malformatted and
> sendmail throws your bonkers -f "address" at it which causes the sender
> verify to fail.
>
> And of course because your envelope-from is broken, the bounce (reject)
> info does not make it to you.
>
> May I recommend to check the mails in mail/ and spec/ before sending
> them out. You can also check them for a valid From: address after the
> fact of course :)
>
> BOFH excuse #208:
>
> Your mail is being routed through Germany ... and they're censoring us.
Thanks!
--mark
next prev parent reply other threads:[~2020-02-25 21:51 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 21:45 [MODERATED] [PATCH v2 0/2] v2: more sampling fun 0 mark gross
2020-01-16 22:16 ` [MODERATED] [PATCH v2 2/2] v2: more sampling fun 2 mark gross
2020-02-06 22:11 ` [MODERATED] [PATCH v2 1/2] v2: more sampling fun 1 mark gross
2020-02-25 16:55 ` [MODERATED] Re: [PATCH v2 0/2] v2: more sampling fun 0 Josh Poimboeuf
2020-02-25 17:43 ` mark gross
2020-02-25 20:47 ` Thomas Gleixner
2020-02-25 21:51 ` mark gross [this message]
[not found] ` <5e5595e6.1c69fb81.69e80.2880SMTPIN_ADDED_BROKEN@mx.google.com>
2020-02-26 7:27 ` [MODERATED] Re: [PATCH v2 2/2] v2: more sampling fun 2 Greg KH
2020-02-26 18:02 ` mark gross
2020-02-26 11:07 ` [MODERATED] Re: [PATCH v2 1/2] v2: more sampling fun 1 Borislav Petkov
2020-02-26 17:11 ` mark gross
2020-02-26 17:59 ` Borislav Petkov
2020-02-26 18:16 ` Thomas Gleixner
2020-02-26 22:13 ` [MODERATED] " mark gross
2020-02-26 23:53 ` Thomas Gleixner
2020-02-27 16:43 ` [MODERATED] " mark gross
2020-02-26 22:11 ` mark gross
2020-02-26 22:43 ` Borislav Petkov
2020-02-26 23:34 ` mark gross
2020-02-26 18:55 ` Thomas Gleixner
2020-02-26 22:23 ` [MODERATED] " mark gross
2020-02-26 21:13 ` Andi Kleen
2020-02-26 22:01 ` Thomas Gleixner
2020-02-27 7:08 ` [MODERATED] " Greg KH
2020-02-26 11:46 ` [MODERATED] Re: [PATCH v2 2/2] v2: more sampling fun 2 Borislav Petkov
2020-02-26 17:35 ` mark gross
2020-02-26 18:13 ` Borislav Petkov
2020-02-26 22:37 ` mark gross
2020-02-26 22:50 ` Borislav Petkov
2020-02-26 23:42 ` mark gross
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=20200225215130.GA111853@mtg-dev.jf.intel.com \
--to=mgross@linux.intel.com \
--cc=speck@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.