Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×
The Internet Technology

Hosting Services with DBCS-Enabled Webmail? 33

Dan asks: "I'm looking for an ISP that has double-byte capable Web mail. I have a small personal Web site where I blog on the Japanese game industry. The hosting at my current provider has been perfectly reliable, but I can't send or receive Japanese e-mail through their Web mail system, which can be a problem when I'm on the road. I'd prefer not to switch to a Japan-based hosting service because that would mean a Japanese UI for the Webmail, and I want to be able to give addresses to my friends that don't read Japanese. Does anyone know of a U.S. hosting service that might fill my needs? Thanks for all suggestions."
This discussion has been archived. No new comments can be posted.

Hosting Services with DBCS-Enabled Webmail?

Comments Filter:
  • Horde? (Score:5, Informative)

    by m0rph3us0 ( 549631 ) on Friday March 12, 2004 @07:37PM (#8548456)
    I think Horde provides DBCS support. I know it certainly supports a japanese interface. They seem to have lots of i18n support so I would imagine it works.
  • Verio Signature... (Score:4, Informative)

    by Anonymous Coward on Friday March 12, 2004 @07:41PM (#8548498)
    Verio Signature [viaverio.com]. Right now only available to resellers, but I'm sure it would be easy to find a reseller to buy from. Includes webmail that supports Japanese and English.
  • What's the problem? (Score:2, Interesting)

    by jjhlk ( 678725 )
    How is it a problem to send that sort of mail on 'normal' servers? Double-byte characters are made of two single-bytes. :)

    Is it a 7-bit byte versus 8-bit byte? I don't how the protocol needs to know anything about your e-mails content.
    • by sakusha ( 441986 ) on Saturday March 13, 2004 @12:29AM (#8549885)
      The answer is: it depends. Any mail system can store and transmit messages made with several different double-byte character encodings. But a truly compatible webmail system would look at the headers, detect the type of encoding (i.e. EUC, ISO-1022), and set the HTML headers to make the browser switch to the proper coding, so it displays properly instead of showing mojibake.
      • ut a truly compatible webmail system would look at the headers, detect the type of encoding (i.e. EUC, ISO-1022), and set the HTML headers to

        make the browser switch to the proper coding, so it displays properly instead of showing mojibake.

        More precisely, convert the text from the charset the email is stored in to the one negociated with the web browser (most likely, UTF8). The problem is that some mail client *cough*Eudora*cough* may not specify a correct charset for the body, or fail to encode headers

        • Right. I described that a little bit unclearly, sorry. Obviously I meant that the email headers, which (usually) indicate the text encoding, must be used by the webmail system to present the correct code type to the browser.
          I even made an error, Japanese is ISO-2022, oopsie. That's what I get from going off the top of my head, there are too many damn codes in this world to remember them all with precision.
          • No prob. I just thought it would be a good idea to shime in as I am currently fighting such an issue with Horde/IMP. Some mail sent from Eudora (older version, I think) don't encode headers properly. Thus, when a subject contain accented characters (in my case, ISO-8859-1), the mail summary is full of ??? as the browser asked for UTF-* but received some part in ISO-8859-1 (and IMP can't do nothing about it as it doe snot know the source charset).
  • .Mac (Score:5, Informative)

    by sakusha ( 441986 ) on Saturday March 13, 2004 @12:24AM (#8549872)
    Mac.com webmail supports Japanese, I just got some Japanese email and I checked the web interface (I usually use mail.app) and it works great. I know lots of people using .Mac for blogs.
    • Since this got modded up, I suppose I should point out that .Mac supports WebDAV and you can upload HTML content from any platform, and of course the webmail is universal as well.
  • i18n (Score:3, Insightful)

    by osewa77 ( 603622 ) <naijasms@gma[ ]com ['il.' in gap]> on Saturday March 13, 2004 @03:04AM (#8550357) Homepage
    [sigh] internalization is one of those things that we developers only start to add on when our code becomes widely popular. If only the programming techniques for adding i18n support were more straightforward.
  • by malachid69 ( 306291 ) on Saturday March 13, 2004 @05:54AM (#8550795) Homepage
    All ISPs should be capable of supporting Unicode email. For example, a quick google shows that SquirrelMail [squirrelmail.org], WebMail [mintersoft.com], et cetera all support it.

    Likelyhood is that it just needs configured... For example, look under "Text Encoding" here [jonoke.com].

    • SquirrelMail supports Japanese, only if you use Japanese translation and php supports mbstring. You won't be able to use Japanese translation, if php does not have mbstring support.

      utf-8 support works only if you use utf-8 translation or if your utf-8 symbols does not contain four bytes or more.
      • utf-8 support works only if you use utf-8 translation or if your utf-8 symbols does not contain four bytes or more.

        Is that just a bug in SquirrelMail or in the mbstring support of php?

        • Is that just a bug in SquirrelMail or in the mbstring support of php?

          squirrelmail does not use mbstring to read utf-8. mbstring/recode/iconv decoding is not perfect and depends on specific php modules. SquirrelMail should be able to run without those php modules.

          SquirrelMail uses own functions that convert utf-8 to html codes. developers just need time to go nuts, play with calculator and create complex cycle that works with 4 byte symbols.

          two and three bytes decoding works in most of the cases. I t

          • Well, if we are talking about UTF-8, the number of bytes is determined by the code point you are trying to represent -- and the specific bytes specify if there is another byte following or not. I have done an implementation converting to/from UTF-8, and it is really very simplistic. However, whether there is 2-3 bytes, 4 bytes, or even 6 bytes is determined by which codepoint is being represented.

            Malachi
      • I just tried configuring Squirrelmail for Japanese on Dreamhost, my web host - I got some Japanese text messages but it didn't work well, and gave a fatal error due to PHP's multibyte support. So I don't recommend that host at least - presumably a web/mail host based in Asia will have the best support.
  • It depresses me sometimes to be reminded at how very slowly things like this catch on. We are stuck in obsolete, bad decisions from the past (like ASCII). The problem is simple: it is easy to do the wrong thing. Why would someone add unicode support when they don't even have to put any thought to just using the ASCII their C-strings compile to?
  • by Anonymous Coward
    mail.yahoo.co.jp Their web mail works.... and if you don't want an account with them, you can use POP on their webmail from any pop server.... and you can do it for free....

    I use yahoo for web-mail when at work. I have them pull it off of my pop server, and they have an option to leave it on the pop server too. So when I go home, all of my e-mail still shows up in my mail client.... Also, you can change the "reply-to" header to anything that you want.... It is a great solution that won't cause you to cha
  • Myhosting.com (Score:2, Informative)

    by Space Cow ( 93479 )
    I have been using them since 1999. Price is reasonable, service is good, and they support DBCS (I use them for Japanese).

Never test for an error condition you don't know how to handle. -- Steinbach

Working...