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 673528 - Unable to send via EWS - "user account ... does not have the right to send mail on behalf..."
Unable to send via EWS - "user account ... does not have the right to send ma...
Status: RESOLVED DUPLICATE of bug 664749
Product: evolution-ews
Classification: Other
Component: Mail
3.2.x
Other Linux
: Normal major
: ---
Assigned To: Evolution EWS maintainer(s)
Evolution EWS maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2012-04-04 19:10 UTC by Jeff Skaistis
Modified: 2012-07-25 15:07 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jeff Skaistis 2012-04-04 19:10:20 UTC
Attempting to send an email message using EWS (Exchange 2007) results in the following message box:
------
An error occurred while sending. How do you want to proceed?

The reported error was "The user account which was used to submit this request does not have the right to send mail on behalf of the specified sending account.".
------

After some research and fiddling, it appears that EWS will return this when sending a message that includes a From: header with any valid email address. It appears the recommendation is to exclude the From: header submitted message and let Exchange add it instead.  I was able to confirm this by saving the unsent message in the Outbox, manually editing the file, then re-sending. When I removed the header or changed it to something that's not an address, it was sent.

I don't know how this issue applies to other Exchange versions, or when using non-NTLM authentication.
Comment 1 Milan Crha 2012-07-25 15:07:23 UTC
Thanks for a bug report. Your investigation is correct. This had been fixed within bug #664749, thus I'm marking this as a duplicate of it.

*** This bug has been marked as a duplicate of bug 664749 ***