Jens Hatlak wrote:
Bill Davidsen wrote:
Jens Hatlak wrote:
OTOH the average user won't have to care about the two prefs that
caused the problem here once the bug fix is available as part of the
next release.
Do you have any idea how elitist that sounds?
Maybe you just got me wrong, please r
Bill Davidsen wrote:
> Jens Hatlak wrote:
>> OTOH the average user won't have to care about the two prefs that
>> caused the problem here once the bug fix is available as part of the
>> next release.
>>
> Do you have any idea how elitist that sounds?
Maybe you just got me wrong, please read on.
>
NoOp wrote:
On 11/24/2009 10:20 AM, Bill Davidsen wrote:
Jens Hatlak wrote:
Bill Davidsen wrote:
It seems that a fix is available for this problem, assuming you are
willing to build your own SeaMonkey from source. Bug #484656 seems to
change the "You have your config wrong" to "we were parsing
Jens Hatlak wrote:
Bill Davidsen wrote:
Is there any doc on all those config fields, particularly those
which only appear when you know they exist?
No.
Would make submitting a useful bug report easier, and source is not
really a great resource, even if you know how to read it, it takes
time.
On 11/24/2009 10:20 AM, Bill Davidsen wrote:
> Jens Hatlak wrote:
>> Bill Davidsen wrote:
>>> It seems that a fix is available for this problem, assuming you are
>>> willing to build your own SeaMonkey from source. Bug #484656 seems to
>>> change the "You have your config wrong" to "we were parsing
Bill Davidsen wrote:
Is there any doc on all those config fields, particularly those
which only appear when you know they exist?
No.
Would make submitting a useful bug report easier, and source is not
really a great resource, even if you know how to read it, it takes
time.
Prefs that do not
Jens Hatlak wrote:
Bill Davidsen wrote:
Thanks for the info, now the next question is why it works for anyone
with the official 2.0 release.
Bug 484656 comment 18 suggests that only people with a
mail.server.serverX.realhostname pref are affected. I for one have no
account with such a pref a
Bill Davidsen wrote:
Thanks for the info, now the next question is why it works for anyone
with the official 2.0 release.
Bug 484656 comment 18 suggests that only people with a
mail.server.serverX.realhostname pref are affected. I for one have no
account with such a pref and I don't know whic
Jens Hatlak wrote:
Bill Davidsen wrote:
It seems that a fix is available for this problem, assuming you are
willing to build your own SeaMonkey from source. Bug #484656 seems to
change the "You have your config wrong" to "we were parsing your config
wrong." In any case the problem is identified,
Bill Davidsen wrote:
It seems that a fix is available for this problem, assuming you are
willing to build your own SeaMonkey from source. Bug #484656 seems to
change the "You have your config wrong" to "we were parsing your config
wrong." In any case the problem is identified, and *maybe* this wi
Bill Davidsen wrote:
I have put my full config up as screen shots:
http://www.tmr.com/~davidsen/Private/E-S_post_bug_SM2/
Note that SeaMonkey sends *no packets* to the NNTP host, other than
"always offer auth" my working server definitions, those without auth
needed, are identical.
I have
11 matches
Mail list logo
