|
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
|
Re: [PLUG] Problems w/SMTP on Verizon DSL, none on Comcast Cable?
|
I too have DCA.NET as my ISP running over a Verizon ADSL line. DCA.NET is very good. They provide static IP addresses (up to 5 I believe). I'm running my own mail server also (using qmail) and have not had any problems.
They do bind the IP address they give you to a MAC address you give them but later you can change the association if you change NICs or reconfigure your network. However, they only provide one e-mail address free. It costs extra for additional e-mail addresses on their mail server. My web server works well also across the DCA.NET/Verizon connection.
The reason I changed was because of Verizon (the ISP) blocking ports such that I could not run a mail or web server. The switch was not all that easy since it was troublesome getting Verizon to relinquish control of the line and DCA.NET can not take control until the line is free. Of course that is not a problem if you have a whole new line installed or have a second line you can put DCA.NET on.
On 03 Nov 2002 12:25:08 -0500
Michael Leone <turgon@mike-leone.com> wrote:
> On Sun, 2002-11-03 at 01:11, Paul wrote:
> > When I had Telocity (DirectTV) DSL I think they used Verizon to make the
> > connection. Do you think that I would have the port 25 problem now if I
> > singed up for a service which uses Verizon's lines? (Of course the
> > accepted domains would be different.)
>
> I have Verizon as a DSL line provider, and DCA.NET as an ISP. The
> blocking, if any, is done by the ISP, not the line provider. I run my
> own mailserver, tho, and so don't use DCA's mailservers.
>
> >
> > >I've done a little searching, and the only reference I can find ATM is
> > >at <http://slashdot.org/article.pl?sid=01/08/09/0323208>: "Verizon is
> > >apparently... blocking outgoing port 25 and requiring use of Verizon's
> > >SMTP servers to send email." And then the Verizon SMTP servers reject
> > >mail without a From: line with an @verizon.net or @bellatlantic.net. I
> > >know that this is the case because a former co-worker had Verizon DSL
> > >(with Verizon as both line provider and ISP) and he confirmed this.
> > >
> >
> > _________________________________________________________________________
> > Philadelphia Linux Users Group -- http://www.phillylinux.org
> > Announcements - http://lists.netisland.net/mailman/listinfo/plug-announce
> > General Discussion -- http://lists.netisland.net/mailman/listinfo/plug
> --
>
> PGP Fingerprint: 0AA8 DC47 CB63 AE3F C739 6BF9 9AB4 1EF6 5AA5 BCDF
> PGP public key:
> <http://www.mike-leone.com/~turgon/turgon-public-key.gpg>
>
> These are the memories which make me a wealthy soul ...
>
> _________________________________________________________________________
> Philadelphia Linux Users Group -- http://www.phillylinux.org
> Announcements - http://lists.netisland.net/mailman/listinfo/plug-announce
> General Discussion -- http://lists.netisland.net/mailman/listinfo/plug
>
_________________________________________________________________________
Philadelphia Linux Users Group -- http://www.phillylinux.org
Announcements - http://lists.netisland.net/mailman/listinfo/plug-announce
General Discussion -- http://lists.netisland.net/mailman/listinfo/plug
|
|