From: Matti Aarnio <matti.aarnio@zmailer.org>
To: Rajiv Majumdar <rmajumda@tcg-software.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: detecting bounced mails
Date: Wed, 17 Jan 2001 13:10:16 +0200 [thread overview]
Message-ID: <20010117131016.B25659@mea-ext.zmailer.org> (raw)
In-Reply-To: <652569D7.003CB690.00@gemini.tcg-software.com>
In-Reply-To: <652569D7.003CB690.00@gemini.tcg-software.com>; from rmajumda@tcg-software.com on Wed, Jan 17, 2001 at 04:33:08PM +0530
On Wed, Jan 17, 2001 at 04:33:08PM +0530, Rajiv Majumdar wrote:
> Sorry..the topic does not fit here. But wanted to know, how can we check
> validity of an email id "in advance" so that we can skip "bounce".
There are theorethical ways using SMTP's VRFY command, however
it has never been implemented at all systems, and modern
environment of firewalls just simply doesn't allow it to work.
The only thing you *can* verify is to look for the domain
part in the address from the DNS. At first query for MX
record(s), and if *not* found any, then query for A record(s).
If you encounter CNAME, do resolve it couple times towards
MX or A.
If you find neither MX, nor A, then the DOMAIN part is non-routable
in the internet, but nothing can be said about the left side of
the @-character (the LOCAL part).
If you have a RFC-821 statemachine scanner to recognize the address
syntax and accept only LOCAL@DOMAIN form (not @GW1,@GW2:LOCL@DOM),
plus do that MX/A lookup, you should pretty much be done.
It will trap honest mistakes - usually.
I have code to do this type of analysis at my ZMailer, works fine.
> Thanks!
> Rajiv
/Matti Aarnio
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-17 11:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-17 11:03 Rajiv Majumdar
2001-01-17 11:10 ` Matti Aarnio [this message]
2001-01-17 22:50 ` Igmar Palsenberg
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=20010117131016.B25659@mea-ext.zmailer.org \
--to=matti.aarnio@zmailer.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmajumda@tcg-software.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
all inboxes | Powered by JetHome®