Bug 330787

Summary:	E-mail failed to send. Too many recipients.
Product:	[Applications] kmail2	Reporter:	Phil Davison <phil.davison1>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	montel, phil.davison1
Priority:	NOR
Version:	4.10.5
Target Milestone:	---
Platform:	Mint (Ubuntu based)
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Phil Davison 2014-02-05 09:54:07 UTC

I have just started getting this message which suggests it is a server problem rather than a KMail problem, but on very rare occasions I don't. 

Also I don't have this problem if I use webmail but I don't know enough about how that works to know if it is done in a different way. 

I note from the internet that other people have had this issue as well and it always gets blamed on the SMTP server but I am not so sure seeing as KMail has enough other bugs to make me consider dumping what always used to be my favourite e-mail client.

Reproducible: Sometimes

Steps to Reproduce:
1. Send an e-mail, or
2. Forward an e-mail, or
3. Reply to an e-mail
Actual Results:  
I get an error message which says, 

E-Mail Sending Failed. 
Failed to transport message. Message sending failed since the following recipients were rejected by the server: [a single e-mail address] (The server responded: "Too Many Recipients (VM502)"
This is a temporary failure. You may try again later.)

Expected Results:  
The software should have sent the message.

From my personal, possibly selfish. perspective this is either major or grave but I will mark it as "Normal" and to be fixed because I could just leave KMail and use something else instead, but I don't like webmail so I don't want to have to rely on that. And, of course, it might not actually be a KMail problem although I am sure the webmail page uses the same servers to send and receive mail.

Comment 1 Laurent Montel 2014-02-05 14:08:01 UTC

1) we need an example  (type of address perhaps you use specific characters)
2) Did it work in thunderbird for example ? Perhaps it's your smtp server which has a problem
3) 4.10.5 is very very old (we will release 4.13 in 2 months)

Comment 2 Phil Davison 2014-02-06 10:21:50 UTC

On Wednesday 05 February 2014 14:08:01 you wrote:
> https://bugs.kde.org/show_bug.cgi?id=330787
> 
> Laurent Montel <montel@kde.org> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
> CC|                            |montel@kde.org
> 
> --- Comment #1 from Laurent Montel <montel@kde.org> ---
> 1) we need an example  (type of address perhaps you use specific characters)
> 2) Did it work in thunderbird for example ? Perhaps it's your smtp server
> which has a problem
> 3) 4.10.5 is very very old (we will release 4.13 in 2 months)

1. Just an ordinary e-mail address with alpha and numeric characters plus of course the 
"@" in the middle (and not just one).
2. It worked with my webmail at the time.  I don't know enough about how email works to 
know if that is done in the same way but I can't see how it wouldn't. It's not like the 
difference between POP3 and IMAP is it?  Also I just sent a message to one of my other 
email addresses and that worked OK with Thunderbird.  I am sending this using KMail.
3. I use what is on the repository. I don't use Linux, I use the programs which run in Linux. I 
am not a computer expert but I am probably more confident about using different 
software than the average Windows user.  I don't want to go through installing something 
from outside a repository and then having to keep it up to date. I want my computer to do 
that sort of work for me.

Anyway, fingers crossed and here goes.

Comment 3 Denis Kurz 2016-09-24 18:17:52 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.

Comment 4 Denis Kurz 2017-01-07 22:40:29 UTC

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