Hiya !
I ended up seeing your actual pics on Facebook. I quite like you a lot. Why
don't we communicate !
I can send you my pics as well if you want...
Sending you all my love,
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Co
tags 618569 + pending
thanks
Dear maintainer,
I've prepared an NMU for avelsieve (versioned as 1.9.9-2.3) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards.
--
.''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
: :' : De
On 30 June 2012 23:34, Alex Owen wrote:
> Upstream have "accepted" upstream bug:
> http://email.uoa.gr/avelsieve/ticket/275.
>
> Upstream changeset 1144 is a "Possible fix for #275":
> http://email.uoa.gr/avelsieve/changeset/1144
>
> The approach is to lowercase the auth strings at all points in
Upstream have "accepted" upstream bug: http://email.uoa.gr/avelsieve/ticket/275.
Upstream changeset 1144 is a "Possible fix for #275":
http://email.uoa.gr/avelsieve/changeset/1144
The approach is to lowercase the auth strings at all points in the
code so that the result is a case insensitive matc
I have taken the liberty of open upstream bug #275 to track this upstream
https://email.uoa.gr/avelsieve/ticket/275
Regards
Alex Owen
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Looking at the upstream code it would appear that upstream svn
revision 851 is to "blame" for this bug.
http://email.uoa.gr/avelsieve/changeset/851
Changeset 851 is titled: "Ignore case for Sieve capabilities list".
There are 3(or 4) places the code needs to be changed to have the
desired effect
As you have probably noticed in my submission to this bug yesterday
the patch is the wrong way round. oops!
Here is the correct patch:
--- managesieve.lib.php.orig2012-06-07 15:09:28.0 +0100
+++ managesieve.lib.php 2012-06-07 17:20:30.0 +0100
@@ -887,10 +8
Package: avelsieve
Version: 1.9.9-2
Severity: normal
Guido Günther's analysis is only half the story so his patch is NOT the fix.
On fist connection dovecot (with TLS configured) will correctly NOT advertise
PLAIN authentication (unless you have configured it to allow non-TLS login).
avelsieve
tags 618569 +patch
thanks
Hi,
I was seeing the same problem. The attached patch fixes this for me. The
issue here is that dovecot isn't properly advertising PLAIN. Details can
be found in the patch.
Cheers,
-- Guido
>From 8dec6396b8744f88a7bfc44bb1217d12c385a769 Mon Sep 17 00:00:00 2001
From: =?U
Hi all,
maybe I can shed some light on the issue.
Some hours ago I tried to setup squirrel-avelsieve against dovecot
with STARTTLS and 'plaintext auth' turned off on both sides.
Following the logfiles (see below /var/log/apache/error.log)
I decided playing around with the auth-mechanisms and the
On 03/21/11 08:54, Tom Jägermeister wrote:
> Hi,
>
>> After upgrade to squeeze (1.9.9-2) avelsieve does not connect to dovecot
>> (pidgenhole) sieve implementation any more: cannot connect to timsieve
>> server.
>
> I had this as well and it is because avelsieve tries to connect to port
> 4190
Hi,
> After upgrade to squeeze (1.9.9-2) avelsieve does not connect to dovecot
> (pidgenhole) sieve implementation any more: cannot connect to timsieve
> server.
I had this as well and it is because avelsieve tries to connect to port
4190 instead of 2000 (see below), which dovecot uses by defa
Package: avelsieve
Version: 1.9.7-6+lenny1
Severity: normal
Tags: squeeze upstream
After upgrade to squeeze (1.9.9-2) avelsieve does not connect to dovecot
(pidgenhole) sieve implementation any more: cannot connect to timsieve server.
After downgrading to the lenny (1.9.7-6+lenny1) version again
13 matches
Mail list logo
