[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    Bug#24981: kmail to cc addresses without '@'
From:       Ingo =?iso-8859-1?q?Kl=F6cker?= <ingo.kloecker () epost ! de>
Date:       2001-06-15 20:10:12
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday, 15. June 2001 09:47, Michael Häckel wrote:
> On Thursday, 14. June 2001 15:14, Don Sanders wrote:
> > As a workaround to this drawback of mimelib KMail should scan the
> > address fields (To, Cc, Bcc) for local addresses, i.e. addresses
> > without domain part, and add '@localhost' to them, so that these
> > local addresses aren't removed by mimelib.
> >
> > Regards,
> > Ingo
> > </quote>
>
> Or we could add auto completion like present in pine for example,
> which also adds the real name of the user automatically.

Normally if a user only enters a single name like "ingo" in the To 
field he expects the mail to be send to ingo@localhost. I don't think 
that auto completion is the right solution for this. What we could do 
and IIRC this is what Netscape did is the following: We could 
temporarily add the characters the user has already entered appended 
with "@localhost" to the auto completion pop up.
Example:
The user starts to enter something in the To/CC/BCC field.
The user enters "i".
The auto completion pop up pops up and shows "i@localhost" followed by 
all other email addresses that start with "i".
The user enters "n".
The auto completion pop up now shows "in@localhost" followed by all 
other email addresses that start with "in".
And so on.

The problem with this is that this will only work if the user uses the 
auto completion in pop up mode and if he really selects ingo@localhost 
if he wants to send a message to this user. If he doesn't select this 
address or any other fully qualified email address there will still be 
a simple "ingo" in the To field.

Therefore IMHO the only solution for this is to automagically add a 
"@localhost" to all email addresses which are not fully qualified.

Regards,
Ingo

P.S.: Michael please send your replies to <bugnumber>@bugs.kde.org and 
not simply to this mailing list because otherwise the bug tracking 
system can't log your replies.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7KmukGnR+RTDgudgRAsFQAJ41NfM0huW/16OxnK/pb+1iI/ZwkwCgiqla
+NbXUMHa3q/KKCkFbzsPaZU=
=DfK8
-----END PGP SIGNATURE-----

[prev in list] [next in list] [prev in thread] [next in thread]