Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 7 Sep 1997 18:16:02 -0700 (PDT)
From:      "Jonathan M. Bresler" <jmb>
To:        ahd@kew.com (Drew Derbyshire)
Cc:        jmb@FreeBSD.ORG, hackers@hub.freebsd.org, support@kew.com
Subject:   Re: spam and the FreeBSD mailing lists
Message-ID:  <199709080116.SAA23646@hub.freebsd.org>
In-Reply-To: <3413480B.BADF1376@kew.com> from "Drew Derbyshire" at Sep 7, 97 08:34:19 pm

next in thread | previous in thread | raw e-mail | index | archive | help
Drew Derbyshire wrote:
> 
> Jonathan M. Bresler wrote:
> > Drew Derbyshire wrote:
> > > The TCP/IP protocol implicitly requires public IP address to be properly
> > > registered to be routed (otherwise, you don't get your ACK's back!),
> > 
> >         please remember to distinguish between "mail from:" addresses
> >         and relays.  
> 
> The relay name (host name of the SMTP client) need not be resolvable in
> DNS, I didn't mean to imply it did.  I mean the actual IP addresss had
> to be routable. Someone else was confused by my wording as well.

	how do i probe routing tables with sendmail.
	rfc-1918 addresses are blocked by the routers and be many ISPs

> 
> >         if the "don't get your ACK's back" they cant establish the TCP
> >         session in order to transfer the mail in the first place.
> 
> Correct, which goes back to my original statement that the network
> routing must be registered -- not with DNS, but with the backbone
> routers.
> 
> > there is *not* reasone that i know of that a
> >         "mail from:" address must be resolvable.
> 
> Yes, there is.    The address in the SMTP "MAIL FROM" line is used for

	uucp mail from is valid.  even though i cannot doa DNS on it.
	our uucp relay will accept the message and attempt delivery for us.

> bounce messages by sendmail.  Consider if you send mail via a
> third-party relay (such as a back-up MX forwarder, something both
> kew.com and freebsd.org have) and mail lands on the backup MX forwarder
> because the primary is down.   When the intermediate relay connects to
> the ultimate destination, if the user id on the final is bad then the
> intermediate relay's bounce message will be sent to the "MAIL FROM"
> address.  Thus, the bounce message is lost if the "MAIL FROM" address is
> bad.

	everyone please,  in your mails to me about this be kind to an 
	old man ;) and differentiate between "mail from", relay host,
	uucp and all the rest of the nuances of mail <whew>
	ahhhh...now i feel better
jmb


an example of some of the crazy stuff i see:


hub cf[183] grep 22278 /var/log/maillog
Sep  7 17:51:03 hub sendmail[22278]: NOQUEUE: ruleset=check_relay, arg1=[200.241.133.2], arg2=200.241.133.2, relay=root@localhost, reject=451 Domain does not resolve

hub cf[190] whois 200.241.133
RNP (Brazilian Research Network) (NETBLK-BRAZIL-BLK2)
   Rua Pio XI, 1500 - CEP 05468-901
   Sao Paulo - SP - BRAZIL

   Netname: BRAZIL-BLK2
   Netblock: 200.128.0.0 - 200.255.255.0
   Maintainer: RNP

   Coordinator:
      Gomide, Alberto Courrege  (ACG8)  gomide@FAPESP.BR
      +55-11-203-1617 telex +55-11-82014 (FAX) +55-11-260-5749

   Domain System inverse mapping provided by:

   DIXIT.ANSP.BR                143.108.1.17
   FPSP.FAPESP.BR               143.108.1.1

   Record last updated on 31-May-95.
   Database last updated on 7-Sep-97 04:42:18 EDT.


traceroute to 200.241.133.2 (200.241.133.2), 30 hops max, 40 byte packets
 1  gate-free.cdrom.com (204.216.27.17)  2.786 ms  1.615 ms  1.568 ms
 2  R-CRL-SFO-01-EX.US.CRL.NET (165.113.118.1)  9.740 ms  6.604 ms  11.760 ms
 3  T3-GW1.F0.US.CRL.NET (165.113.55.1)  6.169 ms  11.495 ms  9.854 ms
 4  pb-nap-A.sprint.net (198.32.128.11)  90.045 ms  67.609 ms  53.307 ms
 5  144.232.4.53 (144.232.4.53)  45.483 ms  48.438 ms  51.077 ms
 6  144.232.4.62 (144.232.4.62)  47.819 ms  52.356 ms  45.453 ms
 7  144.232.4.26 (144.232.4.26)  59.962 ms  62.978 ms  55.018 ms
 8  sl-dc-22-H1/1/0-T3.sprintlink.net (144.228.10.1)  145.308 ms  141.519 ms  158.803 ms
 9  gip-dc-3-Fddi0-0.gip.net (204.59.144.197)  159.809 ms  185.180 ms  183.921 ms
                                                                               10  204.59.224.210 (204.59.224.210)  298.138 ms  295.839 ms  300.674 ms
11  200.255.197.66 (200.255.197.66)  279.356 ms  299.283 ms  286.813 ms
12  200.244.174.234 (200.244.174.234)  340.029 ms  360.515 ms  348.143 ms
13  200.241.133.2 (200.241.133.2)  351.569 ms  333.830 ms  338.070 ms




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199709080116.SAA23646>