public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: ChristopherFaylorme@cgf.cx
To: Jonathan Larmour <jiflsw@jifvik.org>
Cc: Sourceware overseers <overseers@sourceware.org>
Subject: Re: eCos bugs list rejecting bugzilla mail
Date: Thu, 3 Sep 2020 12:57:13 -0400	[thread overview]
Message-ID: <20200903165713.GB28599@cgf.cx> (raw)
In-Reply-To: <5F511827.5030009@jifvik.org>

[private reply]
On Thu, Sep 03, 2020 at 05:21:59PM +0100, Jonathan Larmour wrote:
>On 02/09/20 15:12, Christopher Faylor wrote:
>> On Tue, Sep 01, 2020 at 10:33:46PM +0100, Jonathan Larmour wrote:
>>> I've been informed that the ecos-bugs mailing list is rejecting mail from the
>>> eCos project's bugzilla. [snip]
>>
>> ecos.sourceware.org was missing as a valid recipient domain in postfix
>> so I added it.  Does it work now?
>
>Sort of... the mails are waiting for approval, but I don't have perms to do
>anything about that, or whitelist bugzilla-daemon@ecoscentric.com. Or maybe it
>makes a difference that the destination is an address
>@bugs.ecos.sourceware.org rather than just ecos.sourceware.org or sourceware.org.

The mailman password for ecos-bugs is .  You can access the
administrative interface here: https://sourceware.org/mailman/admin/ecos-bugs .

You can deal with messages held for processing at this page and maybe
changing the "Host name this list prefers for email." under General
Options will help with messages not being held.


  reply	other threads:[~2020-09-03 16:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-01 21:33 Jonathan Larmour
2020-09-02 14:12 ` Christopher Faylor
2020-09-03 16:21   ` Jonathan Larmour
2020-09-03 16:57     ` ChristopherFaylorme [this message]
2020-09-03 16:57       ` Christopher Faylor

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=20200903165713.GB28599@cgf.cx \
    --to=christopherfaylorme@cgf.cx \
    --cc=jiflsw@jifvik.org \
    --cc=overseers@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).