GNOME Bugzilla – Bug 664749
Cannot send message "Service not connected"
Last modified: 2013-03-20 11:35:45 UTC
I tried to send a message in current git master, after 3.3.2 release, and I cannot, because I receive an error when I press Send (Ctrl+Enter): > An error occurred while sending. How do you want to proceed? > > The reported error was "Service not connected". That's new, isn't it?
Also can't send any mail with 3.3.4, don't know if this actually is the same bug (I'll open a new one if you prefer so). After some time trying I get a popup with: "The reported error was "Could not connect to derstandard.at: NSPR error code -5961"."
Hmm, I just got similar issue with my MAPI account, which was caused by account editing, its transport URL was changed from mapi:// to smtp://, and the error message came from the smtp provider. Can this be the same issue, thus it might be moved to Evolution itself? Please check with: $ gconftool-2 --get /apps/evolution/mail/accounts | grep ews:// | \ grep transport
Well I indeed had smtp:// listed in the accounts key (which means the setup is somehow broken, this account was newly added with 3.3.4). BUT: When manually changing to ews:// I now get the same error you initially reported: The reported error was "Service not connected". So not a very huge step forward ;)
Just for a record, I filled bug #668714 for the garbled protocol after account preferences editing.
Created attachment 207169 [details] [review] proposed ews patch for evolution-ews; This made the "Service not connected" error go away for me, but I still cannot send messages, because I receive a different error, this time: "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", which I think is something with my setup, thus I would like to ask you, Andreas, to try with this patch too. Thanks in advance.
Perfect, with that patch applied sending mails finally works :) Thanks a lot !
Do you know the server version you use ews against? I have Exchange 2007, and there it claims the other error I mentioned above.
Created attachment 207180 [details] [review] proposed ews patch (send-as-denied) for evolution-ews; This is for my other issue, for the send-as-denied error. It's done as described here [1]. Maybe it's relevant only for exchange 2007 servers. [1] http://social.technet.microsoft.com/Forums/da/exchangesvrdevelopment/thread/bf0e5ea1-7ec6-4386-9637-3f37f9d4a653
(In reply to comment #7) > Do you know the server version you use ews against? I have Exchange 2007, and > there it claims the other error I mentioned above. Yep this is with Exchange 14.1.270.1 === Exchange 2010 SP1.
(In reply to comment #9) > Yep this is with Exchange 14.1.270.1 === Exchange 2010 SP1. Then it might be the 2007 thing, it seems.
Created attachment 207186 [details] [review] updated ews patch (send-as-denied) for evolution-ews; As we spoke about this with David on IRC, this is updated patch for send-as-denied, which checks whether the From address matches the address for which the account was configured and claims if not. It removes the From header content and let's the exchange server fill it itself. I miss better error messages :)
Looks good; thanks. I'd prefer to see that error message make it clearer that this is an *Exchange* bug, not a limitation in our EWS client implementation. And if/when we get round to fixing the fact that Evolution forces us to do send and save as two *separate* operations, and prevents us from using the SendAndSaveCopy operation, we may have even more fun. But we'll deal with that when we come to it. Would be useful if ema were to have similar behaviour... I think you told me it just strips the From address without the comparison?
(In reply to comment #12) > Would be useful if ema were to have similar behaviour... I think you told me it > just strips the From address without the comparison? Yup, I'm going to commit similar checking on send in evolution-mapi too.
I changed the two errors to "Exchange server cannot..." and then: Created commit 546b2d7 in ews master (3.3.90+)
(In reply to comment #13) > Yup, I'm going to commit similar checking on send in evolution-mapi too. Hrm, I do not have the email address available during message send in ema, the one to which was the account configured. Maybe I'll change it later. (Just for your information.)
*** Bug 673528 has been marked as a duplicate of this bug. ***