|
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
|
Re: [PLUG] OT: Comcast & Mail Servers
|
I believe Comcast is still allowing the mail submission port (587/tcp)
- so that can be used to relay mail to a relay server. Most smtp relay
servers support 587. But I'm not 100% sure. I know previous customers
of mine who have been smtp blocked were able to submit to my servers
using port 587.
I'm a Comcast hater too, but..... Its actually a good thing what their
doing. You really are shooting yourself in the foot when running your
own server behind Comcast. Most recipients wont get your email anyway
because your in DUL blacklists, or the recipient is blocking Comcast -
or someone with your IP from earlier abuse was blacklisted.
Its also not Green! All these people leaving computers on 24x7 to do
one mailbox. 1000 PC's shutoff for an additional 12 hours a day (or in
sleep mode) is 1200Kilowatt-hours (figure 120watts for your PC) a day
saved (28,000Kwhrs a month - enough monthly power to run 25 homes). And
I would venture to say, and this is a complete estimate, that in all of
Philly and surrounding areas, maybe a couple 1000 people run their PC's
24x7 just to run a few services like smtp - and it could easily be
more. Each person would save about $5.60 a month in power - and you can
easily afford a hosting package for that.
It will cut down on spam significantly, since most of it comes from
infected broadband PCs. Honestly, if Comcast, Verizon, SBC, Qwest, and
ATT blocked residential broadband smtp - the public would see a big
change. Combined those providers cover about 60 million users.
-john
On Jan 11, 2008, at 12:40 AM, Jeremy Kister wrote:
> On 1/7/2008 12:52 AM, Brian Vagnoni wrote:
>> you are currently running a e-mail server on residential Comcast HS
>> they are blocking port 25 on people. So if your mail server suddenly
>> stopped working Sunday morning this is why. There is always port 465
>
> It doesnt only effect email servers -- they're blocking all outbound
> sockets on dest 25/tcp (for me anyway). I haven't been able to make
> the
> socket since [at least] 2008.01.06 at 7am EST.
>
>> asked them what's up and they told me if they detect even one piece
>> of SPAM coming from your connection they will permanently block it.
>
> I just called and "technician #x80" told me that I was personally
> filtered for sending spam, specifically for sending over 100 messages
> per day. I told her that I was smarter than to accept that, as I was
> clued in by other comcast users on this list who were blanket filtered
> the same day :) She then said that I'd have to contact the "Comcast
> Customer Security Assurance department" to have the filter lifted. I
> did, but they're closed, and their mailbox is full, LMAO.
>
> It's of no consequence really. I signed up for the 2 year triple play
> JUST before Verizon enabled fios in my area. if they want to change my
> service without proof of abuse, that should get me out of the contact
> and let me go over to verizon.
>
> --
>
> Jeremy Kister
> http://jeremy.kister.net./
>
> _______________________________________________________________________
> ____
> Philadelphia Linux Users Group --
> http://www.phillylinux.org
> Announcements -
> http://lists.phillylinux.org/mailman/listinfo/plug-announce
> General Discussion --
> http://lists.phillylinux.org/mailman/listinfo/plug
>
___________________________________________________________________________
Philadelphia Linux Users Group -- http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|