Paul B. Gallagher wrote:
Phillip Jones wrote:
Paul B. Gallagher wrote:
[email protected] wrote:

Paul B. Gallagher wrote:
As many of you know, AT&T is doing away with its WorldNet service and
switching those users to its Dial Internet service. After making the
appropriate changes to my server settings in SeaMonkey, I get the
following error message every time I poll for new mail:

============================================================
Security Error: Domain Name Mismatch


Paul,

I also used Worldnet and have changed over to the Dial Internet
service.

I've not had problems receiving email so I'd expect that you should
have
success with the settings I'm using.

new address [email protected] old address [email protected]

Server Type: POP Mail Server
Server Name: postoffice.att.net Port: 110

Connection security: none

Outgoing Server (SMTP): mailhost.att.net


Because this was an account change from Worldnet to Dial Internet and
not a new account, no change in email password was necessary.

Well, obviously if I switch from SSL to an unsecured connection, SM
won't look at the certificate and the issue vanishes. But they recommend
port 995 and I'm happy to oblige.

When I first made the changeover (see upthread), I followed instructions
and used ipostoffice.att.net on port 995 and SM kept nagging me that the
certificate didn't belong to ipostoffice.att.net, but to
ipostoffice.worldnet.att.net. I was clicking "OK, go ahead and make the
connection, thank you very much for asking AGAIN, but I tired of it and
asked for an automated way to tell SM that this particular certificate
was OK. Turns out there's no way, so I've gone back to specifying
ipostoffice.worldnet.att.net.

But you would know that if you had read the whole thread, or even my
original query.

I'm going to ask a dumb question so feel free to pummel me into the
ground.;-)

If you like, but I won't get any pleasure out of it.

does the message give you an option to accept permanently the
certificate?

No. If it had, I would have done so and that would've been the end of it.

--------------
And as to the fellow's suggestion above. he was trying to do a good
faith effort to get you running.

The tone of your message, you sounded as if you were trying make him
look stupid, for suggesting such a thing.

Let's not overdramatize; I wasn't trying to make him look stupid. But to
join at the end of a thread after an issue has been resolved and propose
something that has already been discussed as if it were new isn't helpful.

You tried your way, you failed, So he was suggesting an alternative
method to get you running.

Now it begins to look like you haven't read the thread either. If you'll
read upthread you'll see that the issue has been resolved, though not
exactly the way I would have hoped. I've gone back to using the
soon-to-be-obsolete worldnet address, which does not provoke the prompt.
Somewhere between now and March 15, AT&T will probably fix the
certificate issue and I'll find I have to use the new mail server
address; easily managed.

This will be the last time I go to the trouble of reiterating everything
that has gone before in the thread. If you have something to contribute,
great, but if you just want to see how well I can paraphrase, please go
somewhere else. I have better things to do with my time.

Thank you.

try usingseamonkey 2.02 to view CALL HISTORY from within att Uverse ... Tech says it uses Flash
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to