[61526] in North American Network Operators' Group
RE: Fun new policy at AOL
daemon@ATHENA.MIT.EDU (Vivien M.)
Fri Aug 29 16:25:05 2003
From: "Vivien M." <vivienm@dyndns.org>
To: "'Matthew Crocker'" <matthew@crocker.com>
Cc: "'Mikael Abrahamsson'" <swmike@swm.pp.se>, <nanog@merit.edu>
Date: Fri, 29 Aug 2003 16:20:02 -0400
In-Reply-To: <93950C8C-DA5D-11D7-8DC7-000A956885D4@crocker.com>
Errors-To: owner-nanog-outgoing@merit.edu
> -----Original Message-----
> From: Matthew Crocker [mailto:matthew@crocker.com]=20
> Sent: August 29, 2003 4:16 PM
> To: Vivien M.
> Cc: 'Mikael Abrahamsson'; nanog@merit.edu
> Subject: Re: Fun new policy at AOL
>=20
> Port forward 127.0.0.1:25 through to someplace.edu:25 using SSH. Or=20
> VPN. Or ...
>=20
> More than one way to skin this cat.
If you have a shell account on someplace.edu, yes, I agree, that's =
probably
the best way (and if anyone looks at the headers of this message, that's =
how
I've been doing SMTP for like three years now... Too lazy to set up SMTP
AUTH somewhere where I'm the admin).=20
But if you have no shell account, or you're not technologically clueful,
you're still hopeless... So, the conclusion still seems to be that SPF =
and
such things will break your email, unless
i) SMTP AUTH is available
ii) You're sufficiently clueful (and required things like VPN, SSH, etc =
are
available) that you can implement a workaround.
Vivien
--=20
Vivien M.
vivienm@dyndns.org
Assistant System Administrator
Dynamic DNS Network Services
http://www.dyndns.org/=20
