On 13/07/10 16:53, Dan vi5u0-alug@yahoo.co.uk wrote:
On Tue, 13 Jul 2010, Wayne Stallwood wrote:
But is there a reason you can't ask the admin to set up a server side rule or just simply redirect your mail to another address ?
The sysadmins volunteered the answer to this without being asked. The answer was that they won't countenance the use of the Exchange equivalent of a .forward file under any circumstances whatever. And a somewhat pointed offer of the opportunity to attend a training course in the use of OWA.
Thanks to all who replied. One or two of the leads sound promising.
Dan,
We have a very similar issue here in BT, the Exchange systems have forwarding disabled, so in order to read my email from a Debian desktop, I have used (in chronological order):
Evolution: ok-ish with Exchange 2003 OWA using Ximian connector
Outlook 2003 in a Qemu VM against Exchange 2007 (I was 'upgraded')
Thunderbird or Evolution or any IMAP/CalDAV/LDAP client via DavMail to the Exchange 2007 OWA - works very nicely, is 100% FOSS and written in Java so runs anywhere (currently on my local mail server). I was so impressed I gave the guy a donation!
http://davmail.sourceforge.net/ - it rocks :)
P
On Tue, Jul 13, 2010 at 05:14:30PM +0100, Phil Ashby wrote:
On 13/07/10 16:53, Dan vi5u0-alug@yahoo.co.uk wrote:
On Tue, 13 Jul 2010, Wayne Stallwood wrote:
But is there a reason you can't ask the admin to set up a server side rule or just simply redirect your mail to another address ?
The sysadmins volunteered the answer to this without being asked. The answer was that they won't countenance the use of the Exchange equivalent of a .forward file under any circumstances whatever. And a somewhat pointed offer of the opportunity to attend a training course in the use of OWA.
Thanks to all who replied. One or two of the leads sound promising.
Dan,
We have a very similar issue here in BT, the Exchange systems have forwarding disabled, so in order to read my email from a Debian desktop, I have used (in chronological order):
Evolution: ok-ish with Exchange 2003 OWA using Ximian connector
Outlook 2003 in a Qemu VM against Exchange 2007 (I was 'upgraded')
Thunderbird or Evolution or any IMAP/CalDAV/LDAP client via DavMail to the Exchange 2007 OWA - works very nicely, is 100% FOSS and written in Java so runs anywhere (currently on my local mail server). I was so impressed I gave the guy a donation!
http://davmail.sourceforge.net/ - it rocks :)
There's a little tool I used when I was at BT that does a sort of 'fetchmail' on Outlook. It was written in Java. I'm desperately trying to think of its name - but can't at the moment. If I do remember I will add it here.
A quick update. Solved the problem by resorting to IE and using the filtering-rules functionality in the resulting fuller version of OWA. Not quite what I had in mind, but it seemed to work.
On Tue, 13 Jul 2010, Phil Ashby wrote:
We have a very similar issue here in BT, the Exchange systems have forwarding disabled, so in order to read my email from a Debian desktop, I have used (in chronological order):
Evolution: ok-ish with Exchange 2003 OWA using Ximian connector
It appears that Evolution's Exchange connectivity has been borked by a recent library upgrade: http://forums.gentoo.org/viewtopic-t-834437.html?sid=471d5835dbeae08fe952e5735d8e23e5.
Outlook 2003 in a Qemu VM against Exchange 2007 (I was 'upgraded')
This didn't work out due to something I forgot to mention about the server: its security certificate expired months ago. Couldn't suss out how to override the resulting client-side security panic in Outlook.
http://davmail.sourceforge.net/ - it rocks :)
Are all components of this open source? I downloaded what's supposed to be the source tarball and it contains (among other stuff) a bunch of .class files - but I thought .class files were pre-compiled JVM bytecode. Yes? No?
On 15/07/10 23:46, Dan wrote:
This didn't work out due to something I forgot to mention about the server: its security certificate expired months ago. Couldn't suss out how to override the resulting client-side security panic in Outlook.
It sounds like you have awesome admins looking after that exchange server :)