From: John Bradford <john@grabjohn.com>
To: davem@redhat.com (David S. Miller)
Cc: yiding_wang@agilent.com, linux-kernel@vger.kernel.org
Subject: Re: Server down?
Date: Fri, 24 Jan 2003 10:42:58 +0000 (GMT) [thread overview]
Message-ID: <200301241042.h0OAgwlm000380@darkstar.example.net> (raw)
In-Reply-To: <1043380941.16486.10.camel@rth.ninka.net> from "David S. Miller" at Jan 23, 2003 08:02:21 PM
> > The list server probably de-subscribed you. Try re-subscribing.
>
> This is absolutely NOT WHAT YOU SHOULD DO.
No, infact what you are suggesting is absolutely not what you should
do - the postmasters are already overworked, and don't need to be
troubled as a first resort.
Please, read the FAQ. If you wish to embarrase yourself on this
mailing list, that is up to you, but please do not make me look
stupid, AND THERE IS NO NEED TO SHOUT YOUR INCORRECT ADVICE.
The relevant section of the FAQ is:
Section 3, subsection 14
"I am not getting any mail anymore from the list! Is it down or
what?"
Note that there is NO problem with any of the original poster's
mailservers, they are all accessible, so it is not a case of mail
getting bounced from some of them.
The FAQ actually says, "Just resubscribe. Majordomo will get you a
nice note saying you're still subscribed if suddenly everybody went
dumb".
It also says, "Asking for help from postmaster@vger.kernel.org could
expedite the issue.", but common sense suggests that it's best to try
re-subscribing at least once before contacting the already overworked
postmasters.
> You should INSTEAD, send a mail to postmaster@vger.kernel.org
> asking why you were removed.
Only if you have persistant problems.
> People who continually keep resubscribing eventually get black
> listed. This means DO NOT DO IT. Ask why you are being removed
> so that the problems at your site can be fixed.
>
> When an address bounces, it puts a major burdon on both vger and
> the postmasters here.
Ask for the FAQ to be updated if it is wrong.
John.
next prev parent reply other threads:[~2003-01-24 10:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-23 18:38 Server down? yiding_wang
2003-01-23 19:02 ` John Bradford
2003-01-24 4:02 ` David S. Miller
2003-01-24 10:42 ` John Bradford [this message]
2003-01-24 15:03 ` Nuno Monteiro
2003-01-24 15:18 ` John Bradford
2003-01-24 16:20 ` [OT] " Nuno Monteiro
2003-01-24 15:20 ` Richard B. Tilley (Brad)
2003-01-24 17:57 ` David S. Miller
2003-01-24 20:17 ` Eli Carter
2003-01-24 20:30 ` John Bradford
2003-01-24 20:48 ` David S. Miller
[not found] ` <mailman.1043440382.11577.linux-kernel2news@redhat.com>
2003-01-24 23:03 ` Pete Zaitcev
2003-01-25 0:25 ` Matti Aarnio
2003-01-25 10:29 ` John Bradford
2003-01-25 12:53 ` Matti Aarnio
2003-01-25 13:19 ` John Bradford
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=200301241042.h0OAgwlm000380@darkstar.example.net \
--to=john@grabjohn.com \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yiding_wang@agilent.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