From: Simon Josefsson <jas@extundo.com>
Subject: Re: Emacs 21.2, smtpmail and vm
Date: Thu, 30 Jan 2003 01:06:42 +0100 [thread overview]
Message-ID: <iluof5zmrfx.fsf@latte.josefsson.org> (raw)
In-Reply-To: 5l3cnb94ab.fsf@rum.cs.yale.edu
"Stefan Monnier <foo@acm.com>" <monnier+gnu.emacs.help/news/@flint.cs.yale.edu> writes:
>>> Could anybody give me the skinny about "why would an ISP require SMTP AUTH"?
>> Isn't the answer the same as why authentication is required it all, in
>> any protocol?
>
> I'd only buy that if its use were systematic, which it obviously isn't.
It takes time for people to realize that authentication is required.
Few of the old Internet protocols included authentication from the
start.
>> If you are thinking that ISPs should use IP based ACLs to allow
>> relaying for their customers, it's not going to work with todays
>> computer habits (people travel with their laptop and expect the mail
>> server to continue to work).
>
> By "laptop" you mean "those things with small screens and shallow
> keyboards"?
Yes.
> I must admit I don't know enough of how those things work when you
> try to use the Internet away from home (or office). But it seems
> you'll need to get your IP from some ISP which is responsible for
> routing to/from your IP and which has a mail server which you should
> be able to use (like you probably use their DNS server). And given
> such a context, it seems that IP-based authentication would be
> pretty safe for SMTP.
Ordinary users doesn't know about IP addresses and forgets about the
SMTP server after configuring it once. One might think that DHCP
could set the SMTP server address as it does the DNS server address,
but there are practical problems: You cannot easily abuse a DNS server
as a client, but you can very easily abuse a SMTP server as a client
(spam). Just because people with their laptops get their IP from an
ISP doesn't mean that the ISP know whom that person is, or know how to
sue her when she sends spam through their network. If people route
their stuff via their home, it is not the ISPs problem any more.
next prev parent reply other threads:[~2003-01-30 0:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-28 12:22 Emacs 21.2, smtpmail and vm Chris Hall
2003-01-28 17:12 ` Kai Großjohann
2003-01-29 10:06 ` Chris Hall
2003-01-28 18:13 ` Kevin Rodgers
2003-01-29 10:04 ` Chris Hall
2003-01-28 19:06 ` Stefan Monnier <foo@acm.com>
2003-01-29 10:08 ` Chris Hall
2003-01-29 17:29 ` Simon Josefsson
2003-01-29 18:53 ` Stefan Monnier <foo@acm.com>
2003-01-29 19:55 ` Kai Großjohann
2003-01-29 20:42 ` Stefan Monnier <foo@acm.com>
2003-01-30 0:06 ` Simon Josefsson [this message]
2003-01-30 15:40 ` Stefan Monnier <foo@acm.com>
2003-01-30 21:01 ` Simon Josefsson
2003-01-28 20:19 ` Martin Stemplinger
2003-01-29 10:15 ` Chris Hall
2003-01-29 17:25 ` Simon Josefsson
2003-01-30 20:18 ` Martin Stemplinger
2003-01-30 20:52 ` Simon Josefsson
-- strict thread matches above, loose matches on Subject: below --
2003-01-29 11:00 Chris Hall
2003-02-03 1:39 Emacs 21.2, smtpmail, " Chris Hall
2003-02-03 8:25 ` Kai Großjohann
2003-02-04 6:18 ` Chris Hall
2003-02-03 10:30 ` Simon Josefsson
2003-02-04 6:45 ` Chris Hall
2003-02-04 9:30 ` Kai Großjohann
2003-02-05 7:25 ` Simon Josefsson
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=iluof5zmrfx.fsf@latte.josefsson.org \
--to=jas@extundo.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).