On 4/28/08 5:26 AM, Bill Cheeseman at [EMAIL PROTECTED] wrote: >>> one she >>> uses at home where we're on Comcast cable, and one that requires different >>> Entourage settings because at work she has to go through Budget Dialup >>> because she doesn't have cable. But, ultimately, both Entourage accounts >>> connect to the same, single ISP account. ... > As I understand the service Budget Dialup (and others like it) provides, > they are forwarding my wife's email to and from our regular ISP. They > operate as a backup Internet access service via PPP where cable isn't > available (they have phone numbers everywhere), and when you're traveling > beyond the area where your regular ISP has phone numbers. Part of the > attraction is that all mail is sent and received through your regular ISP. > I's very inexpensive. <http://www.budgetdialup.com/html/learn_usrbackup.htm>
The ISP where your mail is received and the ISP you use to connect to the Internet are really independent of each other (sending mail can be a different matter). For receiving mail, generally the POP or IMAP protocol is used. Most ISPs will not care where the connection is coming from (e.g. If you're connected via Budget Dialup, Comcast will happily let you retrieve your mail via POP or IMAP) and there are no changes required to the Entourage account information to do so. Sending is a different matter. No respectable ISP will allow mail to be sent via their servers without authentication unless it originates on their own network. So in the base case, you need separate account settings for sending via a different ISP. Entourage is happy to allow you to set up a "Send only" account - just leave the "Receiving Mail" portion of the account settings empty (I think it will warn you about this but it will still let you do so). Note also that it will send mail as whoever you want it to send as. Just because you're sending via Budget Dialup doesn't stop you from sending as [EMAIL PROTECTED] (although I've heard of ISPs that will not allow this - they should be avoided). But I think you know that as you have your own domain name (cheeseman.name). There are other ways to deal with sending while connected to different ISPs. Some support authentication. Unfortunately, some ISPs block you from sending via another ISP on the default port (25). Ideally, your mail ISP support sending via TCP/IP ports other than the default. My mail "ISP" (which is actually me on my own computer as I run my own mail server on the iMac sitting right behind me) permits sending on the "secure submission" port (465) and the regular "submission" port (587) and I've never run into an ISP that blocks sending via those ports. To avoid having to do any account settings changes when traveling, I always have mail sent via 465 even when I'm at home with the computer on the local network. -- Larry Stone [EMAIL PROTECTED] http://www.stonejongleux.com/ -- To unsubscribe: <mailto:[EMAIL PROTECTED]> archives: <http://www.mail-archive.com/entourage-talk%40lists.letterrip.com/> old-archive: <http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
