M. J. [Mike] O'Brien wrote:
Hi Humberto:
That's quite a range of installations. Yes there is a bug in
2.1.-latest. It is not likely what you want for a production
environment just yet.
Perhaps your troubleshooting should start with a double check that the
'dbmail.conf' is correct for the version you are using and that the
databases schema is ok.
(If you are still using the database schema from 2.1.-Latest there
should be no problem that I know about. Not all tables will be
utilized but all the tables 2.0.4 needs are in there.)
You are currently using 2.0.4? I don't know of anything in RH Linux 4
that would conflict with DbMail.
Could you send back a copy of your 'dbmail.conf' and lets take a look
see?
Do you know what event(s)causes the CPU peek? Which programme?
(dbmail- lmtpd/pop3d/imapd)
What if anytrthing do the logs say while this problem occurs? ( tail
-f /var/log/maillog )
best... Mike
----- Original Message ----- From: "Humberto Valiente G."
<[EMAIL PROTECTED]>
To: <dbmail@dbmail.org>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, July 14, 2005 3:45 AM
Subject: [Dbmail] DBMAIL RHL4
Hello Mike
At this moment I have CentOS 4.0/4.1 and WBLE 3.0 running well with
the stable version 2.0.4
I tried using version 2.1.1 and the with those flavor and everything
becaume really unstable.
In a previous email you toll me that version 2.1.1 is not yet ready
to flavors based on RHL4
Im having two problems wright now
1. The version 2.1.1 solve a bug related to auto replies. (fixed
auto-reply. No more loops or mail-storms) that version 2.0.4 doesnt have
Q. There's a snapshot for version 2.0.4 that I can use or I
should wait for version 2.1.1 to be stable
2. With version 2.1.1 and RHL4 based linux flavor I was having
problems with %CPU.
Taking your recommendation I tried to install again version
2.04 .
In one of the servers Im receiving and error regarding to sort
and sort_delivery so I cannot install version 2.0.4 again. I found
that this is a bug in this version but I didn't find something
clearly about how to fix it.
What I did was to use an old snapshot. It works but sometimes
I have problems with %CPU too
I may appreciate any help
Regards,
Humberto
_______________________________________________
Dbmail mailing list
Dbmail@dbmail.org
https://mailman.fastxs.nl/mailman/listinfo/dbmail
_______________________________________________
Dbmail mailing list
Dbmail@dbmail.org
https://mailman.fastxs.nl/mailman/listinfo/dbmail
Hello Mike
A-1: Yes now I'm using dbmail v.2.04 with RHL4 and is working fine
A-2 : I was having problems with v.2.1.1 and RHL4
dbmail-imapd and mysql was causing the CPU peaks
I really have problem with v.2.0.4 and RHL4 with "autoreply" .
I know you have a warning about using dbmail autoreply but I was testing It
v.2.1.1 solve this situation but I can't use this version with RHL4
because of the CPU peaks.
Im using dbmail-imapd/pop3d
I have not try with lmtp
Configuration File
[SMTP]
SENDMAIL=/usr/sbin/sendmail # sendmail executable for forwarding mail
AUTO_NOTIFY=yes
AUTO_REPLY=yes
TRACE_LEVEL=2
[POP]
EFFECTIVE_USER=dbmail # the user that dbmail-pop3d will run
as (need to be root to b
ind to a port<1024)
EFFECTIVE_GROUP=dbmail # the group that dbmail-pop3d will run as
BINDIP=* # the ipaddress the dbmail-pop3d
server has to bind to, * for
all addresses
PORT=110 # the port number the dbmail-pop3d
server has to bind to.
NCHILDREN=10 # default number of POP3 handlers
(each is a process)
MAXCHILDREN=100 # mac. number of POP3 handlers
MINSPARECHILDREN=2
MAXSPARECHILDREN=4
MAXCONNECTS=10000 # the maximum number of connections a
default childs makes
TIMEOUT=4000 # the time (s) before the dbmail-pop3d
should shutdown a conne
ction which is being idle.
RESOLVE_IP=no # if yes, the pop daemon resolves IP
numbers to DNS names in th
e log
POP_BEFORE_SMTP=yes
TRACE_LEVEL=1
[IMAP]
EFFECTIVE_USER=nobody
EFFECTIVE_GROUP=nogroup
BINDIP=*
PORT=143
NCHILDREN=15
MAXCHILDREN=100 # mac. number of IMAPD handlers
MINSPARECHILDREN=2
MAXSPARECHILDREN=4
MAXCONNECTS=10000 # the maximum number of connections a
default childs makes
TIMEOUT=4000 # the time (s) before the dbmail-imapd
should shutdown a conne
ction which is being idle.
RESOLVE_IP=no # if yes, the imap daemon resolves IP
numbers to DNS names in t
he log
IMAP_BEFORE_SMTP=yes
TRACE_LEVEL=1
