Bug 353008

Summary:	Cannot send email with 150 recipients in BCC list
Product:	[Applications] kmail2	Reporter:	pietz
Component:	MDN	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	winter
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:

Description pietz 2015-09-21 22:21:19 UTC

When I create a mail with 150 emails as BCC and click on "send  now" it is stored in the oubox folder but never gets send. No error appears.

When I remove step-by-step half of the email addresses it works. thunderbird has no problem with 150 BCCs. I just wante4d to see if it is my ISP or kmail. Seems like a problem in kmail? Some limit?

Reproducible: Always

Comment 1 Allen Winter 2015-09-23 00:02:05 UTC

under Configure KMail =>  Composer page => General tab you'll see an option for "Maximum number of recipient entries".  mine is set to 200.  try playing with that value and see if it helps.

Comment 2 pietz 2015-09-24 23:32:42 UTC

OK, I found it. Many thanks! That was the reason.

But now, honestly.. WHO needs such a setting? Wasn't KDE once founded to keep or make things simple?

How about removing this setting and allow an infinte (or maybe 64 bit integer *g*) recipients? Who cares about this limit?!? Who are you gonna protect with this limit? Viruses?

Can this be discussed somewhere? I don't want kmail getting as complex as emacs ;-)

Cheers
Pietz

Comment 3 Denis Kurz 2017-06-23 20:17:49 UTC

This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.

Comment 4 Denis Kurz 2018-01-31 16:52:23 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12, preferably more recent), please open a new one unless it already exists. Thank you for all your input.