XPost: alt.comp.software.thunderbird   
   From: address@is.invalid   
      
   Adam,   
      
   > I use the email address from the ISP for service-related messages.   
   > I have addresses used for specific purposes and I use SMTP servers   
   > associated with the respective inbox. The connection is made to   
   > the Submit server (port 587) per RFC 3676 instead of the SMTP port   
   > (25).   
      
   Thanks for confirming that SMTP traffic is not, by DPI boxes or otherwise,   
   blocked in an ISPs network or at its border.   
      
   Yes, using an encrypted connection instead of a plain-text one is ofcourse a   
   good idea, and I can easily imagine why an ISP decides that /its own/ email   
   service does not offer plain-text access (port 25 and others) to them   
   anymore.   
      
   Heck, even my own ISP has (just a few years ago!) stopped doing that.   
      
   ... and with it ofcourse negating the whole reason for blocking port 25   
   traffic. :-)   
      
      
   By the way: I just took a look at that RFC you mentioned and could neither   
   find "25", "587" nor the word "port" in it.   
      
   Another "by the way" : did you know that one of the email related RFCs   
   specifies that an email server should accept *all* SMTP requests, even from   
   people who are unknown to it ?   
      
   Years ago I was quite disgusted when I found out that not even enabeling   
   name/password access to the email service ment it would stop anyone from   
   using my name and email-addy in theirs - not even on that same server   
   (making it *very* hard to spot a joe-jobber).   
      
   regards,   
   Rudy Wieser   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)