[Greylist-users] Strange Occurrences when MySQL Database Goes Away
tonyb at go-concepts.com
Fri Feb 25 15:36:29 PST 2005
I have the same problem. If mysql dies, or even if you just restart
mysql the graylisting milter will die also.
I haven't done much debugging but there is nothing in the log that would
point to where the error is. It just dies without logging anything.
I am running the latest CVS version.
Tony Bunce, CCNA, Network+
GO Concepts, Inc.
From: greylist-users-bounces at lists.puremagic.com
[mailto:greylist-users-bounces at lists.puremagic.com] On Behalf Of Ade
Sent: Wednesday, February 23, 2005 7:47 AM
To: Greylisting Users and Developers Discussion
Subject: [Greylist-users] Strange Occurrences when MySQL Database Goes
Further to my message of a couple of weeks ago, I have further
investigated the problems we have been having when the MySQL database
behind relaydelay goes away. For what it's worth, we're running on
Solaris 9 SPARC, Sendmail 8.13.3, relaydelay 0.05 prerelease and MySQL
I have the following in relaydelay.conf:
$check_stale_db_handles = 1;
$pass_mail_when_db_unavail = 1;
When I deliberately kill the MySQL server, sendmail continues to connect
to the milter ok, but the milter responds with 'tempfail' for all
mails. This is not what I would expect with the above configuration -
am I correct or confused? Additionally, once I then restart the MySQL
server, the milter reconnects to it and then the first mail that
sendmail handles talk fine to the milter. However, relaydelay then dies
completely and so sendmail accepts the messages anyway (by design).
At the moment I am still in testing and so not normally tempfailing any
messages at all - operating in 'learn' mode only to test scalability and
reliability. Thus, the tempfailing that occurs as described above is
Has anybody else any similar experience or advice?
Greylist-users mailing list
Greylist-users at lists.puremagic.com
More information about the Greylist-users