chicagofan wrote:
u...@domain.invalid wrote:
chicagofan wrote:
Did you see Gabrielle's message which said, her problems went away after
she deleted her existing news account, and set it up again? Have you
tried
that?
I have the same problem with my upgrade using news.ett.com.ua - and
this is
a test on news.mozilla.org so if you can read this, then using a new news
server does not cause problems which are there for an old news server
(pre-upgrade).
Reading you just fine. :) I'm not following what you are saying about
"causing" problems, but I understood Gabrielle to have solved her
problems by
re-creating the accounts and newsgroups she needed, with 2.0... after
the migration.
Yes, my post was not a model of clear communication.
If you're saying mozilla.org worked on your previous version, and also
works in
2.0, but ett.com does not, I get it. :) I'm just guessing, but it seems
like
the varying methods ISPs or news servers use for log in are throwing SM
a curve.
I did not have mozilla.org set up in the 1.x version. But I added it in 2.0 and
it works fine.
I did have ett.com set up in the 1.x version, and obviously it worked, but I
cannot post in SM 2.0. As I am more of a reader than a poster it's not really a
big deal for me.
I am using a relay for SMTP and I have a password and "Use secure
authentication" checked. But that is between me and my ISP isn't it.
I wish I had the answer, but other than verifying that server settings are
correct for each server used, and checking the SMTP settings, I'm at a
loss.
Have you checked with ett. com for some suggestions?
I'm worried about what may happen to me this month, when my ISP makes some
changes to my sign on [for security purposes they say]. We are going to
have to
add our zip code to the sign in. That should be interesting. :(
bj
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
