From: Joel Sherrill <joel@rtems.org>
To: Mark Wielaard <mark@klomp.org>
Cc: Overseers mailing list <overseers@sourceware.org>
Subject: Re: Bugzilla Account/Email Forwarding
Date: Mon, 1 Aug 2022 16:14:25 -0500 [thread overview]
Message-ID: <CAF9ehCUryxcW8pa-D=GbbAZs0Be15Np8QjsHATbY7vuC5VHh2w@mail.gmail.com> (raw)
In-Reply-To: <CAF9ehCXL-+X42abRi7FFQOryKkTVU-sw0b8tgNPv+opC256k9w@mail.gmail.com>
Weird. The email showed up after well over an hour and the emails between
us.
Not sure what happened. I did contact the rtems.org admin but he is on a
holiday and didn't do anything.
--joel
On Mon, Aug 1, 2022 at 3:36 PM Joel Sherrill <joel@rtems.org> wrote:
>
>
> On Mon, Aug 1, 2022 at 3:25 PM Mark Wielaard <mark@klomp.org> wrote:
>
>> Hi Joel,
>>
>> On Mon, Aug 01, 2022 at 10:03:12PM +0200, Mark Wielaard via Overseers
>> wrote:
>> > Although that doesn't really explain why you didn't get a reset
>> > password. I'll see if I can reset my own password.
>>
>> I can reset my own. bugzilla does sent a token reset email through my
>> @gcc.gnu.org account. Then the same for you. It seems to work and
>> sent email to your rtems.org address. The postfix logs say:
>>
>> postfix/smtp[3049158]: 6E87A38582BF: to=<joel@rtems.org>,
>> orig_to=<joel@gcc.gnu.org>, relay=mx.rtems.org[140.211.10.141]:25,
>> delay=0.88, delays=0/0/0.62/0.26, dsn=2.0.0, status=sent (250 2.0.0
>> Ok: queued as 140DA35E210
>>
>> So if you didn't get that email maybe you can ask the rtems.org admin?
>>
>
> Thanks. I will. Weird that email gets through when I sent it myself
> directly.
>
> --joel
>
>>
>> Cheers,
>>
>> Mark
>>
>
prev parent reply other threads:[~2022-08-01 21:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 19:37 Joel Sherrill
2022-08-01 20:03 ` Mark Wielaard
2022-08-01 20:19 ` Joel Sherrill
2022-08-01 20:25 ` Mark Wielaard
2022-08-01 20:36 ` Joel Sherrill
2022-08-01 21:14 ` Joel Sherrill [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='CAF9ehCUryxcW8pa-D=GbbAZs0Be15Np8QjsHATbY7vuC5VHh2w@mail.gmail.com' \
--to=joel@rtems.org \
--cc=mark@klomp.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).