Re: [Evolution] Evolution to Exchange 2007?
If you have any specific issue to be resolved we can target that for 0.28.x I have one. I am not able to connect to exchange 2007, because i am connected through RPC over HTTP behind a proxy and AFAIK this is not supported yet :(. Another flaw is that i can not enter domain name of a server - that crashes Evolution. If this was not reported yet, i would fill a bug report - just point me to some bug tracker please. -- Kind Regards Patryk Benderz IT Specialist Linux Registered User #377521 +48 22 538 6292 ERSTE Securities Polska S.A. ul. Królewska 16 Warszawa 00-103 KRS 065121 NIP 526-10-27-638 REGON 011136053 Kapitał akcyjny: 15.500.000 złotych (w pełni opłacony) This message and any attached files are confidential and intended solely for the addressee(s). Any publication, transmission or other use of the information by a person or entity other than the intended addressee is prohibited. If you receive this in error please contact the sender and delete the material. The sender does not accept liability for any errors or omissions as a result of the transmission. ___ Evolution-list mailing list Evolution-list@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] Evolution to Exchange 2007?
On Thu, 2009-06-25 at 07:50 -0400, Scott Ehrlich wrote: Hello to all: What is the most recent status of MAPI support for Evolution connectivity to Exchange 2007 server for calendaring, etc? We have released 0.26.x and working towards 0.28.x If you have any specific issue to be resolved we can target that for 0.28.x Thanks. -- Johnny [johnnyjacob.wordpress.com | johnnyjacob.org] May you share freely, never taking more than you give signature.asc Description: This is a digitally signed message part ___ Evolution-list mailing list Evolution-list@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-list
[Evolution] Evolution to Exchange 2007?
Hello to all: What is the most recent status of MAPI support for Evolution connectivity to Exchange 2007 server for calendaring, etc? I've seen various blogs and email threads, but I wanted to tap this list's resources, too. Thanks. Scott ___ Evolution-list mailing list Evolution-list@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] Evolution and Exchange 2007 (aka 5.5) on Fedora - port 135
On Wed, Sep 10, 2008 at 3:03 PM, Paul Smith [EMAIL PROTECTED] wrote: On Wed, 2008-09-10 at 08:23 +0200, Valent Turkovic wrote: The Evolution Exchange connector uses the Exchange Open Web Access (OWA) interface, which is essentially the Exchange webmail interface, to contact Exchange. Thus, to use the connector you need to have the Web ports open (80 and 443, for HTTP and HTTPS respectively). However, the new mapi-provider backend talks to the server using Microsoft MAPI protocol, which is the same protocol that Outlook uses to talk to Exchange. This protocol uses different ports, of course, since it's a different protocol. Before my company switched to new Exchange 2007 I could read email from wherever I was (over public facing owa through Evolution Exchange Connector), and if I understand you now this is not possible now because ports that are needed to do the communication are usually blocked by corporate firewall. Ok, I can use my email via Evolution now when I'm inside the company's LAN but before I had been spoiled by accessing my email from home or from anywhere else. Is there some solution to this? The right answer is that your company should be providing a VPN for remote access. Having the Exchange server HTTP interface (or MAPI interface) directly available through their firewalls to the internet is... well, it's just not a good idea and we'll leave it at that. The question is, can Windows users use Outlook when they are remote? If so, then you can use Evolution. If Windows users have to use a browser to read mail when they're remote then you will have to do the same. The only solution that would allow you to continue to use Evolution with only a Web interface is for someone to rework the Evolution Connector backend so that it can parse the new HTTP format that Exchange 2007 is using. The problem with the model used by Evo Connector is that it relies on the HTTP interface provided by Exchange. However, Microsoft can (and does) feel free to modify that interface at any time: there is no backward-compatibility etc. issue, because the code is all on the server and clients only have a browser to connect with. They can rewrite the entire interface with every release if they like. And, creating software to bridge between the HTTP provided by Exchange and the functionality required by Evolution is not a simple task, at all. It's a constant effort to stay current. That's why developers are moving to MAPI, which is a (more) stable protocol and much easier to manage. Thank you for really great answer, I admit I didn't use VPN because I didn't need to, now that I need it I'll configure it (it is a pain to configure it). Cheers, Valent . -- http://kernelreloaded.blog385.com/ linux, blog, anime, spirituality, windsurf, wireless registered as user #367004 with the Linux Counter, http://counter.li.org. ICQ: 2125241, Skype: valent.turkovic ___ Evolution-list mailing list Evolution-list@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] Evolution and Exchange 2007 (aka 5.5) on Fedora - port 135
On Tue, Sep 9, 2008 at 8:31 AM, Johnny Jacob [EMAIL PROTECTED] wrote: On Mon, 2008-09-08 at 10:48 -0400, Paul Smith wrote: On Mon, 2008-09-08 at 15:55 +0200, Valent Turkovic wrote: I tracked the issue and got a confirmation on irc that the port 135 needs to be opened on corporate firewall in order for mapi-provider to work. I thought that ports 80 and 443 were enough because older evolution-exchange provider worked like that, and I saw no mention of this on official FAQ. If you have access to the server then there are several guides online on how to configure exchange / outlook under a firewall. Would be nice if this could be tested with the provider :) Thanks a lot ! The Evolution Exchange connector uses the Exchange Open Web Access (OWA) interface, which is essentially the Exchange webmail interface, to contact Exchange. Thus, to use the connector you need to have the Web ports open (80 and 443, for HTTP and HTTPS respectively). However, the new mapi-provider backend talks to the server using Microsoft MAPI protocol, which is the same protocol that Outlook uses to talk to Exchange. This protocol uses different ports, of course, since it's a different protocol. Before my company switched to new Exchange 2007 I could read email from wherever I was (over public facing owa through Evolution Exchange Connector), and if I understand you now this is not possible now because ports that are needed to do the communication are usually blocked by corporate firewall. Ok, I can use my email via Evolution now when I'm inside the company's LAN but before I had been spoiled by accessing my email from home or from anywhere else. Is there some solution to this? Cheers, Valent. -- http://kernelreloaded.blog385.com/ linux, blog, anime, spirituality, windsurf, wireless registered as user #367004 with the Linux Counter, http://counter.li.org. ICQ: 2125241, Skype: valent.turkovic ___ Evolution-list mailing list Evolution-list@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] Evolution and Exchange 2007 (aka 5.5) on Fedora - port 135
On Wed, 2008-09-10 at 08:23 +0200, Valent Turkovic wrote: The Evolution Exchange connector uses the Exchange Open Web Access (OWA) interface, which is essentially the Exchange webmail interface, to contact Exchange. Thus, to use the connector you need to have the Web ports open (80 and 443, for HTTP and HTTPS respectively). However, the new mapi-provider backend talks to the server using Microsoft MAPI protocol, which is the same protocol that Outlook uses to talk to Exchange. This protocol uses different ports, of course, since it's a different protocol. Before my company switched to new Exchange 2007 I could read email from wherever I was (over public facing owa through Evolution Exchange Connector), and if I understand you now this is not possible now because ports that are needed to do the communication are usually blocked by corporate firewall. Ok, I can use my email via Evolution now when I'm inside the company's LAN but before I had been spoiled by accessing my email from home or from anywhere else. Is there some solution to this? The right answer is that your company should be providing a VPN for remote access. Having the Exchange server HTTP interface (or MAPI interface) directly available through their firewalls to the internet is... well, it's just not a good idea and we'll leave it at that. The question is, can Windows users use Outlook when they are remote? If so, then you can use Evolution. If Windows users have to use a browser to read mail when they're remote then you will have to do the same. The only solution that would allow you to continue to use Evolution with only a Web interface is for someone to rework the Evolution Connector backend so that it can parse the new HTTP format that Exchange 2007 is using. The problem with the model used by Evo Connector is that it relies on the HTTP interface provided by Exchange. However, Microsoft can (and does) feel free to modify that interface at any time: there is no backward-compatibility etc. issue, because the code is all on the server and clients only have a browser to connect with. They can rewrite the entire interface with every release if they like. And, creating software to bridge between the HTTP provided by Exchange and the functionality required by Evolution is not a simple task, at all. It's a constant effort to stay current. That's why developers are moving to MAPI, which is a (more) stable protocol and much easier to manage. ___ Evolution-list mailing list Evolution-list@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] Evolution and Exchange 2007 (aka 5.5) on Fedora - port 135
On Mon, 2008-09-08 at 10:48 -0400, Paul Smith wrote: On Mon, 2008-09-08 at 15:55 +0200, Valent Turkovic wrote: I tracked the issue and got a confirmation on irc that the port 135 needs to be opened on corporate firewall in order for mapi-provider to work. I thought that ports 80 and 443 were enough because older evolution-exchange provider worked like that, and I saw no mention of this on official FAQ. If you have access to the server then there are several guides online on how to configure exchange / outlook under a firewall. Would be nice if this could be tested with the provider :) Thanks a lot ! The Evolution Exchange connector uses the Exchange Open Web Access (OWA) interface, which is essentially the Exchange webmail interface, to contact Exchange. Thus, to use the connector you need to have the Web ports open (80 and 443, for HTTP and HTTPS respectively). However, the new mapi-provider backend talks to the server using Microsoft MAPI protocol, which is the same protocol that Outlook uses to talk to Exchange. This protocol uses different ports, of course, since it's a different protocol. signature.asc Description: This is a digitally signed message part ___ Evolution-list mailing list Evolution-list@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-list
[Evolution] Evolution and Exchange 2007 (aka 5.5) on Fedora - port 135
Hi, I managed to install new evolution-mapi-provider on Fedora 9 and it works while I'm connected on the local LAN but it doesn't connect when I try to read the email over the internet. I got these errors: failed to connect host 213.191.xxx.xxx on port 135 - NT_STATUS_CONNECTION_RERUSED I tracked the issue and got a confirmation on irc that the port 135 needs to be opened on corporate firewall in order for mapi-provider to work. I thought that ports 80 and 443 were enough because older evolution-exchange provider worked like that, and I saw no mention of this on official FAQ. Can somebody clarify this a bit more, and thank you in advance. Cheers, Valent. -- http://kernelreloaded.blog385.com/ linux, blog, anime, spirituality, windsurf, wireless registered as user #367004 with the Linux Counter, http://counter.li.org. ICQ: 2125241, Skype: valent.turkovic ___ Evolution-list mailing list Evolution-list@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] Evolution and Exchange 2007 (aka 5.5) on Fedora - port 135
On Mon, 2008-09-08 at 15:55 +0200, Valent Turkovic wrote: I tracked the issue and got a confirmation on irc that the port 135 needs to be opened on corporate firewall in order for mapi-provider to work. I thought that ports 80 and 443 were enough because older evolution-exchange provider worked like that, and I saw no mention of this on official FAQ. The Evolution Exchange connector uses the Exchange Open Web Access (OWA) interface, which is essentially the Exchange webmail interface, to contact Exchange. Thus, to use the connector you need to have the Web ports open (80 and 443, for HTTP and HTTPS respectively). However, the new mapi-provider backend talks to the server using Microsoft MAPI protocol, which is the same protocol that Outlook uses to talk to Exchange. This protocol uses different ports, of course, since it's a different protocol. ___ Evolution-list mailing list Evolution-list@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] Evolution and Exchange 2007
I see my previous reply never made it to the list. Here goes again! Johnny Jacob wrote: Please add /opt/samba4/lib to /etc/ld.so.conf run a `ldconfig -v`. ( I should add this to the post installation scripts in the package ) To keep with the Fedora way of doing things, I actually created /etc/ld.so.conf.d/samba4 and added that line to it. After running `ldconfig -v` I ran Evolution without adding environment variables (just to see if it would work) and the plugin showed up and was checked! I'll have to try connecting from work to see if I can actually get to my mail. I can see my folders but have Refreshing folder(...) which could take a really long time, and I'm running late. [End of message from 03 Apr 2008] OK, now for the new info: I haven't gotten around to trying it at work yet. I saw there are updates available, but when I tried to install I got: Error: Missing Dependency: libtalloc.so.1 is needed by package evolution-mapi-provider It didn't want me to work around it easily, so I removed all the mapi stuff and reinstalled it to get the new version. After running `ldconfig` again, I'm able to connect to Exchange via MAPI. I can see new messages in the list but still can't actually view any. I've tried double clicking messages as well but get nothing. Clicking other folders does not show the messages in those folders. The oldest message in my inbox shows Feb 2008, but there really are messages from last year, so that's a little concerning as well. Is there a list showing what is expected to work? (I don't want to sound like a complainer; it's really cool that this much works!) Thanks! ___ Evolution-list mailing list Evolution-list@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-list
[Evolution] Evolution and Exchange 2007
Hi All, I just tried the last days to connect the Evolution Client 2.8.2 to a Exchange 2007 server without any luck. Now I read that Exchange 2007 should be supported with release 2.9.3. Is this true? Does it work with this version? Thanks thomas ___ Evolution-list mailing list Evolution-list@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] Evolution and Exchange 2007
Hi Smith, Can you file a bug on exchange connector? A bug will help us exchange patches/test comments. V. Varadhan On Wed, 2006-10-18 at 11:04 -0600, Smith,Karl N wrote: When configuring an Evolution client to connect to an Exchange 2007 server the following error message is received: The Exchange server URL you provided is for an Exchange 5.5 server. Ximian connector supports Microsoft Exchange 2000 and 2003 only. Entourage clients that connect with the same WebDav mechanism are able to authenticate without a problem. Are there any plans to update the Exchange connector to support Exchange 2007 in the recent future? Let me know if there is any data collection or log files needed to troubleshoot this problem. I would be happy to pass them along. Nick Smith Academic Computing and Networking Services Colorado State University [EMAIL PROTECTED] 970.491.2356 ___ Evolution-list mailing list Evolution-list@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-list ___ Evolution-list mailing list Evolution-list@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] Evolution and Exchange 2007
hej veerapuram, Am Donnerstag, den 09.11.2006, 23:49 +0530 schrieb Veerapuram Varadhan: Can you file a bug on exchange connector? A bug will help us exchange patches/test comments. for future reference, please add a link and use the correct name of the product - don't make it too hard for users. ;-) http://bugzilla.gnome.org/enter_bug.cgi?product=Evolution%20Exchange thanks, andre -- mailto:[EMAIL PROTECTED] | failed! http://www.iomc.de signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Evolution-list mailing list Evolution-list@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] Evolution and Exchange 2007
On Thu, 2006-11-09 at 19:48 +0100, Andre Klapper wrote: hej veerapuram, Am Donnerstag, den 09.11.2006, 23:49 +0530 schrieb Veerapuram Varadhan: Can you file a bug on exchange connector? A bug will help us exchange patches/test comments. for future reference, please add a link and use the correct name of the product - don't make it too hard for users. ;-) http://bugzilla.gnome.org/enter_bug.cgi?product=Evolution%20Exchange Noted and will be taken care in future replies and thanks for the link. ;-) V. Varadhan ___ Evolution-list mailing list Evolution-list@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-list
[Evolution] Evolution and Exchange 2007
When configuring an Evolution client to connect to an Exchange 2007 server the following error message is received: The Exchange server URL you provided is for an Exchange 5.5 server. Ximian connector supports Microsoft Exchange 2000 and 2003 only. Entourage clients that connect with the same WebDav mechanism are able to authenticate without a problem. Are there any plans to update the Exchange connector to support Exchange 2007 in the recent future? Let me know if there is any data collection or log files needed to troubleshoot this problem. I would be happy to pass them along. Nick Smith Academic Computing and Networking Services Colorado State University [EMAIL PROTECTED] 970.491.2356 ___ Evolution-list mailing list Evolution-list@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-list
Re: [Evolution] Evolution and Exchange 2007
On Wed, 2006-10-18 at 11:04 -0600, Smith,Karl N wrote: When configuring an Evolution client to connect to an Exchange 2007 server the following error message is received: The Exchange server URL you provided is for an Exchange 5.5 server. Ximian connector supports Microsoft Exchange 2000 and 2003 only. Entourage clients that connect with the same WebDav mechanism are able to authenticate without a problem. Are there any plans to update the Exchange connector to support Exchange 2007 in the recent future? You could consider using evolution-brutus. e-b support Exchange 5.5, 2000, 2003 and 2007. -- jules ___ Evolution-list mailing list Evolution-list@gnome.org http://mail.gnome.org/mailman/listinfo/evolution-list
