Aaron Stone wrote:
I've done some libtool work before, and am planning on working towards making
the database and auth providers modular during the next development cycle.
Somehow I suspect that these are not the layers that you're thinking about
tying to Python, however :-P Would you want to
Now there's another problem with deliveries. I get every mail twice!
I'm firing up gdb as I type..
Ilja
Aaron Stone wrote:
Posted to SourceForge. A little patch to pipe.c and header.c, which fixes a
buffer boundary issue in the newline/rfc counting, the forgotten delivery
useridnr loop and a
There is no problem when sending messages through dbmail-smtp, only when
using lmtp. Strange..
looking further
Ilja
Ilja Booij wrote:
Now there's another problem with deliveries. I get every mail twice!
I'm firing up gdb as I type..
Ilja
Aaron Stone wrote:
Posted to SourceForge. A little
I haven't found the cause of this bug yet. There is also still a problem
with the read_header() function. It's constantly hanging on an fgets there..
Ilja
Ilja Booij wrote:
There is no problem when sending messages through dbmail-smtp, only when
using lmtp. Strange..
looking further
Ilja
Hi,
don't know why, but I just cannot find the reason why the delivery
user_idnr is added to the userids-list in the dsn twice. It does not
happen when using dbmail-smtp, only when using dbmail-lmtp.
Aaron (or anybody else), can you take a look at this? I'm completely
lost at the moment.. :
Hallo Everyone,
What about the function in db.c named db_insert_message_block_multiple ? It
seems to only be called by injector.c as well. Is that function also a
candidate for removal?
Blessings in Jesus,
Paul F. De La Cruz
-- Original Message -
Subject: Re: [Dbmail-dev] W
You're right.
After removal of the function everything still works :)
I'll update CVS
Ilja
Paul F. De La Cruz wrote:
Hallo Everyone,
What about the function in db.c named db_insert_message_block_multiple ? It
seems to only be called by injector.c as well. Is that function also a
candidate
Ilja & Aaron,
I am looking for this patch. I cannot access it from sourceforge? Or do I
have to checkout from cvs differently than the default dbmail root? I
would be glad to look at this Also Aaron, i was working on your sieve
code but there are some issues between the current libsieve you h
Ilja,
Correction I wiped my cvs out and re-checked it out and the changes are
there. I was expecting the update command to merge the changes is this
not the case with the dbmail cvs tree?
On the list.c stuff I see this with the dmalloc lib we talked about a
while back, do you knotice a state wh
Nevermind on the not exiting that was a issue I was causing with the
debuging options. thx.
-leif
> Ilja,
>
> Correction I wiped my cvs out and re-checked it out and the changes are
> there. I was expecting the update command to merge the changes is this
> not the case with the dbmail cvs tree?
I have a series of patches under the thread "[ 895107 ] Delivery status in
pipe and getopt support in main" in the patch tracker... Sometimes I've
uploaded files that SourceForge pukes on when other people try to download
them. Very odd; methinks SourceForge is a little finicky in places.
The lib
> I have a series of patches under the thread "[ 895107 ] Delivery status in
> pipe and getopt support in main" in the patch tracker... Sometimes I've
> uploaded files that SourceForge pukes on when other people try to download
> them. Very odd; methinks SourceForge is a little finicky in places.
>
12 matches
Mail list logo
