SeaMonkey seems not to post to NNTP using auth
Bill Davidsen
Fails on port NNTP (119) and NNTPS (563 with SSL) with this message:
http://www.tmr.com/~davidsen/Private/SS-NoPost-SM2.0.png
And my first test post to this server failed silently as well. WTH?
NOTE: since tested on another server with auth, fails there as well.
NoOp
news.eternal-september.org works just fine for me. Server settings 563
SSL/TLS 'Always request authentication when connecting to this server-
outgoing server is the same as this email account.
Followup-To: set to mozilla.support.seamonkey
Barry Edwin Gilmour
Don't think I've seen it on port 563 (NNTP/SSL~)
My workaround has been to reopen another instance of the compose-window
(usually a reply-to newsgroup/sender/etcetera), and then to cut and
paste my-reply into the newly-opened compose-window, which sends OK.
It doesn't seem to matter whether I close the first (borked) instance,
before or after I have successfully-sent the second (good) instance.
(You can retry sending the first instance as-often as you like, but it
will return that message every-time.)
Fairly-frequently, but not-always, I have also previously-observed a
similar-event when my composed-email-reply has the sender's
signature-images therein (business-footers), or even when my own
signature-image is in a respondent's email that I am replying-to
(sometimes with an extra popup saying I don't own my _own_ image).
Removal of the offending image/s sometimes-worked in these cases, but
there-too, I often had to do the reopen another instance of the
Compose-window, using the original-menu-entry
(reply-to-newsgroup/sender/etcetera), and then do the cut-and-paste
trick, which has so-far been a total-success for me, on dozens of
borked-email-sends.
I have noticed that if I am too-long composing-a-reply, even to non-HTML
ordinary-text emails, I get the same-message, and the cut and -paste
workaround is likewise successful for these events.
Bill Davidsen
check or not checked (which asks for auth, so it still should work), and
since I have no idea what "outgoing server is the same as this email
account" means, I have tried with accounts called just
"eternal-september" (the original) and "news.eternal-september.org" in
case that's what you meant. The outgoing SMTP host name is the same as
all other accounts, which have no auth and work fine.
Here's the positive indication of a problem:
I ran tcpdump to see if SM was using the open socket or starting a new
one, possibly without auth, and it is *not* generating any packets at
all! WTH can that indicate, other than some internal sanity check is
failing?
I've tried with migrated accounts, and with newly created accounts,
tried fresh profiles, it really looks as if there's a bug here in in
accounts requiring auth (not just e-s).
A rethink is requested, WFM doesn't fix the problem and others are
reporting it as well.
Bill Davidsen
Reported as bug https://bugzilla.mozilla.org/show_bug.cgi?id=525649 if
anyone else seeing this would please confirm, vote, etc.
This is kind of blocking migration from 1.1.18 for several groups with a
customer support news server.
chicagofan
>> On 10/30/2009 02:50 PM, Bill Davidsen wrote:
>>> Server: news.eternal-september.org Fails on port NNTP (119) and NNTPS
>>> (563 with SSL) with this message:
>>> http://www.tmr.com/~davidsen/Private/SS-NoPost-SM2.0.png
That's the same message I get *anytime* ES has too much traffic or they are
doing maintenance, etc., which is not uncommon. Is this the only message you
have gotten, besides not being able to connect, of course?
>>> And my first test post to this server failed silently as well. WTH?
>>>
>>> NOTE: since tested on another server with auth, fails there as well.
>>
>> news.eternal-september.org works just fine for me. Server settings 563
>> SSL/TLS 'Always request authentication when connecting to this server-
>> outgoing server is the same as this email account.
It's working fine for me too, on Port 119, as news.eternal-september.org, with
the "Always request authentication" box checked under the news server settings.
Note, my setup isn't using SSL [Port 563] though.
Hope something works for you, but I don't think it's a SM 2.0 problem. :)
bj
lr...@superlink.net
I have a problem that has the same symptoms that started after I
installed SM 2.0. I had to sign on to my google(tm) account to post
here.
Suggestions?
LR
NoOp
Not sure what the issue might be Bill. I've migrated 4 machines (linux)
from 1.1.18 to 2.0 and _all_ have no issues accessing
news.eternal-september.org (port 563/SSL). I've 2 test machines that
have yet to be migrated & I'll see if I can get them done this weekend &
let you know if they have issues. Have you tried from a different profile?
Sledge Hammer
NoOp
I've just tested on a 2.0 Win2KPro machine and now experience the same
issue as Bill. It's not the server as I can post to the server via my
linux machine (posted a response in the same thread as Bill tried to),
but not from the Windows machine where I created a new
news.eternal-september.org account. That however is from a
VirtualMachine, so I'll need to load up an actual WinXP box to test
further (one with a 1.1.18 mail/news & then migrate to 2.0) and test on
another linux box as well.
So Bill... you may not be spitting in the wind afterall :-) I'll keep
testing and see if I can figure out the issue.
Gary
NoOp
...
> I've just tested on a 2.0 Win2KPro machine and now experience the same
> issue as Bill. It's not the server as I can post to the server via my
> linux machine (posted a response in the same thread as Bill tried to),
> but not from the Windows machine where I created a new
> news.eternal-september.org account. That however is from a
> VirtualMachine, so I'll need to load up an actual WinXP box to test
> another linux box as well.
>
> So Bill... you may not be spitting in the wind afterall :-) I'll keep
> testing and see if I can figure out the issue.
>
> Gary
And just to confirm that nntp is working on this Win2KPro VM test machine...
NoOp
Seems to have been a profile issue; switched to a clean 'test' profile -
the same one that I use for litmus testing w/no add-ons, created a new
news.eternal-september.org server nntp, posted to both the support and
the test groups without issue on the Win2KPro machine. This indicates to
me that: 1) Bill may have had an issue with:
<quote>
I've tried with migrated accounts, and with newly created accounts,
tried fresh profiles, it really looks as if there's a bug here in in
accounts requiring auth (not just e-s).
</quote>
2) possible add-on/extension's that are part of the problem (my test
profile has zero add-on's or extensions.
Don't know, but it works for me in the test profile, does not work for
me in the migrated 1.1.18 profile.
Bill, can you please test again with a clean, newly created test profile
w/o any add-ons or extensions?
Bill Davidsen
from 2.0 any time.
I notice that 2.0 unchecks my "ask about more than 500 messages" box, although
it seems to ask. Ideas?
--
Bill Davidsen <davi...@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
Gabriele
> Bill Davidsen wrote:
>> Server: news.eternal-september.org
>> Fails on port NNTP (119) and NNTPS (563 with SSL) with this message:
>> http://www.tmr.com/~davidsen/Private/SS-NoPost-SM2.0.png
>>
>> And my first test post to this server failed silently as well. WTH?
>>
>> NOTE: since tested on another server with auth, fails there as well.
>
> Reported as bug https://bugzilla.mozilla.org/show_bug.cgi?id=525649 if
> anyone else seeing this would please confirm, vote, etc.
Hello,
I have the same problem using my ISP news server!
I don't think it's a matter of authentication or not, cause I've tried all
kind of settings and the error it's the same as yours.
I can post using news.mozilla.org (which apparently works through giganews),
but no way to send using the other news server (which is news.mclink.it
which was working since I upgraded to SM 2.0).
I will try now to delete the news server and retry. Stay tuned!
bye
Gabriele
chicagofan
> On Oct 31, 1:40 pm, chicagofan<m...@privacy.net> wrote:
>> NoOp wrote:
>>>> On 10/30/2009 02:50 PM, Bill Davidsen wrote:
>>>>> Server: news.eternal-september.org Fails on port NNTP (119) and NNTPS
>>>>> (563 with SSL) with this message:
>>>>> http://www.tmr.com/~davidsen/Private/SS-NoPost-SM2.0.png
>>>>>
>>
>>>>> NOTE: since tested on another server with auth, fails there as well.
>>
>>>> news.eternal-september.org works just fine for me. Server settings 563
>>>> SSL/TLS 'Always request authentication when connecting to this server-
>>>> outgoing server is the same as this email account.
>>
>> It's working fine for me too, on Port 119, as news.eternal-september.org,
>> with the "Always request authentication" box checked under the news server
>> settings. Note, my setup isn't using SSL [Port 563] though.
>>
>> Hope something works for you, but I don't think it's a SM 2.0 problem. :)
>
>
> SM 2.0. I had to sign on to my google(tm) account to post here.
> Suggestions?
I think maybe I spoke too soon now, although I have read many users posting
that have nntp access on Linux and Windows with no problems. :\
What messages are you getting? Same as the OP? What news servers aren't
working for you? Do you have any extensions or security programs that might be
interfering? What O/S or platform are you using?
Check to make sure all your news server settings are correctly set, individually
[i.e., I have 2 news server that require no authentication, but one does].
I seem to remember that I had a similar problem with mail connections, after my
*first* update to SM 2.0 beta. Something had changed my outgoing SMTP settings
to require secure settings. I didn't know if my ISP had changed something, but
I had not... and expected my old SM settings to be the same, and work as before.
Anyway [though it is probably TOTALLY unrelated to this problem], I edited the
settings under my Outgoing SMTP server, and unchecked the box ... for name and
password, and that corrected my connection problem.
Note that was 2.0b1, and regarding *mail* problems, but it's worth checking your
SMTP settings, until someone comes along with the right answer about 2.0. :)
Plus, you should add your experience w/ more details to the bug that has been filed
by Bill Davidsen: https://bugzilla.mozilla.org/show_bug.cgi?id=525649
bj
NoOp
> NoOp wrote:
...
>> Not sure what the issue might be Bill. I've migrated 4 machines (linux)
>> from 1.1.18 to 2.0 and _all_ have no issues accessing
>> news.eternal-september.org (port 563/SSL). I've 2 test machines that
>> have yet to be migrated & I'll see if I can get them done this weekend &
>> let you know if they have issues. Have you tried from a different profile?
>>
> Yes. Tried different profile, machine, etc. Works from 1.1.18 every time, not
> from 2.0 any time.
I'll see if I can try a few more test cases (linux) over the next few
days. As you can see from my test posts on news.eternal-september.org
(support and test) the Win2KP test profile had no issues, but the
default/existing profile did - as in your case.
>
> I notice that 2.0 unchecks my "ask about more than 500 messages" box, although
> it seems to ask. Ideas?
Different thread/issue; see: "SM 2.0 RC2: News server setttings don't hold"
https://bugzilla.mozilla.org/show_bug.cgi?id=523958
dupe of:
https://bugzilla.mozilla.org/show_bug.cgi?id=457882
Harmut filed mailto:4A20DE79...@hfigge.myfqdn.de but no clue what
that is as you can't search this group with that info. Harmut, how about
providing a link to the msg?
Hartmut Figge
>Harmut filed mailto:4A20DE79...@hfigge.myfqdn.de but no clue what
>that is as you can't search this group with that info. Harmut, how about
>providing a link to the msg?
'mailto:' isn't correct, should be 'news'. Required by some RFC. But
'news:'' is a dangerous thing for mozilla based NUAs. Very old bug.
Nevertheless, MIDF shows, that this posting was not catched by google.
But it can be found on newsservers or here:
This bug is fixed for my SM 2.1.
Hartmut
Gabriele
[cut]
Hello,
as I posted a few hours ago, I had the same problem with a non-auth news server.
I deleted it, and created a new news account: now it's working, so the
problem is probably related to some bug in the migration step.
bye,
Gabriele
chicagofan
Apparently... let's hope your experience will be helpful to others. :)
bj
NoOp
> NoOp wrote:
...
>> from 1.1.18 to 2.0 and _all_ have no issues accessing
>> news.eternal-september.org (port 563/SSL). I've 2 test machines that
>> have yet to be migrated & I'll see if I can get them done this weekend &
>> let you know if they have issues. Have you tried from a different profile?
>>
> Yes. Tried different profile, machine, etc. Works from 1.1.18 every time, not
> from 2.0 any time.
Bill, getting back to why I think it's a profile issue; just tested SM
2.0 w/new install on a machine that never had SM installed on it
previously - no issues. You'll find my test post (along with the Windows
one) in eternal-september.test - news.eternal-september.org: "Test from
SM 2.0".
Windows:
From: NoOp <gl...@sbcglobal.net.invalid>
Newsgroups: eternal-september.test
Subject: Test from SM 2.0
Date: Sat, 31 Oct 2009 20:26:12 -0800
...
Message-ID: <hcj2l4$mqt$1...@news.eternal-september.org>
...
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.4)
Gecko/20091017 SeaMonkey/2.0
Linux:
From: NoOp <gl...@sbcglobal.net.invalid>
Newsgroups: eternal-september.test
Subject: Re: Test from SM 2.0
Date: Mon, 02 Nov 2009 12:12:42 -0800
...
Message-ID: <hcnefs$rgq$1...@news.eternal-september.org>
References: <hcj2l4$mqt$1...@news.eternal-september.org>
...
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.4)
Gecko/20091017 SeaMonkey/2.0
So not sure what the issue could be on your system. However, for the
sake of keeping this thread to a minimum, I'll be happy to test other
scenarios if you'll contact me directly (just drop the .invalid from the
email address & keep the same subject so that I don't automatically drop
the msg in the spam filters). I can test on linux (ubuntu 9.04 & 9.10 -
gnome only, I'm alergic to kde), WinXPPro & Win2KPro (both fully updated).
Gary
LR
> lr...@superlink.net wrote:
> > On Oct 31, 1:40 pm, chicagofan<m...@privacy.net> wrote:
> >> NoOp wrote:
> >>>> On 10/30/2009 02:50 PM, Bill Davidsen wrote:
> >>>>> Server: news.eternal-september.org Fails on port NNTP (119) and NNTPS
> >>>>> (563 with SSL) with this message:
> >>>>>http://www.tmr.com/~davidsen/Private/SS-NoPost-SM2.0.png
>
> >>>>> And my first test post to this server failed silently as well. WTH?
>
> >>>>> NOTE: since tested on another server with auth, fails there as well.
>
> >>>> news.eternal-september.org works just fine for me. Server settings 563
> >>>> SSL/TLS 'Always request authentication when connecting to this server-
> >>>> outgoing server is the same as this email account.
>
> >> It's working fine for me too, on Port 119, as news.eternal-september.org,
> >> with the "Always request authentication" box checked under the news server
> >> settings. Note, my setup isn't using SSL [Port 563] though.
>
> >> Hope something works for you, but I don't think it's a SM 2.0 problem. :)
>
> > I have a problem that has the same symptoms that started after I installed
> > SM 2.0. I had to sign on to my google(tm) account to post here.
> > Suggestions?
>
> I think maybe I spoke too soon now, although I have read many users posting
> that have nntp access on Linux and Windows with no problems. :\
>
> What messages are you getting? Same as the OP?
Yes. It seems like I have the same behavior.
> What news servers aren't working for you?
I'm trying to post using newsread.uslec.net
> Do you have any extensions or security programs that might be
> interfering?
I have Zone Alarm running. Seemed ok with the previous version I had
installed which was, I think, 1.1.18.
What O/S or platform are you using?
Win XP.
>
> Check to make sure all your news server settings are correctly set, individually
> [i.e., I have 2 news server that require no authentication, but one does].
I've tried both ways. BTW, when I first installed 2.0 I had to fiddle
with the settings for email, unclicking the user name and password
setting for the outgoing SMTP server.
>
> I seem to remember that I had a similar problem with mail connections, after my
> *first* update to SM 2.0 beta. Something had changed my outgoing SMTP settings
> to require secure settings.
I think what I just described above.
> Plus, you should add your experience w/ more details to the bug that has been filed
> by Bill Davidsen: https://bugzilla.mozilla.org/show_bug.cgi?id=525649
Ok, I did that too.
LR
Bill Davidsen
Fedora in a fresh virtual machine. All behave the same. No clue... :-(
Sledge Hammer
problem...
Hammer
NoOp
> NoOp wrote:
...
>> sake of keeping this thread to a minimum, I'll be happy to test other
>> scenarios if you'll contact me directly (just drop the .invalid from the
>> email address & keep the same subject so that I don't automatically drop
>> the msg in the spam filters). I can test on linux (ubuntu 9.04 & 9.10 -
>> gnome only, I'm alergic to kde), WinXPPro & Win2KPro (both fully updated).
>>
> I noted the test I made, new profile, new install with no migration, even new
> Fedora in a fresh virtual machine. All behave the same. No clue... :-(
>
Could it be that the VM is the issue? Do you experience the same on a
non VM?
Bill Davidsen
look for them:
http://www.tmr.com/~davidsen/Private/E-S_post_bug_SM2/
I've tried on multiple machines, real and virtual, new SM installs (no migrate),
and new profiles. Something unique about servers which allow limited access
without authentication, I see it on another private server as well.
Bill Davidsen
Yes, I even tried creating a whole new user on a machine I just built, installed
SM2.0 (not one of the snapshots), no add-on or themes, and it still happens.