@VectorVictor wrote:
@Justin wrote:
@kemosabay wrote:your incoming port setting should be 110, I believe. At least that's what mine is. I also reset my port settings per the e-mail and it didn't work so I set them back and all is ok now....
Then you did something wrong.
What email client are you using? There are samples of correct definitions posted here for the most commonly used email clients.
__________________________________
Justin
FiOS TV, 25/25 Internet, and Digital Voice user
QIP7232, QIP7100-P2, IMG 1.9
Keller, TX 76248Whoa there, Justin--he didn't do anything wrong. The port settings that Verizon sent out for the incoming server are still set to 110 on Verizon's side--the settings they sent flat out do not work yet, so don't be jumping all over Kemosabay.
If you follow the instructions Verizon provides for outlook, you cannot access incoming.verizon.net because the port they are using is still 110, not 995, bottom line.
If anything, save your snark for Verizon. as they sent these changes out via email without a clear and defined date in which they will go live.
If you are going to post something here criticizing someone else, you should at least make an attempt to be correct with what you post. Your statements are plain and simply wrong!
And yes, he did something wrong!
The email Verizon sent out contains a link to a Verizon web page describing the changes to be made. This is directly from that web page:
That web page also has links for each of the various Outlook versions; here is what is shown on the Outlook 2010 page:
The pages for each of the other Outlook versions have the same text.
So, where is the port 110 setting you claim Verizon has specified?
As to a "clear and defined date", they don't need to provide one, the settings have worked for months. I know this for a fact because I have been using them for months.
Care ot Apologize?
__________________________________
Justin
FiOS TV, 25/25 Internet, and Digital Voice user
QIP7232, QIP7100-P2, IMG 1.9
Keller, TX 76248
@whatagain wrote:Justin, you seem to know a lot about this issue, so I am hoping you will reply. I have been uasing computers since 1985, so I am not a neophyte. I had an XT with DOS3 in 1987, moved to DOS4, 5, and 6, then Windows, and am now running XP. I have beta tested for IBM, you name it.
Now, I am stuck. I use Outlook 2002, and it's been running fine for years. Now Verizon comes along with "improvements." The last thing they "improved" was killing access to my Web site via FTP. When I received their e-mail on 12/21, I changed Outlook exactly as suggested. When I could not access my e-mail, I called them (1-800-567-6789).
The first technician told me (falsely, I assume) that this was not going to be a mandatory change, and that I could leave the settings at 110 and 25. Uh-huh.
Remembering what happened with the FTP change eventually becoming mandatory, I waited a couple of days, and tried again. Still nothing doing, so I called another tech, He linked to my computer, and tried everything, even turning off my Fire Wall. He put me on hold, and checked something, or checked with someone, and came back to inform me that Verizon was having problems with the server, which would be fixed within 24 hours, and to try again later.
Well, it is later. Days later. Still not working. I do not want to use Verizon's clunky Web mail any more than I wanted to use Verizon's clunky Web-based method to access my Web site.
Any suggestions from you, anyone else, or someone from Verizon would be welcome.
I am happy to reply, just not sure how helpful I can be.....and some here obviously think I do not know what I am talking about....
What I know for sure is that I am successfully using the SSL ports with Verizon email using Windows Live Mail, Outlook Express, and Thunderbird clients. And have been for 4 or 5 months. 
I do not have any version of Outlook so I have no way to test any settings with that. However, the settings should be very similar to the settings for Outlook Express, for which I did post a thread here documenting the Account Settings that will work with SSL.
I went to the Verizon web page for Outlook 2002 and found this info:
Have you done all of the steps documented? I think what is tripping most people up is they change the port number but don't choose the "use SSL" option, which is required when using the new ports, for both sending and receiving. Another possibility for a problem I think is some people are apparently setting the login to use "login using secure password authentication" (that is the wording on Windows Live Mail, I assume there is something similar with Outlook). I tried that setting in WLM and it broke my login, but from what I can tell using either plain text or authenticated POP works (at least both worked for me on WLM).
What error message are you getting?
Oh, and are you by chance using Avast anti-virus? That changes things a quite a bit.
As to the change being mandatory, I have no idea. But I think it would be a good idea if Verizon did eventually make it mandatory. The problem they are addressing is that without using the new ports and SSL, all emails are transferred between your computer and the email server unencrypted, in both directions. You may not care if others can read your emails, but I think lots of people, and especially companies, do care. And SSL (Secure Sockets Layer) has been around for a long time, it is also the basis for HTTPS for web browsers. Verizon is very late implementing SSL for email, many other email providers, probably most, already use it as an option or require it. But again, I have no idea whether Verizon plans to make using SSL with their email mandatory or not, and if so, when, as far as I know they have not made any announcement regarding it possibly being mandatory.
I hope this helps. If you still can't get it working, please post whatever error message(s) you get and maybe we can get it figured out.
Just an aside since you mentioned beta testing for IBM; I got into the computer business in 1965 as a programmer for Western Electric, worked for IBM from 1967 until 1992, then an IBM Business Partner from 1992 through 2002, when I finally decided I had had enough I worked in the mainframe area the whole time, but I was a big loser in the employee's IBM PC lottery in 1981, I unfortunately got one that summer - 64K, two single-sided 8" diskette readers, a monochorme monitor, DOS, a printer, and a word processing program, all for the measly sum of about $4800. Just think what you can get for that sum today!
__________________________________
Justin
FiOS TV, 25/25 Internet, and Digital Voice user
QIP7232, QIP7100-P2, IMG 1.9
Keller, TX 76248
Perhaps that will help someone, especially if a Verizon tech reads my post. However, my problem and the solution, may be unique to my setup. After all, how many people are still using XP, with its firewall disabled in favor of Sygate, which is a six year old app no longer available, thanks to Norton Symantec? Not to mention the Westell DSL modem and its firewall?
However, the second tech did come close, turning off Sygate. If he had he accessed the modem, who knows? But none of this is for the faint of heart. I've done a lot of tweaking in my time, and there are some things I'm still wary of clicking on. 
Again, good luck helping others here, Justin.
_______________________________________________
"Where does it say to change to an SSL connection?"
_______________________________________________
You are kidding right? I sure hope so, but just in case you aren't......
Copied directly from the email text you posted:
I don't think Verizon could make it much clearer.....
__________________________________
Justin
FiOS TV, 25/25 Internet, and Digital Voice user
QIP7232, QIP7100-P2, IMG 1.9.1
Keller, TX 76248
