ZimbraNotify (aka: toaster wannabe)

[internalkernel]

This thread seems to have gone dormant... but hopefully, someone out there is still listening... This is a great project! and something that is so needed for the linux end.

I'm getting an Error: 501 can only handle messagesappointmentstasksdocuments

I've tried SSL on/off, all my packages are properly installed... just at a loss here. Any info would be helpful... thanks again

[homesfortomes]

Hello,

I am using Ubuntu 8.10 and I cannot seem to get this to work. I get an error stating: Error: 501 can only handle messagesappointmentstasksdocuments

I used the GTK2::Trayicon and Crypt:SSLeay packages available through synaptic as they seem to be the same versions as those at The CPAN Search Site - search.cpan.org and also seem to satisfy the dependencies. Any ideas?

[homesfortomes]

Pretty bizzare! Two nearly identical questions posted within minutes of eachother!

[pbruna]

Hi,
First im going to try to make some time an post the new version of zimbranotify im working on.
The error 501 is coming from the Zimbra Server, it has nothing to do with perl or any perl module, did you make any modification to the script? if is so, what modification did you do?

[homesfortomes]

Hi PBruna,

I did not make any modifications to the script. A new version would be great! Please let me know if I can help test anything.

[internalkernel]

Likewise, no modifications... Server side, I have changed the default ports that Zimbra is listening on - since I'm also running Apache on there, it needed to default to different ports.

In preferences, I set the port number with the domain name - mail.example.com:1234 If the port number is not set, the connection just times out... which I would expect. So, it seems to be hitting the Zimbra server at least...

Could this configuration be an issue? Is there a work around?

Thanks for the reply!

[sanek84]

Very usefull app. Thanx!

[sysinit]

Hi!

I also got the 501 HTTP error, but was able to find out the cause of the problem. If there is an ampersand (@) in the password, authentication fails because the GET-Request looks like this:

https://user:p@ssword@host.domain/zimbra/home/user/inbox.atom?query=is:unread

Of course this won't work...

The solution is to authenticate using the HTTP::Headers function:

--- zimbranotify.orig 2008-02-14 13:42:07.000000000 +0100
+++ zimbranotify 2009-06-16 18:51:49.000000000 +0200
@@ -707,10 +707,12 @@
my @username = split(/\@/,$user);
my $httpmode = $save_ssl ? "https" : "http";

- my $req_string = "$httpmode://$username[0]:$password\@$server$zimbra_path$user$zimbra_mail_u ri";
+ my $req_string = "$httpmode://$server$zimbra_path$user$zimbra_mail_uri";
$http_status->enqueue($trans{notify_check});

- my $req = HTTP::Request->new(GET => $req_string);
+ my $hdr = new HTTP::Headers;
+ $hdr->authorization_basic($username[0], $password);
+ my $req = HTTP::Request->new("GET", $req_string, $hdr);
my $error;

my $response = $ua->request($req);


Hope this helps... ;-)

Regards,
Daniel

[storm]

Originally Posted by pbruna

Hi,
First im going to try to make some time an post the new version of zimbranotify im working on.

That's great news, I assume it's the SOAP version.
Looking forward to, I'm sure it's highly sought-after.
Is there any help or support you need?

Thanks,
Störm

[storm]

Exchange Web Services OSX Widget - Release: EWSMacWidget 1.0.0.0

This is Mac OS X (open source) app which uses soap to communicate with exchange.

Perhaps this is useful?