From: Georgi Chorbadzhiyski <gf@unixsol.org>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] send-mail: Add option to sleep between sending each email.
Date: Thu, 08 Sep 2011 12:11:20 +0300 [thread overview]
Message-ID: <4E6886B8.8080902@unixsol.org> (raw)
In-Reply-To: <CALkWK0kH+pD6ymtt9oWLhT0Bftp4EvtrwTtNVw6mjX0aObb-BQ@mail.gmail.com>
Around 09/08/2011 11:43 AM, Ramkumar Ramachandra scribbled:
> Hi Georgi,
>
> Georgi Chorbadzhiyski writes:
>> Sometimes when sending lots of changes it is not nice
>> to send emails as fast as possible. Of course you can
>> confirm each email after waiting couple of seconds but
>> this is not optimal. This patch adds --sleep option
>> to git-send-mail and corresponding sendmail.sleep config
>> variable to control how much seconds to wait between
>> sending each email. The default is 0 (not wait at all).
>
> I use git-send-email a lot, and I ask it to print out the list of all
> emails once before confirming. After confirming, I just switch back
> to Emacs and continue work- in the many instances, I've never actually
> needed to slow the process down. If anything, I wished it could
> concurrently send many emails and do things /faster/ *. I'm a little
> curious about why you want to slow it down- is your SMTP server
> configured to block you because it suspects that you're trying to
> spam?
>
> Thanks.
>
> * I first need to see if SMTP servers today can take in emails at this
> speed without suspecting spam.
It is not the mail server, it is workaround mainly for web archives and
MUAs that look at received dates when sorting threads.
When they receive a lot of email in one thread very quickly (and out of
order) they do not thread correctly.
See for example this: http://mailman.videolan.org/pipermail/dvblast-devel/2011-August/thread.html
The thread named: [dvblast-devel] [PATCH 0/4] Post git migration changes
See how 1,3,4/4 are not detected to be part of the thread even when
all headers are set correctly by git-send-email.
Probably my mail server send them out of order and that is why I have
the idea to introduce some small delay between sending each email. Easier
on the MTA, works around the possibility to send emails out of order
the flip side is that it takes more time.
--
Georgi Chorbadzhiyski
http://georgi.unixsol.org/
prev parent reply other threads:[~2011-09-08 9:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-07 20:43 [PATCH] send-mail: Add option to sleep between sending each email Georgi Chorbadzhiyski
2011-09-08 8:43 ` Ramkumar Ramachandra
2011-09-08 9:03 ` Matthieu Moy
2011-09-08 9:28 ` Ramkumar Ramachandra
2011-09-08 9:35 ` Ramkumar Ramachandra
2011-09-08 10:44 ` Ramkumar Ramachandra
2011-09-08 10:57 ` Georgi Chorbadzhiyski
2011-09-08 11:15 ` Matthieu Moy
2011-09-08 13:58 ` Georgi Chorbadzhiyski
2011-09-08 14:07 ` Georgi Chorbadzhiyski
2011-10-03 20:17 ` Jakub Narebski
2011-09-08 17:14 ` Georgi Chorbadzhiyski
2011-09-08 17:12 ` Junio C Hamano
2011-09-08 20:50 ` Matthieu Moy
2011-09-09 2:12 ` mfwitten
2011-09-12 5:34 ` Ramkumar Ramachandra
2011-09-08 9:11 ` Georgi Chorbadzhiyski [this message]
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=4E6886B8.8080902@unixsol.org \
--to=gf@unixsol.org \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).