XPost: alt.comp.software.thunderbird   
   From: address@is.invalid   
      
   Paul,   
      
   > I believe who is blocked, is anyone from outside an ISP   
   > attempting to use an "open" SMTP implemented inside the ISP.   
      
   And that would solve .... what exactly ?   
      
   You can't just throw some SMTP traffic at an IP (within your own ISPs   
   segment or not) and expect it to work.   
      
   > If I move my server to 1.2.3.4:1025, it is the protocol   
   > which is effectively blocked,   
      
   Trying to do any kind of inspection, even a deep one, doesn't work all that   
   well when SSL is used.   
      
   > You're not supposed to be running *any* server on a $39.95   
   > per month consumer plan.   
      
   Why not ?   To an ISP its the ammount of data that counts.   Also, having a   
   home server for VPN access from your smartphone (and than out into the world   
   again)  is a rather accepted thing to do.   Heck, the some modems/routers   
   have build-in VPN server capabilities.   
      
   Heck, even my own internet modem has port-forwarding capabilities - for   
   exactly that purpose.   
      
   > If any ISP were to start emitting spam email traffic,   
   > there are tables of spammers available for other ISPs to   
   > block, so you would soon find that your ability to "handle   
   > (spam) mail successfully" was blocked.   
      
   You are the only one here that is talking about spam...   
      
   > If there is a naughty thing you should not be doing,   
   > the ISP has a filter for that.   
      
   Ah yes, trying to use a different email provider than the one your ISP (not)   
   offers is *ofcourse* naughty.   
      
   Funny that I can use a newsgroup provider (ES) which is *definitily* not in   
   my ISPs segment, but wanting to be able to use another email provider is a   
   no-no.   
      
   Regards,   
   Rudy Wieser   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)