how-to block ads
|
NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
 ·Pacific Bell - SBC
| reply to jeffkrol
Re: Stupid email and Yahooo and ATT....
said by jeffkrol  :Yes, that's what was suggested in my first call re: this issue, and at the time I was using Netscape 7.2 as a mail client and apparently they didn't feel that that would be free to fix. Anyways I ignored the phone number.. Netscape 7.2? Ancient. Creaky. Insecure. Unsupported by anybody (Netscape doesn't exist any more, got swallowed up by AOL). Try this:
»www.seamonkey-project.org/
Components and GUI are identical to Netscape 7.2
Not that I think this is part of the problem; but, unlike Netscape 4.x, which has some modest reason why people try to keep it alive, there is nothing about Netscape 7.2 to recommend it over SeaMonkey.
Decided it was time to get aggressive and go to Thunderbird.
I'm really not going to go into all the clients/permutations that failed including the multiple SMTP addresses ect. Only thing that does is give me a different error message..
Of which I have seen not one in the entire thread. You say you "patched Outlook". By that, do you mean "MS Outlook", the mail client that is a part of the MS Office suite?
So far, WRT the problems you have cited, I can honestly say, "You are the only one". Others have had problems, but managed to get things working again.
So...what does the error message look like? In its entirety, please.
Your first screen shot shows that you are trying to add a sub account which already exists. What were you trying to do? And what is the screen shot trying to show? If you don't mind filling in the details.
Otherwise, this really belongs in another place.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum | |
jeffkrol
join:2004-02-22
Stevens Point, WI
·AT&T Midwest
edit:
May 7th, @09:28AM
| I know about the"old" Netscape but old habits die hard.
And according to the FAQ, one version of MS Office (w/ Outlook) apparently needed a patch to get it to work correctly. I had downloaded and installed it per the instructions.
As to the ROOT CAUSE of all my gnashing and wailing, APPARENTLY the "verification process" never took, even though, as you can see they told me it was and yet was not listed in the box to the left.....that was the whole problem.
Last night I re-did all the verifications and they took.
The brand spanking new "test account" I created last month needed further verification as well. How much of this was all my fault? Not sure. I had done all the same steps the first time I tried to verify but this time all worked as it should have.
ALL problems seem to be solved now. I still have to poke ATT/Yahoo a bit as to the fact that finding the "verification process" page was not very easy and it was a good thing I have the old tech support emails to help on this...BUT it was mostly an ID10T problem.... 
Actually looking over my screne captures I can probably see the error of my ways...
ONE major question remains for me to check out is why it all worked in Outlook Express (which is probably as good as Netscape 7.2) w/ out the "good" verification???
Unfortunately since I have been half heartedly working on this "project" since March, I may never know what I did right/wrong or what may have gotten changed in the meantime.. | |
NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
·Pacific Bell - SBC
| 
Merged and Extra |
said by jeffkrol :I know about the"old" Netscape but old habits die hard. Give SeaMonkey a spin. Should be the same as, and more secure than, Netscape 7.2. No learning curve at all; menus are identical. Should be able to just import your Netscape settings and fly. (Recommend backup of user data, naturally.)
And according to the FAQ, one version of MS Office (w/ Outlook) apparently needed a patch to get it to work correctly. I had downloaded and installed it per the instructions.
MS Outlook patch is for an SSL compatibility, which is a separate issue from email address verification.
As to the ROOT CAUSE of all my gnashing and wailing, APPARENTLY the "verification process" never took, even though, as you can see they told me it was and yet was not listed in the box to the left...
Verification should not be required for the ID of the account used. I.e., log in to the server with '%User_ID-foo10@ameritech.net', and send from '%User_ID-foo10@ameritech.net', should work. Only when you log in to the server as '%User_ID-foo10@ameritech.net', but try to send from '%User_ID-foo11@ameritech.net' would you need to verify the sender email address.
ALL problems seem to be solved now. I still have to poke ATT/Yahoo a bit as to the fact that finding the "verification process" page was not very easy...
I tried an unverified send a bit earlier, to get the error message for a fellow who hasn't seen it, yet. The link is in the error message; I bookmarked it the first time I got it.
BUT it was mostly an ID10T problem....
Trying to recover from one of those, myself, right now. I managed to scramble the registry of a Windows Me computer. The next oldest registry database is nearly a year old, and I have know idea how many changes may have been made in that year.
BTW, when I first migrated to SBC Yahoo! DSL Service, they allowed us to merge Yahoo! accounts, so I created a free Yahoo! Mail account to merge with the '@pacbell.net' account in the screen shot. Later, they took away the ability to merge accounts, but added the ability to create an "Extra email address", so I created on on this account. Each of the '@yahoo.com' email addresses was "pre-verified" by virtue of being a merged ID, or being created within the account. Only the "Verified" email address had to go through the verification process.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum | |
-
|
