You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Giuseppe Scelsi <gi...@analog.com> on 2006/09/15 02:02:51 UTC

"Precedence: bulk" header in mailer.py

Hi all,

I have just found that notification messages sent by
"/trunk/tools/hook-scripts/mailer/mailer.py" do not have any feature
that lets an out-of-office responder realize they are not to be replied
to.  So I added a "Precedence: bulk" header in my copy of mailer.py and
that solved the problem for me (I am using "vacation" under Solaris.)

Anybody agrees this is a feature worth adding to mailer.py?

Cheers,

Giuseppe

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: "Precedence: bulk" header in mailer.py

Posted by Justin Erenkrantz <ju...@erenkrantz.com>.
On 9/18/06, Karl Fogel <kf...@google.com> wrote:
> In a post earlier today, Justin Erenkrantz gave some reasons why we
> shouldn't:

Note that I'm not against the feature per se, but I'm against it being
the default for the reasons I described.  Now, whether we think it's
ideal to add a knob for this is beyond my little brain to comprehend.
=)  -- justin

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: "Precedence: bulk" header in mailer.py

Posted by Karl Fogel <kf...@google.com>.
Giuseppe Scelsi <gi...@analog.com> writes:
> I have just found that notification messages sent by
> "/trunk/tools/hook-scripts/mailer/mailer.py" do not have any feature
> that lets an out-of-office responder realize they are not to be replied
> to.  So I added a "Precedence: bulk" header in my copy of mailer.py and
> that solved the problem for me (I am using "vacation" under Solaris.)
>
> Anybody agrees this is a feature worth adding to mailer.py?

In a post earlier today, Justin Erenkrantz gave some reasons why we
shouldn't:

  > "Justin Erenkrantz" <ju...@erenkrantz.com> writes:
  >> For example, I'm telling it to send the commit as me and it's
  >> configured to send the commit emails to myself and a bunch of
  >> colleagues.  One of those colleagues (call him John) is on vacation
  >> and set up vacation.  Now, if 'vacation' has already informed me that
  >> John is away, it won't notify me again.  However, if 'vacation' hasn't
  >> done that yet, it'll send me an email that John is gone.  That's good.
  >> I now know that John won't be reviewing my commit.  This is ideal for
  >> small groups which don't justify the overhead of a mailing list.
  >>
  >> Now, if you really want bulk precedence, you should just set up a list
  >> and point the mailer at it - most list managers will add the
  >> precedence header by default.  But, if you send it to a bunch of
  >> people directly (sans list), the intention (to me) is that you want to
  >> know if they won't read that commit message.  In either of those
  >> 'normal' cases, mailer shouldn't add the header.  Note that some
  >> mailing lists are configured to reject emails if the Precedence: Bulk
  >> header is already set in an attempt to limit spam - so doing so might
  >> cause those commits to be rejected.  -- justin
  > 
  > *nod* I'll buy that.  And the second paragraph describes a better
  > solution than setting this as a default in mailer.py.
  > 
  > Thanks for taking the time to write it up,
  > -Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org