[115457] in North American Network Operators' Group
RE: Is your ISP blocking outgoing port 25?
daemon@ATHENA.MIT.EDU (John R. Levine)
Mon Jun 22 12:38:34 2009
Date: Mon, 22 Jun 2009 17:38:14 +0100 (BST)
From: "John R. Levine" <johnl@iecc.com>
To: Frank Bulk <frnkblk@iname.com>
In-Reply-To: <!&!AAAAAAAAAAAuAAAAAAAAAKTyXRN5/+lGvU59a+P7CFMBAN6gY+ZG84BMpVQcAbDh1IQAAAATbSgAABAAAAB9POZZ61cfQrsvm3hZ4R+OAQAAAAA=@iname.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
> The bootstrap question is addressed by requiring the end-user to know their
> e-mail address and password. Based on the domain name, the implementation
> would reach out to https://something.domain-name.tld and download the
> relevant "schema" and data for IMAP, SMTP, POP3, etc, in ordered priority.
> Based on what the e-mail client could support, the desired settings would be
> displayed, and upon end-user approval, applied.
End-user approval? That means support calls, ISPs wouldn't like that.
I can believe something like this could be made to work, but I would think
hard about all the way that web sessions can get screwed up or hijacked
before I persuaded myself that a scheme was likely to work where it needed
to work (e.g., when connecting to a hotspot that hijacks all web sessions
until you log in) while not being subject to hostile spoofing.
Followups definitely to IETF-something.
R's,
John
