From: Martin Jambor <mjambor@suse.cz>
To: overseers@sourceware.org
Subject: Re: Issues attempting to subscribe to libc-alpha@sourceware.org
Date: Tue, 24 Jan 2023 14:19:32 +0100 [thread overview]
Message-ID: <ri64jsgcbob.fsf@suse.cz> (raw)
In-Reply-To: <ri68rhsccoj.fsf@suse.cz>
Hello again,
On Tue, Jan 24 2023, Martin Jambor wrote:
> Hello overseers@sourceware.org,
>
> when attempting to subscribe to the libc mailing list
> libc-alpha@sourceware.org with this email address, I get the following
> error immediately after hitting the subscribe button on the web
> interface:
>
> Internal Server Error
>
> The server encountered an internal error or misconfiguration and was unable to complete your request.
>
> Please contact the server administrator at root@localhost to inform them of the time this error occurred, and the actions you performed just before this error.
>
> More information about this error may be available in the server error log.
>
> In case this is not a known problem I thought you'd want to be notified.
> A notice when the bug is fixed would be greatly appreciated.
>
What is worse, the attempt (and there were not that many) seems to have
put me on some sort of black-list and whenever I try to access any
sourceware.org resources (such as GCC bugzilla) from my computer (coming
from 193.86.92.180) or any other machine in SUSE Prague office, I get
the same 500 Internal error message.
I sort of need to access GCC bugzilla bugs, can you please have a look
at what is going on?
Thank you very much,
Martin
next prev parent reply other threads:[~2023-01-24 13:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 12:57 Martin Jambor
2023-01-24 13:08 ` Frank Ch. Eigler
2023-01-24 13:19 ` Martin Jambor [this message]
2023-01-24 13:31 ` Frank Ch. Eigler
2023-01-24 14:43 ` Martin Jambor
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=ri64jsgcbob.fsf@suse.cz \
--to=mjambor@suse.cz \
--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).