Date: Sat, 8 Apr 2000 12:11:04 +0930 From: Greg Lehey <grog@lemis.com> To: groggy@iname.com Cc: FreeBSD Questions <questions@FreeBSD.org> Subject: Re: mail Q. Message-ID: <20000408121104.G95946@freebie.lemis.com> In-Reply-To: <200004080136.BAA13505@groggy.anchorage.ptialaska.net> References: <200004080136.BAA13505@groggy.anchorage.ptialaska.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday, 8 April 2000 at 1:36:43 +0000, groggy@iname.com wrote: >>>>> ps. it seems my favorite maillist and a few others these days >>>>> block mail originating from a server with a private IP >>>>> behind a proxying gateway. is there i way i can continue >>>>> to use my own sendmail to mail from my FBSD machine behind >>>>> a proxying gateway? is my only choice to use the proxies >>>>> mailserver to send mail? this sucks for various reasons. >>>>> >>>>> more and more my email bounces with "originating domain must exist" >>>>> messages. :( >>>> >>>> This problem is indicative of the general quality of ISPs nowadays. >>>> The only good reason not to have reverse mapping is in order to spam. >>>> If your ISP is too stupid to set up reverse mapping, you probably >>>> want to change anyway. >>> >>> what do you mean? how can my ISP reverse map my private IP numbers? >>> if i send from 192.168.0.26 or whatever ... >> >> They can't. But they're not the addresses that get posted, they're >> the ISPs address. >> >>> i don't understand why they are stupid. >> >> Because they're not sticking to the DNS conventions, and (in case you >> hadn't noticed) they're causing you problems as a result. Look: >> >> + > ptialaska.net >> + Server: freebie.lemis.com >> + Address: 0.0.0.0 >> + >> + ptialaska.net >> + origin = ns2.ptialaska.net >> + mail addr = dnstech.ptialaska.net >> + serial = 2000032701 >> + refresh = 10800 (3H) >> + retry = 3600 (1H) >> + expire = 604800 (1W) >> + minimum ttl = 14400 (4H) >> + ptialaska.net nameserver = ns1.ptialaska.net >> + ptialaska.net nameserver = ns2.ptialaska.net >> + ptialaska.net nameserver = ns3.ptialaska.net >> + ns1.ptialaska.net internet address = 209.193.30.248 >> + ns2.ptialaska.net internet address = 209.193.30.245 >> + ns3.ptialaska.net internet address = 208.151.127.1 >> + > 209.193.30.248 >> + Server: freebie.lemis.com >> + Address: 0.0.0.0 >> + >> + *** freebie.lemis.com can't find 209.193.30.248: Non-existent host/domain >> + >> + > 209.193.30.245 >> + Server: freebie.lemis.com >> + Address: 0.0.0.0 >> + >> + *** freebie.lemis.com can't find 209.193.30.245: Non-existent host/domain >> + > 208.151.127.1 >> + Server: freebie.lemis.com >> + Address: 0.0.0.0 >> + >> + *** freebie.lemis.com can't find 208.151.127.1: Non-existent host/domain >> >> Not even their name servers reverse map. > > ******************************************************************************* > ISP's reply :) > > Note: i do not have any problem resolving their IP numbers ... > ******************************************************************************* > > who is right? i am really confused now :) Looks like a temporary problem. Try again, and if it doesn't work, show the complete message. Your headers seem to be messed up: > From: groggy@iname.com > Message-Id: <200004080136.BAA13505@groggy.anchorage.ptialaska.net> > X-Authentication-Warning: groggy.anchorage.ptialaska.net: abc set sender to groggy@iname.com using -f > Subject: RE: mail Q. > Sender: owner-freebsd-questions@FreeBSD.ORG > X-Loop: FreeBSD.ORG > Precedence: bulk > To: undisclosed-recipients: ; You should at least have a valid 'To:' line. Maybe something else is causing the bounce. What MUA is this? Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000408121104.G95946>