From: "Torsten Bögershausen" <tboegi@web.de>
To: Philip Oakley <philipoakley@iee.org>,
Git MsysGit <msysgit@googlegroups.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [msysGit] Difficulties senting patches to Git list using msmpt (send-email)
Date: Mon, 3 Aug 2015 15:09:28 +0200 [thread overview]
Message-ID: <55BF6808.1000500@web.de> (raw)
In-Reply-To: <25E3342F2D4A420D8A25A1B22B5266FE@PhilipOakley>
Seems like a greylist problem ?
(I take the freedom to forward your mail to upstream git,
in the hope that somebody has has an idea)
On 03.08.15 13:13, Philip Oakley wrote:
> I'm scratching my head as to why patches I try to send upstream (git@vger.kernel.org) via my MSysGit install's send-email appear to be being dropped at gver/gmane.
>
> It's only the patches I originate via send-email, using the windows MSysGit msmtp mailer that aren't getting through. Other emails I send in reply to threads on gmane (via OE6) get through OK.
>
> I have confirmed I'm subscribed (as per FAQs), and I've also tested the auto-answer facility.
>
> The one peculiarity of the auto-answers is that the OE6 email reply had a delay:
>
> X-Greylist: delayed 592 seconds by postgrey-1.27 at vger.kernel.org; Sat, 01 Aug 2015 16:11:58 EDT
> [...]
> X-Mailer: Microsoft Outlook Express 6.00.2900.5931
>
> while msmpt did not:
> [ no X-Greylist: ]
> X-Mailer: git-send-email 2.3.1
>
> The delay may be a red-herring as it occurred on the non-problematic route, but may be an indication of some extra processing within gmane that affects the patches.
>
> I have had a reply to one of the patch emails's direct addressees ($gmane/275141), and I'd also received a copy of the patch as I'd cc'd myself, so at least the outbound routing is getting beyond my ISP.
>
> Does anyone have suggestions as to how I determine where/why my patche emails dropped into >dev/null ?
>
> --
>
> Philip
>
> PS I'm using the old msysgit infrastructure as msmpt wasn't available in the new SDK at this moment.
>
> I don't believe it's anything to do with the recompile at v2.3.1 (rather than the plain vanilla msysgit.1.9.5), but then again...
parent reply other threads:[~2015-08-03 13:09 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <25E3342F2D4A420D8A25A1B22B5266FE@PhilipOakley>]
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=55BF6808.1000500@web.de \
--to=tboegi@web.de \
--cc=git@vger.kernel.org \
--cc=msysgit@googlegroups.com \
--cc=philipoakley@iee.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 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.