public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Overseers mailing list <overseers@sourceware.org>
Cc: "Frank Ch. Eigler" <fche@elastic.org>,
	Paul-Antoine Arras <pa@codesourcery.com>
Subject: Re: Fwd: Log into Bugzilla as parras@gcc.gnu.org
Date: Tue, 27 Sep 2022 12:20:51 -0400	[thread overview]
Message-ID: <20220927162051.GG7916@redhat.com> (raw)
In-Reply-To: <960695e6-7c2f-1e3e-e202-0a31809f628f@codesourcery.com>

Hi -

> Thank you for creating the Bugzilla account. However, I am still not
> receiving the token to set a password after entering parras@gnu.gcc.org in
> the "Forgot password" field.

The system should have sent you an initial notification about the new
account.  Indeed the system shows delivery of that mail:

Sep 27 14:59:46 server2 postfix/qmgr[1061427]: E1BC63858435: from=<gcc-bugzilla@gcc.gnu.org>, size=1887, nrcpt=1 (queue active)
Sep 27 14:59:50 server2 postfix/smtp[3540549]: E1BC63858435: to=<pa@codesourcery.com>, orig_to=<parras@gcc.gnu.org>, relay=mx1.mentor.iphmx.com[68.232.129.153]:25, delay=3.2, delays=0/0/1.8/1.5, dsn=2.0.0, status=sent (250 ok:  Message 86494360 accepted)
Sep 27 14:59:50 server2 postfix/qmgr[1061427]: E1BC63858435: removed

(The "forgot password" function wouldn't be expected to work before there
was an account in the first place.)


- FChE


  reply	other threads:[~2022-09-27 16:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAH6eHdSqb6ShVWuuMWYu0-wEW_RZp2nsuWTRQNZMNEDN5Tx_CQ@mail.gmail.com>
2022-09-27 14:32 ` Paul-Antoine Arras
2022-09-27 14:58   ` Frank Ch. Eigler
2022-09-27 16:16     ` Paul-Antoine Arras
2022-09-27 16:20       ` Frank Ch. Eigler [this message]
2022-09-27 16:35         ` Paul-Antoine Arras

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=20220927162051.GG7916@redhat.com \
    --to=fche@redhat.com \
    --cc=fche@elastic.org \
    --cc=overseers@sourceware.org \
    --cc=pa@codesourcery.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).