<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Arial; font-size: 12pt; color: #000000'>That's a good point, Derek. But block lists are for your outbound mail (i.e. inbound to the recipient) and the question was about inbound access. You could always use the EC2 IP for your MX record for inbound mail and route your outbound mail through your ISP or some other service. Still, it's something you have to be aware of to work around.<br><br><div>Scott<br><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Derek Atkins" <warlord@MIT.EDU><br><b>To: </b>"Atlanta Linux Enthusiasts" <ale@ale.org><br><b>Sent: </b>Friday, June 8, 2012 9:48:32 AM<br><b>Subject: </b>Re: [ale] [OT] AT&T/UVerse going to carrier grade NAT?<br><br>Scott Plante <splante@insightsys.com> writes:<br><br>> You could do that with an Amazon EC2 instance. It's free for the first year<br>> and pretty cheap after. You get a virtual Linux box and you can even get a<br>> static IP. You could set up ssh (or better, autossh) with port forwarding,<br>> then just go to your instance's IP (or name). You could probably set up<br>> OpenVPN on the instance too, and then connect from to it from both ends (home<br>> and wherever you are).<br><br>Except, of course, that most of the Amazon EC2 network block is on every<br>DNSBL around because spammers use EC2 hosts. So EC2 is generally<br>useless if you want a mail server.<br><br>-derek<br>-- <br> Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory<br> Member, MIT Student Information Processing Board (SIPB)<br> URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH<br> warlord@MIT.EDU PGP key available<br>_______________________________________________<br>Ale mailing list<br>Ale@ale.org<br>http://mail.ale.org/mailman/listinfo/ale<br>See JOBS, ANNOUNCE and SCHOOLS lists at<br>http://mail.ale.org/mailman/listinfo<br></div><br></div></div></body></html>