Jochen, Aaron, and all sql gurus:
I've done this (tiny, trivial, minor) change and have pushed it onto
svn-trunk. Dbmail now does the body search directly in the database
using HAVING SQL_INSENSITIVE_LIKE '%somestring%' against the messageblks.
A massive improvement of body searches both in
A quick update here, this is what i am getting back from the mail server:
Your message did not reach some or all of the intended recipients.
Subject:
Sent: 12/07/2006 4:49 p.m.
The following recipient(s) could not be reached:
[EMAIL PROTECTED] on 12/07/2006 4:50 p.m.
Simon,
this is a postfix issue.
Simon wrote:
A quick update here, this is what i am getting back from the mail server:
Your message did not reach some or all of the intended recipients.
Subject:
Sent:12/07/2006 4:49 p.m.
The following recipient(s) could not be
Hi,
When I create a mailbox (rev 2192) with latest Thundebird, I see in the
logs that dbmail checks for the existance of the mailbox twice, so that
it wouldn't create two mailboxes with the same name. But why twice? It
does no harm, but I see no point in doing so either, the SQL is exactly
Jochen, Aaron, and all sql gurus:
I've done this (tiny, trivial, minor) change and have pushed it onto
svn-trunk. Dbmail now does the body search directly in the database
using HAVING SQL_INSENSITIVE_LIKE '%somestring%' against the messageblks.
A massive improvement of body searches both in
A quick update here, this is what i am getting back from the mail server:
Your message did not reach some or all of the intended recipients.
Subject:
Sent: 12/07/2006 4:49 p.m.
The following recipient(s) could not be reached:
[EMAIL PROTECTED] on 12/07/2006 4:50 p.m.
Hi,
...have testet like you described.
But now the error occours, but the Clients doesent recognize it.
But on my Production System often Outlook drops the IMAP Connection cause
the Authentication fails.
Must I set the Timeout in Outlook to a higher Value?
Or can dbmail-imapd wait for reporting
Hi Paul,
the idea looks good, but postgresql is a little bit more fussy then
mysql, so your SQL failed.
1. for your select postgresql needs a grouping
2. at the moment there is no case insensitive operator for bytea
datatypes (but I'm searching for a workaround)
this statement work
Hi Paul,
it works great in postgresql if you convert the datatype bytea to text
before compare, than it is possible to use ILIKE
SELECT m.message_idnr,k.messageblk FROM dbmail_messageblks k JOIN
dbmail_physmessage p ON k.physmessage_id = p.id JOIN dbmail_messages m
ON p.id = m.physmessage_id
Excellent. I'll see how I can integrate the encode() call.
Jochen Schroer wrote:
Hi Paul,
it works great in postgresql if you convert the datatype bytea to text
before compare, than it is possible to use ILIKE
SELECT m.message_idnr,k.messageblk FROM dbmail_messageblks k JOIN
I am experementing with dbmail as a replacement for the local mailer for a
host of servers that the company I work for maintains. I would like to be
able to move into using dbmail but am having a few issues. We use sendmail
and I would rather not get rid of that. I have dbmail running and
So before I do something monumentally stupid. Paul can you
tell me if this is correct for finding my unconnected physmessages.
SELECT dbmail_physmessage.id, dbmail_messages.physmessage_id
FROM dbmail_physmessage
LEFT JOIN dbmail_messages
ON dbmail_physmessage.id =
12 matches
Mail list logo
