On 2013-04-13 09:26, Adam Tauno Williams wrote:
> On Sat, 2013-04-13 at 12:56 +0100, Charles Bradshaw wrote:
> This seems very unreliable, slow, and hacky. When I login to my e-mail
> the system typically tells me the last time I logged in [at least to
> that app]. Doesn't the meta-data in the IM
On 2012-11-15 15:51, Bron Gondwana wrote:
> On Thu, Nov 15, 2012, at 09:46 PM, Chris Conn wrote:
>> On 2012-11-15 15:34, Dan White wrote:
>>> On 11/15/12 11:59 +1100, Puthick Hok wrote:
>>>> Hi,
>>>>
>>>> I am migrating my cyrus imap from th
On 2012-11-15 15:34, Dan White wrote:
> On 11/15/12 11:59 +1100, Puthick Hok wrote:
>> Hi,
>>
>> I am migrating my cyrus imap from the current server with cyrus 2.3.7
>> to a new server with better hardware running cyrus 2.3.16.
>>
>> I've googled for the command to dump the seen database in
>> /va
On 2012-04-24 15:42, Jules Agee wrote:
> On 04/24/2012 02:00 AM, Martin Kraus wrote:
>> Hi. I hoped that cyrus would be managable through ldap but that doesn't
>> seem to be the case. Is the cyrus ldap support strictly for authentication?
>> It's just that sasl can do that as well.
>>
>> I'd like t
On 2012-01-19 11:40, Rosenbaum, Larry M. wrote:
Are there any RPMs available yet for cyrus-imapd v2.4.13? We're
running RHEL6.
Larry M. Rosenbaum
Oak Ridge National Laboratory
http://www.invoca.ch/pub/packages/cyrus-imapd/
I built them on a Centos 6.2 server and they worked well in my se
> "IMPLEMENTATION" "Cyrus timsieved v2.4.8-Invoca-RPM-2.4.8-1.el4"
> "SASL" "PLAIN"
> "SIEVE" "comparator-i;ascii-numeric fileinto reject vacation imapflags
> notify envelope relational regex subaddress copy"
> "STARTTLS"
> OK
>
> Other question, do you have cyrus-sasl-plain installed?
>
> Thanks,
Hello,
I am trying to get sieve working with a RPM distro of Cyrus I built
using Invoca. I believe my problem is caused by timsieved not
advertising LOGIN or PLAIN capability and causing the client
(horde/ingo) to fail`;
"IMPLEMENTATION" "Cyrus timsieved v2.4.8-Invoca-RPM-2.4.8-1.el6"
"SA
> BTW: What happened to the rpms published by Simon Matter? Nothing to be
> found at http://www.invoca.ch/pub/packages/cyrus-imapd/ recently.
>
> -psi
>
>
> Cyrus Home Page: http://www.cyrusimap.org/
> List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
http://www.invoca.ch/
> No. This kind of bogus, racy, non-deterministing messing is precisely what
> the strong consistent locking design of Cyrus 2.4 is designed to avoid!
>
> You could always:
>
> cd /var/imap/proc; grep -l $username * | xargs kill
>
> if you actually want to kill the user connections.
>
> Bron.
T
Hello,
I am looking at this option for 2.4.5;
disconnect_on_vanished_mailbox: 1
If enabled, IMAP/POP3/NNTP clients will be disconnected by the server if
the currently selected mailbox is (re)moved by another session.
Otherwise, the missing mailbox is treated as empty while in use by the
clien
Hello,
I'm toying with a Horde module that allows to create SIEVE filters and
store them in an ldap directory. This works, however I haven't found
any documentation as to how it might be (is it?) possible to read these
filters from the mailSieveRuleSource: of a ldap dn.
The module is Ingo, an
On 2010-11-29 16:49, Bron Gondwana wrote:
> So set the clocks on the machines out by a few more seconds and you'll
> be fine.
>
> Seriously - the problem is that it works when you test manually because
> they're not happening at the same time. "things die" because
> replication is asynchronous, a
>> Hmm I hadn't read that. I was aware that doing it in a high volume
>> scenario was problematic, but was under the impression that an
>> occasional delivery here and there was theoretically possible. Its
>> pretty amazing since I test it manually and I can send to either one or
>> the other and
>
> I didn't think that the slave was supposed to be setup to accept
> incoming mail?
>
>
> http://comments.gmane.org/gmane.mail.imap.cyrus/33805
>
>
Hello,
Hmm I hadn't read that. I was aware that doing it in a high volume
scenario was problematic, but was under the impression that an
occasi
> As for your earlier errors...
>
> There is a bug with sync_crc calculation in 2.4.4, so I would recommend
> waiting for 2.4.5 before upgrading again. I'm hoping we can release
> 2.4.5 very soon, and Kolab will be building their RPMs pretty quickly
> too I imagine.
Hello,
I'm hoping that this
15 matches
Mail list logo
