A NOTE has been added to this issue.
==
http://www.dbmail.org/mantis/view.php?id=401
==
Reported By:yuen
Assigned To:
Hello!
I like to have dbmail and libsieve packages for ubuntu.
Bulding dbmail packages itself is quite easy. It works out of the box.
But building libsieve is a little bit tricky. So far there exists no working
deb package.
The library from Paul's debian repository has a strange numbering schema.
A NOTE has been added to this issue.
==
http://www.dbmail.org/mantis/view.php?id=401
==
Reported By:yuen
Assigned To:
Lars Kneschke wrote:
> Hello!
>
> I like to have dbmail and libsieve packages for ubuntu.
>
> Bulding dbmail packages itself is quite easy. It works out of the box.
>
> But building libsieve is a little bit tricky. So far there exists no
> working deb package.
libsieve is now part of debian/u
Can't you download paul's source package, and use his debian build tree
as base for yours?
Thank you for the links, they are a great help.
I have a question though,
if I telnet to the sieve port I get to the timesieved. It states to
support PLAIN authentication, but doesn't accept it.
Below is the transcript of the telnet session:
Escape character is '^]'.
"IMPLEMENTATION" "DBMail tims
On Mon, 2006-09-18 at 09:21 +0200, Paul J Stevens wrote:
> This libsieve2-1_2.1.12-1_i386.deb numbering scheme is *required*, and
> also you'll need the dfsg source, not the tarball Aaron has provided on
> libsieve.sf.net. That one contains RFC docs which are non-free.
Yep, the RFC's are coming o
On Mon, 2006-09-18 at 09:39 +0200, Marc Dirix wrote:
> authenticate "PLAIN"
> NO "Authentication scheme not supported."
It's a bug. The response to that line should be something like
NO "Authenticate requires an argument"
Unfortunately, there's no simple plain-text login option. You'll need to
g
A NOTE has been added to this issue.
==
http://www.dbmail.org/mantis/view.php?id=401
==
Reported By:yuen
Assigned To:
the base64 of usernameNULLpasswordNULL
username\0username\0password\0
It's a bug. The response to that line should be something like
NO "Authenticate requires an argument"
However as I read in the RFC:
The optional initial-response argument to the AUTHENTICATE command
is used to sav
On Thu, 2006-09-14 at 01:31 -0400, Morty wrote:
> On Tue, Sep 12, 2006 at 08:39:12AM -0600, Jesse Norell wrote:
> > That's most likely the order in which the database returns the
> > message id's .. eg. see what something like "select message_idnr
> > from dbmail_messages where mailbox_idnr = "
On Thu, 2006-09-14 at 10:19 +0200, Lars Kneschke wrote:
> Aaron Stone <[EMAIL PROTECTED]> schrieb:
> >> Ok. I changed my code. But should not change that value at least on
> >>delete?Â
> >
> >Nope, I don't think so. When UIDVALIDITY changes, it means all UID's that
> >you have cached must be th
On Mon, 2006-09-18 at 14:01 -0400, Geo Carncross wrote:
> > SELECT pm.messagesize, msg.message_idnr, msg.status, msg.unique_id
> > FROM dbmail_messages msg, dbmail_physmessage pm WHERE msg.mailbox_idnr =
> > '81'
> > AND msg.status < '2' AND msg.physmessage_id = pm.id order by status ASC
In SVN,
On Mon, 2006-09-18 at 11:34 -0700, Aaron Stone wrote:
> On Mon, 2006-09-18 at 14:01 -0400, Geo Carncross wrote:
>
> > > SELECT pm.messagesize, msg.message_idnr, msg.status, msg.unique_id
> > > FROM dbmail_messages msg, dbmail_physmessage pm WHERE msg.mailbox_idnr =
> > > '81'
> > > AND msg.status
Done.
On Mon, 2006-09-18 at 16:14 -0400, Geo Carncross wrote:
> Put message_idnr ASC first. Don't order by status; Consider what happens
> if another client changes the status after UIDL but before TOP?
>
> If they exclusively use POP3 clients, they'll see it "ordered by status"
> anyway (becaus
15 matches
Mail list logo
