From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: Sourceware Overseers <overseers@sources.redhat.com>,
"Frank Ch. Eigler" <fche@redhat.com>
Subject: Re: qpsmtpd whitelisting
Date: Thu, 07 Oct 2010 20:39:00 -0000 [thread overview]
Message-ID: <20101007203908.GB24824@ednor.casa.cgf.cx> (raw)
In-Reply-To: <20101005192110.GI16489@redhat.com>
On Tue, Oct 05, 2010 at 03:21:10PM -0400, Frank Ch. Eigler wrote:
>Hi -
>
>To reduce the annoying time taken by bugzilla outgoing emails, I
>turned on email job-queuing for both gcc and sourceware sides. It
>appears to be working, however it appears as if the arrival rate for
>outgoing gcc bugzilla messages is about as high as the serialized
>service rate. It appears that spamd is processing these outgoing
>messages, and this is slowing things down quite a bit.
>
>Chris, could you look into activating qpsmtpd whitelisting for locally
>originated email?
Why would we be whitelisting bugzilla email? Can't it still be filled
in from an external source? Can't it still be spam?
cgf
prev parent reply other threads:[~2010-10-07 20:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 19:21 Frank Ch. Eigler
2010-10-07 20:39 ` Christopher Faylor [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=20101007203908.GB24824@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--cc=fche@redhat.com \
--cc=overseers@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).