[olug] Cox and port 25
Brian Roberson
roberson at olug.org
Mon Jun 30 15:49:32 UTC 2003
telnet olug.org 25
----- Original Message -----
From: "Nathan Rotschafer" <olug at geniussystems.net>
To: "Omaha Linux User Group" <olug at olug.org>
Sent: Monday, June 30, 2003 8:31 AM
Subject: Re: [olug] Cox and port 25
> I can say that my server (also on a Cox network...fiber link to be exact)
> works fine from my residential service site, but I have not tried another
> server as I have no other server off the cox network to try...anyone wanna
> give me an account to try and see??
>
> Nate
>
> On Monday 30 June 2003 08:34 am, Tim V - DZ wrote:
> > I 'support' three small business owners in the area...as in the rent
> > space, have employees and such (not a little guy working out of his
> > basement kinda thing). As a precaution after seeing jeff's and
> > subsequent posts I emailed them to see if they could email me back. I
> > sent the email on Friday just after 9 AM. All three called before the
> > morning was over, and over the phone I was able to convey how to change
> > the smtp server to cox's, which fixed the problem.
> >
> > I'm not sure how the port 25 block is actually implemented...i'd imagine
> > that it's an 'edge-based' thing and as long as you're connecting from a
> > computer on the cox network to a server that on the cox network you'd be
> > OK...i'm not sure that's what you were getting at in you # 1 or not
> > though...anyone with easy access to cox addresses at 2+ locations to
> > try?
> >
> > -t
> >
> >
> >
> > -----Original Message-----
> > From: olug-bounces at olug.org [mailto:olug-bounces at olug.org] On Behalf Of
> > Bob McCoy
> > Sent: Monday, June 30, 2003 7:44 AM
> > To: 'Omaha Linux User Group'
> > Subject: RE: [olug] Cox and port 25
> >
> > Tim V - DZ said:
> > > Cox at work customers are effected also.
> >
> > OK. I'm always one of the first to say, "I may be confused." But
> > please tell me where you came up with your $0.02 worth. Because here
> > are my observations:
> >
> > 1. I maintain mail servers for two different Cox at Work customers.
> > Neither have been effected by the block. Both can telnet to port 25 on
> > any valid mail server.
> >
> > 2. I called Cox Business customer service and they said that they have
> > not applied a universal block to port 25 traffic for their business
> > customers.
> >
> > A. They did say that some businesses mistakenly come up with DHCP
> > which will give them a residential IP. In which case, they get the
> > block.
> >
> > B. They also said that individual spammers will get blocked.
> >
> > So what gives here? You're not the only one to say that @Work customers
> > are also effected. I just want to know what that's based on.
> >
> > Bob
> >
> > -----Original Message-----
> > From: olug-bounces at olug.org [mailto:olug-bounces at olug.org] On Behalf Of
> > Tim V - DZ
> > Sent: Sunday, June 29, 2003 11:13 PM
> > To: 'Omaha Linux User Group'
> > Subject: RE: [olug] Cox and port 25
> >
> >
> > Cox at work customers are effected also.
> >
> > $0.02
> >
> > -t
> >
> > -----Original Message-----
> > From: olug-bounces at olug.org [mailto:olug-bounces at olug.org] On Behalf Of
> > Bob McCoy
> > Sent: Sunday, June 29, 2003 8:55 AM
> > To: 'Omaha Linux User Group'
> > Subject: RE: [olug] Cox and port 25
> >
> > To Nathan's point about running a valid business and work at home, Cox
> > would probably maintain that you should be using Cox at Work and not
> > Cox at Home.
> >
> > From the acceptable use policy
> > <http://support.cox.net/custsup/policies/acceptableuse.shtml#aup>:
> > Commercial Use. The Service is designed for personal use of the
> > Internet and may not be used for commercial purposes. You may not
> > resell or otherwise charge others to use the residential Service. You
> > agree not to use the Service for operation as an Internet service
> > provider, or for any other business enterprise, including, without
> > limitation, IP address translation, or similar facilities intended to
> > provide additional access.
> >
> > I'm not saying it's right. I'm just saying that you wouldn't get a lot
> > of sympathy from Cox for your argument.
> >
> > I do not work for Cox. I am not siding with Cox. Nor do I wish to
> > argue about the Cox at Work pricing structure, the fact that life is
> > unfair, or anything else. However, as a sidebar, I have observed that
> > our Cox at Work connection at the office is not affected by the port 25
> > block (yet).
> >
> > Now if you're using Cox at Work and have this issue, I truly apologize for
> > mischaracterizing your email and I believe you have a legitimate case.
> > Otherwise, I think you're just stuck like the rest of us.
> >
> > Bob
> >
> > -----Original Message-----
> > From: olug-bounces at olug.org [mailto:olug-bounces at olug.org] On Behalf Of
> > Jay Hannah
> > Sent: Saturday, June 28, 2003 10:56 PM
> > To: Omaha Linux User Group
> > Subject: Re: [olug] Cox and port 25
> >
> >
> >
> > What a strange situation... I never thought I'd be defending Cox when
> > they (once again) block something and piss me off. I guess I'm just a
> > lot angrier at spammers nowadays than ISP who try to fight them...
> >
> > Anyhoo, here's two more cents:
> >
> > "Nathan Rotschafer (OLUG)" wrote:
> > > Now consider I run a valid business and work from home and need to
> > > send company email from my house what do I do? If the email comes
> > > through Cox's servers some place will tag it as spam or refuse
> > > delivery based upon the fact that it is "forged". Now what do I do?
> > > In my opinion Cox just put a major blow to work from home business
> > > people and that is completely unacceptable.
> >
> > [deletia]
> >
> >
> >
> > _______________________________________________
> > OLUG mailing list
> > OLUG at olug.org
> > http://lists.olug.org/mailman/listinfo/olug
> >
> > _______________________________________________
> > OLUG mailing list
> > OLUG at olug.org
> > http://lists.olug.org/mailman/listinfo/olug
>
> _______________________________________________
> OLUG mailing list
> OLUG at olug.org
> http://lists.olug.org/mailman/listinfo/olug
>
More information about the OLUG
mailing list