Thanks for the informative response.
etresoft wrote:
I am talking about your SMTP address. You have at least two e-mail addresses. There is your IMAP/POP server for your incoming mail and your SMTP server for your outgoing mail.
Some ISPs don't like people connecting to any other SMTP servers but their own and will intercept any SMTP port 25 connections. Then, when you use your Yahoo credentials to try to connect to SMTP, the ATT server will intercept it and reject your login attempt. To avoid this, always configure your e-mail to use SSL. It is more secure anyway.
Throughout this process my incoming and outgoing servers have remained unchanged. And in mentioning AT&T/Yahoo I didn't mean to suggest that I had two sets. Yahoo is the email provider for AT&T. My SMTP address, e.g., is smtp.att.yahoo.com. Per AT&T's instructions the port for outgoing mail is 465. SSL is also used.
I have been using OpenDNS most of the time for the past year or so. The technician I hired tried setting the IPv4 configuration manually and experimented with different DNS addresses. The Genius Bar set it back to DHCP, which seemed to make a difference at the time. It's still set on configure by DHCP. I have the two DNS addresses given by OpenDNS and one given to me by the technician on my DNS address list.
I'll take that as a "yes". OpenDNS isn't bad. I don't like the idea of technician "experimenting". Who knows what else was changed.
Thanks for the reassurance about OpenDNS. I have been getting different reactions when I tell the people from whom I've been seeking help that I use it. And I believe the technician, whom I have used for years, did identify and, with AT&T's help, fix some associated internet connection problems. And when I switched over to the other two email clients I did not experience the problem one time.
I did once, but there was so much information and I had no idea what to look for anyway.
That is what we are for. Run Console.app and then try to trigger your e-mail problem. If the problem occurs, copy and paste the most recent Console.app entires here and we can tell you if there is something amiss than can be easily fixed.
I don't know how to trigger the email problem. [If I did, I might have a solution. -;) ] Can I take the alternative approach of checking Console entries when I experience the problem? Or does Console have to be running in order to log the events? If so, could I just keep it running the next few days till I know one way or another whether the problem has been solved by the reinstall? [I've not encountered it so far, but there hasn't been much outgoing mail the past couple days.]
Not sure what you mean by a new account. If you mean with an ISP, I've only got one. I wouldn't know how to go about creating another.
I mean a new account on your computer. Some of the preference files can be hard to track down. If you can reliably reproduce this problem on demand. Create a new account on your Mac, setup the e-mail the same way it is on the old account, and try to reproduce the problem. If you can't, then you can copy the most recently modified preference files in ~/Library/Preferences back to your home account. That is an easy way to fix preference files if you aren't sure which ones have problem or how to fix them.
I'm inclined to wait to try this till I experience the problem. And by "new account on your computer" I'm taking you to be referring to an internet connection account, i.e., to duplicating the current one under a different name to see if that solves the problem.
You say if it does to copy the recently modified preferences back to the home account. Since I would be duplicating the current account, couldn't I simply continue using it as my home account?
Thanks again,
Eric Weir