Bug 367983 - "ContactName <Contact.Name@domain.xxx>" invitations with smtp.gmail.com server causes errors
Summary: "ContactName <Contact.Name@domain.xxx>" invitations with smtp.gmail.com serve...
Status: RESOLVED FIXED
Alias: None
Product: korganizer
Classification: Applications
Component: invitations (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR minor
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-08-30 01:29 UTC by Steeven Hudon
Modified: 2017-07-07 15:11 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.6.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Steeven Hudon 2016-08-30 01:29:35 UTC
When sending invitations from my contacts or recent addresses drop-down list, with outgoing mail server smtp.gmail.com, I get the following error : " Message sending failed since the following recipients were rejected by the server".

Reproducible: Always

Steps to Reproduce:
1. I send an invitation to someone from the drop-down list (from my contact list) with the format  "ContactName <Contact.Name@domain.xxx>".


Actual Results:  
I always get the following error : "E-Mail Sending Failed - Failed to transport message.  Message sending failed since the following recipients were rejected by the server: ContactName (The server responded: "5.5.2 Syntax error g78sm112724itb.12 - gsmtp")

Expected Results:  
To receive a notification displaying that the e-mail has been sent successfully. 

1. My outgoing mail server is "smtp.gmail.com".  
2. I tried with the outgoing mail server "smtp-mail.outlook.com" and it works as expected.  
3. It is a google-smtp-related problem.
4. An easy, but not user-friendly, workaround is to remove the "ContactName<" and ">" part of the drop-down list contact.  The drop-down list is useful to get contacts and recent e-mail addresses, but with this bug, it becomes less useful.
Comment 1 Dan 2016-10-20 13:48:46 UTC
Does not only apply to Google's SMTP server. I have the same issue with an MS Exchange 2013 server on the other end.
Comment 2 Laurent Montel 2017-07-07 15:11:50 UTC
it's fixed in 5.6.0