Richard,
At first glance this doesn't look like a loop to me. I'm sure I don't
understand the current mime-parsing code (nobody does really), but still
I don't see anything obviously suspicious here. If I read this right I
see two messages being retreived.
Next time perhaps you could attach
dbmail doesn't support (x)inetd. So unless you are running special
patches to accomodate this, you must be running standalone daemons.
Leonel Nunez wrote:
On Fri, 2004-07-09 at 15:32, Scott Johnson wrote:
I have dbmail 1.2.8b, running on a RH ES3 server. When I try to connect, I
get:
Connec
Perhaps you could try to normalize your mailbox with procmails formail
command:
formail -ds < old.mailbox > new.mailbox
procmail/formail is very good at handling non-compliant mailboxes, and
can convert them really fast.
Shadow wrote:
That would be nice.
Not compliant with rfc(2)822 how? I
Hello List:
For those currently running/testing the current CVS of dbmail
DbMail Administrator (DBMA) V2.0 with "dbmail_" prefixed database table
names has been released and is available at
http://library.mobrien.com/dbmailadministrator It includes a few new
features as well does the V1.01 release
Kevin Baker wrote:
I am setting up a new mail system next month. It will
require redundancy and failover.
Our current systems run Postfix+Cyrus+Amavis+MySQL/Auth.
Cryus is a complete pain in the rear to setup with account
failover. DBMail seems like a great solution. By just
setting up MySQL
Changes from pre-1.0 to 1.0-final were many. Table layout didn't change
very much, but many fields were renamed, fields were added, some tables
were added and dropped, indexes were a total mess iirc.
So you would first have to update to 1.x. After that there are some very
complete conversi
