From owner-freebsd-questions@FreeBSD.ORG Sat Mar 22 16:59:14 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 462751065679 for ; Sat, 22 Mar 2008 16:59:14 +0000 (UTC) (envelope-from alex@schnarff.com) Received: from mho-02-bos.mailhop.org (mho-02-bos.mailhop.org [63.208.196.179]) by mx1.freebsd.org (Postfix) with ESMTP id 1E7B98FC25 for ; Sat, 22 Mar 2008 16:59:13 +0000 (UTC) (envelope-from alex@schnarff.com) Received: from c-98-204-176-196.hsd1.va.comcast.net ([98.204.176.196] helo=schnarff.com) by mho-02-bos.mailhop.org with esmtpa (Exim 4.68) (envelope-from ) id 1Jd6ot-000PI0-RQ for freebsd-questions@freebsd.org; Sat, 22 Mar 2008 16:43:48 +0000 Received: (qmail 18859 invoked by uid 67); 22 Mar 2008 16:43:46 -0000 Received: from 192.168.2.68 ([192.168.2.68]) by mail.schnarff.com (Horde) with HTTP for ; Sat, 22 Mar 2008 12:43:46 -0400 X-Mail-Handler: MailHop Outbound by DynDNS X-Originating-IP: 98.204.176.196 X-Report-Abuse-To: abuse@dyndns.com (see http://www.mailhop.org/outbound/abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX18a7FsKhAGZSIUoLUF5kMldp39ofneQsik= Message-ID: <20080322124346.factw4f04kwwocss@mail.schnarff.com> Date: Sat, 22 Mar 2008 12:43:46 -0400 From: alex@schnarff.com To: freebsd-questions@freebsd.org References: <47E52ADD.4070103@n3gqf.us> In-Reply-To: <47E52ADD.4070103@n3gqf.us> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.0.4) Subject: Re: Anyone have Comcast for an ISP? 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: Sat, 22 Mar 2008 16:59:14 -0000 >>> Does anyone on here have comcast for an ISP? I use them and today I was >>> messing around on a machine I use for FTP service over my LAN (Not >>> accessible from the net so I'm not worried about using it for back ups) >>> and anyway, I wanted to set up one of my comcast accounts on it so I >>> could do as I've done for years, and use SSH to log into that machine >>> and use fetchmail to grab my email off comcast, and then use Mutt to >>> check it since I really like Mutt. >>> >>> Well, I got sendmail up ad tested that it was working and it was working >>> fine. After that I tried sending a test email with Mutt. >>> >>> For some reason ti failed even though it was the backed up copy of my >>> Muttrc that I used to use on EVERY machine I used mutt on. I always >>> backed it up because I had it looking really nice with colors and also >>> my email address was in there and I built in a mini addy book for my >>> friends and mailing lists I'm on so I didn't have to worry about an >>> address book being deleted by accident. >>> >>> Well, it failed horribly. I can't send an email because it's blocked, >>> and also, using fetchmail isn't exactly working either and I can't stand >>> how getmailrc works.... >>> >>> So does anyone here use Comcast and Mutt for an email client that could >>> maybe reply and let me know how they do it? Id' like to use Mutt and >>> also I do like how simple fetchmail is to use, so fi you use these and >>> have Comcast for internet please reply with how you did it. I'm googling >>> right now but everything I find isn't exactly helpful, so if anyone here >>> uses Mutt and has Comcast please let me know how you did it. >>> >>> >> >> What you have available in the e-mail realm when you are >> on the Comcast network: >> >> For e-mail CLIENTS you may retrieve mail via the standard >> IMAP or POP3 ports from a remote non-comcast mailserver. >> >> For e-mail CLIENTS you may send mail through a remote >> non-comcast mailserver using the submission port 587 and >> authenticated SMTP. >> >> For e-mail SERVERS you can use fetchmail to pretend the >> server is a mail client, then redistribute the mail >> internally. However you cannot use sendmail to send >> out outgoing mail to port 25 on remote mailservers - unless >> it's to the comcast mailserver. >> >> Comcast's residential >> TOS prohibits servers and they enforce this by blocking incoming >> traffic going to SMTP, IMAP and POP3 ports. >> >> > I'd like to call BS here. My mail server runs on a Comcast connection. > I send all my out going mail through them, but incoming mail works > without issue. My employer does pay for my Internet connection, so it > might be on some exception list for business service. But, it > definitely works. It's very much a location-by-location, and sometimes even a connection-by-connection kind of thing. I'm in Northern Virginia (DC area), and I've been running a mail server on my Comcast connection for over a year. I found that a lot of providers like Yahoo, AOL, etc. refused to take mail I sent directly out (though Gmail was awesome, shocker, huh?), so I use DynDNS to send outbound mail. For a few months starting last November or so, they blocked all mail -- said there'd been some sort of spike in traffic on my connection that they refused to give me details about, and felt I was infected with something (nevermind that it was a fully patched OpenBSD server running the mail) -- and I had to switch to port 587 for a while. With no notice at all, though, port 25 re-opened at some point later, so I think it was some sort of dynamic block that had an auto-timeout. In any case, you definitely can run mail on Comcast...just not legitimately per their TOS, so you're kind of at the mercy of the local techs. Alex Kirk