After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 770754 - Can't send email with Amazon Workmail
Can't send email with Amazon Workmail
Status: RESOLVED DUPLICATE of bug 758374
Product: evolution-ews
Classification: Other
Component: Mail
3.20.x
Other Linux
: Normal normal
: ---
Assigned To: Evolution EWS maintainer(s)
Evolution EWS maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2016-09-02 13:49 UTC by Luca
Modified: 2016-09-06 10:07 UTC
See Also:
GNOME target: ---
GNOME version: 3.19/3.20


Attachments
ews debug log (94.77 KB, text/x-log)
2016-09-02 13:49 UTC, Luca
Details

Description Luca 2016-09-02 13:49:46 UTC
Created attachment 334649 [details]
ews debug log

Sending an email seems successful, i.e. Evolution does not report any error. However after a few seconds an error email is sent from the mailer daemon, with the following message:

---->8--->8---->8--->8---->8--->8---->8--->8----

Unfortunately, I was unable to deliver your mail.
The error given was:

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.

---->8--->8---->8--->8---->8--->8---->8--->8----

As suggested in bug 695311 I checked the output of
$ grep "^Email= *" .config/evolution/sources/*
and is my email address

I attach a log of
$ EWS_DEBUG=2 evolution 2>&1 >evolution-ews-send.log

Tested on Debian sid:
$ dpkg -l evolution-ews
...
ii  evolution-ews                              3.20.5-1                   amd64                      Exchange Web Services integration for Evolution
Comment 1 David Woodhouse 2016-09-02 19:41:21 UTC
If you base64-decode the MimeContent of the message that's sent, it has an empty From: header...

Subject: test
From: 
To: dar…
Comment 2 Luca 2016-09-04 19:08:43 UTC
Hi, I see that this is cleared in camel_ews_utils_create_mime_message(), introduced in commit 546b2d73fb72a75d54cd035bda3567247f78a67a.
If I delete the lines that remove the From: header, I can send emails successfully.
Comment 3 Milan Crha 2016-09-05 17:44:47 UTC
Thanks for a bug report. Does the Amazon use real Exchange server? It claims to be Exchange2007_SP3, I'm afraid the SP3 added some functionality which broke the previous, which is that if the From address was empty then the server auto-added correct address. The problem is that the user's email not always matches what the server uses for sending, which resulted in the email-related changes from the commit you cited above.

There is bug #758374, where the suggested change there should fix your issue. Let's mark this as a duplicate of it and deal with this there.

*** This bug has been marked as a duplicate of bug 758374 ***
Comment 4 Luca 2016-09-05 18:36:55 UTC
I don't know if Amazon uses a real Exchange server.. I can try and gather more information, is there a debug tool for this?
Comment 5 Milan Crha 2016-09-06 10:05:55 UTC
There's nothing more than the EWS_DEBUG=2, which you already provided. I attached a proposed patch at the other bug report (see comment #3), could you give it a try, please?
Comment 6 Milan Crha 2016-09-06 10:07:58 UTC
(In reply to Milan Crha from comment #5)
> There's nothing more than the EWS_DEBUG=2, which you already provided. I
> attached a proposed patch at the other bug report (see comment #3), could
> you give it a try, please?

Ah, you already tried it, thanks.