> Hi,
>
> sure that's possible: if you create an alias and the deliver_to field
> starts with a pipe sign ('|'), a pipe will be opened to the command
> following the pipe sign and the mail will be send to it. So if you
> create an alias using dbmail-adduser like this:
>
> dbmail-adduser f [EMAIL PR
I have used Evolution, Outlook Express, Mozilla, Thunderbird and to a
lesser extent Outlook. They all work well. To me the main reason to
use dbmail is for IMAP. Traditional unix based imap servers really
hit a performance wall when mailboxes start getting big. dbmail is
MUCH better. I hav
On Nov 5, 2003, at 8:10 PM, Matthew T. O'Connor wrote:
Eric Soroos wrote:
Maybe it's just my setup, but I've found that synching a 18k item
mailbox gets me a message or two a seconds. Smaller mailboxes are
damn fast.
I'm on debian/stable, updated as of yesterday, runn
Could you set the tracelevel to 5 and send the exact imap commands
mail.app is generating? This way we might be able to speed things up a
bit.
Attached as text.
I've also noticed that after every inserted message, there is one
query per folder on my mailbox to determine the total size of
Could you set the tracelevel to 5 and send the exact imap commands
mail.app is generating? This way we might be able to speed things up a
bit.
I've gone through and it appears that the imap sections between 1.1-1
and 1.2.1 are identical for my purposes. I can't get 1.2.1 to work
properly wi
I'm having trouble building dbmail 2.0/cvs.
Mac 10.3.1, PG 7.4rc2, current developer tools (gcc 3.3). Postgres was
recently (yesterday) built from source, so I know I have at least a
nominally functioning system.
It seems like there's something screwy referring to libraries, as this
is what
I've just tried that, by changing the linking calls to gcc by putting
the
'-L/usr/local/pgsql/lib -lpq' at the back. And this works.
So, there is a solution. Only one problem left. How to change
Makefile.am and/or configure.in to make this work.
Is there anybody on the list with a little more
Now that I have 2.0 built, I was poking around a bit and noticed that
there are no transactions used. This will tend to hurt performance (at
least for postgresql) for inserts and that sort of thing since the
database can batch writes to the database during a transaction.
With a really basic ad
On Nov 17, 2003, at 7:20 AM, Gary Murphy wrote:
Ilja:
To truly benefit from transaction control you really need to
advantage, not
just by grouping DML statements, but also by use of the "rollback"
statement
in the case of an individual statement's failure.
Correct, although you don't actual
I believe your choice is better, in that, it requires many less
changes to
the underlying db_ methods, so I'll back mine out and proceed with
yours. I
may need one new db_ method to add a user mailbox to an existing
message.
I think there's a way to do this entirely in the the database laye
On Nov 18, 2003, at 10:46 AM, Gary Murphy wrote:
The current quota implementation is definitely costly. Establishing a
transaction with failure and/or over-quota control for the message
inserts
(rollback inserted data) could be a first step; but I agree a more
elegant
solution is desirable.
quick question. Why remove physmessage? Can't you use it to your
advantage here? The physmessage table already makes sure that multiple
copies of a single message will only be stored as messageblocks once.
You should be able to use this to allow multiple users to use the same
physmessage. Or i
Why can't you store the msg_block fingerprint in the msg_block table?
Like (with mysql syntax)
CREATE TABLE messageblks (
messageblk_idnr bigint(21) NOT NULL auto_increment,
physmessage_id bigint(21) NOT NULL default '0',
messageblk longtext NOT NULL,
blocksize b
You can. That's effectively what I was doing in my message, except
that you're not seeing it in the messageblk view. You probably don't
want a unique constraint on messageblk, since the idea of the
fingerprint is that it's a 1:1 mapping of the messageblk down to 128
bits.
I agree with you i
On Nov 20, 2003, at 8:28 AM, Magnus Sundberg wrote:
Eric Soroos wrote:
You can. That's effectively what I was doing in my message, except
that you're not seeing it in the messageblk view. You probably
don't want a unique constraint on messageblk, since the idea of the
fing
Well the first is something I have found out earlier, consider a table
with the fields A and B and the following records:
A B
1 1
1 2
2 1
for that record, you can not add the constraint UNIQUE(A) nor
UNIQUE(B), but you can add the constraint UNIQUE(A,B)
Correct. But if we're starting with A
Hi,
I'm getting the following error with dbmail-pop3d and dbmail-imapd on
startup:
dbmail/pop3d[663]: pool.c,scoreboard_new: scoreboard init failed
[Permission denied]
I'm currently using OSX 10.4.1, with Xcode 2.0 and dbmail from svn,
version below. (2.04 didn't compile for me)
URL:
On Jul 12, 2005, at 11:28 PM, Eric Soroos wrote:
Hi,
I'm getting the following error with dbmail-pop3d and dbmail-imapd
on startup:
dbmail/pop3d[663]: pool.c,scoreboard_new: scoreboard init failed
[Permission denied]
Here's the full trace from debugging=5
Jul 13 21
On Jul 14, 2005, at 11:13 AM, Brandon Mercer wrote:
Sri Gupta wrote:
Are you using BSD make or GNU make?
Try gmake.
Thanks for the tip :-). I got further this time. Now it's giving me
the following error:
/usr/include/stdlib.h:179: error: conflicting types for 'dm_getopt'
dm_getopt.h
On Aug 1, 2005, at 8:29 AM, William Finn wrote:
I'm getting a different error on 10.4.2 with 2.0.4. MySQL 4.1.12.
./configure --with-mysql
make all
sort.c:68: error: conflicting types for 'sort_and_deliver'
../sort.h:59: error: previous declaration of 'sort_and_deliver' was
here
I trie
Eric, as what user are you starting imapd? You *are* running as
root, right?
Root.
I posted a trace on 7/13, here are the important bits:
Jul 13 21:41:42 rum dbmail/imap4d[288]: CreateSocket(): socket created
Jul 13 21:41:42 rum dbmail/imap4d[288]: CreateSocket(): socket IP
requested [*
On Sep 28, 2005, at 1:42 PM, Paul J Stevens wrote:
Leonel Nunez wrote:
Eugene Prokopiev wrote:
Hi,
Which minimal PostgreSQL version can I use for DBMail?
I think pretty much any version of postgresql that's not really
ancient will do.
dbmail sure doesn't exactly push the envelope o
22 matches
Mail list logo
