Junio C Hamano <junkio@cox.net> wrote:
quoted text
> One thing that people need to be careful about is which SMTP
> server they use.  I had an impression (I do not use send-email
> myself) that it defaulted to local MTA, so the mail trail would
> look like your local MTA receives from the MUA (which is
> send-email), which forwards it to whereever destination (or
> intermediaries).  On the other hand, I suspect many people use
> their ISP's SMTP server when using their usual MUA, so the mail
> trail would look different.  I do not know what filtering vger
> does, but if it is filtering based on the MTA address
> (dul.dnsbl.sorbs filtering comes to mind), that would make a
> difference.

I'm pretty sure the last time I tried git-send-email I had the
MTA path exactly the same.  My mutt sends to `localhost`, which
forwards over an SSL channel to my colo'd spearce.org mail server,
and that relays to the final destination.  Hence spearce.org mail
always originates from spearce.org.

Now I ran git-send-email on a different system, but had it connect
over SMTP to port 25 of the same system mutt runs on, so the
initial Received line was different, but othewrise the mail path
was the same.

I also have a few other addresses that I can send to that will go
out the spearce.org colo'd box to another SMTP system, then bounce
back, and the round-trip was the same for anything from mutt and
from git-send-email.

I marked the whole mess up to some mail header difference that
git-send-email wasn't sending the same way mutt was, and that vger
cared about. I didn't see the difference easily.  I just gave up.
;-)

-- 
Shawn.
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html