[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: How to run fetchmail as daemon at startup



On Thu, Mar 29, 2007 at 10:14:43PM -0400, Greg Folkert wrote:
> On Thu, 2007-03-29 at 19:56 -0500, Ron Johnson wrote:
> > On 03/29/07 19:12, cga2000 wrote:
> > > On Thu, Mar 29, 2007 at 07:59:48AM EST, Ron Johnson wrote:
> > [snip]
> > >> Maybe, but I doubt it.  Usually ISPs just block 80, 25 & 20/21.
> > > 
> > > IOW, they have no clue what's really going on .. :-)
> > 
> > I'm sure they have many people who do.  Remember, though, that as
> > much as The Eeeeeeeeeeeeevil Government would like it, ISPs can't
> > monitor every port that every customer is using.  So, they use the
> > blunt instrument of blocking popular ports.
> 
> Comcast has scanned on ports:
> 
>         119, 137, 138, 139, 445, 563, 1433, 1434, 5000
> 
> But usually the only ones I see anymore are:
> 
>         119, 138, 139, 445 and 5000
> 
> And mostly on 138 and 139, though regularly 119.
> 
> I can't imagine why they would scan 138 and 139 ...
> 

I have comcast and haven't bothered to see what they scan aroudn here,
but they block nothing on my home connection. I"ve currently got
IMAPS, HTTP and HTTPS all running on standard ports with not problems
at all. 

A

Attachment: signature.asc
Description: Digital signature


Reply to: