Re: Managesieve bug recurring?

Jesse Jarzynka <[email protected]> Fri, 1 Apr 2011 13:03:12 -0400
Newsgroups gmane.mail.perdition.user
Message-ID <[email protected]>
Hi Simon,

Thank you so much for the reply, I've been banging at this all week
searching for an answer. I'm trying to build perdition from mercurial,
and keep getting:

./configure: line 11270: syntax error near unexpected token
`VANESSA_LOGGER,vanessa-logger'
./configure: line 11270:
`PKG_CHECK_MODULES(VANESSA_LOGGER,vanessa-logger >= 0.0.10)'

I removed the vanessa packages from the debian repos and even
installed them from source and tried again and get the same error. Any
ideas? -Jesse

On Thu, Mar 31, 2011 at 9:56 PM, Simon Horman <[email protected]> wrote:
> Hi Jesse,
>
> there is a sieve authentication bug that I have fixed in mercurial
> but not yet pushed out into an rc release or Debian package.
>
> http://hg.vergenet.net/perdition/perdition/rev/6544c58ec144
>
> Would it be possible for you to try the latest mercurial code?
>
> http://hg.vergenet.net/perdition/perdition/
>
> On Thu, Mar 31, 2011 at 11:07:41AM -0400, Jesse Jarzynka wrote:
>> Just as an update, I tried running with my exact same perdition.conf
>> config on Lenny using the package from the backports which is version
>> 1.19~rc3-1~bpo50+1 (changed ports on both perdition and managesieve
>> servers to 2000 from 4190) and I'm getting less verbose logs but got
>> an additional "Fatal Error reading authentication information from
>> client":
>>
>> Mar 31 10:58:52 samus-lenny-dev perdition.managesieve[28360]: Connect:
>>  10.30.40.197:47761->10.30.40.166:2000
>> Mar 31 10:59:49 samus-lenny-dev perdition.managesieve[28360]: Fatal
>> Error reading authentication information from client
>> 10.30.40.197:47761->10.30.40.166:2000: Exiting child
>> Mar 31 11:00:18 samus-lenny-dev perdition.managesieve[28618]: Connect:
>>  10.30.40.197:47765->10.30.40.166:2000
>> Mar 31 11:00:27 samus-lenny-dev perdition.managesieve[28618]: Exiting
>> on signal 11
>>
>> On Wed, Mar 30, 2011 at 2:52 PM, Jesse Jarzynka <[email protected]> wrote:
>> > Hello All,
>> > I'm setting up perdition for IMAP and Managesieve proxying with LDAP.
>> > LDAP proxying is working fine, I'm getting my mailhost from there, but
>> > for managesieve I keep getting: "perdition.managesieve[7871]: Exiting
>> > on signal 11" and I'm wondering if it's a recurrence of this bug -
>> > http://lists.vergenet.net/pipermail/perdition-users/2010-July/002332.html
>> > . I'm using the Debian Squeeze with has the following packages in the
>> > repos:
>> >
>> > ii  perdition                           1.19~rc4-2
>> > POP3 and IMAP4 Proxy server
>> > ii  perdition-ldap                      1.19~rc4-2
>> > Library to allow perdition to access LDAP based popmaps
>> >
>> > Here is more of my log:
>> >
>> > Mar 30 14:40:00 perdition-dev perdition.managesieve[7871]: Connect:
>> > 10.30.40.197:37245->10.30.40.163:4190
>> > Mar 30 14:40:00 perdition-dev perdition.managesieve[7871]: SELF:
>> > "\"IMPLEMENTATION\" \"perdition\"\r\n\"SIEVE\" \"comparator-i;octet
>> > comparator-i;ascii-casemap fileinto reject envelope encoded-character
>> > vacation subaddress comparator-i;ascii-numeric relational regex
>> > imap4flags copy include variables body enotify environment mailbox
>> > date\"\r\n\"SASL\" \"PLAIN\"\r\n\"NOTIFY\" \"mailto\"\r\n\"VERSION\"
>> > \"1.19-rc4\"\r\nOK \"predition ready on perdition-dev.localnet.sys
>> > 0002b5e3\"\r\n"
>> > Mar 30 14:40:04 perdition-dev perdition.managesieve[7871]: CLIENT:
>> > "AUTHENTICATE \"PLAIN\"
>> > \"AHRlc3RhY2NvdW50MDBAbG9jYWxuZXQuY29tAFRlY2g5OTk=\"\r\n"
>> > Mar 30 14:40:04 perdition-dev perdition.managesieve[7871]:
>> > username_add_domain: username_add_domain 0 1
>> > Mar 30 14:40:04 perdition-dev perdition.managesieve[7871]:
>> > username_add_domain: username_add_domain 0 4
>> > ///////////////////////////// THIS RESPONSE IS FROM THE CORRECT
>> > MANAGESIEVE SERVER SO THE PROXY IS WORKING
>> > /////////////////////////////
>> > Mar 30 14:40:04 perdition-dev perdition.managesieve[7871]: REAL:
>> > "\"IMPLEMENTATION\" \"dovecot\"\r\n\"SIEVE\" \"comparator-i;octet
>> > comparator-i;ascii-casemap fileinto reject envelope encoded-character
>> > vacation subaddress comparator-i;ascii-numeric relational regex
>> > imap4flags copy include variables body enotify environment mailbox
>> > date spamtest spamtestplus virustest\"\r\n\"SASL\" \"PLAIN
>> > LOGIN\"\r\n\"STARTTLS\"\r\n\"NOTIFY\" \"mailto\"\r\n\"VERSION\"
>> > \"1.0\"\r\nOK \"Dovecot ready.\"\r\n"
>> > Mar 30 14:40:04 perdition-dev perdition.managesieve[7871]: Exiting on signal 11
>> >
>> >
>> > So as you can see it exits after it connects to the correct
>> > managesieve server. I can provide any more logging and answers if
>> > someone has an idea where to look. Thanks, Jesse
>> >
>> ______________________________________________
>> Perdition-users mailing list
>> [email protected]
>> http://lists.vergenet.net/listinfo/perdition-users
>>
>
______________________________________________
Perdition-users mailing list
[email protected]
http://lists.vergenet.net/listinfo/perdition-users