Hi There,
Is there a way to customise the bounce back if a quota is full, or is
this a thing for postfix?
Thanks
Simon
A NOTE has been added to this issue.
==
http://www.dbmail.org/mantis/view.php?id=305
==
Reported By:variable
Assigned To:paul
I've installed dbmail on several boxes, but it has always bugged me,
that configure won't check for the existence of asciidoc and xmlto.
Older distros like SLES9 don't have these. I remember configure not
checking for a few other apps as well, not sure what they were anymore.
I've seen Paul
A NOTE has been added to this issue.
==
http://www.dbmail.org/mantis/view.php?id=368
==
Reported By:rhstone
Assigned To:paul
A NOTE has been added to this issue.
==
http://www.dbmail.org/mantis/view.php?id=368
==
Reported By:rhstone
Assigned To:paul
A NOTE has been added to this issue.
==
http://www.dbmail.org/mantis/view.php?id=368
==
Reported By:rhstone
Assigned To:paul
Hi Paul,
okay, after getting no answer from you i have compiled now the actual
SVN version (v 2192) and compiled it on debian sarge.
The body search looks fixed there, but I get some other problems,
specially with postgresql, but I think it's better to open there a extra
mail-thread.
Kind
Hi Jesse,
Yes just to finish, i'll need forward's for sure, but still not for now, and
when i do i'll edit this to make sure.
So i think the case is solved :P
Thanks to all.
Jorge
Also, just to be complete, you probably would want to delete all
dbmail_alias entries where deliver_to is
Hi,
at my tests with svn 2192 and postgresql I find out that there is a huge
diff if you install dbmail with mysql or postgresql.
In postgresql the SQL operators = and LIKE are case-sensitive, so a
simple search over headerfields failed for me because e.g. the header
subject is saved in the
Hi There,
Is there a way to customise the bounce back if a quota is full, or is
this a thing for postfix?
Thanks
Simon
Jochen Schroer wrote:
Hi Paul,
okay, after getting no answer from you i have compiled now the actual
SVN version (v 2192) and compiled it on debian sarge.
I've started providing debian/sarge packages.
The body search looks fixed there, but I get some other problems,
specially with
Paul,
O.K. now my Testinstall is working, many Thanks!
But I have to install manual with dpkg -i cause apt-get said has no
installation candidate or so.
With only one Client there is no error.
Is it possible that Active Directory (AD) cancels some LDAP connections if
there are too much?
I think
Reading the logs, it very much looks like someone is simply stopping the
imap server.
Jochen Entenmann wrote:
Paul,
i have attached the log.
I hope it is the right section.
At this time i set up a dedicated testing installation, so i can give you
more detailed Information.
I have set up
Jochen,
Jochen Entenmann wrote:
Paul,
O.K. now my Testinstall is working, many Thanks!
But I have to install manual with dpkg -i cause apt-get said has no
installation candidate or so.
The new packages are available for apt-get now.
With only one Client there is no error.
Is it
... I am digging.
I have stopped the imap-server, cause the Clients are kicked out.
After restarting dbmail (/etc/init.d/dbmail restart) all works for 15
Minutes.
Jochen
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Im Auftrag von Paul J Stevens
Jochen Schroer wrote:
Hi,
at my tests with svn 2192 and postgresql I find out that there is a huge
diff if you install dbmail with mysql or postgresql.
In postgresql the SQL operators = and LIKE are case-sensitive, so a
simple search over headerfields failed for me because e.g. the header
Hi Paul,
Hi Paul,
okay, after getting no answer from you i have compiled now the actual
SVN version (v 2192) and compiled it on debian sarge.
I've started providing debian/sarge packages.
yes, of course, I have see it, but for me svn looks like the better way
because I like it to
Jochen Schroer wrote:
Hi Paul,
Hi Paul,
okay, after getting no answer from you i have compiled now the actual
SVN version (v 2192) and compiled it on debian sarge.
I've started providing debian/sarge packages.
yes, of course, I have see it, but for me svn looks like the better
Paul J Stevens schrieb:
[...]
I know. The asciidoc in sarge is too old (buggy). I'm providing a sarge
backport of a recent version on debian.nfgd.net.
Hmmm, okay, I will update it.
Because at the moment I'm playing with dbmail on a vm-engine I have the
option to use any debian I like/need.
Hi Paul,
that's the benefit of using svn directly, I update the source, see what
you have changed, compile it and it works.
Fine, fine :-)
OK, let's come to the next problem, I will send a new mail.
Kind regards,
Jochen
Jochen Schroer wrote:
Hi,
at my tests with svn 2192 and postgresql
Hi,
I try to make a imap body-search with german-umlauts, specially the word
Kündigung, but the search failed and I get ALL messages in the mailbox
back.
(Search without german-umlaut works)
Here a log (Level 5) what happens:
Jul 12 11:43:24 localhost dbmail/imap4d[11372]: Info COMMAND: [19 uid
Jochen Schroer wrote:
Paul J Stevens schrieb:
[...]
I know. The asciidoc in sarge is too old (buggy). I'm providing a sarge
backport of a recent version on debian.nfgd.net.
Hmmm, okay, I will update it.
Because at the moment I'm playing with dbmail on a vm-engine I have the
option to
Paul J Stevens schrieb:
[...]
Is it better to use etch or Sid?
Yes. Especially gmime on sarge is quite old, and contains a bug that may
result in messed up headers (if the complete mail header is very long).
Also, glib has seen some important improvements in memory handling that
Etch is ok.
Jochen Schroer wrote:
Paul J Stevens schrieb:
[...]
Is it better to use etch or Sid?
Yes. Especially gmime on sarge is quite old, and contains a bug that may
result in messed up headers (if the complete mail header is very long).
Also, glib has seen some important
Please try again. It should work now, but please note that ü appears to
be encoded differently in different charsets (iso-8859-15 versus
iso-8859-1). This is (at the moment) not dealt with properly.
Jochen Schroer wrote:
Hi,
I try to make a imap body-search with german-umlauts, specially the
Paul,
I have tested in my Test Environment.
Here ist a log.
I have installed a imap/pop checker on my Desktop to simulate many
Connections.
Now the error occours.
The binding to the LDAP Server works:
Debug authldap.c,auth_ldap_bind: successfully bound to ldap server
But by the authentication
Hi Paul,
fine, your fix work :-)
Multilingual code is not so easy, I know.
Kind regards,
Jochen
Please try again. It should work now, but please note that ü appears to
be encoded differently in different charsets (iso-8859-15 versus
iso-8859-1). This is (at the moment) not dealt with
Jochen Entenmann wrote:
Paul,
I have tested in my Test Environment.
Here ist a log.
I have installed a imap/pop checker on my Desktop to simulate many
Connections.
Now the error occours.
The binding to the LDAP Server works:
Debug authldap.c,auth_ldap_bind: successfully bound to ldap
The problem is ü can be encoded in utf-8 (like I did just now) or in
iso-8859-XX. Matching during body searches should convert the body and
search key to utf-8 before searching...
Jochen Schroer wrote:
Hi Paul,
fine, your fix work :-)
Multilingual code is not so easy, I know.
Kind
Hi Paul,
this multiple cenversations decrease the oerformance of body search
again, because at the meoment the search process has to load every
messagepart of every message the performance is not really good.
I'm thinking a little bit about a universal solution, but I have now
idea up to now.
Jochen Schroer wrote:
Hi Paul,
this multiple cenversations decrease the oerformance of body search
again, because at the meoment the search process has to load every
messagepart of every message the performance is not really good.
I'm thinking a little bit about a universal solution, but I
I'm trying to store mail alerts from a monoitoring system and then send the
recieved messages on to the mail server that will send the mail out the the
internet. Here are my issues:
1) I want to store all mail, regardless of To address or From address, in the
database.
2) I want all
Jochen,
Just to keep you up to date though. I've been playing a little with the
non-indexed HAVING queries. Looks like a massive improvement over the
current situation (surpise! :-\ not!)
some thing like
select m.message_idnr,k.messageblk
from dbmail_messageblks k
join
33 matches
Mail list logo