----- Original Message ----- From: "Adam Campbell" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Wednesday, March 02, 2005 06:37 Subject: Re: [IMail Forum] ISP's blocking port 25 except to their own mail servers
> I make my home users connect via VPN. If they have dialup, they dial > their ISP then use VPN. If they have cable or DSL, they use VPN. I had > one recently who had enough of using our 800 dialup and got cable; he > didn't have an ISP. > > I block messages where the sender's address has my company's domain. > > My thinking is that a tele-commuting(?) employee should use his ISP's > server with his ISP-given address to send mail or use his employer's > server with his employer-given address. There are a lot of roaming users out there. Their only other alternative is a webmail service (whether through us via IMail's webmail or through Yahoo). However, if they are using a client like MS-Outlook, they are very likely using calendaring, task-management and the like, and likely that means that they want to have a POP3 or IMAP connection to us. With the growing number of ISPs (like the one I work for) that block port 25 outgoing (it's the easiest way to at least prevent worms and the like from spreading out of our network), the roaming user is in a very serious position. Opening up port 587 with SMTP AUTH solves the problem, and as long as port 587 isn't blocked by ISPs, and as long as mail admins are making sure that there are no open relay problems, then things will go quite smoothly. I hope that this picks up enough steam in the next few years that eventually mail clients will come with port 587 and SMTP AUTH turned on automatically. -- Aaron Clausen To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
