public inbox for
 help / color / mirror / Atom feed
From: Chad Walstrom <>
Subject: Re: how to include database name in mails
Date: Mon, 18 Apr 2005 18:31:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1.1: Type: text/plain, Size: 1400 bytes --]

On Mon, Apr 18, 2005 at 09:06:45PM +0800, Lan Yufeng wrote:
> Hi, is there any way to send notification mail with database name
> set dynamically, such as:
> Subject: FooProduct cat1/pr#123
> * FooProduct is the database name.
> Because we gonna have a lot of databases, manually modify dbconfig
> for each database is time consuming.
> help! Suggestion on soucecode hacking are welcome too.

My first suggestion is to use a separate email for each database.  It
is relatively easy to tell your email server to pipe to  "queue-pr
--database DATABASE".  You could probably generate a quick sed script
to walk over the dbconfig files and insert the appropriate address.

I personally email addresses named after the database in some way.
For example, bug-DATABASE@bugs.domain.tld.  I then use procmail to
match the "To:" and "Cc:" headers for the database name and pipe it to
the appropriate queue-pr command:

# One recipe to rule them all...
* ^(To|Cc): bug-\/[_-a-zA-Z0-9]+
	:0 w
	| queue-pr --database=${DB}

	:0 e

# Or you can have separate recipes for each database
:0 w
* ^(To|Cc): PRODUCT@bug.domain.tld
| queue-pr --database=PRODUCT

:0 e

Chad Walstrom <> 
           assert(expired(knowledge)); /* core dump */

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 140 bytes --]

Help-gnats mailing list

  reply	other threads:[~2005-04-18 18:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-18 13:12 Lan Yufeng
2005-04-18 18:31 ` Chad Walstrom [this message]
2005-04-19  1:14   ` Lan Yufeng

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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 read-only IMAP folder(s) and NNTP newsgroup(s).