Can't send a mail with a JA mail list Platform: Mac OSX Steps: 1. In your Address Book, create a mail list and give it a JA name 2. Include a card in that mail list 3. Put the JA list name in the recipient field of compose window and make sure it's auto-completed and recognized as a list 4. Send your mail. (I used IMAP account) 5. You'll see an error: An error occurred while sending mail. The mail server responded: Invalid address syntax. Please check the message recipients and try again. Note: On windows, sending from the same IMAP server with the same list name (and everything) is working fine. I only see this on Mac platform
Jeesun, i tried your steps but the mail was sent without an error. I tried POP, IMAP with various combinations: higlighting the list, opening a new composition and typing the list name and in both cases i didn't get any error
I'll try this again. It was always reproducible for me on the Mac only.
Marina, Could you try this again? I still see this on 0822 branch build. I used mac osx and used さんぽ (sanpo-see this in shift_jis) for the name of mail list. I included two cards which have also JA names.
Jeesun, i just tried it again and it still works for me, i'll attach the screen shot where you'll see the japanese list name (using iso-2022 and shift-jis) that i used for testing
Hmmmm.... it's weird. It's not working for me. Well... I'll pass this for now and look into it later
I have a similar problem using Chinese with Mozilla 1.2B on Linux (Redhat-6.2). Steps: 1. Open compose window. 2. In To: field input "宇 <email@example.com>" (Chinese Big5 encoding) 3. Send the message. (I'm using SMTP account) 4. Error message: An error occurred while sending mail. The mail server responded: 5.1.1 <"e.<joe\"@numa.com.tw>"> User unknown. Please check the message recipients and try again. In step 2, delete the Chinese character then the mail can be sent correctly. Also, using other Chinese character is OK. Seems some character will cause mozilla to generate wrong recipient list. Should I file another bug regarding this?
Seems the character is translated to Unicode :o Also, sending mail with that character works fine in Mozilla 1.1.
It seems my problem is the same with this one. The bug I reported was caused by the modification of bug 168269.
Kasumi and Marina, Could you try this again? Please make sure that you open a new compose window and type a list name with JA chars and send mail on native mac osx.
Jeesun, what do you mean "native MACOSX". Do you have one? I am localizing it through the System Preferences.
Marina, Yes. that's what I meant: Mac OSX with Japanese encoding as a system encoding.
with 2002-12-02-10 build on MacOSX i had no problem sending email with JA list name. I typed it into the "To" foeld, waited till it autocompletes and clicked send. MacOSX with ja locale, IMAP server. It WFM
Thanks for trying this, Marina. Let me do this again with a new build later. It never worked for me only on Mac OSX. Don't know why.... :-)
No problem to me. tested on 2002-11-20-16-1.0-JA Mac OSX JA(pure JA) IMAP, Netscape Webmail, AOL アカウント List name: さんぽリスト containing card name: さんぽ サンポ さんぽめーる サンポメール さんぽAOL サンポAOL
changing qa contact
QA Contact: jeesun → marina
both naoki and I are off mozilla for about 20 monthes. If these bugs are still here, the real status is 'wont fix'. If you want to reopen it, please find a better owner who really looking at the bug database now.
Status: ASSIGNED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → WONTFIX
Mass Reassign Please excuse the spam
Assignee: nhottanscp → nobody
Mass Re-opening Bugs Frank Tang Closed on Wensday March 02 for no reason, all the spam is his fault feel free to tar and feather him
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Reassigning Franks old bugs to Jungshik Shin for triage - Sorry for spam
Assignee: nobody → jshin1987
Status: REOPENED → NEW
Not reproduce on 3.1 (20100405). Also it is tested on comment #15. mark as WFM.
Assignee: jshin1987 → m_kato
Status: NEW → RESOLVED
Last Resolved: 14 years ago → 8 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.