Bug 237646 - Cannot set the return to address in kontact/kmail
Summary: Cannot set the return to address in kontact/kmail
Status: RESOLVED DUPLICATE of bug 280151
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-14 18:06 UTC by Jon
Modified: 2011-11-09 16:33 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jon 2010-05-14 18:06:48 UTC
Version:            (using KDE 4.4.2)
OS:                Linux
Installed from:    Ubuntu Packages

When attempting to set the return address in kontact/kmail
it gives the error 

"The email address you entered is not valid because it does not seem to contain an actual email address, i.e. something of the form joe@example.org."

and you only have the option of clicking cancel. The email address tested was a valid address at gmail.com

this bug prevents you from sending mail because you must have a reply to address. 

Bug found on Kubuntu 10.04 (All updates applied)

Keep up the awesome work with KDE! It's so awesome!!!
Comment 1 Jon 2010-05-14 18:13:25 UTC
I confirmed this bug on my brothers system anybody else experiencing this?
Comment 2 MuH4hA 2011-11-09 16:18:11 UTC
The actual problem is NOT the return address. I had the same problem right now on an openSUSE 11.3 with kmail version 1.13.6 (KDE 4.6.00).

The problem seems to be, that after setting up kmail, the Identity has no email-address (Edit Identiy -> General -> Email Adress). The error message is about this empty field.
You probably ignored it, went straight to (Edit Identiy -> Advanced) and got the error message after filling out the reply-to-address. But it's about the general mail-address of your identity, which is probably still an empty string.

regards,
Ingo
Comment 3 MuH4hA 2011-11-09 16:30:34 UTC
this bug is a duplicate of 280151 btw...
Comment 4 David Nadlinger 2011-11-09 16:33:35 UTC

*** This bug has been marked as a duplicate of bug 280151 ***