evolution-ews changes the from field to invalid@invalid

Bug #1673548 reported by Dravida
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
evolution-ews (Ubuntu)
Incomplete
Low
Unassigned

Bug Description

Exchange connection works fine. The mail comes. But when I try to send mail, there is a replacement in the FROM field to invalid@invalid address instead of that I pointed out. And I get the following error from server:
__________________________
Unfortunately, the system was unable to deliver your mail.
The error given was:

2017-03-16 17:24:40 : You are not allowed to send as user or group invalid@invalid

You may need to contact your e-mail administrator to solve this problem.
_________________________

Evolution version is 3.18.5.2
evolution-ews the same

My system is Linux Mint 18.1 4.4.0-57-generic
Architecture: amd64

Description: Linux Mint 18.1 Serena
Release: 18.1

I use Amazon WorkMail service.

Revision history for this message
Corey Seliger (seliger) wrote :
Download full text (3.2 KiB)

Ubuntu 16.04.3 here.

I can confirm this issue with Amazon WorkMail. I ran Evolution with EWS_DEBUG=2 and dumped out the transaction between the client and AWS. The transaction itself is successful. However, if you un-MIME the actual message being sent, you will notice in the headers:

From:

(Literally, the from field is blank.)

I wiped my Evolution configuration and started from scratch and yielded the same result. I also have an EWS account configured with Exchange 2013 and have been using it successfully.

I have attached three files that demonstrate the situation:

debug.log - The dump of the interchange between AWS and Evolution
soap_post.xml - The prettied up version of the POST sent to AWS containing the message payload
mime_decode.txt - The decoded message as contained within the MimeContent field in the XML

I am happy to provide more information; let me know what is needed.

seliger@core:~$ dpkg -l | grep evolution
ii evolution 3.18.5.2-0ubuntu3.2 amd64 groupware suite with mail client and organizer
ii evolution-common 3.18.5.2-0ubuntu3.2 all architecture independent files for Evolution
ii evolution-data-server 3.18.5-1ubuntu1 amd64 evolution database backend server
ii evolution-data-server-common 3.18.5-1ubuntu1 all architecture independent files for Evolution Data Server
ii evolution-data-server-online-accounts 3.18.5-1ubuntu1 amd64 evolution data server integration with Ubuntu Online Accounts
ii evolution-ews 3.18.5-1ubuntu1 amd64 Exchange Web Services integration for Evolution
ii evolution-plugins 3.18.5.2-0ubuntu3.2 amd64 standard plugins for Evolution
ii libebackend-1.2-10:amd64 3.18.5-1ubuntu1 amd64 Utility library for evolution data servers
ii libebook-1.2-16:amd64 3.18.5-1ubuntu1 amd64 Client library for evolution address books
ii libebook-contacts-1.2-2:amd64 3.18.5-1ubuntu1 amd64 Client library for evolution contacts books
ii libecal-1.2-19:amd64 3.18.5-1ubuntu1 amd64 Client library for evolution calendars
ii libedata-book-1.2-25:amd64 3.18.5-1ubuntu1 amd64 Backend library for evolution address books
ii libedata-cal-1.2-28:amd64 3.18.5-1ubuntu1 amd64 Backend library for evolution calendars
ii libedataserver-1.2-21:amd64 3.18.5-1ubuntu1 amd64 Utility library for evolution data servers
ii libedataserverui-1.2-1:amd64 3.18.5-1ubuntu1 amd64 Utility library for evolution data servers
ii ...

Read more...

Revision history for this message
Corey Seliger (seliger) wrote :
Revision history for this message
Corey Seliger (seliger) wrote :
Revision history for this message
Corey Seliger (seliger) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in evolution-ews (Ubuntu):
status: New → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

The error looks like https://bugzilla.gnome.org/show_bug.cgi?id=770754 which should be fixed on newer versions, can you try on Ubuntu 18.04 if that's still a problem?

Changed in evolution-ews (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.