Version: 1.5.4 (using KDE 3.1.4) Installed from: (testing/unstable) Compiler: gcc version 3.3.2 (Debian) OS: Linux (i686) release 2.4.23-1-686 Domain names with non-ASCII characters are coming! Currently .com und .net Domains with special characters, e.g. German Umlauts, can be registered, .de and .at domains will follow in March. A major problem, however, is that most e-mail clients disallow the specification of a domain name (i.e. mailserver) with non-ASCII characters in the network settings. (I only know of Ximian, for now, that doesn't do that.) While this was intentious in the past it is now starting to be obsolete to disallow the input of non-ASCII characters! Please fix that quickly! Thanks very much! Peter P.S.: KMail disallows the input of Umlauts here: Properties -> KMail Settings... -> Network -> Incoming (tab) -> Change... (button) => Server (input field)
IDN support elsewhere in KDE is already done for KDE 3.2, so it's a simple bug of not allowing non-ASCII in that field. I've just tested for the sending field and it has worked fine with a testing server. Confirmed in HEAD 20031222.
This is no bug, and by far no simple one, sorry. It's a missing feature and thus a wish. Enter the ACE form for now or hope the best.
Marc: I meant the POP3 server name, not an e-mail address. As I said, the SMTP server configuration already works. From what I can tell, the only missing thing here is for the text-edit field to allow non-ASCII characters.
On e-mail addresses, KMail is currently RFC-2047 encoding. This one is I agree with you to be a new feature.
@Thiago: How can we check whether the string the user entered is a valid server name, i.e. how do we check that conversion to punycode was successful?
The functions in namespace KIDNA (kdecore/kidna.h) will tell you that. If a Unicode-hostname is valid, toAscii will return its ACE form; if it's invalid, it returns empty. This is what you should know. You don't have to check if an ACE-encoded hostname is valid -- all ASCII-only hostnames are valid, provided they don't break STD 3 rules. toAscii and name resolution verify STD 3-compliance. Anyways, this is not the case here. Just allow the full range of Unicode in the server name widget. If the user enters something that is invalid, it will be the same as entering a hostname that doesn't exist -- the lookup routines take care of that.
This is still present in KDE 3.3 rc2. May I remind you this affects Incoming mail servers only? Outgoing is fine.
What you are talking about here is using an IDN server as incomming mail server in KMails network settings right? May I ask if anyone is thinking about what needs to be done to actually send email to an IDN server. Should this be left up to the smtp server to handle or should some translation be done in KMail? For the record kmail translates danish hostnames incorrectly. For instance andersa@ellenshøj.dk becomes andersa@=?iso-8859-1?q?ellensh=F8j=2Edk?= but should be andersa@xn--ellenshj-c5a.dk
No, let me repeat comment #3: === Marc: I meant the POP3 server name, not an e-mail address. As I said, the SMTP server configuration already works. From what I can tell, the only missing thing here is for the text-edit field to allow non-ASCII characters. === The email destination address has to be properly translated, but that is not the issue of this bug report. It's just there because I can't type non-ASCII letters into the text-field, when the ioslave can already accept such names.
Yeah.. That's also what I said.. Read the first one or two lines again. :)
IDNs still do not work with KMail in KDE 3.3. I tried sending a mail to a IDN e-mail address. KMail converts it like text to "recipient@iso-8859-15?q?whatever" instead of converting it to puny code internally (or whatever there is to do). I think this is an important feature that is missing. (For the german guys: GMX webmail can handle IDNs, why shouldn't KMail?)
On Wednesday 09 February 2005 21:28, Peter Bittner wrote: > I tried sending a mail to a IDN e-mail address. KMail converts it like text > to "recipient iso-8859-15?q?whatever" instead of converting it to puny code > internally (or whatever there is to do). Actually, I think that particular problem belongs with bug #87836 - "Can't send mail to IDN hosts or domains". > I think this is an important feature that is missing. How about throwing some votes on those bugs then? Anders
I was about to close this bug since entering IDNs (e.g. Umlaut domains) in KMail works for the dialogs of Identities and Outgoing Mail Servers. (Read: Entering IDNs and sending mail as the *owner* of an IDN e-mail address works!) The only thing that is still missing is modifying the 'Server' text field in the Incoming Mail Server dialog to allow IDNs to be entered. (KMail: Settings -> Configure KMail -> Network -> Incoming -> Change: 'Server' field) When this will be fixed we can close this bug. (Please refer to bug #87836 for inability to send e-mail *to* an IDN mail address recipient! - I was in error too, sorry for that.)
Still an issue, r449049.
Created attachment 12224 [details] Attempt at fixing the problem The attached patch solves this issue by removing the validator. Unfortunately, with IDN, it's no longer possible to tell which letters are allowed. At most, we'd be able to say which ones aren't. Could this be a security issue? I don't know.
How about doing a dns lookup on the host name?
I think the way to solve this is to write an rfc compliant validator just as we have for email addresses, unless such a thing already exists elsewhere in KDE I mean it seems pretty general and not KMail specific to me. The validator I mean
Matt: this is not an email validator, but a simple hostname. I don't know anywhere else in KDE code that does such validations. It would be possible to construct a QValidator that uses Network::KResolver::normalizeDomain to validate -- but note that the validation can only happen after the user has finished typing because it might be an expensive one and partial hostnames may be invalid.
I know it is not an email validator, but what I ment was that the validation is similar, and the QValidators sucks for this kind of validating since as you say partially typed addresses can still be valid later on, I am yet to find a way to fire a Qvalidator after typing stopped, I mean this char by char validation is just plain wrong in this case. but it should not be to hard to validate on another event do you think?
Yes, we could easily validate the hostnames typed when the Ok or Apply buttons are pressed. But let me say again that nowhere else is this kind of validation done, including in KMail itself: the outgoing account dialog doesn't validate, so it has supported IDN all along.
Thank you for your feature request. Kmail1 is currently unmaintained so we are closing all wishes. Please feel free to reopen a feature request for Kmail2 if it has not already been implemented. Thank you for your understanding.
Instead of creating a new feature request, please confirm here if the wishlist is still valid for kmail2.