Bug 118284

Summary:	"Send again" doesn't work with undisclosed recipients
Product:	[Unmaintained] kmail	Reporter:	Tristan Miller <psychonaut>
Component:	general	Assignee:	kdepim bugs <pim-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	dwmw2, jjm
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Tristan Miller 2005-12-14 00:06:49 UTC

Version:            (using KDE KDE 3.5.0)
Installed from:    SuSE RPMs

To reproduce:
1. Message->New Message…
2. Enter an recipient address as BCC, but do not enter a To address.
3. Message->Send Mail
4. Go to the sent-mail folder
5. Click on the message you just sent
6. Message->Send Again…
7. Message->Send Mail

Observed behaviour:
8. Error dialog pops up:
Invalid EMail Address - KMail
Undisclosed.Recipients: ;@port-3108
The email address you entered is not valid because it contains an illegal character

Expected behaviour:
8. KMail should have properly filled in the To field (or left it blank) and sent the mail without any errors.

Comment 1 Jonathan Marten 2006-10-28 14:06:03 UTC

Reproducible in KMail 1.9.5, KDE 3.5.5

Comment 2 Daniel Hahler 2006-10-28 14:14:05 UTC

Yes, confirmed.

I get "Undisclosed.Recipients: ;" in the "To:" field of the mail popup after "Send Again..."

Comment 3 Jonathan Marten 2006-10-28 16:44:24 UTC

*** Bug 123162 has been marked as a duplicate of this bug. ***

Comment 4 Michal Bukovsky 2007-01-09 19:43:35 UTC

Group addresses like "Undisclosed.Recipients: ;" and other is disabled by KPIM::isValidEmailAddress function which is used before sending mail. (In KMMessage::isValidEmailAddressList)

Colon char is on blacklist for this bug http://bugs.kde.org/show_bug.cgi?id=98720

Comment 5 Chris Samuel 2007-07-13 01:45:52 UTC

I too have been bitten by this bug preventing valid RFC 2822 group addresses from working, and have left a comment to that effect on 98720.

Comment 6 Thomas McGuire 2008-06-17 18:47:15 UTC


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