All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, Paul Gortmaker <paul.gortmaker@windriver.com>
Subject: Re: [RFC/PATCH 2/2] git-send-email: Do not require that addresses added from  body be valid
Date: Sat, 7 May 2011 15:21:05 +0200	[thread overview]
Message-ID: <201105071521.06344.jnareb@gmail.com> (raw)
In-Reply-To: <201105051601.46012.jnareb@gmail.com>

On Thu, 5 May 2011, Jakub Narebski wrote:

>                 $smtp->to( @recipients ) or die $smtp->message;
> +               $smtp->to( @recipients_extra, { Notify => ['NEVER'], SkipBad => 1 });
                                                  ^^^^^^^^^^^^^^^^^^^^

Note: contrary to what I thought this doesn't mean to not send any
notification request, but to send DSN (Delivery Status Notification)
request of 'NEVER'.  For example when using smtp.gmail.com gives:

  Net::SMTP::recipient: DSN option not supported by host at ./git-send-email line 1140

So the underlined part has to be removed.

-- 
Jakub Narebski
Poland

      parent reply	other threads:[~2011-05-07 13:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-14 20:10 RFC: git send-email and error handling Paul Gortmaker
2011-04-14 21:09 ` Jeff King
2011-04-15  0:30   ` Paul Gortmaker
2011-04-15  3:42     ` Jeff King
2011-05-04 16:12       ` [RFC/PATCH] git-send-email: Remember sources of Cc addresses Jakub Narebski
2011-05-04 21:35         ` Jeff King
2011-05-05 14:01           ` [RFC/PATCH 2/2] git-send-email: Do not require that addresses added from body be valid Jakub Narebski
2011-05-06 11:22             ` [RFC/PATCH 3/2 (squash!)] git-send-email: Warn about rejected automatically added recipients Jakub Narebski
2011-05-07 13:21             ` Jakub Narebski [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=201105071521.06344.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=paul.gortmaker@windriver.com \
    --cc=peff@peff.net \
    /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.