From owner-freebsd-questions@FreeBSD.ORG Mon Jun 23 19:32:16 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DA7591065672 for ; Mon, 23 Jun 2008 19:32:16 +0000 (UTC) (envelope-from wmoran@potentialtech.com) Received: from mail.potentialtech.com (internet.potentialtech.com [66.167.251.6]) by mx1.freebsd.org (Postfix) with ESMTP id A4FD38FC17 for ; Mon, 23 Jun 2008 19:32:16 +0000 (UTC) (envelope-from wmoran@potentialtech.com) Received: from vanquish.ws.pitbpa0.priv.collaborativefusion.com (pr40.pitbpa0.pub.collaborativefusion.com [206.210.89.202]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.potentialtech.com (Postfix) with ESMTPSA id E12E7EBC08; Mon, 23 Jun 2008 15:32:15 -0400 (EDT) Date: Mon, 23 Jun 2008 15:31:29 -0400 From: Bill Moran To: Ethan Furman Message-Id: <20080623153129.c84a1aea.wmoran@potentialtech.com> In-Reply-To: <486001D1.7090500@stoneleaf.us> References: <20080623070556.GA1618@remdog.net> <485FAA07.5050904@pukruppa.net> <20080623171207.GA1000@remdog.net> <20080623172602.GG27531@ece.pdx.edu> <486001D1.7090500@stoneleaf.us> X-Mailer: Sylpheed 2.4.8 (GTK+ 2.12.9; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: FT , FreeBSD Subject: Re: Simple Text Mail Setup X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2008 19:32:16 -0000 In response to Ethan Furman : > FT wrote: > >>>> ... But I can't send mail because the system > >>>>isn't configured for that, and I'm in the dark as how to accomplish it. > >>>>Is there somewhere that I can go for info on setting up a simple > >>>>configuration which will let me send mail from Mutt? ... > >> > >>Well, I have had sendmail enabled, but my outgoing mail gets > >>bounced with a message saying that Comcast has blocked the process. > > > > Yes. On most residential connections, Comcast blocks port 25 to reduce > > the spam burden created by compromised hosts. Your options are not to > > send mail on port 25 (using port 587, for instance, but that makes you > > unable to communicate with many servers) or to buy business class > > service from Comcast, if they'll let you. You can try calling support > > and asking to have 25 unblocked, but I have yet to hear of a case > > where that was effective. > > As an aside, I recently had a similar problem being able to send e-mail > to my host (webgator.com) through Comcast's network -- a Comcast tech > suggested using port 26 instead of 25, and that worked for me. That's exactly the kind of brain-dead answer I'd expect from Comcast. The Internet community comes up with a solution, and publishes the fact that port 587 is specifically _for_ this purpose, yet Comcast suggests 26 ... go figure. -- Bill Moran http://www.potentialtech.com