From: asjo@koldfront.dk (Adam Sjøgren)
To: ding@gnus.org
Subject: Re: sendmail ssl authentication
Date: Sun, 18 May 2008 06:07:12 +0200 [thread overview]
Message-ID: <87d4nk45n3.fsf@topper.koldfront.dk> (raw)
In-Reply-To: <8763tc7auk.fsf@newsguy.com>
On Sat, 17 May 2008 18:46:27 -0500, reader@newsguy.com wrote:
> So did you mean that it is common for ISPs to block their own users
> but not users from the internet? What would that do for them.
It would prevent their users from beying exploited as a spam-relay and
sending spam out through their own ISP.
> It seems it would more likely help them to do it the other way round
> or like you said... just block all to port 25.
Spam makes people do annoying things.
> But it turns out there is an smtp server running on port 25 but I
> cannot get to it, but people on the internet can...
> On the face of it, it sounds ridiculous, so I don't understand why
> they would do that.
They need to accept email from the net, obviously.
A guess would be that for their own users - to minimize the spam that
they are "responsible" for - they have a description that says how their
users should send email (probably via another port, 587 maybe, and with
a login/password) and port 25 is blocked.
It is important for some ISPs to "keep their own backyard clean" - but
they can't ask other people in the world to follow their special
guidelines (only their own customers have login/passwords).
I think it makes perfect, albeit twisted, sense.
Best regards,
Adam
--
"Gravity is arbitrary!" Adam Sjøgren
asjo@koldfront.dk
next prev parent reply other threads:[~2008-05-18 4:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-15 14:31 [OT]sendmail " reader
2008-05-16 1:47 ` Dave Goldberg
2008-05-16 7:42 ` David
2008-05-16 17:58 ` reader
2008-05-16 19:29 ` David
2008-05-16 23:15 ` reader
2008-05-17 9:56 ` sendmail " Adam Sjøgren
2008-05-17 23:46 ` reader
2008-05-18 4:07 ` Adam Sjøgren [this message]
2008-05-19 14:41 ` reader
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=87d4nk45n3.fsf@topper.koldfront.dk \
--to=asjo@koldfront.dk \
--cc=ding@gnus.org \
/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).