VERY SERIOUS BUG IN TB! - Mozilla

This is a discussion on VERY SERIOUS BUG IN TB! - Mozilla ; Hello. The subject is in handling the recipient address, I think. When I try to send a mail to ka$a@tvk6.ru (in address present dollar sign, this is quite valid) I have a sending error like this: > Your message > ...

+ Reply to Thread
Results 1 to 15 of 15

Thread: VERY SERIOUS BUG IN TB!

  1. VERY SERIOUS BUG IN TB!

    Hello.

    The subject is in handling the recipient address, I think.
    When I try to send a mail to ka$a@tvk6.ru (in address present dollar
    sign, this is quite valid) I have a sending error like this:

    > Your message
    >
    > To: Serge Kandakov
    > Subject: sdsdsd
    > Sent: Fri, 2 Jun 2006 15:23:16 +0800
    >
    > did not reach the following recipient(s):
    >
    > Serge Kandakov on Fri, 2 Jun 2006 15:23:19 +0800
    > The recipient name is not recognized
    > The MTS-ID of the original message is: c=RU;a= ;p=TVK6;l=LEGACY0606020723KMBKNJ6P
    > MSEXCH:IMS:TVK6:TVK:LEGACY 0 (000C05A6) Unknown Recipient
    >
    >
    >
    >
    > Subject:
    > sdsdsd
    > From:
    > Serge Kandakov
    > Date:
    > Fri, 2 Jun 2006 15:23:16 +0800
    > To:
    > Serge Kandakov <"ka$a"@tvk6.ru> <---- Here is the trouble!
    >
    > sdsdsd



    TB tries to enclose the first part of the address in quotation marks.
    But, for what?!?
    Please, correct it as soon as possible. My work is stopped now


    Best regards, Serge

  2. Re: VERY SERIOUS BUG IN TB!

    On 02-06-2006 09:42 CET, Serge Kandakov composed this enchanting statement:
    > Hello.
    >
    > The subject is in handling the recipient address, I think.

    Sort of, the mail server involved can't find that user name/identifier (
    see below).
    > When I try to send a mail to ka$a@tvk6.ru (in address present dollar
    > sign, this is quite valid) I have a sending error like this:
    >> Your message
    >>
    >> To: Serge Kandakov
    >> Subject: sdsdsd
    >> Sent: Fri, 2 Jun 2006 15:23:16 +0800
    >>
    >> did not reach the following recipient(s):
    >>
    >> Serge Kandakov on Fri, 2 Jun 2006 15:23:19 +0800
    >> *The recipient name is not recognized*
    >> The MTS-ID of the original message is: c=RU;a=
    >> ;p=TVK6;l=LEGACY0606020723KMBKNJ6P
    >> MSEXCH:IMS:TVK6:TVK:LEGACY 0 (000C05A6) *Unknown Recipient*

    It is a user error, most likely: the mail server cannot find the
    recipient user name in its records.
    >
    > TB tries to enclose the first part of the address in quotation marks.
    > But, for what?!?
    > Please, correct it as soon as possible. My work is stopped now

    The first part, really?

    --
    Kind regards,

    Melchert

    MacOS 10.3.9/Firefox 1.5/Thunderbird 1.5

  3. Re: VERY SERIOUS BUG IN TB!

    Melchert Fruitema said the following On 02.06.2006 17:34:
    > On 02-06-2006 09:42 CET, Serge Kandakov composed this enchanting statement:
    >> Hello.
    >>
    >> The subject is in handling the recipient address, I think.

    > Sort of, the mail server involved can't find that user name/identifier (
    > see below).
    >> When I try to send a mail to ka$a@tvk6.ru (in address present dollar
    >> sign, this is quite valid) I have a sending error like this:
    >>> Your message
    >>>
    >>> To: Serge Kandakov
    >>> Subject: sdsdsd
    >>> Sent: Fri, 2 Jun 2006 15:23:16 +0800
    >>>
    >>> did not reach the following recipient(s):
    >>>
    >>> Serge Kandakov on Fri, 2 Jun 2006 15:23:19 +0800
    >>> *The recipient name is not recognized*
    >>> The MTS-ID of the original message is: c=RU;a=
    >>> ;p=TVK6;l=LEGACY0606020723KMBKNJ6P
    >>> MSEXCH:IMS:TVK6:TVK:LEGACY 0 (000C05A6) *Unknown Recipient*

    > It is a user error, most likely: the mail server cannot find the
    > recipient user name in its records.
    >>

    No. The user name is [ka$a] but TB encloses it and send to the server
    enclosed name like ["ka$a"]. Of course, the server can not find that name.

    >> TB tries to enclose the first part of the address in quotation marks.
    >> But, for what?!?
    >> Please, correct it as soon as possible. My work is stopped now

    > The first part, really?

    yes

  4. Re: VERY SERIOUS BUG IN TB!

    Serge Kandakov wrote:
    > Hello.
    >
    > The subject is in handling the recipient address, I think.
    > When I try to send a mail to ka$a@tvk6.ru (in address present dollar
    > sign, this is quite valid) I have a sending error like this:
    >
    >> Your message
    >>
    >> To: Serge Kandakov
    >> Subject: sdsdsd
    >> Sent: Fri, 2 Jun 2006 15:23:16 +0800
    >>
    >> did not reach the following recipient(s):
    >>
    >> Serge Kandakov on Fri, 2 Jun 2006 15:23:19 +0800
    >> The recipient name is not recognized
    >> The MTS-ID of the original message is: c=RU;a=
    >> ;p=TVK6;l=LEGACY0606020723KMBKNJ6P
    >> MSEXCH:IMS:TVK6:TVK:LEGACY 0 (000C05A6) Unknown Recipient
    >>
    >>
    >>
    >>
    >> Subject:
    >> sdsdsd
    >> From:
    >> Serge Kandakov
    >> Date:
    >> Fri, 2 Jun 2006 15:23:16 +0800
    >> To:
    >> Serge Kandakov <"ka$a"@tvk6.ru> <---- Here is the trouble!
    >>
    >> sdsdsd

    >
    >
    > TB tries to enclose the first part of the address in quotation marks.
    > But, for what?!?
    > Please, correct it as soon as possible. My work is stopped now
    >


    Well, I can confirm what you're seeing. I just tried to send a message
    to that address, and though TB thinks it was sent successfully, it
    wasn't. Checking the "Sent" item in TB, the address it was sent to is
    "ka$a"@tvk6.ru

    I did a quick Google search, and in a nutshell, the info I found said
    "don't use the $ in an e-mail address". Though it may be valid, some
    software doesn't handle it properly - specifically, it's the mail server
    software that may not know what to do with an address such as
    "ka$a"@tvk6.ru and therefore the advice is not to use it.


    See:
    http://www.remote.org/jochen/mail/info/chars.html
    http://www.quirksmode.org/js/mailcheck.html

  5. Re: VERY SERIOUS BUG IN TB!

    Ken Wagner wrote:

    > Serge Kandakov wrote:
    >
    >>Hello.
    >>
    >>The subject is in handling the recipient address, I think.
    >>When I try to send a mail to ka$a@tvk6.ru (in address present dollar
    >>sign, this is quite valid) I have a sending error like this:
    >>
    >>
    >>>Your message
    >>>
    >>> To: Serge Kandakov
    >>> Subject: sdsdsd
    >>> Sent: Fri, 2 Jun 2006 15:23:16 +0800
    >>>
    >>>did not reach the following recipient(s):
    >>>
    >>>Serge Kandakov on Fri, 2 Jun 2006 15:23:19 +0800
    >>> The recipient name is not recognized
    >>> The MTS-ID of the original message is: c=RU;a=
    >>>;p=TVK6;l=LEGACY0606020723KMBKNJ6P
    >>> MSEXCH:IMS:TVK6:TVK:LEGACY 0 (000C05A6) Unknown Recipient
    >>>
    >>>
    >>>
    >>>
    >>>Subject:
    >>>sdsdsd
    >>>From:
    >>>Serge Kandakov
    >>>Date:
    >>>Fri, 2 Jun 2006 15:23:16 +0800
    >>>To:
    >>>Serge Kandakov <"ka$a"@tvk6.ru> <---- Here is the trouble!
    >>>
    >>>sdsdsd

    >>
    >>
    >>TB tries to enclose the first part of the address in quotation marks.
    >>But, for what?!?
    >>Please, correct it as soon as possible. My work is stopped now
    >>

    >
    >
    > Well, I can confirm what you're seeing. I just tried to send a message
    > to that address, and though TB thinks it was sent successfully, it
    > wasn't. Checking the "Sent" item in TB, the address it was sent to is
    > "ka$a"@tvk6.ru
    >
    > I did a quick Google search, and in a nutshell, the info I found said
    > "don't use the $ in an e-mail address". Though it may be valid, some
    > software doesn't handle it properly - specifically, it's the mail server
    > software that may not know what to do with an address such as
    > "ka$a"@tvk6.ru and therefore the advice is not to use it.
    >
    >
    > See:
    > http://www.remote.org/jochen/mail/info/chars.html
    > http://www.quirksmode.org/js/mailcheck.html

    based on what you said then this is the clue: some software doesn't
    handle it properly - *specifically*, it's the mail server software

    Therefore, its NOT a TB problem. It's the mail server problem.

    --
    Interesting Modern Philosophies: The colder the X-ray table, the more
    of your body is required on it.

  6. Re: VERY SERIOUS BUG IN TB!

    On 6/2/2006 3:49 PM gwtc spake these words of knowledge:

    > Ken Wagner wrote:
    >
    >> Serge Kandakov wrote:
    >>
    >>>Hello.
    >>>
    >>>The subject is in handling the recipient address, I think.
    >>>When I try to send a mail to ka$a@tvk6.ru (in address present dollar
    >>>sign, this is quite valid) I have a sending error like this:
    >>>
    >>>
    >>>>Your message
    >>>>
    >>>> To: Serge Kandakov
    >>>> Subject: sdsdsd
    >>>> Sent: Fri, 2 Jun 2006 15:23:16 +0800
    >>>>
    >>>>did not reach the following recipient(s):
    >>>>
    >>>>Serge Kandakov on Fri, 2 Jun 2006 15:23:19 +0800
    >>>> The recipient name is not recognized
    >>>> The MTS-ID of the original message is: c=RU;a=
    >>>>;p=TVK6;l=LEGACY0606020723KMBKNJ6P
    >>>> MSEXCH:IMS:TVK6:TVK:LEGACY 0 (000C05A6) Unknown Recipient
    >>>>
    >>>>
    >>>>
    >>>>
    >>>>Subject:
    >>>>sdsdsd
    >>>>From:
    >>>>Serge Kandakov
    >>>>Date:
    >>>>Fri, 2 Jun 2006 15:23:16 +0800
    >>>>To:
    >>>>Serge Kandakov <"ka$a"@tvk6.ru> <---- Here is the trouble!
    >>>>
    >>>>sdsdsd
    >>>
    >>>
    >>>TB tries to enclose the first part of the address in quotation marks.
    >>>But, for what?!?
    >>>Please, correct it as soon as possible. My work is stopped now
    >>>

    >>
    >>
    >> Well, I can confirm what you're seeing. I just tried to send a message
    >> to that address, and though TB thinks it was sent successfully, it
    >> wasn't. Checking the "Sent" item in TB, the address it was sent to is
    >> "ka$a"@tvk6.ru
    >>
    >> I did a quick Google search, and in a nutshell, the info I found said
    >> "don't use the $ in an e-mail address". Though it may be valid, some
    >> software doesn't handle it properly - specifically, it's the mail server
    >> software that may not know what to do with an address such as
    >> "ka$a"@tvk6.ru and therefore the advice is not to use it.
    >>
    >>
    >> See:
    >> http://www.remote.org/jochen/mail/info/chars.html
    >> http://www.quirksmode.org/js/mailcheck.html

    > based on what you said then this is the clue: some software doesn't
    > handle it properly - *specifically*, it's the mail server software
    >
    > Therefore, its NOT a TB problem. It's the mail server problem.
    >


    What some software doesn't handle correctly, apparently, is an address
    with quotes. That's a problem, but it's secondary. It isn't the mail
    server that's changing the email address, it's Thunderbird. That's a
    problem, and the problem is in Thunderbird.

    The solution "don't use '$' in an email address" will certainly work,
    but the root of the problem is in Thunderbird, according to what Ken
    said above.

    RFT!!!
    Dave Kelsen
    --
    I just got slapped with my seventh sexual harassment suit this year.
    Man, I tell ya, the broads in my office -- great racks, no sense of humor.

  7. Re: VERY SERIOUS BUG IN TB!

    In article ,
    gwtc wrote:
    >Ken Wagner wrote:
    >
    >> Serge Kandakov wrote:
    >>
    >>>Hello.
    >>>
    >>>The subject is in handling the recipient address, I think.
    >>>When I try to send a mail to ka$a@tvk6.ru (in address present dollar
    >>>sign, this is quite valid) I have a sending error like this:
    >>>
    >>>
    >>>>Your message
    >>>>
    >>>> To: Serge Kandakov
    >>>> Subject: sdsdsd
    >>>> Sent: Fri, 2 Jun 2006 15:23:16 +0800
    >>>>
    >>>>did not reach the following recipient(s):
    >>>>
    >>>>Serge Kandakov on Fri, 2 Jun 2006 15:23:19 +0800
    >>>> The recipient name is not recognized
    >>>> The MTS-ID of the original message is: c=RU;a=
    >>>>;p=TVK6;l=LEGACY0606020723KMBKNJ6P
    >>>> MSEXCH:IMS:TVK6:TVK:LEGACY 0 (000C05A6) Unknown Recipient
    >>>>
    >>>>
    >>>>
    >>>>
    >>>>Subject:
    >>>>sdsdsd
    >>>>From:
    >>>>Serge Kandakov
    >>>>Date:
    >>>>Fri, 2 Jun 2006 15:23:16 +0800
    >>>>To:
    >>>>Serge Kandakov <"ka$a"@tvk6.ru> <---- Here is the trouble!
    >>>>
    >>>>sdsdsd
    >>>
    >>>
    >>>TB tries to enclose the first part of the address in quotation marks.
    >>>But, for what?!?
    >>>Please, correct it as soon as possible. My work is stopped now
    >>>

    >>
    >>
    >> Well, I can confirm what you're seeing. I just tried to send a message
    >> to that address, and though TB thinks it was sent successfully, it
    >> wasn't. Checking the "Sent" item in TB, the address it was sent to is
    >> "ka$a"@tvk6.ru
    >>
    >> I did a quick Google search, and in a nutshell, the info I found said
    >> "don't use the $ in an e-mail address". Though it may be valid, some
    >> software doesn't handle it properly - specifically, it's the mail server
    >> software that may not know what to do with an address such as
    >> "ka$a"@tvk6.ru and therefore the advice is not to use it.


    >based on what you said then this is the clue: some software doesn't
    >handle it properly - *specifically*, it's the mail server software
    >
    >Therefore, its NOT a TB problem. It's the mail server problem.


    Well, rfc 2822 section 3.4.1 (Addr-spec specification) says:

    If the string can be represented as a dot-atom (that is,
    it contains no characters other than atext characters or
    "." surrounded by atext characters), then the dot-atom
    form SHOULD be used and the quoted-string form SHOULD NOT
    be used.

    where atext as defined in 3.2.4 includes "$". I interpret
    this to mean TB should not double quote ka$a .

    --
    WL
    real mail: wliao at sdf loSnPesAtarM org
    (remove the uppercase letters...)

  8. Re: VERY SERIOUS BUG IN TB!

    Dave Kelsen wrote:
    > On 6/2/2006 3:49 PM gwtc spake these words of knowledge:
    >
    >> Ken Wagner wrote:
    >>
    >>> Serge Kandakov wrote:
    >>>
    >>>> Hello.
    >>>>
    >>>> The subject is in handling the recipient address, I think.
    >>>> When I try to send a mail to ka$a@tvk6.ru (in address present dollar
    >>>> sign, this is quite valid) I have a sending error like this:
    >>>>
    >>>>
    >>>>> Your message
    >>>>>
    >>>>> To: Serge Kandakov
    >>>>> Subject: sdsdsd
    >>>>> Sent: Fri, 2 Jun 2006 15:23:16 +0800
    >>>>>
    >>>>> did not reach the following recipient(s):
    >>>>>
    >>>>> Serge Kandakov on Fri, 2 Jun 2006 15:23:19 +0800
    >>>>> The recipient name is not recognized
    >>>>> The MTS-ID of the original message is: c=RU;a=
    >>>>> ;p=TVK6;l=LEGACY0606020723KMBKNJ6P
    >>>>> MSEXCH:IMS:TVK6:TVK:LEGACY 0 (000C05A6) Unknown Recipient
    >>>>>
    >>>>>
    >>>>>
    >>>>>
    >>>>> Subject:
    >>>>> sdsdsd
    >>>>> From:
    >>>>> Serge Kandakov
    >>>>> Date:
    >>>>> Fri, 2 Jun 2006 15:23:16 +0800
    >>>>> To:
    >>>>> Serge Kandakov <"ka$a"@tvk6.ru> <---- Here is the trouble!
    >>>>>
    >>>>> sdsdsd
    >>>>
    >>>>
    >>>> TB tries to enclose the first part of the address in quotation
    >>>> marks. But, for what?!?
    >>>> Please, correct it as soon as possible. My work is stopped now
    >>>>
    >>>
    >>>
    >>> Well, I can confirm what you're seeing. I just tried to send a
    >>> message to that address, and though TB thinks it was sent
    >>> successfully, it wasn't. Checking the "Sent" item in TB, the address
    >>> it was sent to is "ka$a"@tvk6.ru
    >>>
    >>> I did a quick Google search, and in a nutshell, the info I found said
    >>> "don't use the $ in an e-mail address". Though it may be valid, some
    >>> software doesn't handle it properly - specifically, it's the mail
    >>> server software that may not know what to do with an address such as
    >>> "ka$a"@tvk6.ru and therefore the advice is not to use it.
    >>>
    >>>
    >>> See:
    >>> http://www.remote.org/jochen/mail/info/chars.html
    >>> http://www.quirksmode.org/js/mailcheck.html

    >> based on what you said then this is the clue: some software doesn't
    >> handle it properly - *specifically*, it's the mail server software
    >>
    >> Therefore, its NOT a TB problem. It's the mail server problem.
    >>

    >
    > What some software doesn't handle correctly, apparently, is an address
    > with quotes. That's a problem, but it's secondary. It isn't the mail
    > server that's changing the email address, it's Thunderbird. That's a
    > problem, and the problem is in Thunderbird.


    Well, I'm not about to pretend to understand it all, that's for sure...

    However, here's some info that brought me to my conclusion:

    The following is from the link at
    http://www.quirksmode.org/js/mailcheck.html in my original reply:
    > First of all, if the user name (left of the @) is between quotes "", a lot more is allowed. As far as I've understood this
    >
    > "J. P. 's-Gravezande, a.k.a. The Hacker!"@server.com
    >
    > is a valid email address, since all strange characters are between quotes. However, this syntax is rarely used. I didn't know it was allowed until my friend told me, and I guess most people don't know about it.
    >
    > Also, the strict syntax for addresses with IP numbers in them is
    >
    > me@[187.223.45.119]
    >
    > However, it seems that even some mail servers don't know about this syntax and don't correctly deliver mails sent to such addresses. It is rarely used.


    Then there's
    http://www.breakingpar.com/bkp/home....256C40004CC8C6

    > (\".+\")
    > This grouping is a bit easier to understand. A literal quote character can appear, followed by one or more characters (here, the period indicates any single character) followed by another qoute. So, "johndoe"@ is a valid starting part of the email address. And if there truly was a case where consecutive periods were in the part before the @ sign, the whole thing could be enclosed in quotes to make it valid ("john..doe"@ would be a valid first part, but john..doe@ would not be valid).


    From http://www.landfield.com/usefor/2000/Apr/0005.html
    > Basically, most the standards define a few special characters which
    > can only be used in the ID if they are quoted. [ ] are characters that
    > must be quoted in all the standards.
    >
    > 822 says that atoms must be quoted. So for example, you could do this:
    >
    > <"[special_stuff]".a.b@domain>
    >
    > that is, you don't have to quote the entire local part, but you can


    The above 3 quotes make me think that it's the mail server and not TB
    that is at fault. If "ka$a"@tvk6.ru is a valid address (as each of them
    say that it is), then it's the mail server that isn't handling it properly.

    I also found this in section 3.2.5 of RFC 2822 at
    http://www.ietf.org/rfc/rfc2822.txt
    > Strings of characters that include characters other than those
    > allowed in atoms may be represented in a quoted string format, where
    > the characters are surrounded by quote (DQUOTE, ASCII value 34)
    > characters.

    and
    > A quoted-string is treated as a unit. That is, quoted-string is
    > identical to atom, semantically.



    Then there's this from http://en.wikipedia.org/wiki/Email_address :
    > According to RFC 2822, the local-part of the e-mail may use any of these ASCII characters:
    >
    > * Uppercase and lowercase letters
    > * The digits 0 through 9
    > * The characters, ! # $ % & ' * + - / = ? ^ _ ` { | } ~
    > * The character "." provided that it is not the first or last character in the local-part.
    >
    > Additionally, RFC 2821 and RFC 2822 allow the local-part to be a quoted-string, as in "John Doe"@example.com, thus allowing characters in the local-part that would otherwise be prohibited. However, RFC 2821 warns: "a host that expects to receive mail SHOULD avoid defining mailboxes where the Local-part requires (or uses) the Quoted-string form".



    All that was simply to say that IMHO, *I* think TB is handling it properly.

  9. Re: VERY SERIOUS BUG IN TB!

    me@privacy.net (WL) wrote in 6dnWiKBqyIVR3ZnZ2dnUVZ_sednZ2d@mozilla.org>:

    > Well, rfc 2822 section 3.4.1 (Addr-spec specification) says:
    >
    > If the string can be represented as a dot-atom (that is,
    > it contains no characters other than atext characters or
    > "." surrounded by atext characters), then the dot-atom
    > form SHOULD be used and the quoted-string form SHOULD NOT
    > be used.
    >
    > where atext as defined in 3.2.4 includes "$". I interpret
    > this to mean TB should not double quote ka$a .


    I agree with you. At the least, Thunderbird should provide a way to
    override turning the atom into a quoted string.

    --
    »Q«

  10. Re: VERY SERIOUS BUG IN TB!

    On 02.06.2006 21:23, »Q« wrote:

    --- Original Message ---

    > me@privacy.net (WL) wrote in > 6dnWiKBqyIVR3ZnZ2dnUVZ_sednZ2d@mozilla.org>:
    >
    >> Well, rfc 2822 section 3.4.1 (Addr-spec specification) says:
    >>
    >> If the string can be represented as a dot-atom (that is,
    >> it contains no characters other than atext characters or
    >> "." surrounded by atext characters), then the dot-atom
    >> form SHOULD be used and the quoted-string form SHOULD NOT
    >> be used.
    >>
    >> where atext as defined in 3.2.4 includes "$". I interpret
    >> this to mean TB should not double quote ka$a .

    >
    > I agree with you. At the least, Thunderbird should provide a way to
    > override turning the atom into a quoted string.
    >


    Yes, it IS Thunderbird. I sent out a mail directly from sendmail on my
    server and it went through just fine, no return.

    --
    Jay Garcia Netscape/Mozilla Champion
    UFAQ - http://www.UFAQ.org

  11. Re: VERY SERIOUS BUG IN TB!

    Jay Garcia wrote:
    > On 02.06.2006 21:23, »Q« wrote:
    >
    > --- Original Message ---
    >
    >> me@privacy.net (WL) wrote in >> 6dnWiKBqyIVR3ZnZ2dnUVZ_sednZ2d@mozilla.org>:
    >>
    >>> Well, rfc 2822 section 3.4.1 (Addr-spec specification) says:
    >>>
    >>> If the string can be represented as a dot-atom (that is,
    >>> it contains no characters other than atext characters or
    >>> "." surrounded by atext characters), then the dot-atom
    >>> form SHOULD be used and the quoted-string form SHOULD NOT
    >>> be used.
    >>>
    >>> where atext as defined in 3.2.4 includes "$". I interpret
    >>> this to mean TB should not double quote ka$a .

    >> I agree with you. At the least, Thunderbird should provide a way to
    >> override turning the atom into a quoted string.
    >>

    >
    > Yes, it IS Thunderbird. I sent out a mail directly from sendmail on my
    > server and it went through just fine, no return.
    >

    I don't think it is TB. I sent a mail dirctly to Serge, using TB, and
    recieved a response back from him with the email "ka$a"@tvk6.ru My TB
    worked fine. It is something else, the firewall, a virus filter, or
    possibly an email filter that is not letting the changed address come
    through. In my email filter, that is TB email filter, the address was
    changed from ka$a... to "ka$a".... That could be a problem for some
    address filters, but I think TB sending and recieving is working fine.
    Yours,
    Peter
    BTW, Jay I read your exchange with the Britannica Encyclopedia about IE
    vs Netscape. Bully for you!!! Standing against the mighty storm! :0


    --
    Yours,
    PeterInMinnesotaaaah!
    "In Him we live and move and have or being"--Some Geek poet!

  12. Re: VERY SERIOUS BUG IN TB!

    PeterInMn wrote:

    > BTW, Jay I read your exchange with the Britannica Encyclopedia about IE
    > vs Netscape. Bully for you!!! Standing against the mighty storm! :0


    Where? I too was disgusted to see the Britannica become a windows-only
    creature. Had it been OS-independent I would have been happy to buy
    newer versions.

    --
    Cheers, Bev (Happy Linux User #85683, Slackware 10.2)
    <<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>
    Please hassle me, I thrive on stress.

  13. Re: VERY SERIOUS BUG IN TB!

    The Real Bev wrote:
    > PeterInMn wrote:
    >
    >> BTW, Jay I read your exchange with the Britannica Encyclopedia about
    >> IE vs Netscape. Bully for you!!! Standing against the mighty storm! :0

    >
    > Where? I too was disgusted to see the Britannica become a windows-only
    > creature. Had it been OS-independent I would have been happy to buy
    > newer versions.
    >

    Bev
    it was from Mozilla.Support.Firefox NG. Here is the post:
    On 29.04.2006 19:29, Ron Hunter wrote:

    --- Original Message ---

    > > However, you are well within your rights to complain, and to refrain
    > > from buying any further products from them...


    I won a bid several years ago to supply 375 copies of Brittanica CD, I
    forget which version, to the local school system. Came to find out that
    this particular version was IE compatible ONLY and did not work with the
    many thousands of installed issues of "Netscape" Communicator throughout
    the system. I contacted Brittanica and their response was basically,
    "too bad, install IE". I returned ALL 375 copies and got a refund. I
    subsequently put out a memo to every school system nationwide that was
    on our info-network. Funny, the next version of Brittanica was
    "all-browser" compatible and has been ever since .. fancy that!! :-)


    -- Jay Garcia Netscape/Mozilla Champion UFAQ - http://www.UFAQ.org


    --
    Yours,
    PeterInMinnesotaaaah!
    "In Him we live and move and have or being"--Some Geek poet!

  14. Re: VERY SERIOUS BUG IN TB!

    »Q« wrote:
    > me@privacy.net (WL) wrote in > 6dnWiKBqyIVR3ZnZ2dnUVZ_sednZ2d@mozilla.org>:
    >
    >> Well, rfc 2822 section 3.4.1 (Addr-spec specification) says:
    >>
    >> If the string can be represented as a dot-atom (that is,
    >> it contains no characters other than atext characters or
    >> "." surrounded by atext characters), then the dot-atom
    >> form SHOULD be used and the quoted-string form SHOULD NOT
    >> be used.
    >>
    >> where atext as defined in 3.2.4 includes "$". I interpret
    >> this to mean TB should not double quote ka$a .

    >
    > I agree with you. At the least, Thunderbird should provide a way to
    > override turning the atom into a quoted string.
    >

    Why the heck does TB do that anyway? OE does not do it!

    --
    Yours,
    PeterInMinnesotaaaah!
    "In Him we live and move and have or being"--Some Geek poet!

  15. Re: VERY SERIOUS BUG IN TB!

    PeterInMn wrote:

    > The Real Bev wrote:
    >> PeterInMn wrote:
    >>
    >>> BTW, Jay I read your exchange with the Britannica Encyclopedia about
    >>> IE vs Netscape. Bully for you!!! Standing against the mighty storm! :0

    >>
    >> Where? I too was disgusted to see the Britannica become a windows-only
    >> creature. Had it been OS-independent I would have been happy to buy
    >> newer versions.
    >>

    > Bev
    > it was from Mozilla.Support.Firefox NG. Here is the post:
    > On 29.04.2006 19:29, Ron Hunter wrote:
    >
    > --- Original Message ---
    >
    > > > However, you are well within your rights to complain, and to refrain
    > > > from buying any further products from them...

    >
    > I won a bid several years ago to supply 375 copies of Brittanica CD, I
    > forget which version, to the local school system. Came to find out that
    > this particular version was IE compatible ONLY and did not work with the
    > many thousands of installed issues of "Netscape" Communicator throughout
    > the system. I contacted Brittanica and their response was basically,
    > "too bad, install IE". I returned ALL 375 copies and got a refund. I
    > subsequently put out a memo to every school system nationwide that was
    > on our info-network. Funny, the next version of Brittanica was
    > "all-browser" compatible and has been ever since .. fancy that!! :-)


    Windows/Mac only. No linux. No dice.

    "Redesigned Interface - The Ultimate Reference Suite is easier to use
    than ever! Articles are easier to find and read; the Ultimate Reference
    Suite integrates perfectly with your Operating System, whether it be Mac
    or Windows!"

    And further on in "Requirements":

    Windows

    * Windows® 98 SE, 2000, Me, XP
    * Pentium® 350MHz or faster processor... and

    Macintosh

    * Mac® OS 10.3
    * iMac or G3 350 MHz or faster processor

    Nope, my buck stays in my pocket.

    --
    Cheers, Bev (Happy Linux User #85683, Slackware 10.2)
    ================================================== ===================
    Some people have told me they don't think a fat penguin really
    embodies the grace of Linux, which just tells me they have never seen
    an angry penguin charging at them in excess of 100mph. They'd be a
    lot more careful about what they say if they had. -- Linus Torvalds

+ Reply to Thread