Cyrus issues with Outlook 2013 IMAP?
Hi! Has anyone runnign Outlook 2013 flawless with cyrus? We do run debian cyrus-imapd 2.4.12-2+b1 (still) and do have some issues with Outlook 2013. In detail, we got always mails in outlook 2013, which cannot be deleted, as they are already deleted (error shown by Outlook 2013). But if we use a different client, the email is still perfect in mailbox and not deleted, neither marked for deletion. We did not have had any idea why this happens. Also we do message filtering with sieve and Outlook does not show new messages in folders. Has anyone tips about this? Thank you. MfG, Lars Schimmer -- - TU Graz, Institut für ComputerGraphik WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schim...@cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723 signature.asc Description: OpenPGP digital signature Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: Cyrus issues with Outlook 2013 IMAP?
I've had a couple of people with Outlook 2013 who copied entire folder trees into what they thought was uploaded to the server, but when they later wiped their machine, discovered the messages had never been synchronised, or the folders created, at all. I'm of the opinion that Outlook is still totally broken as an IMAP client, unfortunately. It sounds like it's not good at detecting if it's really in sync :( Bron. On Fri, Sep 19, 2014, at 05:04 PM, Lars Schimmer wrote: Hi! Has anyone runnign Outlook 2013 flawless with cyrus? We do run debian cyrus-imapd 2.4.12-2+b1 (still) and do have some issues with Outlook 2013. In detail, we got always mails in outlook 2013, which cannot be deleted, as they are already deleted (error shown by Outlook 2013). But if we use a different client, the email is still perfect in mailbox and not deleted, neither marked for deletion. We did not have had any idea why this happens. Also we do message filtering with sieve and Outlook does not show new messages in folders. Has anyone tips about this? Thank you. MfG, Lars Schimmer -- - TU Graz, Institut für ComputerGraphik WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schim...@cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723 Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus Email had 1 attachment: + signature.asc 1k (application/pgp-signature) -- Bron Gondwana br...@fastmail.fm Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: High avaliabilty for IMAP/PROXY
Hi, Quoting Fabio S. Schmidt fa...@improve.inf.br: Hi, - Sorry if it seems to be a little off-topic - We have deployed Cyrus Aggregator and currently we provide load balancing and high availability for the Cyrus Front Ends through DNS. With this scenario, if a Frontend is unavailable it will receive connections unless we remove it from the DNS record for the IMAP service. Does anyone have any better ideas to improve the high availability? I was wondering about using HAPROXY vs NGINX but I do not know their behaviours in cases like I mentioned above. We use ClusterIP for load balancing and HA. With ClusterIP you use one IP for all of your Cyrus Front Ends. The ClusterIP will use a multicast MAC an the local firewall cluisterIP rule determin which of the frontends will be used, by hashing source IP, [source Port], [destination Port] in a hash. These hash is distributed to N buckets and each bucket must be serviced by one of your front ends. If one front end goes down you configure the buckets of that front end on the other front ends. http://www.rkeene.org/projects/info/wiki/102 http://www.linux-ha.org/ClusterIP M.MengeTel.: (49) 7071/29-70316 Universität Tübingen Fax.: (49) 7071/29-5912 Zentrum für Datenverarbeitung mail: michael.me...@zdv.uni-tuebingen.de Wächterstraße 76 72074 Tübingen smime.p7s Description: S/MIME Signatur Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
CalDav - public calendars
Hello, are public calendars supported? man imapd.conf ... The public calendar hierarchy will be at the toplevel of the shared namespace. A user's personal calendar hierarchy will be a child of their Inbox. ... If so, what is the right URL to access them? Regards, Vladimir Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: High avaliabilty for IMAP/PROXY
Thanks Ken and Michael for the answers ! Kind regards, Fabio On 19 September 2014 04:49, Michael Menge michael.me...@zdv.uni-tuebingen.de wrote: Hi, Quoting Fabio S. Schmidt fa...@improve.inf.br: Hi, - Sorry if it seems to be a little off-topic - We have deployed Cyrus Aggregator and currently we provide load balancing and high availability for the Cyrus Front Ends through DNS. With this scenario, if a Frontend is unavailable it will receive connections unless we remove it from the DNS record for the IMAP service. Does anyone have any better ideas to improve the high availability? I was wondering about using HAPROXY vs NGINX but I do not know their behaviours in cases like I mentioned above. We use ClusterIP for load balancing and HA. With ClusterIP you use one IP for all of your Cyrus Front Ends. The ClusterIP will use a multicast MAC an the local firewall cluisterIP rule determin which of the frontends will be used, by hashing source IP, [source Port], [destination Port] in a hash. These hash is distributed to N buckets and each bucket must be serviced by one of your front ends. If one front end goes down you configure the buckets of that front end on the other front ends. http://www.rkeene.org/projects/info/wiki/102 http://www.linux-ha.org/ClusterIP M.MengeTel.: (49) 7071/29-70316 Universität Tübingen Fax.: (49) 7071/29-5912 Zentrum für Datenverarbeitung mail: michael.me...@zdv.uni-tuebingen.de Wächterstraße 76 72074 Tübingen Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus -- My best regards, Fabio Soares Schmidt Linux Professional Institute - LPIC-3 Microsoft Certified Technology Specialist: Active Directory Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
