From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] /n/sources/patch/spamhaus
Date: Tue, 13 May 2008 08:01:35 -0400 [thread overview]
Message-ID: <e84f9db56df982ded3503397edd7efe3@quanstro.net> (raw)
In-Reply-To: <be09049ad9740104d6c0c3e2297b3805@terzarima.net>
>> The solution for people on dynamic addresses (typically with some
>> generic and non-matching PTR record, though I haven't checked yours) is
>> likely to relay out through your ISP's mail server.
>
> because of the way the DNS is put together, PTR records cannot be relied upon.
> ownership of the DNS entries for a name are unrelated to the DNS entries for the in-addr
> entries for a set of IP addresses to which they map.
while true, this doesn't change many large site's email practices.
many do check reverse mappings. (i don't recall particular sites.)
barracuda boxes check reverse ip mappings.
rfc 2317 allows arbitrary cidrs to be delegated. so far, i've always
been able to get reverse mappings set up for static addresses.
- erik
next prev parent reply other threads:[~2008-05-13 12:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 19:19 [9fans] upas/fs rfc 2047 encoding erik quanstrom
2008-05-12 20:36 ` [9fans] /n/sources/patch/spamhaus Charles Forsyth
2008-05-12 20:39 ` Charles Forsyth
2008-05-12 22:34 ` Charles Forsyth
2008-05-12 22:47 ` erik quanstrom
2008-05-13 17:41 ` Anant Narayanan
2008-05-13 17:54 ` erik quanstrom
2008-05-12 23:35 ` Armando Camarero
2008-05-12 23:54 ` a
2008-05-13 0:20 ` erik quanstrom
2008-05-13 4:11 ` Jason Gurtz
2008-05-13 8:58 ` Charles Forsyth
2008-05-13 12:01 ` erik quanstrom [this message]
2008-05-13 13:23 ` a
2008-05-13 14:57 ` Wes Kussmaul
2008-05-12 23:53 ` erik quanstrom
2008-05-13 17:22 ` Russ Cox
2008-05-13 17:31 ` erik quanstrom
2008-05-13 19:52 ` Russ Cox
2008-05-13 20:07 ` erik quanstrom
2008-05-14 0:44 ` Russ Cox
2008-05-14 2:39 ` Nate S
2008-05-14 22:13 erik quanstrom
2008-05-14 23:22 ` Russ Cox
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=e84f9db56df982ded3503397edd7efe3@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).