From owner-freebsd-isp Sun Jun 13 10:29: 3 1999 Delivered-To: freebsd-isp@freebsd.org Received: from noop.colo.erols.net (noop.colo.erols.net [207.96.1.150]) by hub.freebsd.org (Postfix) with ESMTP id 09E8C1519C for ; Sun, 13 Jun 1999 10:29:00 -0700 (PDT) (envelope-from gjp@noop.colo.erols.net) Received: from localhost ([127.0.0.1] helo=noop.colo.erols.net) by noop.colo.erols.net with esmtp (Exim 2.12 #1) id 10tE45-0008Vl-00; Sun, 13 Jun 1999 13:29:01 -0400 To: Niklas Saers Cc: Khetan Gajjar , freebsd-isp@FreeBSD.ORG From: "Gary Palmer" Subject: Re: Sendmail In-reply-to: Your message of "Sun, 13 Jun 1999 11:15:06 +0200." <4.1.19990613111339.01fa8ad0@pop.saers.com> Date: Sun, 13 Jun 1999 13:28:45 -0400 Message-ID: <32720.929294925@noop.colo.erols.net> Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Niklas Saers wrote in message ID <4.1.19990613111339.01fa8ad0@pop.saers.com>: > Wouldn't it minimize the abuse if it checked upon request if the user > existed, and if it existed, it would allow relaying? Perhaps even with the > possibillity to stop certain standard users for relaying (i.e, root etc) That just opens you up to unauthorized relaying, except that you make the spammer make it look like it comes from your domain (on the from line) which would just make people think that its authorized. Also, places like ORBS check for that form of `relay protection' and will list you if you allow it. POP Before SMTP, Authenticated SMTP and limiting access to your own netblocks are the only ``secure'' methods of denying relaying. Unfortunately, authenticated SMTP (by far the best solution) isn't all that widespread yet, and I don't know any freeware programs that come with AuthSMTP built in. Sendmail doesn't have it yet, although Eric says it will be in the next rev (I believe) Gary Palmer Senior System Administrator, E-Mail RCN Corporation To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message