From: sqweek <sqweek@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] yes, comcast really *does* suck
Date: Mon, 10 Nov 2008 22:57:45 +0900 [thread overview]
Message-ID: <140e7ec30811100557s64dd97c4qbcecc0fa76333a8e@mail.gmail.com> (raw)
In-Reply-To: <436dfc83-aeb9-4e53-9b40-cb90a7f60412@c36g2000prc.googlegroups.com>
On Mon, Nov 10, 2008 at 6:59 PM, jfmxl <jfmxl@yahoo.com> wrote:
> My ISP was blocking port 25 outgoing, so I could send mail to my own
> mailserver. It turned out that sendmail was listening on port 587 as
> well, so I use that instead.
>
> I assumed my ISP was blocking outgoing port 25 to stop captured
> machines from spamming. Why do you think yours stopped incoming port
> 25? Probably just easier to block it in both directions?
My ISP blocks common incoming ports (25, 80) by default, presumably
because they see much more abuse than legitimate use - just think of
the number of people who run mail/www servers over residential
broadband vs the number of people with potentially vulnerable windows
machines. Fortunately for me, my ISP also provides an easy way to turn
the filtering off.
-sqweek
next prev parent reply other threads:[~2008-11-10 13:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 6:06 ron minnich
2008-11-06 6:28 ` Tharaneedharan Vilwanathan
2008-11-06 6:52 ` Tharaneedharan Vilwanathan
2008-11-08 2:09 ` Lyndon Nerenberg
2008-11-08 15:10 ` LiteStar numnums
2008-11-10 6:09 ` Enrico Weigelt
2008-11-10 9:59 ` jfmxl
2008-11-10 11:59 ` Bruce Ellis
2008-11-10 13:57 ` sqweek [this message]
2008-11-10 14:06 ` John Waters
2008-11-10 18:42 ` Eris Discordia
2008-11-11 2:35 ` Enrico Weigelt
2008-11-10 11:29 erik quanstrom
[not found] <4802f02f68ee35d61a35e7533cba1663@quanstro.net>
2008-11-10 18:06 ` Enrico Weigelt
2008-11-10 19:22 ` Charles Forsyth
2008-11-10 21:29 ` Bruce Ellis
2008-11-11 1:26 ` Dan Cross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=140e7ec30811100557s64dd97c4qbcecc0fa76333a8e@mail.gmail.com \
--to=sqweek@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).