Hi,
This fix has finally made it into the 1.2 series. Why I've never applied
it I don't know.
Anyway, this fix, and the fix to not let dbmail-maintenance log errors
when encountering empty mailboxes are in the DBMail 1.2.5 release, which
can be downloaded from http://www.dbmail.org/
Ilja
Paul J Stevens wrote:
This is caused by a tcp socket bug in the server code that somehow never
made it into dbmail-1.2.
--- dbmail-1.2/server.c.orig 2003-10-16 10:22:17.000000000 +0200
+++ dbmail-1.2/server.c 2003-10-16 10:22:40.000000000 +0200
@@ -218,7 +218,7 @@
{
int sock, r, len;
struct sockaddr_in saServer;
- int so_reuseaddress;
+ int so_reuseaddress = 1;
/* make a tcp/ip socket */
sock = socket(PF_INET, SOCK_STREAM, 0);
Micah wrote:
Update: This problem seems to not happen at ALL if I set the log level
to 5 or higher. Dunno if it's chance, as I've only tried it three
times, but it seems to be consistant. Sure doesn't make much sense
though. Oh, and I was testing on imapd only.
-Micah
---------- Forwarded Message ----------
Subject: Startup problem
Date: Monday 22 March 2004 09:08 pm
From: Micah <[EMAIL PROTECTED]>
To: "'DBMail mailinglist'" <[email protected]>
Hi everyone,
I'm running dbmail 1.2 on a redhat 7.2 server with mysql 4.x
I've been getting this error when I'm starting up imapd and pop3d lately:
CreateSocket(): could not bind address to socket
if I retry enough times, it works. Once started, everything works
fine. It's
kinda like starting my old 68 Chrysler.. Any ideas on what might be
causing
this? I cranked the log level and this is all I get.
Thanks,
-Micah
-------------------------------------------------------
_______________________________________________
Dbmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
