From: Matti Aarnio <matti.aarnio@zmailer.org>
To: linux-kernel@vger.kernel.org
Subject: ADMIN: Reminder to VERIFY your email routing functionality!
Date: Thu, 26 Apr 2001 11:06:36 +0300 [thread overview]
Message-ID: <20010426110636.M805@mea-ext.zmailer.org> (raw)
I am getting *somewhat* annoyed with subscribers whose domains
have backup servers not willing to receive email for them.
On average each day we get dozens to hundreds of bounces of this
routing-trouble type pointing to 2-3 domains each time.
Do use the MX verifier server at page:
http://vger.kernel.org/mxverify.html
by entering your down address into the entry box (for VGER), and
then click on associated SUBMIT button.
Get into habit of using that tool weekly, things often *do* change
in cases where you rely on other people giving you some service.
That tool does email domain routing by the generic Internet Rules
(See RFC 2821 for concise presentation), and then tests SMTP level
protocol transactions for actual delivery. YOU, the subscriber,
do not need to understand the algorthms behind it, it does tell if
all goes ok, or if something fails. In case of failures, do contact
your ISP email wranglers; usually <postmaster@isp-domain>, possibly
also <helpdesk@isp-domain>. (And if they reject MAIL FROM:<>, do
ask them why the violate RFC 821/2821 ?)
I am also contemplating a change into policy -- we (me and DaveM)
have been somewhat lenient if people cause less than whole day of
bounces by "we do not relay to that domain" (or some other text of
same meaning) messages. NEW POLICY might soon be: EVEN ONE SUCH
BOUNCE, AND YOUR SUBSCRIPTION IS HISTORY. (Until you resubscribe,
that is. We don't blacklist, just remove.)
Analyzing reasons and tracking bounces is bloody timeconsuming.
Statistics being a continuum of event kinds, during past 7 days there
has been one day when we got unusually low number of MX bounces, and
it wasn't any way quiet day at linux-kernel list...
There are presently 3165 subscribers with 2608 different domains, thus
I can guess that many feel that this does not concern them - especially
if you subscribe/use some large email service provider to give you
the service. Don't consider that to be any sort of safety - we have
seen people like HOME.COM to blow it in the past...
If you have your own domain served at some ISP bulk server, they PROBABLY
have blown it.
/Matti Aarnio -- co-postmaster at vger.kernel.org
-- watching the world by received error reports, never seeing
success reports...
reply other threads:[~2001-04-26 8:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010426110636.M805@mea-ext.zmailer.org \
--to=matti.aarnio@zmailer.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®